Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing of mdadm + lvm initiation

2015-01-18 Thread Ben Hutchings
Control: fixed -1 3.2.5-6 On Sun, 2015-01-18 at 16:03 +, Ben Hutchings wrote: Version: 3.3-1 The proposed change to udevadm was made in version 3.3-1 but was accidentally omitted from the changelog. Actually, it is mentioned in the changelog but in a version that was never uploaded.

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing of mdadm + lvm initiation

2013-03-04 Thread Thomas Parmelan
reassign 644876 mdadm tags 644876 + patch thanks Le mercredi 14 mars 2012 à 01:29, d'après Dave Whitla dave.whi...@wotifgroup.com : The condition will never be true because udevsettle was a symlink to /sbin/udevadm which has been absent from Debian since Lenny. Try editing this file to

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing of mdadm + lvm initiation

2012-03-13 Thread Dave Whitla
I believe this might be the culprit: In /usr/share/initramfs-tools/scripts/local-top/mdadm: if [ -x $(command -v udevsettle) ]; then verbose log_begin_msg Waiting for udev to process events udevsettle 10 verbose log_end_msg fi The condition will never be true because udevsettle was a

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing of mdadm + lvm initiation

2011-10-10 Thread Jort Koopmans
Additional thoughts; As I'm no expert on the whole initramfs boot sequence I'm unsure about the total workings of timing of device scanning, mdadm + lvm2 routines and rootdelay. Imho it should be something like this; init Device scanning | some scanning delay parameter (for slow devices) |

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing of mdadm + lvm initiation

2011-10-09 Thread Jort Koopmans
Package: initramfs-tools Version: 0.98.8 Severity: important Dear kernelteam, After installing a vanilla debian kernel (2.6.32-5-amd64) to 2 similar USB thumbdrives in software RAID1 and using LVM2 an error occurs at boot stating ROOT can not be found. In my case / is locted on an lv managed