Debian Bug report logs - #568838
Init script finishes before /dev entries created causing boot to fail

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Anthony DeRobertis <anthony@derobert.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Init script finishes before /dev entries created causing boot to fail

Date: Mon, 08 Feb 2010 00:01:03 -0500

Package: lvm2
Version: 2.02.54-1
Severity: important
File: /etc/init.d/lvm2

Sometimes when I boot my laptop, cryptsetup fails & then the machine
fails to boot. Config is:

lvm on bare disk
	crypto on lv
		ext4 on crypto

It appears this is a race condition between udev creating the devices
(after the lvm2 init script starts lvm) and cryptsetup looking for them.

I tried a few boots after adding a udevadm settle in the start action,
and that appears to fix it. But its a race condition, so its hard to
test.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 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 lvm2 depends on:
ii  dmsetup                      2:1.02.39-1 The Linux Kernel Device 
Mapper use
ii  libc6                        2.10.2-2    GNU C Library: Shared libraries
ii  libdevmapper1.02.1           2:1.02.39-1 The Linux Kernel Device 
Mapper use
ii  libreadline5                 5.2-7       GNU readline and history 
libraries
ii  lsb-base                     3.2-23      Linux Standard Base 3.2 
init scrip

lvm2 recommends no packages.

lvm2 suggests no packages.

-- no debconf information

Message #10 received at 568838@bugs.debian.org (full text, mbox, reply):

From: StalkR <debian-reportbug@stalkr.net>

To: Debian Bug Tracking System <568838@bugs.debian.org>

Subject: lvm2: initramfs-tools/scripts/local-top/lvm2 does not wait to detect LVM on devices that need time to appear

Date: Sat, 20 Feb 2010 00:20:29 +0100

[Message part 1 (text/plain, inline)]

Package: lvm2
Version: 2.02.54-1
Severity: normal


On my embedded system the root filesystem is on an LVM volume on an SD card.

On a lucky day, the SD card gets recognized soon enough and scripts/local-top/lvm2 achieves to activate logical volume so that the root filesystem can be mounted.

The other days, the SD card does not get recognized soon enough and scripts/local-top/lvm2 fails to activate logical volume (volume group cannot be found), then scripts/local:pre_mountroot() complains that rootfs cannot be found and ironically waits ROOTDELAY for the rootfs to appear... but this cannot happen since lvm2 only is responsible for volume activation.

Just as in pre_mountroot(), I suggest to wait for the logical volume to appear. I attached a patch with a working solution: it scans with lvscan until the logical volume appears or until ROOTDELAY is reached. Note that in case detection fails after ROOTDELAY it does not return and it still tries to activate volume in order to inform the user with the error (unable to find LVM volume).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.32.2
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 lvm2 depends on:
ii  dmsetup                      2:1.02.39-1 The Linux Kernel Device Mapper use
ii  libc6                        2.10.2-6    Embedded GNU C Library: Shared lib
ii  libdevmapper1.02.1           2:1.02.39-1 The Linux Kernel Device Mapper use
ii  libgcc1                      1:4.4.3-1   GCC support library
ii  libreadline5                 5.2-7       GNU readline and history libraries
ii  lsb-base                     3.2-23      Linux Standard Base 3.2 init scrip

lvm2 recommends no packages.

lvm2 suggests no packages.

-- no debconf information

[lvm2_wait-lvm.patch (text/plain, attachment)]

Message #15 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Alexander Clouter <alex@digriz.org.uk>

To: 568838@bugs.debian.org

Subject: Re: Init script finishes before /dev entries created causing boot to fail

Date: Fri, 9 Apr 2010 11:48:50 +0100

[Message part 1 (text/plain, inline)]

Hi,

I also have been battling with this race condition for the past few 
years.  I have a non-complicated non-RAID (although I do see this on my 
software RAID boxen too) where /usr, /var and /home are part of an LVM 
however my root is not.

