Your message dated Sun, 18 Jan 2015 16:03:44 +0000 with message-id <1421597024.31046.159.ca...@decadent.org.uk> and subject line Re: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing of mdadm + lvm initiation has caused the Debian Bug report #644876, regarding initramfs-tools: Boot failure from software RAID1 + LVM2 by timing of mdadm + lvm initiation to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 644876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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 by lvm (/dev/mapper/vgbase-lvroot), of which the volume group is located on a raid1 (using partitions from both usb drives) The origin of the problem is the combination of late detection of the USB devices in combination with the bootsequence. After some research it became clear to me that the mdadm and lvm routines (located in /scripts/local-top?) are performed before the rootdelay loop (located in /scripts/local). On systems without a complex raid or lvm setup this poses no problem since the root will instantly be present when the slow device is recognised. In my case adding a rootdelay=x does NOT solve the problem because when the USB drives become available there are still no started MD devices or LVM volumes. The (quick and dirty) solution for me was adding 3 lines to the /scripts/local file after the rootdelay loop (ends at line 42); /sbin/mdadm --assemble --scan /sbin/lvm vgscan --ignorelockingfailure /sbin/lvm vgchange --ignorelockingfailure -a y In essence this repeats the mdadm and lvm2 routines but then without the nice checking of earlier mentioned scripts. Of course it would be better to get the routines programmed nicely after the rootdelay parameter. Is it possible to fix this? I am happy to assist in testing better solutions than the dirty one I proposed. Also I will try to answer any questions if the above is unclear or if more information is needed. See also bug #433905 for a similar case (only first post applies). Best regards, Jort Koopmans -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 11M Oct 9 22:59 /boot/initrd.img-2.6.32-5-amd64 -rw-r--r-- 1 root root 11M Oct 9 11:57 /boot/initrd.img-2.6.32-5-amd64.bakorig -rw-r--r-- 1 root root 11M Oct 9 15:22 /boot/initrd.img-2.6.32-5-amd64.bakworks -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/vgbase-lvroot ro quiet -- resume RESUME=/dev/mapper/vgbase-lvswap -- /proc/filesystems ext3 -- lsmod Module Size Used by loop 11799 0 evdev 7352 4 pcspkr 1699 0 i2c_i801 7830 0 i2c_core 15819 1 i2c_i801 snd_hda_intel 20035 0 snd_hda_codec 54244 1 snd_hda_intel snd_hwdep 5380 1 snd_hda_codec snd_pcm 60487 2 snd_hda_intel,snd_hda_codec snd_timer 15598 1 snd_pcm snd 46526 5 snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 4598 1 snd snd_page_alloc 6249 2 snd_hda_intel,snd_pcm ioatdma 34876 16 dca 3761 1 ioatdma button 4650 0 processor 29935 8 ext3 106710 3 jbd 37221 1 ext3 mbcache 5050 1 ext3 sd_mod 29921 6 crc_t10dif 1276 1 sd_mod dm_mod 53898 9 raid1 18431 2 md_mod 73872 3 raid1 usbhid 33292 0 hid 63257 1 usbhid usb_storage 40057 4 uhci_hcd 18521 0 ahci 32534 0 libata 133776 1 ahci scsi_mod 126533 3 sd_mod,usb_storage,libata ehci_hcd 32081 0 e1000e 124772 0 usbcore 122674 5 usbhid,usb_storage,uhci_hcd,ehci_hcd nls_base 6377 1 usbcore thermal 11674 0 thermal_sys 11942 2 processor,thermal -- /etc/initramfs-tools/modules -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip BOOT=local DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : [raid1] md1 : active raid1 sda2[0] sdb2[1] 15051704 blocks super 1.2 [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 306164 blocks super 1.2 [2/2] [UU] unused devices: <none> -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox dmsetup keymap klibc lvm2 mdadm thermal udev -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-4 GNU cpio -- a program to manage ar ii findutils 4.4.2-1+b1 utilities for finding files--find, ii klibc-utils 1.5.20-1+squeeze1 small utilities built with klibc f ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii udev 164-3 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.17.1-8 Tiny utilities for small and embed Versions of packages initramfs-tools suggests: ii bash-completion 1:1.2-3 programmable completion for the ba -- no debconf information
--- End Message ---
--- Begin Message ---Version: 3.3-1 The proposed change to udevadm was made in version 3.3-1 but was accidentally omitted from the changelog. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou
signature.asc
Description: This is a digitally signed message part
--- End Message ---
