Bug#808123: lvm2: adding LVM support after the installation makes the machine unbootable

Sandro Tosi morph at debian.org
Wed Dec 16 09:44:41 UTC 2015

Source: lvm2
Version: 2.02.95-8
Severity: grave

we added support for LVM after the installation of the machine, created an LV
and add it to /etc/fstab to mount it at boot. but then the boot process halts at
fsck as it cant find the device in /dev.

upon inspection, the initscript in /etc/rcS.d was created as S26, which start
loooong after all the other initialization scripts, and after the S08checkfs
which causes the boot to halt.

moving the S26lvm2 to S05lvm2 (as on other machine where we created the lvm at
installation-time) fixed the issue.

I know it's the wheezy packages, but it's a rather painful bug, which should
be addressed even in oldstable (but I'm not sure if it might apply even on other


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

More information about the pkg-lvm-maintainers mailing list