My /etc/fstab typically looks like:
----
LABEL=swap      none            swap    sw                               0  0

LABEL=root      /               auto    relatime                         0  1

LABEL=usr       /usr            auto    relatime,nodev                   0  2
LABEL=var       /var            auto    relatime,nodev,nosuid            0  2
LABEL=home      /home           auto    relatime,nodev,nosuid,noexec     0  2

tmpfs           /tmp            tmpfs   nodev,nosuid,noexec,size=32M     0  0
tmpfs           /var/tmp        tmpfs   nodev,nosuid,noexec,size=8M      0  0
varrun          /var/run        tmpfs   nodev,nosuid,noexec,size=512k    0  0
varlock         /var/lock       tmpfs   nodev,nosuid,noexec,size=96k     0  0

#/dev/hda       /media/cdrom0   auto    ro,user,noauto                   0  0
#/dev/hdf       /media/cdrom1   auto    ro,user,noauto                   0  0
#/dev/fd0       /media/floppy0  auto    rw,user,noauto                   0  0
----

When my box boots I can often stumble onto:
----
Setting up LVM Volume Groups  Reading all physical volumes.  This may 
take a while...
  Found volume group "lvm-oghma" using metadata type lvm2
  3 logical volume(s) in volume group "lvm-oghma" now active
.
Checking file systems...fsck 1.41.3 (12-Oct-2008)
/sbin/fsck.xfs: XFS file system.
/sbin/fsck.xfs: XFS file system.
/sbin/fsck.xfs: LABEL=home does not exist
fsck died with exit status 8
failed (code 8).
File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file sy
A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. (warning).
Give root password for maintenance
(or type Control-D to continue): 
----

This happens about 80% of the time on some kit, 10% on others.  
Sometimes it grumbles that LABEL=usr or LABEL=var does not exist instead 
so it is very obviously a race condition.  Looking at what could be 
going on, /etc/rcS.d/S26lvm2 shoots through without pausing and so udev 
is in a state where it has not quite created all the softlinks in 
/dev/disk/by-label in time for when /etc/rcS.d/S30checkfs.sh kicks in.

This is trivially fixed by amendment to /etc/init.d/lvm2 that 'StalkR' 
suggested, and is done by the patch I have attached.

Now when my boxes boot I get:
----
Setting up LVM Volume Groups  Reading all physical volumes.  This may 
take a while...
  Found volume group "lvm-oghma" using metadata type lvm2
  3 logical volume(s) in volume group "lvm-oghma" now active
.
Checking file systems...fsck 1.41.3 (12-Oct-2008)
/sbin/fsck.xfs: XFS file system.
/sbin/fsck.xfs: XFS file system.
/sbin/fsck.xfs: XFS file system.
done.
Setting kernel variables (/etc/sysctl.conf)...done.
Mounting local filesystems...Filesystem "dm-0": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-0
Filesystem "dm-1": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-1
[snipped]
----

Please include this, get it pushed into 'lenny' too and 'squeeze' as it 
really is a nasty showstopper that makes booting of servers potentially 
very unreliable.

Cheers

-- 
Alexander Clouter
.sigmonster says: What foods these morsels be!

[lvm-race-fix.patch (text/x-diff, attachment)]

Message #20 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Alexander Clouter <alex@digriz.org.uk>

To: 568838@bugs.debian.org

Subject: Re: Init script finishes before /dev entries created causing boot to fail

Date: Fri, 9 Apr 2010 11:52:03 +0100

Hi,

* Alexander Clouter <alex@digriz.org.uk> [2010-04-09 11:48:50+0100]:
>
> [snipped]
> 
> This is trivially fixed by amendment to /etc/init.d/lvm2 that 'StalkR' 
> suggested, and is done by the patch I have attached.
> 
Rather the suggestion Anthony DeRobertis made...

Cheers

-- 
Alexander Clouter
.sigmonster says: Most burning issues generate far more heat than light.

