Hi,
Elimar Riesebieter wrote:
> At boottime I get:
>
> WARNING: Device /dev/md0 not initialized in udev database even after waiting
> 10000000 microseconds.
I get the same warning, too, at boot time and so far also at any time
I call a LVM command. In anycase the command (and hence the boot
itself, too) takes about 7 minutes! (Which makes every reboot very
annoying, and I had plenty of them recently due to #918764.)
So far I've seen it in the following circumstances:
* At boot, probably due to calls to vgchange or so.
* Calling vgs
* Calling lvs
* Calling lvresize
> two times.
I get this type of warning 44 times per boot or LVM command:
# time lvs
WARNING: Device /dev/md0 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-0 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/md1 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/md2 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-2 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-3 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-4 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-5 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-6 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-7 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-8 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-9 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-10 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-11 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-12 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-13 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-14 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-15 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-16 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-17 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-18 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-19 not initialized in udev database even after
waiting 10000000 microseconds.
/dev/sde: open failed: No medium found
/dev/sdf: open failed: No medium found
/dev/sdg: open failed: No medium found
/dev/sdh: open failed: No medium found
/dev/sdi: open failed: No medium found
WARNING: Device /dev/md0 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-0 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/md1 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/md2 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-2 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-3 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-4 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-5 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-6 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-7 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-8 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-9 not initialized in udev database even after waiting
10000000 microseconds.
WARNING: Device /dev/dm-12 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-13 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-14 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-15 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-16 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-17 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-18 not initialized in udev database even after
waiting 10000000 microseconds.
WARNING: Device /dev/dm-19 not initialized in udev database even after
waiting 10000000 microseconds.
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync
Convert
home vgc6 -wi-ao---- <38.61g
log vgc6 -wi-ao---- <1.86g
root vgc6 -wi-ao---- 53.00g
var vgc6 -wi-ao---- 4.25g
anx vgwd -wi-ao---- 200.00g
apt vgwd -wi-ao---- 1.00g
bkup vgwd -wi-ao---- 150.00g
c3pio-sd vgwd -wi-a----- 65.00g
crsh vgwd -wi-ao---- 20.00g
dph vgwd -wi-ao---- 90.00g
games vgwd -wi-ao---- 2.00g
img vgwd -wi-ao---- 70.00g
med vgwd -wi-ao---- 3.00g
pbr vgwd -wi-ao---- 8.00g
scr vgwd -wi-ao---- 60.00g
swap vgwd -wi-ao---- 16.00g
tmp vgwd -wi-a----- 30.00g
wdm-test vgwd -wi-a----- 10.00g
lvs 0.44s user 0.59s system 0% cpu 7:01.58 total
# ^^^^^^^^^^^^^
Please also note the 7 minutes this command took to finish.
/dev/sde to /dev/sdi are the five different slots of an internal USB
3.0 multi-format card reader.
> System boots to maintenance stage.
That's a clear difference to my case, probably because of using a
stock kernel: System boots more or less fine, but takes about 8.5
minutes minutes to boot of which likely 7 minutes are due to LVM.
vgc6 is a VG on two SSDs coupled to a RAID1 with md.
vgwd is a VG on two 3TB spinning disks coupled to a RAID1 with md.
There's also a third md-based RAID1 without LVM for /boot/.
> I am running a custom 4.19.13 which ran fine on stable.
I am running stock Debian unstable kernels.
So far it happened with 4.18.20-2 (last 4.18 which was in sid/buster)
and 4.19.12-1 (current is 4.19.13-1).
Oh, and JFTR: I'm using sysvinit-core as PID1 and it so far happened
with at least udev 240-2 and 240-3.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
