Package: dracut
Version: 020-2
Severity: important
My system boots fine with initramfs-tools, but with dracut, it hangs
just after
lvm vgchange -ay $sysinit $VGS 2>&1 | vinfo
at line 123 of /sbin/lvm_scan. Other than reading code on the initial
ramdisk and booting the system with rd.debug=y to determine what the
last successful thing was, I have not done any debugging. However, I
will do some debugging and either upgrade the severity of this bug or
supply a patch or something as soon as I know more. The last line of
debugging output is "read line" in the vinfo function on line 360 of
/lib/dracut-lib.sh. I haven't determined whether the shell is trying to
read a line and isn't getting one because lvm vgchange is hung or
whether it has just failed to do whatever it is trying to do next. That
won't be too hard to determine.
There's nothing particularly unusual about my system. It's an amd64
with everything except /boot in LVM and all file systems except /boot
running with xfs. (/boot is on a regular device and is ext3.) The only
thing slightly unusual is that I have two physical device on the same
disk as an artifact of previous partitioning. In any case, lvm works
fine and has worked fine for ages, so I seriously doubt this is actually
an lvm issue. I observe the hanging with initrd.img-3.2.0-3-amd64 and
initrd.img-3.2.0-4-amd64 with the corresponding kernels. The system
boots normally with an initrd created by initramfs-tools.
My approach to debugging would be to continue to boot with rd.debug=y
and to add various info statements in various places, to manually
recreate the initial ramdisk with cpio and gzip, and to try booting
again. This is obviously a very unsophisticated way to do it. Any
pointers to a smarter way to debug this would be appreciated. I haven't
consulted any documentation that may come with dracut yet. I have
plenty of programming and sysadmin capability but heard of dracut for
the first time when my system failed to boot after an update. I had to
recover the system by booting off a live image (which I keep on hand on
/boot just in case), chrooting into my system, uninstalling dracut,
reinstalling initramfs-tools, creating a new initrd with it, and saving
it to a safe place.
More later. If I discover what's going on, I'll retitle the bug to
something more useful.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-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 dracut depends on:
ii cpio 2.11-8
ii kbd-compat [kbd] 1:0.2.3dbs-70
ii kpartx 0.4.9+git0.4dfdaf2b-6
ii module-init-tools 9-2
ii udev 175-7.1
ii util-linux 2.20.1-5.2
Versions of packages dracut recommends:
ii cryptsetup 2:1.4.3-4
ii dmraid 1.0.0.rc16-4.2
ii dmsetup 2:1.02.74-5
ii lvm2 2.02.95-5
ii mdadm 3.2.5-3
Versions of packages dracut suggests:
pn dracut-network <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