Message #25 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Alexander Clouter <alex@digriz.org.uk>

To: 568838@bugs.debian.org

Subject: Re: Init script finishes before /dev entries created causing boot to fail

Date: Tue, 24 Aug 2010 16:15:24 +0100

[Message part 1 (text/plain, inline)]

Hi,

This issue is crucial to be included in squeeze, without the trivial 
attached patch it really makes using LVM and Linux with LABEL mounts 
un-usable.

Any comment on this at all?

Cheers

-- 
Alexander Clouter
.sigmonster says: I wouldn't be so paranoid if you weren't all out to get me!!

[lvm2-settle.patch (text/x-diff, attachment)]

Message #30 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Marek Šabo <msabo@buk.cvut.cz>

To: 568838@bugs.debian.org

Subject: Logical volumes not detected for root partition mount

Date: Wed, 10 Nov 2010 23:55:09 +0100

Package: lvm2
Version: 2.02.66-3
squeeze 2.6.32-5-amd64

Hi,

I use Debian inside KVM (qemu) and in three setups where boot partition 
is /dev/sda1 and logical volumes are on volume group consisting of 
physical volume /dev/sda2, similar race condition appears and volumes 
have to be activated manually from ash initramfs console. After that the 
boot process can continue with mounting the root partition.

After applying StalkR's patch (many thanks), boot process goes as expected.

Just my 2c, regards

-- 
Marek Šabo
Server Manager
Club SU CVUT Buben

Message #35 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Mikko Lehto <mikko.lehto@setera.fi>

To: 568838@bugs.debian.org

Subject: lvm2_wait-lvm.patch works

Date: Wed, 23 Feb 2011 14:22:36 +0200

After Debian 5.0 Lenny to Debian 6.0 Squeeze upgrade I also
had to manually activate volume groups (vgchange -ay) in every boot.

The patch lvm2_wait-lvm.patch resolved this issue.
Kernel is linux-image-2.6.32-5-amd64 2.6.32-30 and lmv2 is 2.02.66-5.

-- 
Mikko Lehto
Setera

Message #40 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Lutz Reinhardt <l.reinhardt@gmx.net>

To: 568838@bugs.debian.org

Subject: lvm2_wait-lvm.patch works

Date: Tue, 15 Mar 2011 23:15:34 +0100

I can confirm that the patch works also. I can boot only with this patch
on a 3ware controller with lvm :-/

Debian 6.0
2.6.32-5-amd64 / lvm 2.02.66-5

Message #45 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Pascal Guérin <pascal.guerin@univ-savoie.fr>

To: 568838@bugs.debian.org

Subject: lvm2_wait-lvm.patch not working

Date: Mon, 25 Apr 2011 17:39:38 +0200

Package: lvm2
Version: 2.02.66-5
squeeze kernel 2.6.32-5-686 

After upgrading from debian 5 to 6, i had also to activate manualy my 
three lvm volumes via lvchanche.
I tried the patch but it didn't fix the problem.

Hopefylly, these volumes are data lvm so the boot process gon on with a 
Ctrl d ...

Pascal Guérin -

Message #50 received at 568838@bugs.debian.org (full text, mbox, reply):

From: John Bazik <jsb@cs.brown.edu>

To: 568838@bugs.debian.org

Subject: lvm2_wait-lvm.patch works

Date: Wed, 27 Jul 2011 17:52:52 -0400

I can confirm that the lvm2_wait-lvm.patch works, also.  I have an
entire class of blade systems that will not boot without it.  Please
don't let this go unresolved.

John

Message #55 received at 568838@bugs.debian.org (full text, mbox, reply):

From: John Bazik <jsb@cs.brown.edu>

To: 568838@bugs.debian.org

Subject: oops

Date: Wed, 27 Jul 2011 18:19:59 -0400

Oops - forgot to mention:

squeeze
lvm2 2.02.66-5
kernel 2.6.32-5-amd64

John

