FS#7807 - mkinitcpio produces a non-working image

Attached to Project: Arch Linux
Opened by John (Acid7711) - Monday, 13 August 2007, 07:51 GMT
Last edited by Dale Blount (dale) - Monday, 13 August 2007, 19:11 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08 Don't Panic
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: mkinitcpio produces a non-working image under custom kernels. Fallback image for created kernels does not work either, same error. Stock kernel works fine, however upon creating a compiling a custom kernel (using ABS) I reboot and get the following:

--------------------------
Loading root filesystem module...
Attempting to create root device name for '/dev/sda3'
unknown
ERROR: root fs cannot be detected. Try using the rootfstype=kernel parameter

Waiting for device to settle...done
Root device '/dev/sda3' doesn`t exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sda3'
ERROR: Unable to create/detect root device '/dev/sda3'
Dropping to a recovery shell
NOTE: klibc contains no 'ls' binary
.
.
.
ramfs$
--------------------------


Weeks ago, I had no problems. After some unknown change or update, the kernel simply wouldn't boot after a new version was created. I've since reinstalled, that solved nothing. If I don't use mkinitcpio's image, and compile all support in, the kernel boots just fine, however I don't really like doing this.


Additional info:
Packages are all current versions.



mkinitcpio.conf
------------------
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="amd74xx generic sata_nv"

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
#HOOKS="base udev autodetect ide scsi sata keymap filesystems"

HOOKS="base udev autodetect sata keymap filesystems"
------------------


menu.conf

--------------------
timeout 5
default 1
color light-blue/black light-cyan/blue

# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

# (0) Arch Linux -KamiKaze Kernel
title Arch Linux - KamiKaze Kernel Patchset
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26kamikaze.img

# (0) Arch Linux
title Arch Linux - Stock Kernel
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26.img
--------------------


fstab
--------------------
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0

/dev/sda1 /boot ext2 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / reiserfs noatime 0 0

/dev/hda1 /Backup/Media ntfs-3g defaults,rw,nosuid,nodev,noatime,allow_oth 0 0
/dev/sdb1 /Backup/Apps vfat defaults,users,umask=000
/dev/hdb1 /Backup/Misc vfat defaults,users,umask=000
--------------------
This task depends upon

Closed by  Dale Blount (dale)
Monday, 13 August 2007, 19:11 GMT
Reason for closing:  Works for me
Additional comments about closing:  Reporter says problem is solved.
Comment by John (Acid7711) - Monday, 13 August 2007, 07:56 GMT
The listed mkinitcpio.conf above is before I reinstalled. This listed here is my mkinitcpio.conf after reinstall if it matters.....

mkinitcpio.conf
--------

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="pata_amd ata_generic sata_nv"

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usbinput keymap filesystems"
-----------

Loading...