Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34373 - kernel 3.8.3-2 fails to boot on mdadm + LVM
Attached to Project:
Arch Linux
Opened by Laurent Artaud (laurenta) - Tuesday, 19 March 2013, 14:41 GMT
Last edited by Dave Reisner (falconindy) - Friday, 22 March 2013, 14:21 GMT
Opened by Laurent Artaud (laurenta) - Tuesday, 19 March 2013, 14:41 GMT
Last edited by Dave Reisner (falconindy) - Friday, 22 March 2013, 14:21 GMT
|
DetailsDescription:
kernel starts but soon fails to a minimal console with a message about mdadm (sorry: can't remember the exact message) downgrade to 3.7.10-1 after booting via live USB corrected the problem. Additional info: * package version(s) linux-3.8.3-2 mdadm-3.2.6-3 Steps to reproduce: /boot on mdadm RAID1 / and /home on LVM over another mdadm RAID1 |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 22 March 2013, 14:21 GMT
Reason for closing: Won't fix
Additional comments about closing: No interest in whatever the mdadm hook based failure is. mdadm_udev is the way ahead.
Friday, 22 March 2013, 14:21 GMT
Reason for closing: Won't fix
Additional comments about closing: No interest in whatever the mdadm hook based failure is. mdadm_udev is the way ahead.
I experience the same problem (also with the previous kernel) but sometimes my boot succeeds and sometimes not. I the latter case, I always see the message 'waiting 10 seconds for /dev/mapper/...'. Could it be there is a problem in the order of the hooks ?
Here are mine :
HOOKS="base udev autodetect block mdadm lvm2 keymap filesystems keyboard fsck"
UPDATE : when I get a command prompt "/rootfs" and I assemble my arrays with 'mdassemble' and then I type exit then I can continue to boot.
"""
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-linux root=/dev/mapper/array-root ro quiet
[Linux-bzimage, setup=0x4200,size=0x38d090]
initrd /initramfs-linux.img
[Linux-initrd @ 0x37be8000, 0x407f69 bytes]
early console in decompress_kernel
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
ERROR: device '/dev/mapper/array-root' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/mapper/array-root'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty; job control turned off
[rootfs /]#
"""
I confirm that a downgrade to 3.7.10-1 is the only thing needed to correct the problem.
HOOKS="base udev autodetect modconf block mdadm_udev filesystems keyboard fsck"
So in my case mdadm_udev doesn't solve the issue.
Apologises for not posting up error message but the boot error is non recoverable & appears not to be getting logged.
Thanks.
Was there an announcement about the need for this change? I didn't see any…
Thanks.
You're clearly seeing something entirely unrelated to this bug report. Moreover, I have no idea what's broken for you because you haven't supplied anything of value in describing the boot failure. Please open a new report with actual detail if you think this is a problem with the ARCH kernel (I really don't think it is).
> Was there an announcement about the need for this change? I didn't see any…
We've been pushing people towards mdadm_udev for well over a year. There's been no announcement. The mdadm hook will go away someday and be replaced by what mdadm_udev is now.