You are not logged in.

#1 2007-04-10 09:06:07

kvvier
Member
Registered: 2007-04-10
Posts: 3

Kernel Panic! - "kinit: Unable to mount root fs on device hda1(3,1)"

After upgrading 0.7.1 to 0.8 with "pacman -Syu", when booting:

IP-Config: no devices to configure
kinit: Unable to mount root fs on device hda1(3,1)
kinit: init not found!
Kernel panic - not syncing: Attempting to kill init

Bootloader: grub

Last edited by kvvier (2007-04-10 09:06:53)

Offline

#2 2007-04-10 09:10:40

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,017

Re: Kernel Panic! - "kinit: Unable to mount root fs on device hda1(3,1)"

Have you read what pacman spat out after upgrading?

Have you added "initrd /boot/kernel26.img" line to grub's menu.lst file?

Offline

#3 2007-04-10 09:18:23

kvvier
Member
Registered: 2007-04-10
Posts: 3

Re: Kernel Panic! - "kinit: Unable to mount root fs on device hda1(3,1)"

lucke wrote:

Have you read what pacman spat out after upgrading?

no

lucke wrote:

Have you added "initrd /boot/kernel26.img" line to grub's menu.lst file?

I've added "initrd /kernel26.img" because i have seperate /boot partition (Auto-Prepare HArd Drive when installing  Arch)

Offline

#4 2007-04-10 10:12:57

STiAT
Member
From: Vienna, Austria
Registered: 2004-12-23
Posts: 603

Re: Kernel Panic! - "kinit: Unable to mount root fs on device hda1(3,1)"

Well, look at the output:

kinit: Unable to mount root fs on device hda1(3,1)

Due to mkinitrd changes, there should not be any hda any longer. That's why there is no root fs found.
The kernel image IS found, otherwhise you'd get a sync error (VFS).

Within a kernel upgrade from 0.7.x to 0.8, as long as you don't have earlymodules=piix, you'll need to specify sda instead of hda in your grub configuration and fstab.

As long as you didn't rename your kernel, you actually should not have kernel26, no matter if there is a /boot device (partition) or not.

Closer descriptions can be found about 100000 times here on the boards. Plase, start using the search function.

Kind regards,
STi

Last edited by STiAT (2007-04-10 10:14:01)


Ability is nothing without opportunity.

Offline

#5 2007-04-10 10:37:03

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,017

Re: Kernel Panic! - "kinit: Unable to mount root fs on device hda1(3,1)"

There's ide hook, not pata, in default mkinitcpio.conf - thus it shouldn't change IDE drives to sdX naming scheme by default.

Offline

#6 2007-04-10 10:44:04

STiAT
Member
From: Vienna, Austria
Registered: 2004-12-23
Posts: 603

Re: Kernel Panic! - "kinit: Unable to mount root fs on device hda1(3,1)"

At least on my 2nd PC with IDE it's sda, not hda. That's why i expected it to be for any hardware configuration, not just for pata / sata seperated.

Anyway, he did not mention if he has got sata or pata, at all it's very less information given.


Ability is nothing without opportunity.

Offline

#7 2007-04-10 12:19:08

kvvier
Member
Registered: 2007-04-10
Posts: 3

Re: Kernel Panic! - "kinit: Unable to mount root fs on device hda1(3,1)"

STiAT wrote:

Anyway, he did not mention if he has got sata or pata

I've got pata.

EDIT:
I've changed all "hdXY" to "sdXY" in /etc/fstab, added "pata" to HOOKS in mkinitcpio.conf,
executed "mkinitcpio -g /boot/kernel26.img -k 2.6.20-ARCH", but kernel still panics.

EDIT2:
Reinstalled grub and edited /boot/grub/menu.lst too, of course.

EDIT3:
I don't know what it means but executing /sbin/lilo i've got sth like this:

bash-3.2# /sbin/lilo
/proc/misc: no entry for device-mapper found
Is device-mapper driver missing from kernel?
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Added arch *
Added arch-fallback

Last edited by kvvier (2007-04-10 14:07:58)

Offline

Board footer

Powered by FluxBB