FS#19457 - mkinitcpio 0.6.4-1 / mkinitcpio-busybox 1.16.1-3 causes root not to be found
Attached to Project:
Arch Linux
Opened by Nicky726 (Nicky726) - Friday, 14 May 2010, 20:07 GMT
Last edited by Thomas Bächler (brain0) - Monday, 17 May 2010, 19:03 GMT
Opened by Nicky726 (Nicky726) - Friday, 14 May 2010, 20:07 GMT
Last edited by Thomas Bächler (brain0) - Monday, 17 May 2010, 19:03 GMT
|
Details
Description:
After upgrade to metioned versions of packages my EEE 1005 H netbook fails to boot, respectively it fails to mount root filesystem. It prits stuff like can't find actual root filesystem, bailing out, and I am in ramfs. Downgrading packages back to 0.6.3-1, 1.16.1-1 respectively makes system bootable again. Additional info: encrypted disk with LUKS (except for /boot) LVM on top of encrypted partition resume set up for swap partition intel KMS early start * package version(s) mkinitcpio 0.6.4-1 mkinitcpio-busybox 1.16.1-3 * config and/or log files etc. mkinitcpio hooks are: base, udev, autodetect, pata, scsi, sata, keymap, encrypt, lvm2, resume, filesystems mkinitcpio modules are: intel_agp i915 modprobe.conf options are: i915 modeset=1 and usbcore autosuspend=1 Steps to reproduce: Upgrade mentioned packages on box with mentioned config and watch your root not to be found on next boot. |
This task depends upon
Closed by Thomas Bächler (brain0)
Monday, 17 May 2010, 19:03 GMT
Reason for closing: Not a bug
Additional comments about closing: mkinitcpio should require util-linux-ng>=2.17 though.
Monday, 17 May 2010, 19:03 GMT
Reason for closing: Not a bug
Additional comments about closing: mkinitcpio should require util-linux-ng>=2.17 though.
Problem appears, when Arch is printing "mounting root filesystem read only", or something like that. And I can mount the partition from ramfs manually. When I type "exit" after that, it gives me kernel panick.
...
Running Hook [lvm2]
....
5 logical volume(s) in volume group lvm_storage now active
Running Hook [resume]
Waiting 10 seconds for device /dev/mapper/lvm_storage-lvm_swap...
Waiting 10 seconds for device /dev/mapper/lvm_storage-lvm_root...
BusyBox v1.16.1 (...) mult-call binary.
Usage: mount ....
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
/bin/sh: can't access tty; job control turned off
[ramfs/]
...
PM: Starting manual resume from disk
PM: Resume from partition 254:1
PM: Checking hibernation image.
PM: Error -22 checking image file
PM: Resume from disk failed
Though I didn't suspend, just normally rebooted.
Can you provide the contents of the kernel command line? It seems that everything is fine up to the point where we actually try to mount - this means that the root device is in fact found, only the 'mount' command is incorrect.
kernel /vmlinuz26 root=/dev/mapper/lvm_storage-lvm_root cryptdevice=/dev/sda2:luks_storage resume=/dev/mapper/lvm_storage-lvm_swap ro
BusyBox v1.16.1 (...) multi-call binary.
Usage: mount ....
There should be one line detailing what exactly is going wrong. If you could provide what this says, it would be great.
Any suggestion how to get the line?
You could try the following, just to see what the script tries to do: The last command in /lib/initcpio/init_functions is the 'mount' command. Before that command, insert a new line, copy the command, put 'echo' in front of it. Then regenerate initramfs. At least then I will know which exact command fails.
mount -t af2414b5-3a57-40b2-86a0-9813d0b09f17 1.0 ext4 filesystem -o ro /dev/mapper/lvm_storage-lvm_root /new_root
mkinitcpio runs this to determine the file system type:
/sbin/blkid -u filesystem -o value -s TYPE -p /dev/mapper/lvm_storage-lvm_root
but your output looks like the one from:
/sbin/blkid -u filesystem -o value -p /dev/mapper/lvm_storage-lvm_root