Message #60 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Robert Siemer <Robert.Siemer@backsla.sh>

To: 568838@bugs.debian.org

Date: Sun, 18 Dec 2011 20:21:59 +0800

I got the same problem, that is, I had to manually run on the 
initramfs-shell:

lvm lvchange -aly /dev/vg0/lvol0


but the patch didn’t fix the problem. – Coincidently I used this 
constant rebooting to switch from lilo to grub; and that did the trick! 
I reversed the patch (and reran update-initramfs) the picture was the 
same: lilo 23.2 (released 09-Apr-2011) got stuck and grub 1.99-14 did not.

The resulting cmdline was for lilo:

auto BOOT_IMAGE=linux ro root=fd00

and for grub:

BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/vg0-lvolg0 ro quiet


I did no further investigation.

R

Message #65 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Clemens Lang <neverpanic@gmail.com>

To: 568838@bugs.debian.org

Subject: Still exists in lvm2 2.02.66-5

Date: Sun, 13 May 2012 00:19:40 +0200

I can reproduce this problem on every boot with squeeze, lvm2 2.02.66-5.
lvm2_wait-vlm.patch resolves this problem. Please apply this patch.

-- 
Clemens Lang

Message #72 received at 568838@bugs.debian.org (full text, mbox, reply):

From: "David Magda" <dmagda@ee.ryerson.ca>

To: 568838@bugs.debian.org

Cc: waldi@debian.org

Subject: inactive LVMs on boot bug?

Date: Tue, 12 Jun 2012 13:40:17 -0400

Is there any reason why the patch hasn't been applied? The bug has been
open for two years now.

The squeeze release of lvm2 hasn't been touched since January 2011:

http://packages.debian.org/changelogs/pool/main/l/lvm2/lvm2_2.02.66-5/changelog

But the maintainer (CC'd) has updated the wheezy package about two weeks ago:

http://packages.debian.org/changelogs/pool/main/l/lvm2/lvm2_2.02.95-4/changelog

They're obviously active and keeping on top of some things, but this
particular bug appears to have dropped off the radar or is being actively
ignored.

Message #77 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Bastian Blank <waldi@debian.org>

To: 568838@bugs.debian.org

Subject: fixed

Date: Thu, 21 Jun 2012 14:24:02 +0200

tags 568838 squeeze
fixed 568838 2.02.64-1
thanks

This bug is fixed in Wheezy by using udev sync.

Bastian

-- 
Earth -- mother of the most beautiful women in the universe.
		-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

Message #86 received at 568838@bugs.debian.org (full text, mbox, reply):

From: None None <e.prakashs@gmail.com>

To: 568838@bugs.debian.org

Subject: Story on usb flash drive

Date: Tue, 6 Nov 2012 02:53:36 +0530

[Message part 1 (text/plain, inline)]

I have installed squeeze on a pen drive with separate /boot partition and
/root on lvm.

@initramfs busybox shell

"lvm lvscan -a --ignorelockingfailure" does not work unless "lvm vgscan
--ignorelockingfailure" is executed prior to it.

I applied the patch from
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=lvm2_wait-lvm.patch;att=1;bug=568838but
get infinite messages "no volume group found"

I modified the script to include "lvm vgscan --ignorelockingfailure" before
the loop and it worked.

Hope this helps. I am a linux newbee.

[Message part 2 (text/html, inline)]

Message #91 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Cameron King <cking@ecc12.com>

To: 568838@bugs.debian.org

Subject: Reproducible on 2.02.66-5

Date: Thu, 21 Feb 2013 18:11:35 -0800 (PST)

Adding a new drive causes this error on two servers running 2.02.66-5, this patch resolved the issue.  Package was marked as resolved for 

Found in versions lvm2/2.02.66-3, lvm2/2.02.66-5, lvm2/2.02.54-1
Fixed in version lvm2/2.02.64-1

Can someone verify that this patch was actually committed?  I don’t see it mentioned in the changelog either.

-- 
Cameron King

Message #96 received at 568838@bugs.debian.org (full text, mbox, reply):

From: "David Huecking (gmx.net)" <d.huecking@gmx.net>

To: 568838@bugs.debian.org

Subject: Reproducible with lvm2 2.02.66-5 on Debian 6.0.7 "Squeeze" AMD64

Date: Wed, 13 Mar 2013 10:55:36 +0100

Package: lvm2
Version: 2.02.66-5


Hi!

Yesterday, Tuesday 2013-03-12 I installed Debian 6.0.7 "Squeeze" AMD64
including all available updated packages.

Hard disk is one simple U320 parallel SCSI. No (Software-)RAID.
/dev/sda1 1GB on /boot as ext3
/dev/sda2 45GB as Linux LVM2

Using LVs for "/", "/var" and "swap".

Booting the freshly installed system ended up in the initial RAM disk's
shell.
A
lvm lvscan -a
revealed all LVs inactive.

A manually
lvm vgchange -aly
set them ACTIVE.
Leaving the shell the system continued booting successfully.

I applied patch
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=lvm2_wait-lvm.patch;att=1;bug=568838
and rebuild the initial RAM disk
update-initramfs -u

After that the system boots reliable up.


Regards, David.
-- 
--
Eat, sleep and go running, ;-)
David Huecking.

