Bad magic number on /dev/md0


Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
# 1  
Bad magic number on /dev/md0

Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.

I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting of /dev/md0 fails.
The error message says the superblock no. is wrong and it is expecting ext2 file system.

After this, I login in rescue mode(which the os provided me as soon as mount of /dev/md0 failed).

Once I login, I have to recreate the raid1 array using
mdadm --create /dev/md0 --level=raid1 --raid-devices=2 /dev/sdb1 /dev/sdc1

The above command successfully creates raid1 array after which I mount it to my /home directory.

Now everything works fine(until I restart)

(After full synchronization)
$cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdc1[1] sdb1[0]
17782656 blocks [2/2] [UU]

unused devices: <none>

#mdadm -E /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : 979caf2d:1be05876:14d74325:14ea3ec1
Creation Time : Fri Aug 10 15:47:52 2007
Raid Level : raid1
Device Size : 17782656 (16.96 GiB 18.21 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Fri Aug 17 17:11:05 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 14fdc667 - correct
Events : 0.92278


Number Major Minor RaidDevice State
this 0 8 17 0 active sync /dev/sdb1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 33 1 active sync /dev/sdc1

# mdadm -E /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : 979caf2d:1be05876:14d74325:14ea3ec1
Creation Time : Fri Aug 10 15:47:52 2007
Raid Level : raid1
Device Size : 17782656 (16.96 GiB 18.21 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Fri Aug 17 17:13:11 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 14fdc713 - correct
Events : 0.92292


Number Major Minor RaidDevice State
this 1 8 33 1 active sync /dev/sdc1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 33 1 active sync /dev/sdc1

#cat /etc/mdadm.conf

DEVICE /dev/sdb1 /dev/sdc1
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=979caf2d:1be05876:14d74325:14ea3ec1


#mdadm -E /dev/md0
mdadm: No super block found on /dev/md0 (Expected magic a92b4efc, got 764e5679)


Any help will be appreciated.
(Since I'm relieving from my current position I need to correct this problem...I don't want to pass this problem to my successor)

Regards,
Ravinandan S
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

10 More Discussions You Might Find Interesting

1. Solaris

Bad magic number in disk label.

This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following: Boot device: disk File args: Bad magic number in disk label Can't open disk label package Evaluating: boot Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies

2. Solaris

Bad magic number error

So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it. We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies

3. Solaris

cpio: Bad magic number/header.

Hi, i got the following error while unpacking the archive file. cpio -icvd < as_sun_x86_101202_disk2.cpio Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles/wwdoc.jar Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles... (2 Replies)
Discussion started by: malikshahid85
2 Replies

4. Solaris

Solaris 8.2 Bad magic number

I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies

5. Solaris

OpenSolaris 2009 bad magic number

Hi guys, I have a big problem wiht my old Netra T1 200. I want to install OpenSolaris 2009 but there's a problem, I burned the ISO image on a CD-RW and then I tryied to install it on netra, but the setup won't to start and the error is that in the attached image. Thanks for the support and sorry... (5 Replies)
Discussion started by: Ducati87
5 Replies

6. Solaris

BAD magic number in disc label...

Hello All, I m very new to this forum. i m having SUN NETRA X1 server with 40 GB HDD (Seagate) & 128 MB RAM. i m trying this server for SUN 10 Practise. As i m installing SUN 9 /10 with CD ,its giving me error after OK propmt *************************** #boot cdrom or #boot cdrom... (16 Replies)
Discussion started by: amrut_k
16 Replies

7. Filesystems, Disks and Memory

Bad Super Block: Magic Number Wrong

I had a power outage a day ago and when the power came back on my FreeBSD 4.6 webserver had problems. It said it was unable to mount /var and made me start in single user mode and said to run fsck MANUALY. So i did and this is now what i get. www# fsck /dev/ad0s1e ** /dev/ad0s1e BAD SUPER... (4 Replies)
Discussion started by: matthewbane
4 Replies

8. Filesystems, Disks and Memory

Bad Magic Number

Dear All, i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies

9. UNIX for Advanced & Expert Users

bad magic number

Hi, when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Discussion started by: rein
5 Replies

10. UNIX for Dummies Questions & Answers

Bad magic number in super-block

I am running mandrake 8.2 and when booting I get the message: e2fschk: Bad magic number in super-block while trying to open /dev/hda8. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and really contains a valid an ext2 filesystem (and... (1 Reply)
Discussion started by: Jay
1 Replies

Featured Tech Videos