[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

e2fsck says it fixed corruption, but it didn't



Hiya folks,

I have a corrupted superblock.




System:

Old motherboard based on an Intel 486DX
16 Megs ram
Bustek SCSI controller, I think model 742
Two identical disk drives: DEC DSP3053LS




The disk drives are SCSI IDs 0 and 1.

I have enough disk space that I never really
used the second disk.

When I upgraded to Slackware 96 I simply 
swapped the SCSI IDs on the disks kept the old
disk as a backup of sorts.

Currently the lower drive is SCSI ID 0 and it
is the one I use.

This lower drive developed a corrupted superblock,
so I figured I'd swap the disks again, boot up my old
system from the upper drive, and fix the lower drive.

When I boot from the old upper drive, this is what it
finds on the lower drive (which is now sdb2):

===========================================================

Warning: inode bitmap 196881 for group 23 not in group

/dev/sdb2: unexpected inconsistency; run fsck manually

*************************************************************
fsck returned error code - reboot now!
*************************************************************

(after a minute or so it times out and goes to run level 
5 I think and says more:)

ext2-fs error (device 8/18): ext2-check-descriptors: inode
bitmap for group 23 not in group (block 196881)!

ext2-fs: group descriptors corrupted!

===========================================================


So I log in as root and run e2fsck using a spare superblcok:

e2fsck -b 8193 /dev/sdb2

and I get:

===========================================================

warning: inode bitmap 196881 for group 23 not in group.
Continue<y> (I continue)

Pass 1: checking inodes, blocks, and sizes
relocating group 23's inode bitmap to 196881
Pass 2:....
Pass 3:....
Pass 4:....
Pass 5:....
Fix summary information<y>? (I say yes)

Inode bitmap differences: (a whole bunch of numbers with 
plus signs in front of them) FIXED

/dev/sdb2: file system was modified

===========================================================

So then I shutdown and reboot, thinking I've solved the 
problem, but NO! When I reboot, I get exactly the same problem. 

So my question is, how come e2fsck says it fixed my problem,
but it seems to not have? Am I running e2fsck incorrectly?
Or is there some other problem?



Here is my /etc/fstab, in case this is useful:

/dev/sdb1   swap    swap     defaults   1   1
/dev/sda1   /       ext2     defaults   1   1
none        /proc   proc     defaults   1   1
/dev/sdb2   /u1     ext2     defaults   1   1









Thanks,

Michael Shiloh