Kernel panic after hard reboot
 

Howdy-

I searched some of the threads and I figure this is a common problem, but I don't know enough about Linux and Fedora Core 2 to fix it.

I recently had to do a hard reboot on my machine (Pentium II). When I did so, it started booting up but then gave me this:

Uncompressing Linux ... Ok, booting the kernel.
audit(1127658346.967:0): initialized
Red Hat nahs version 3.5.22 starting
EXT3-fs: error loading journal
mount: error 22 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Kernel panic - not syncing: No init found. Try passing init= option to kernel.

I wouldn't mind reinstalling FC if I had to, but I'd like to get to some of my files if possible. Thanks in advance.

"I recently had to do a hard reboot on my machine (Pentium II). When I did so, it started booting up but then gave me this:"

You should run fsck against every linux partition except swap. Boot a rescue cd and run fsck something like this:

fsck -t ext3 /dev/hda1

Answer yes to everything that fsck asks you. fsck should clean up the errors such as:
"EXT3-fs: error loading journal"

Here is the fsck man page:

http://www.die.net/doc/linux/man/man8/fsck.8.html

-------------------------
Steve Stites

I'm using an old compaq and I the only options I find for booting are from the Hard drive C: and the ethernet device. Is there any other way to get to a command prompt?

"I'm using an old compaq and I the only options I find for booting are from the Hard drive C: and the ethernet device. Is there any other way to get to a command prompt?"

If you have a floppy you can boot tomsrtbt from the floppy and use that.

http://www.tux.org/pub/distributions...inux/tomsrtbt/

If you have another Linux computer you can move the hard drive to the working Linux computer and run fsck there.

How did you boot the installer when you installed Linux? You can probably boot a rescue system the same way.

--------------------------
Steve Stites

It looks like the problem is that the journal of your ext3 filesystem has gotten corrupt. If that's the only damage you should be OK, because you can just boot off a floppy or LiveCD and mount the partition ext2 (no journal -- ext3 is pretty much just ext2 with a journal). Unfortunately, if the journal is corrupt there's probably other filesystem damage too.

Why did you have to hard reboot? If the machine froze, it's possible the hard drive itself is on its way out.