On Nov 15, 2007 9:11 AM, Lan Barnes <[EMAIL PROTECTED]> wrote:
> During the fires, we lost power and our Mailman server (FC6) ended not
> cleanly. Now the image is refusing to boot -- kernel panic. I suspect that
> the superblock on the very-non-virtualized hard drive is corrupted.
>
> I've made these repairs before, and am hoping that they can be made
> through VMWare. I have a rescue disk.
>
> My memory is that I'll need to run
>
> fsck -p /dev/hda1
>
> ... and so on, but probably just for the root/boot partition. Then it will
> tell me if the superblock is corrupt and suggest how to find alternate
> superblocks. I believe that this will be mkfs with a switch that says
> "don't do anything, just give me the information." But I'm pretty sure
> that fsck will tell me what to do. Then my memory is that I return with
>
> fsck -p -b <superblock> /dev/hda1
To run fsck effectively you need to call out the explicit
e2fsck -f <superblock> /dev/hda1
-f means force the check even if the flag in the superblock says "I'm OK".
Not implemented in fsck itself the way it is implemented.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
