I think I might have a problem. ;-) My radius server (an old DELL P75 with two old Western Digitals) had the second drive (holding /usr) go down. e2fsck gave me:
***** e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09 Couldn't find ext2 superblock, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/hdc 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 8193 <device> ***** How do I recover? e2fsck doesn't even try to run. I know that the ext2 filesytem is supposed to be robust, but I haven't had the oportunity to delve in fs corruption or fixing (guess that shows me, huh?). Is there a standard -b <sector> that could be used as the superblock? Any help would be appreciated. Slamming my head into reams of HOWTO's hasn't seemed to increase the rate of osmosis. :-)
