[PLUG] Kernel panic

Russ Johnson russj at dimstar.net
Sat Nov 30 18:22:00 UTC 2002


* Stephen Liu <satimis at writeme.com> [2002-11-30 07:10]:
> >When this is happening, what the output of 'mount' by itself?
> 
> # mount
> rootfs on /type rootfs (rw)
> /dev/root.old on /type ext2 (rw)
> /proc on /proc type proc (rw)
> /dev/pts on /dev/pts type devpts (rw)
> /proc/bus/usb on /proc/bus/usb type usbdevfs (rw)
> /tmp/cdrom on .mnt/source type iso9660 (rw)
> /tmp/loop0 on /mnt/runtime type ext3 (rw)
> /tmp/hdc2 on /mnt/sysimage type ext3 (rw)
> /tmp/hdc1 on /mnt/sysimage/boot type ext3 (rw)
> none on /mnt/sysimage/dev/pts type devpts (rw)
> none on /mnt/sysimage/proc type proc (rw)

OK, it's mounted on /mnt/sysimage. That /tmp/hdc2 is how it's referenced when you boot in rescue mode.

Unmount it 'umount /mnt/sysimage' and run fsck on that 'fsck /tmp/hdc2'.

Another thing. This will only repair the filesystem. If you have damaged files, they may not be recoverable. Unless you want to manually recover those (assuming the fsck fixes the filesystem) it's easier to simply reinstall from scratch.


You can back the information you want from the rescue mode, and then reinstall. Once the reinstall is done, restore the backed up information. 

-- 
Russ Johnson
Stargate Online
http://www.dimstar.net

Love is the delusion that one woman differs from another -- Murphy's Laws on Sex n°58




More information about the PLUG mailing list