11-12-2003
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 not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternative superblock:
e2fsck -b 8193 <device>
fsck ext3 Bad magic number in super-block while trying to open /dev/hda8
Couldn't find ext2 superblock, trying to back up blocks.
At this point it files to load any further and drops to a shell prompt.
Ran the above suggestion and get the same error
I have commented the following line out of the fstab and it now loads to a normal login prompt:
/dev/hda8 /home ext3 defaults 1 2
I have ran mke2fs -n /dev/hda8 and it says there are backups of the superblock at 229376, 294912, 819200, 884736, 1605632, 2654208 and 4096000. I have tried doing e2fsck -b on all these blocks and keep getting the same error.
Any ideas?
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. HP-UX
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
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
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
6. Filesystems, Disks and Memory
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
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. Filesystems, Disks and Memory
Hello all,
I have a hard drive that I can't repair.
The drive is WD15EARS - Filesystem ext4 ( not 100% sure )
It's used in a Synology DS110j NAS.
I try to run fsck -p /dev/sdb on the HD and I get this:
Bad magic number in super-block while trying to open /dev/sdb
/dev/sdb:
The superblock... (4 Replies)
Discussion started by: dallasw1983
4 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
LEARN ABOUT ULTRIX
icheck
icheck(8) System Manager's Manual icheck(8)
Name
icheck - check inode consistency
Syntax
/etc/icheck [ -s ] [ -b numbers ] [ filesystem ]
Description
The command is obsoleted for normal consistency checking by
The command examines a file system, builds a bit map of used blocks, and compares this bit map against the free list maintained on the file
system. If the file system is not specified, a set of default file systems is checked. The normal output of includes a report of:
o The total number of files and the numbers of regular, directory, block special and character special files.
o The total number of blocks in use and the numbers of single-, double-, and triple-indirect blocks and directory blocks.
o The number of free blocks.
o The number of blocks missing, that is, not in any file nor in the free list.
The option causes to ignore the actual free list and reconstruct a new one by rewriting the super-block of the file system. The file sys-
tem should be dismounted while this is done; if this is not possible (for example if the root file system has to be salvaged) care should
be taken that the system is quiescent and that it is rebooted immediately afterwards so that the old, bad in-core copy of the super-block
will not continue to be used. Notice also that the words in the super-block which indicate the size of the free list and of the i-list are
believed. If the super-block has been curdled these words will have to be patched. The option causes the normal output reports to be sup-
pressed.
Following the option is a list of block numbers; whenever any of the named blocks turns up in a file, a diagnostic is produced.
The command is faster if the raw version of the special file is used, since it reads the i-list many blocks at a time.
Diagnostics
For duplicate blocks and bad blocks (which lie outside the file system) announces the difficulty, the i-number, and the kind of block
involved. If a read error is encountered, the block number of the bad block is printed and considers it to contain 0. `Bad freeblock'
means that a block number outside the available space was encountered in the free list. `n dups in free' means that n blocks were found in
the free list which duplicate blocks either in some file or in the earlier part of the free list.
Restrictions
Since is inherently two-pass in nature, extraneous diagnostics may be produced if applied to active file systems.
It believes even preposterous super-blocks and consequently can get core images.
Files
Default file systems vary with installation.
See Also
fs(5), clri(8), dcheck(8), fsck(8), ncheck(8)
icheck(8)