You are not logged in.
During my kernel upgrade via pacman yesterday, I received the following errors:
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.20-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
/lib/initcpio/install/autodetect: line 14: mdadm: command not found
:: Parsing hook [ide]
:: Parsing hook [scsi]
:: Parsing hook [filesystems]
/lib/initcpio/functions: line 138: modinfo: command not found
/lib/initcpio/functions: line 138: modinfo: command not found
/lib/initcpio/functions: line 138: modinfo: command not found
:: Generating image '/boot/kernel26.img'.../sbin/mkinitcpio: line 235: gen_init_cpio: command not found
SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.20-ARCH -c /etc/mkinitcpio.d/kernel26-fallback.conf -g /boot/kernel26-fallback.img
:: Begin build
/lib/initcpio/functions: line 138: modinfo: command not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [ide]
/lib/initcpio/functions: line 138: modinfo: command not found
/lib/initcpio/functions: line 138: modinfo: command not found
/lib/initcpio/functions: line 138: modinfo: command not found
...
:: Parsing hook [pata]
.../lib/initcpio/functions: line 138: modinfo: command not found
...
:: Parsing hook [scsi]
/lib/initcpio/functions: line 138: modinfo: command not found
...
:: Parsing hook [sata]
/lib/initcpio/functions: line 138: modinfo: command not found
...
:: Parsing hook [usbinput]
/lib/initcpio/functions: line 138: modinfo: command not found
...
:: Parsing hook [raid]
/lib/initcpio/functions: line 138: modinfo: command not found
:: Parsing hook [filesystems]
/lib/initcpio/functions: line 138: modinfo: command not found
....
/lib/initcpio/functions: line 138: modinfo: command not found
:: Generating image '/boot/kernel26-fallback.img'.../sbin/mkinitcpio: line 235: gen_init_cpio: command not found
SUCCESS
==> SUCCESS
Please note: the ... in the above code signifies multiple instances of the previous command.
Although I had those errors, pacman did return a SUCCESS. This morning I rebooted my computer and received the following kernel panic:
Not syncing VFS. Unable to mount root fs: root fs on unknown block hda(0,0)
I'm running Arch64, with one IDE hard drive. Here is my grub menu.lst:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/hda3 ro vga=773
#To change to old depracted initrd created by mkinitrd use initrd26.img image
#initrd /initrd26.img
initrd /kernel26.img
Any ideas why my kernel won't boot? Thanks in advance.
Last edited by lnxgrl (2007-03-02 18:40:11)
Offline
try adding rootfstype=<fs type here> to your kernel line. i.e.:
rootfstype=ext3
if this does not fix the problem try also adding:
earymodules=piix
few people had the same problem (including me) and you can see these posts user Newbie Corner.
Offline
modinfo not found? Do you have module-init-tools installed? It's in base and shouldn't be removed.
Offline
Thanks for your responses thus far.
phrakture:
I do have module-init-tools installed:
> pacman -Qs module-init-tools
local/module-init-tools 3.2.2-3
Utilities for inserting and removing modules from the Linux kernel
Not sure why i would get that error.
djidji:
I've tried both ext2 and ext3 as the rootfstype....neither of which worked. This is what I typed in the menu.lst each time:
kernel /vmlinuz26 root=/dev/hda3 ro vga=773 rootfstype=ext3
kernel /vmlinuz26 root=/dev/hda3 ro vga=773 rootfstype=ext2
my /etc/fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/dvd /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/fd0 /mnt/fl vfat user,noauto 0 0
/dev/hda3 / ext3 defaults 0 1
/dev/hda1 /boot ext2 defaults 0 1
/dev/hda2 swap swap defaults 0 0
also tried the earlymodules=piix to no avail.
Offline
I do have module-init-tools installed:
> pacman -Qs module-init-tools
local/module-init-tools 3.2.2-3
Utilities for inserting and removing modules from the Linux kernelNot sure why i would get that error.
Aha, modinfo is in /sbin/, which is most likely not in your path. For right now, this will work:
export PATH=$PATH:/sbin
mkinitcpio -p kernel26
do that as root.
I will also fix mkinitcpio to use absolute paths
Offline
Aha, modinfo is in /sbin/, which is most likely not in your path. For right now, this will work:
Code:export PATH=$PATH:/sbin
mkinitcpio -p kernel26do that as root.
That corrected the issue! The kernel installed without errors AND I was able to reboot. /sbin is now in my path, so this shouldn't happen again. I really appreciate your help
Offline
That corrected the issue! The kernel installed without errors AND I was able to reboot. /sbin is now in my path, so this shouldn't happen again. I really appreciate your help
No problem, it's probably my fault anyway for assuming modprobe and modinfo are in the executor's path... it's fixed in svn. I need to release new versions of klibc and mkinitcpio sometime soon anyway.
Offline