• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Linux and a corrupt superblock.

N

nihil

Golden Member
After noticing some errors on one my secondary drives (ext2 fs) I ran e2fsck, and went off to work.

Upon returning, I noticed that when I tried to re-mount the drive, I got the following error:

mount /dev/hdd1
mount: wrong fs type, bad option, bad superblock on /dev/hdd1,
or too many mounted file systems

Again I ran e2fsck and received this error:

e2fsck /dev/hdd1
e2fsck 1.35-WIP (21-Aug-2003)
Corruption found in superblock. (blocks_count = 0).

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 32768 <device>

I tried doing exactly that and it told me that I had a bad magic number in super-block while trying to read /dev/hdd1 It suggested that I try to specify an alternate superblock, but alas, it was no luck. I even tried mke2fs -n /dev/hdd1 and using more backup superblocks that were printed out, again nothing worked.

I'm pretty stumped. Is there anyway for me to recover this drive? One thing I have noticed to be odd is that the block size is set to 4096, but I'm not sure if it's completely unrelated or not.

Any help is appreciated, thanks in advance.
 
Damn corrupted superblock, eh? That's sucks. I had that happen once after a power outage.

Lost everything.

you could try this:

from man mk2efs
-S
Write superblock and group descriptors only. This is useful if all of the superblock and backup superblocks are corrupted, and a last-ditch recov- ery method is desired. It causes mke2fs to reini- tialize the superblock and group descriptors, while not touching the inode table and the block and inode bitmaps. The e2fsck program should be run immediately after this option is used, and there is no guarantee that any data will be salvageable.
Click to expand...

Probably a good idea if it works to copy all your importatnt data to another disk as a backup.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top