Encrypted eMail welcome!
GnuPG/ PGP-Key: 0x57809216. Fingerprint:
3DF2 CBE0 DFAA 4164 02C2  4E2A E005 8DF7 5780 9216

Message #117 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Sam McLeod <samm@infoxchange.org.au>

To: "568838@bugs.debian.org" <568838@bugs.debian.org>

Subject: Still a bug in Wheezy & Jessie

Date: Mon, 18 May 2015 05:17:43 +0000

[Message part 1 (text/plain, inline)]

This appears to still be a bug in both Wheezy and Jessie – is there any reason this patch never made it in?

[Message part 2 (text/html, inline)]

Message #126 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Matteo Sgalaberni <sgala@sgala.com>

To: 568838@bugs.debian.org

Subject: this bug happen on mine Wheezy

Date: Sat, 22 Oct 2016 20:00:07 +0200 (CEST)

I have several Wheezy 7.11 with
 ii  lvm2                      2.02.95-8         amd64             Linux Logical Volume Manager

this bug happens again on ALL mine systems that have multiple disks (PV)

# pvs
  PV         VG     Fmt  Attr PSize   PFree
  /dev/sda5  debian lvm2 a--    9.76g    0
  /dev/sdb   debian lvm2 a--  240.00g 8.82g
# vgs
  VG     #PV #LV #SN Attr   VSize   VFree
  debian   2   2   0 wz--n- 249.75g 8.82g


I applied the suggested patch but the issue happen again at every bootstrap.

Any hint, solution? I read in this thread about a resolution related to "udev sync" but it's not clear to me, what does this mean?

Thanks

Matteo

Message #131 received at 568838@bugs.debian.org (full text, mbox, reply):

From: Matteo Sgalaberni <sgala@sgala.com>

To: 568838 <568838@bugs.debian.org>

Subject: errata corrige - resolved

Date: Mon, 24 Oct 2016 18:17:15 +0200 (CEST)

I created several VM to reproduce the issue and I found that is not related to this bug report!

My issue was related to a misconfigured device in /boot/grub/device.map

in device map there was:
(hd0)	/dev/sda

but my root device it's /dev/mapper/etc....

and this issue were propagated to lots of my server probably as these VM are cloned from the same source at the beginning...

Also I found that grub was complaining with that error during the apt-get upgrade:
/usr/sbin/grub-probe: error: Couldn’t find PV pv1. Check your device.map

After fixing the device on device.map and a update-grub the system boot correctly.

I'm sorry for the false positive.

Best regards,

M.

Send a report that this bug log contains spam.