08-17-2007
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
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
2. UNIX for Advanced & Expert Users
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
3. Filesystems, Disks and Memory
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
4. Filesystems, Disks and Memory
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
5. Solaris
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
6. Solaris
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
7. Solaris
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
8. Solaris
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
9. Solaris
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
10. Solaris
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
PVMOVE(8) System Manager's Manual PVMOVE(8)
NAME
pvmove - move physical extents
SYNOPSIS
pvmove [--abort] [--alloc AllocationPolicy] [-b|--background] [-d|--debug] [-h|--help] [-i|--interval Seconds] [--noudevsync] [-v|--ver-
bose] [-n|--name LogicalVolume] [SourcePhysicalVolume[:PE[-PE]...] [DestinationPhysicalVolume[:PE[-PE]...]...]]
DESCRIPTION
pvmove allows you to move the allocated physical extents (PEs) on SourcePhysicalVolume to one or more other physical volumes (PVs). You
can optionally specify a source LogicalVolume in which case only extents used by that LV will be moved to free (or specified) extents on
DestinationPhysicalVolume(s). If no DestinationPhysicalVolume is specified, the normal allocation rules for the Volume Group are used.
If pvmove gets interrupted for any reason (e.g. the machine crashes) then run pvmove again without any PhysicalVolume arguments to restart
any moves that were in progress from the last checkpoint. Alternatively use pvmove --abort at any time to abort them at the last check-
point.
You can run more than one pvmove at once provided they are moving data off different SourcePhysicalVolumes, but additional pvmoves will
ignore any Logical Volumes already in the process of being changed, so some data might not get moved.
pvmove works as follows:
1. A temporary 'pvmove' Logical Volume is created to store details of all the data movements required.
2. Every Logical Volume in the Volume Group is searched for contiguous data that need moving according to the command line arguments. For
each piece of data found, a new segment is added to the end of the pvmove LV. This segment takes the form of a temporary mirror to copy
the data from the original location to a newly-allocated location. The original LV is updated to use the new temporary mirror segment in
the pvmove LV instead of accessing the data directly.
3. The Volume Group metadata is updated on disk.
4. The first segment of the pvmove Logical Volume is activated and starts to mirror the first part of the data. Only one segment is mir-
rored at once as this is usually more efficient.
5. A daemon repeatedly checks progress at the specified time interval. When it detects that the first temporary mirror is in-sync, it
breaks that mirror so that only the new location for that data gets used and writes a checkpoint into the Volume Group metadata on disk.
Then it activates the mirror for the next segment of the pvmove LV.
6. When there are no more segments left to be mirrored, the temporary Logical Volume is removed and the Volume Group metadata is updated so
that the Logical Volumes reflect the new data locations.
Note that this new process cannot support the original LVM1 type of on-disk metadata. Metadata can be converted using vgconvert(8).
N.B. The moving of mirrors, snapshots and their origins is not yet supported.
OPTIONS
--abort
Abort any moves in progress.
--noudevsync
Disable udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible
udev processing in the background. You should only use this if udev is not running or has rules that ignore the devices LVM2 cre-
ates.
-b, --background
Run the daemon in the background.
-i, --interval Seconds
Report progress as a percentage at regular intervals.
-n, --name LogicalVolume
Move only the extents belonging to LogicalVolume from SourcePhysicalVolume instead of all allocated extents to the destination phys-
ical volume(s).
EXAMPLES
To move all Physical Extents that are used by simple Logical Volumes on /dev/sdb1 to free Physical Extents elsewhere in the Volume Group
use:
pvmove /dev/sdb1
Any mirrors, snapshots and their origins are left unchanged.
Additionally, a specific destination device /dev/sdc1 can be specified like this:
pvmove /dev/sdb1 /dev/sdc1
To perform the action only on extents belonging to the single Logical Volume lvol1 do this:
pvmove -n lvol1 /dev/sdb1 /dev/sdc1
Rather than moving the contents of the entire device, it is possible to move a range of Physical Extents - for example numbers 1000 to 1999
inclusive on /dev/sdb1 - like this:
pvmove /dev/sdb1:1000-1999
To move a range of Physical Extents to a specific location (which must have sufficent free extents) use the form:
pvmove /dev/sdb1:1000-1999 /dev/sdc1
or
pvmove /dev/sdb1:1000-1999 /dev/sdc1:0-999
If the source and destination are on the same disk, the anywhere allocation policy would be needed, like this:
pvmove --alloc anywhere /dev/sdb1:1000-1999 /dev/sdb1:0-999
The part of a specific Logical Volume present within in a range of Physical Extents can also be picked out and moved, like this:
pvmove -n lvol1 /dev/sdb1:1000-1999 /dev/sdc1
SEE ALSO
lvm(8), vgconvert(8) pvs(8)
Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) PVMOVE(8)