Your message dated Tue, 17 Sep 2013 21:14:47 +0200
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #703879,
regarding initrd hangs after lvm
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 [email protected]
immediately.)
--
703879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703879
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dracut
Version: 020-2
Severity: important
Tags: patch
I build a initrd with dracut. When I boot my system, I got messages that
logical volumes where activated and after a few seconds, that no root
filesystem where found.
I found out, that in my initrd are no udev-rules to create the /dev/mapper
files for my logical volumes. After adding the line "inst_rules 55-dm.rules" to
the file /usr/lib/dracut/modules.d/90lvm/module-setup.sh function install,
everything works for me.
-- System Information:
Debian Release: 7.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'),
(500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8.4 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dracut depends on:
ii cpio 2.11+dfsg-0.1
ii kbd 1.15.3-9
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.3
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-7
ii lvm2 2.02.95-7
ii mdadm 3.2.5-5
Versions of packages dracut suggests:
pn dracut-network <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
This bug was already fixed upstream in 031.
--
regards Thomas
--- End Message ---
