corrupt superblock 4662

# fsckdev-hdc7

fsck 1.37 (21-Mar-2005) e2fsck 1.37 (21-Mar-2005) fsck.ext2: No such file or directory while trying to opendev-hdc7

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

(to be sure, all my linux parbreastions use journaling (ext3), and are not plain ext2)

-----------------------

Also, i did not include in my initial message the following:

When booting up my other FC4 system with this drive as secondary master, I get:

Buffer I-O error on devicedev-hdc, logical block 0

Also, dmesg shows:

hdc: dmaintr: status=0x51 { DriveReady SeekComplete Error } hdc: dmaintr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown ... above three lines repeat 4 x ... ide: failed opcode was: unknown ide1: reset: success

-------

I would get the above errors on the RH9 laptop, when I would boot with the original RH9 kernel (every few minutes or so). These SeekComplete errors went away when I compiled and used a newer (2.6) kernel. My superblock corruption happened during a recent three-day uptime with the original bad kernel (yes, that was stupid, but i thought the errors were benign; nothing bane had happened over three years)

The strange thing is that the SeekComplete errors are back, in my new FC4 (recompiled 2.6.12-1.1398FC4smp). Anything particular about this Seagate ST94811A drive that requires special kernel configuration?

Do all these symptoms appear to be related? Or is the buffer i-o error something different from the SeekComplete and-or bad superblock errors?

thanks again!

andrew