Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Can't repair super block, bad magic number Post 302562204 by pludi on Thursday 6th of October 2011 10:02:17 AM
Old 10-06-2011
That's actually a good hint. Run pvscan (scan for physical volumes with a matching identification), vgscan (search for volume groups on known PVs), and then vgdisplay (show information about known volume groups).

Background: LVM is the logical volume manager used in Linux. What it basically does is collect physical disks into larger volume groups, from which logical volumes can be carved. These behave, as far as the filesystem and up is concerned, like partitions, but are easier to extend and can be given meaningful names.
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. HP-UX

BAD SUPER BLOCK - Run fsck with alternate super block number

Error received when I tried to restore a blank disk with an 'auto recovery' DDS tape via HP-UX recovery system 2.0 onto a 1Gb SCSI. I assumed it would do the setup, wrong. Could someone tell me the procedure to initial disk for recovering files using cpio. The system is a HP-UX 9.04 version on a... (1 Reply)
Discussion started by: admin wanabee
1 Replies

5. 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

6. Solaris

solaris error BAD SUPER BLOCK

I want mount a disk. I have this error. I'm trying to correct with the superblock but i have the same error. Look my procedure. bash-2.03# fsck -F ufs /dev/rdsk/c0t1d0s0 Alternate super block location: 9423392. ** /dev/rdsk/c0t1d0s0 BAD SUPER BLOCK: MAGIC NUMBER WRONG USE AN ALTERNATE... (1 Reply)
Discussion started by: simquest
1 Replies

7. UNIX for Advanced & Expert Users

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... (0 Replies)
Discussion started by: ravinandan
0 Replies

8. Filesystems, Disks and Memory

Bad super block: Magic number wrong

Whenever i run, # fsck -F ufs /dev/dsk/c0t0d0s7 The following error prompt out:- ** /dev/dsk/c0t0d0s7 BAD SUPER BLOCK: MAGIC NUMBER WRONG USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; eg. fsck -o b=# where # is the alternate super block. SEE fsck_ufs(1M). ... (3 Replies)
Discussion started by: beginningDBA
3 Replies

9. 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

10. 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
VGSCAN(8)						      System Manager's Manual							 VGSCAN(8)

NAME
vgscan - scan all disks for volume groups and build /etc/lvmtab and /etc/lvmtab.d/* which are the database for all other lvm commands. SYNOPSIS
vgscan [-d|--debug] [-f|--forcenumbers] [-h|--help] [-r|--remove_snapshots [VolumeGroupName]] [-v|--verbose] DESCRIPTION
vgscan scans all SCSI, (E)IDE disks, multiple devices and a bunch of other disk devives in the system for volume groups defined. OPTIONS -d, --debug Enables additional debugging output (if compiled with DEBUG). -f, --forcenumbers If used volume group and/or logical volume minor numbers are found during scan, replace them. This will potentially cause problems for NFS exported filesystems on logical volumes with changed numbers. -h, --help Print a usage message on standard output and exit successfully. -r, --remove_snapshots [VolumeGroupName] Remove all snapshot logical volumes from all or just the named volume group. -v, --verbose Display verbose information of vgscan's activities. Hint Put vgscan in one of your system startup scripts. This gives you an actual logical volume manager database before activating all volume groups by doing a "vgchange -ay". DIAGNOSTICS
vgscan returns an exit code of 0 for success and > 0 for error: 1 error reading physical volumes 2 error inserting vokume group name into lvmtab 3 no volume group(s) found 4 error creating lvmtab 5 no or not enough free device specials to store volume group in lvmtab 6 error storing VGDA on disk(s) 7 reused LV device number 8 error releasing snapshot logical volume 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 99 invalid command line See also lvm(8), vgcreate(8), vgchange(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS VGSCAN(8)
All times are GMT -4. The time now is 07:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy