Kernel Panic after Upgrade

arew264 · 2007-06-09 01:53:22

I'm hoping I just missed a notice, but I'm pretty sure I didn't.
I haven't upgraded for a while, and decided to get back up to date today, and now I have a kernel panic.

:: Loading udev...done.
/sys/class/graphics/fb0/virtual_size: No such file or directory
Segment Violation
ERROR: Failed to parse block device name for '/dev/hda2'
ERROR: roof fs cannot be detected. Try using the rootfstype= kernel parameter
IP-Config: no devices to configure
kinit: Unable to mount root fs on device dev(0,0)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

I have two partitions, the main one (reiserfs) and then a swap partition.
While I am not sure of the order, the boot entry that has worked until now for this is:

root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/hda2 ro
initrd /boot/kernel26.img

What's going on here? What could have changed to not allow it to parse /dev/hda2? Do I need to get a rescue disk and check fstab?

Last edited by arew264 (2007-06-09 01:56:40)

rayjgu3 · 2007-06-09 02:08:57

what does /etc/mkinitcpio.conf look like?
do you see mknod /dev/sda2 before the kernel panic?
check
http://wiki.archlinux.org/index.php/Con … mkinitcpio

try changing menu.lst & fstab root to /dev/sda2
or reconfigure mkinitcpio & regenerate /boot/kernel26.img

arew264 · 2007-06-12 19:08:19

I thought sda was only for SATA drives? I have 2 hard drives (the mobo has SATA and PATA, I use PATA for reasons I will explain later), one for the system and one for swap. When I first installed, I wasn't sure what I was doing, so the system is all one one partition

Well, it just booted from an install disk with "arch root=/dev/sda2"
But when it wants to know what runlevel to enter, and I put 5, it says no more processes left in this runlevel. For a standard terminal, I want 3 or 5, right? And for me it should make no difference which because I haven't installed X, right?

Last edited by arew264 (2007-06-12 19:09:20)

arew264 · 2007-06-12 19:23:51

You were definitely right with it being /dev/sda2. I put that in and mounted it to /home/hd while in a rescue system (that was booted from cd only).

I changed hda2 to sda2 in /home/hd/etc/fstab and updated menu.lst to

root   (hd0,1)
kernel /boot/vmlinuz26 root=/dev/hda2 ro
initrd /boot/kernel26.img

It yielded the same error, except that it said it couldn't parse block device /dev/sda2

is my system somehow corrupt? Booting the rescue disk with "arch root=/dev/sda2" boots fine and then asks for a runlevel. Tried it with 3 this time same problem (INIT: no more processes left in this runlevel). I pulled a bunch of X related gunk that was leftover from when I ran X before now, did that somehow mess up the inittab?

arew264 · 2007-06-12 19:43:39

Okay, something really wierd is going on with my partitions, and I never noticed it. Somehow I have a leftover debian installation on an ext3 partition on my main drive...

I'm just gonna go in with knoppix, evacuate my system over my network, format, and reinstall. I'll even set everything up in separate partitions this time.

Arch Linux

#1 2007-06-09 01:53:22

Kernel Panic after Upgrade

#2 2007-06-09 02:08:57

Re: Kernel Panic after Upgrade

#3 2007-06-12 19:08:19

Re: Kernel Panic after Upgrade

#4 2007-06-12 19:23:51

Re: Kernel Panic after Upgrade

#5 2007-06-12 19:43:39

Re: Kernel Panic after Upgrade

Board footer