upgrading from f28 to f29 messed up my system...

[François Patte]

Bonjour,

Yesterday I upgraded my system from f28 to f29 and the result is not
what I expected! I can't get my "new" system working correctly: no
graphic interface, a lot of errors in the logs....

I previously upgraded this system from f25 to f27, then from f27 to f28
without any problems...

This system uses raid 1 + lvm: here is the result of lsblk

NAME                      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                         8:0    0 111,8G  0 disk
├─sda1                      8:1    0     1G  0 part
│ └─md2                     9:2    0     1G  0 raid1 /boot
├─sda2                      8:2    0    60G  0 part
│ └─md127                   9:127  0    60G  0 raid1
│   └─debian-deb--racine  253:0    0  29,3G  0 lvm   /
├─sda3                      8:3    0     1G  0 part
└─sda4                      8:4    0  49,8G  0 part
  └─md11                    9:11   0  49,8G  0 raid1
    ├─fedora-racine       253:2    0     2G  0 lvm
    └─fedora-usr          253:3    0    28G  0 lvm
sdb                         8:16   0 111,8G  0 disk
├─sdb1                      8:17   0     1G  0 part
│ └─md2                     9:2    0     1G  0 raid1 /boot
├─sdb2                      8:18   0    60G  0 part
│ └─md127                   9:127  0    60G  0 raid1
│   └─debian-deb--racine  253:0    0  29,3G  0 lvm   /
├─sdb3                      8:19   0     1G  0 part
└─sdb4                      8:20   0  49,8G  0 part
  └─md11                    9:11   0  49,8G  0 raid1
    ├─fedora-racine       253:2    0     2G  0 lvm
    └─fedora-usr          253:3    0    28G  0 lvm
sdc                         8:32   0 465,8G  0 disk
└─sdc1                      8:33   0 465,8G  0 part
  └─md1                     9:1    0 465,7G  0 raid1
    ├─annexes-data        253:7    0   260G  0 lvm   /commun
    └─annexes-sauvegardes 253:8    0   205G  0 lvm   /sauvegardes
sdd                         8:48   0 465,8G  0 disk
└─sdd1                      8:49   0 465,8G  0 part
  └─md1                     9:1    0 465,7G  0 raid1
    ├─annexes-data        253:7    0   260G  0 lvm   /commun
    └─annexes-sauvegardes 253:8    0   205G  0 lvm   /sauvegardes
sde                         8:64   0 931,5G  0 disk
├─sde1                      8:65   0    40G  0 part
│ └─md4                     9:4    0    40G  0 raid1
│   ├─systeme-swap        253:1    0     4G  0 lvm   [SWAP]
│   ├─systeme-var         253:5    0    15G  0 lvm   /var
│   └─systeme-chiffre     253:6    0    15G  0 lvm
└─sde2                      8:66   0 891,5G  0 part
  └─md5                     9:5    0 891,4G  0 raid1
    └─data-home           253:4    0   500G  0 lvm   /home
sdf                         8:80   0 931,5G  0 disk
├─sdf1                      8:81   0    40G  0 part
│ └─md4                     9:4    0    40G  0 raid1
│   ├─systeme-swap        253:1    0     4G  0 lvm   [SWAP]
│   ├─systeme-var         253:5    0    15G  0 lvm   /var
│   └─systeme-chiffre     253:6    0    15G  0 lvm
└─sdf2                      8:82   0 891,5G  0 part
  └─md5                     9:5    0 891,4G  0 raid1
    └─data-home           253:4    0   500G  0 lvm   /home
sr0                        11:0    1  1024M  0 rom
sr1                        11:1    1  1024M  0 rom

Don't pay attention to the names (debian or fedora) these are the names
I gave a long time ago and I did not change the labels for some volumes.

Now here are the errors I get in the boot logs:

1- déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
Main process exited, code=exited, status=1/FAILURE
déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
Failed with result 'exit-code'.
déc. 05 11:33:05 dipankar systemd[1]: Failed to start Load Kernel Modules.
-- Subject: L'unité (unit) systemd-modules-load.service a échoué

This error occurs several times during the boot process.

2- A lot of errors about lvm also occur:

déc. 05 11:33:06 dipankar lvm[1178]:   3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé<---- busy
déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar kernel: device-mapper: table: 253:0: linear:
Device lookup failed
déc. 05 11:33:06 dipankar kernel: device-mapper: ioctl: error adding
target to table
.................

Here are all messages about lvm in the boot logs:

déc. 05 11:33:05 dipankar lvm[909]:   WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Scan found duplicate PVs.
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Not using lvmetad because
cache update failed.
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:05 dipankar lvm[909]:   1 logical volume(s) in volume
group "systeme" monitored
déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:05 dipankar lvm[909]:   1 logical volume(s) in volume
group "debian" monitored
déc. 05 11:33:05 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
-- Subject: L'unité (unit) lvm2-monitor.service a terminé son démarrage
-- L'unité (unit) lvm2-monitor.service a terminé son démarrage, avec le
résultat done.
déc. 05 11:33:06 dipankar systemd[1]: Created slice
system-lvm2\x2dpvscan.slice.
-- Subject: L'unité (unit) system-lvm2\x2dpvscan.slice a terminé son
démarrage
-- L'unité (unit) system-lvm2\x2dpvscan.slice a terminé son démarrage,
avec le résultat done.
-- Subject: L'unité (unit) lvm2-pvscan@9:127.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:127.service a commencé à démarrer.
-- Subject: L'unité (unit) lvm2-pvscan@9:4.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:4.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
-- Subject: L'unité (unit) lvm2-pvscan@9:11.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:11.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Autoactivation reading
from disk instead of lvmetad.
-- Subject: L'unité (unit) lvm2-pvscan@9:5.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:5.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1178]:   2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1182]:   2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
-- Subject: L'unité (unit) lvm2-pvscan@9:1.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:1.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:06 dipankar lvm[1222]:   2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1237]:   2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:06 dipankar lvm[1253]:   2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1178]:   1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1178]:   3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1182]:   1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1222]:   1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1237]:   1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1182]:   3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1182]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1182]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1253]:   1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1222]:   3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1222]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1222]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1237]:   3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1237]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1237]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1253]:   3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1253]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1253]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1182]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1182]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1222]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1222]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1237]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1237]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1253]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1253]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1182]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1182]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1222]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1222]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1237]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1237]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1253]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1253]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1182]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1182]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1178]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1178]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1222]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1222]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1237]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1237]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1253]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1253]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1182]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1182]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1178]:   debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1178]:   Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1178]:   1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1178]:   debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1222]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1222]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1237]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1237]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1253]:   device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1253]:   Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1182]:   debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1182]:   Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1182]:   Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1182]:   1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1182]:   debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1222]:   debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1222]:   Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1222]:   1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1222]:   debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1237]:   debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1237]:   Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1237]:   1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1237]:   debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1253]:   debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1253]:   Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1253]:   1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1253]:   debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1178]:   2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:127.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:127.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:127.service a échoué
-- L'unité (unit) lvm2-pvscan@9:127.service a échoué, avec le résultat
failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:127 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1222]:   2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:11.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:11.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:11.service a échoué
-- L'unité (unit) lvm2-pvscan@9:11.service a échoué, avec le résultat
failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:11 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1182]:   2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:4.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:4.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:4.service a échoué
-- L'unité (unit) lvm2-pvscan@9:4.service a échoué, avec le résultat failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:4 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1237]:   2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:5.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:5.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:5.service a échoué
-- L'unité (unit) lvm2-pvscan@9:5.service a échoué, avec le résultat failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:5 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1253]:   2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:1.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:1.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:1.service a échoué
-- L'unité (unit) lvm2-pvscan@9:1.service a échoué, avec le résultat failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:1 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'

All the boot log (result of journalctl -xb) can be seen here:

http://www.mi.parisdescartes.fr/~patte/journal

I hope that someone could help me.

Thank you.

[stan]

On Wed, 5 Dec 2018 13:03:19 +0100
François Patte  wrote:
> Bonjour,
>
> Yesterday I upgraded my system from f28 to f29 and the result is not
> what I expected! I can't get my "new" system working correctly: no
> graphic interface, a lot of errors in the logs....
>
> I previously upgraded this system from f25 to f27, then from f27 to
> f28 without any problems...
>
> This system uses raid 1 + lvm: here is the result of lsblk
>
> NAME                      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
> sda                         8:0    0 111,8G  0 disk
> ├─sda1                      8:1    0     1G  0 part
> │ └─md2                     9:2    0     1G  0 raid1 /boot
> ├─sda2                      8:2    0    60G  0 part
> │ └─md127                   9:127  0    60G  0 raid1
> │   └─debian-deb--racine  253:0    0  29,3G  0 lvm   /
> ├─sda3                      8:3    0     1G  0 part
> └─sda4                      8:4    0  49,8G  0 part
>   └─md11                    9:11   0  49,8G  0 raid1
>     ├─fedora-racine       253:2    0     2G  0 lvm
>     └─fedora-usr          253:3    0    28G  0 lvm
> sdb                         8:16   0 111,8G  0 disk
> ├─sdb1                      8:17   0     1G  0 part
> │ └─md2                     9:2    0     1G  0 raid1 /boot
> ├─sdb2                      8:18   0    60G  0 part
> │ └─md127                   9:127  0    60G  0 raid1
> │   └─debian-deb--racine  253:0    0  29,3G  0 lvm   /
> ├─sdb3                      8:19   0     1G  0 part
> └─sdb4                      8:20   0  49,8G  0 part
>   └─md11                    9:11   0  49,8G  0 raid1
>     ├─fedora-racine       253:2    0     2G  0 lvm
>     └─fedora-usr          253:3    0    28G  0 lvm
> sdc                         8:32   0 465,8G  0 disk
> └─sdc1                      8:33   0 465,8G  0 part
>   └─md1                     9:1    0 465,7G  0 raid1
>     ├─annexes-data        253:7    0   260G  0 lvm   /commun
>     └─annexes-sauvegardes 253:8    0   205G  0 lvm   /sauvegardes
> sdd                         8:48   0 465,8G  0 disk
> └─sdd1                      8:49   0 465,8G  0 part
>   └─md1                     9:1    0 465,7G  0 raid1
>     ├─annexes-data        253:7    0   260G  0 lvm   /commun
>     └─annexes-sauvegardes 253:8    0   205G  0 lvm   /sauvegardes
> sde                         8:64   0 931,5G  0 disk
> ├─sde1                      8:65   0    40G  0 part
> │ └─md4                     9:4    0    40G  0 raid1
> │   ├─systeme-swap        253:1    0     4G  0 lvm   [SWAP]
> │   ├─systeme-var         253:5    0    15G  0 lvm   /var
> │   └─systeme-chiffre     253:6    0    15G  0 lvm
> └─sde2                      8:66   0 891,5G  0 part
>   └─md5                     9:5    0 891,4G  0 raid1
>     └─data-home           253:4    0   500G  0 lvm   /home
> sdf                         8:80   0 931,5G  0 disk
> ├─sdf1                      8:81   0    40G  0 part
> │ └─md4                     9:4    0    40G  0 raid1
> │   ├─systeme-swap        253:1    0     4G  0 lvm   [SWAP]
> │   ├─systeme-var         253:5    0    15G  0 lvm   /var
> │   └─systeme-chiffre     253:6    0    15G  0 lvm
> └─sdf2                      8:82   0 891,5G  0 part
>   └─md5                     9:5    0 891,4G  0 raid1
>     └─data-home           253:4    0   500G  0 lvm   /home
> sr0                        11:0    1  1024M  0 rom
> sr1                        11:1    1  1024M  0 rom
>
> Don't pay attention to the names (debian or fedora) these are the
> names I gave a long time ago and I did not change the labels for some
> volumes.
>
> Now here are the errors I get in the boot logs:
>
> 1- déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> Main process exited, code=exited, status=1/FAILURE
> déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> Failed with result 'exit-code'.
> déc. 05 11:33:05 dipankar systemd[1]: Failed to start Load Kernel
> Modules. -- Subject: L'unité (unit) systemd-modules-load.service a
> échoué
>
> This error occurs several times during the boot process.
>
> 2- A lot of errors about lvm also occur:
>
> déc. 05 11:33:06 dipankar lvm[1178]:   3 logical volume(s) in volume
> group "systeme" now active
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Device mismatch
> detected for debian/deb-racine which is accessing /dev/md127 instead
> of /dev/sda2. déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper:
> reload ioctl on (253:0) failed: Périphérique ou ressource occupé<----
> busy déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend
> debian/deb-racine. déc. 05 11:33:06 dipankar kernel: device-mapper:
> table: 253:0: linear: Device lookup failed
> déc. 05 11:33:06 dipankar kernel: device-mapper: ioctl: error adding
> target to table
> .................
>
> Here are all messages about lvm in the boot logs:
>
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: found device with
> duplicate /dev/sdb2
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: found device with
> duplicate /dev/md127
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Disabling lvmetad cache
> which does not support duplicate PVs.
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Scan found duplicate
> PVs. déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Not using lvmetad
> because cache update failed.
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Not using device
> /dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Not using device
> /dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: PV
> LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2
> because of previous preference.
> déc. 05 11:33:05 dipankar lvm[909]:   1 logical volume(s) in volume
> group "systeme" monitored
> déc. 05 11:33:05 dipankar lvm[909]:   WARNING: Device mismatch
> detected for debian/deb-racine which is accessing /dev/md127 instead
> of /dev/sda2. déc. 05 11:33:05 dipankar lvm[909]:   1 logical
> volume(s) in volume group "debian" monitored
> déc. 05 11:33:05 dipankar audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd"
> hostname=? addr=? terminal=? res=success'
> -- Subject: L'unité (unit) lvm2-monitor.service a terminé son
> démarrage -- L'unité (unit) lvm2-monitor.service a terminé son
> démarrage, avec le résultat done.
> déc. 05 11:33:06 dipankar systemd[1]: Created slice
> system-lvm2\x2dpvscan.slice.
> -- Subject: L'unité (unit) system-lvm2\x2dpvscan.slice a terminé son
> démarrage
> -- L'unité (unit) system-lvm2\x2dpvscan.slice a terminé son démarrage,
> avec le résultat done.
> -- Subject: L'unité (unit) lvm2-pvscan@9:127.service a commencé à
> démarrer -- L'unité (unit) lvm2-pvscan@9:127.service a commencé à
> démarrer. -- Subject: L'unité (unit) lvm2-pvscan@9:4.service a
> commencé à démarrer -- L'unité (unit) lvm2-pvscan@9:4.service a
> commencé à démarrer. déc. 05 11:33:06 dipankar lvm[1178]:   WARNING:
> found device with duplicate /dev/sdb2
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: found device with
> duplicate /dev/md127
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Disabling lvmetad
> cache which does not support duplicate PVs.
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Scan found duplicate
> PVs. déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Not using lvmetad
> because cache update failed.
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Autoactivation reading
> from disk instead of lvmetad.
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: found device with
> duplicate /dev/sdb2
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: found device with
> duplicate /dev/md127
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Disabling lvmetad
> cache which does not support duplicate PVs.
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Scan found duplicate
> PVs. déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Not using lvmetad
> because cache update failed.
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Autoactivation reading
> from disk instead of lvmetad.
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Not using device
> /dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Not using device
> /dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: PV
> LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2
> because of previous preference.
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Not using device
> /dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Not using device
> /dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: PV
> LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2
> because of previous preference.
> -- Subject: L'unité (unit) lvm2-pvscan@9:11.service a commencé à
> démarrer -- L'unité (unit) lvm2-pvscan@9:11.service a commencé à
> démarrer. déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: found
> device with duplicate /dev/sdb2
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: found device with
> duplicate /dev/md127
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Disabling lvmetad
> cache which does not support duplicate PVs.
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Scan found duplicate
> PVs. déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Not using lvmetad
> because cache update failed.
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Autoactivation reading
> from disk instead of lvmetad.
> -- Subject: L'unité (unit) lvm2-pvscan@9:5.service a commencé à
> démarrer -- L'unité (unit) lvm2-pvscan@9:5.service a commencé à
> démarrer. déc. 05 11:33:06 dipankar lvm[1178]:   2 logical volume(s)
> in volume group "fedora" now active
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: found device with
> duplicate /dev/sdb2
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: found device with
> duplicate /dev/md127
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Disabling lvmetad
> cache which does not support duplicate PVs.
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Scan found duplicate
> PVs. déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Not using lvmetad
> because cache update failed.
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Autoactivation reading
> from disk instead of lvmetad.
> déc. 05 11:33:06 dipankar lvm[1182]:   2 logical volume(s) in volume
> group "fedora" now active
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Not using device
> /dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Not using device
> /dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: PV
> LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2
> because of previous preference.
> -- Subject: L'unité (unit) lvm2-pvscan@9:1.service a commencé à
> démarrer -- L'unité (unit) lvm2-pvscan@9:1.service a commencé à
> démarrer. déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Not using
> device /dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Not using device
> /dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: PV
> LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2
> because of previous preference.
> déc. 05 11:33:06 dipankar lvm[1222]:   2 logical volume(s) in volume
> group "fedora" now active
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: found device with
> duplicate /dev/sdb2
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: found device with
> duplicate /dev/md127
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Disabling lvmetad
> cache which does not support duplicate PVs.
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Scan found duplicate
> PVs. déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Not using lvmetad
> because cache update failed.
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Autoactivation reading
> from disk instead of lvmetad.
> déc. 05 11:33:06 dipankar lvm[1237]:   2 logical volume(s) in volume
> group "fedora" now active
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Not using device
> /dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Not using device
> /dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: PV
> LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2
> because of previous preference.
> déc. 05 11:33:06 dipankar lvm[1253]:   2 logical volume(s) in volume
> group "fedora" now active
> déc. 05 11:33:06 dipankar lvm[1178]:   1 logical volume(s) in volume
> group "data" now active
> déc. 05 11:33:06 dipankar lvm[1178]:   3 logical volume(s) in volume
> group "systeme" now active
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Device mismatch
> detected for debian/deb-racine which is accessing /dev/md127 instead
> of /dev/sda2. déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper:
> reload ioctl on (253:0) failed: Périphérique ou ressource occupé
> déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend
> debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1182]:   1 logical
> volume(s) in volume group "data" now active
> déc. 05 11:33:06 dipankar lvm[1222]:   1 logical volume(s) in volume
> group "data" now active
> déc. 05 11:33:06 dipankar lvm[1237]:   1 logical volume(s) in volume
> group "data" now active
> déc. 05 11:33:06 dipankar lvm[1182]:   3 logical volume(s) in volume
> group "systeme" now active
> déc. 05 11:33:06 dipankar lvm[1182]:   WARNING: Device mismatch
> detected for debian/deb-racine which is accessing /dev/md127 instead
> of /dev/sda2. déc. 05 11:33:06 dipankar lvm[1182]:   device-mapper:
> reload ioctl on (253:0) failed: Périphérique ou ressource occupé
> déc. 05 11:33:06 dipankar lvm[1182]:   Failed to suspend
> debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1178]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1178]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1253]:   1
> logical volume(s) in volume group "data" now active
> déc. 05 11:33:06 dipankar lvm[1222]:   3 logical volume(s) in volume
> group "systeme" now active
> déc. 05 11:33:06 dipankar lvm[1222]:   WARNING: Device mismatch
> detected for debian/deb-racine which is accessing /dev/md127 instead
> of /dev/sda2. déc. 05 11:33:06 dipankar lvm[1222]:   device-mapper:
> reload ioctl on (253:0) failed: Périphérique ou ressource occupé
> déc. 05 11:33:06 dipankar lvm[1222]:   Failed to suspend
> debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1237]:   3 logical
> volume(s) in volume group "systeme" now active
> déc. 05 11:33:06 dipankar lvm[1237]:   WARNING: Device mismatch
> detected for debian/deb-racine which is accessing /dev/md127 instead
> of /dev/sda2. déc. 05 11:33:06 dipankar lvm[1237]:   device-mapper:
> reload ioctl on (253:0) failed: Périphérique ou ressource occupé
> déc. 05 11:33:06 dipankar lvm[1237]:   Failed to suspend
> debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1253]:   3 logical
> volume(s) in volume group "systeme" now active
> déc. 05 11:33:06 dipankar lvm[1253]:   WARNING: Device mismatch
> detected for debian/deb-racine which is accessing /dev/md127 instead
> of /dev/sda2. déc. 05 11:33:06 dipankar lvm[1253]:   device-mapper:
> reload ioctl on (253:0) failed: Périphérique ou ressource occupé
> déc. 05 11:33:06 dipankar lvm[1253]:   Failed to suspend
> debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1182]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1182]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1178]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1178]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1222]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1222]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1237]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1237]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1253]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1253]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1182]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1182]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:06 dipankar lvm[1178]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:06 dipankar lvm[1178]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1222]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1222]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1237]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1237]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1253]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1253]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1182]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1182]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1178]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1178]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1222]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1222]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1237]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1237]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1253]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1253]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1182]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1182]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1178]:
> debian: refresh before autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1178]:   Cannot activate LVs in VG
> debian while PVs appear on duplicate devices.
> déc. 05 11:33:07 dipankar lvm[1178]:   1 logical volume(s) in volume
> group "debian" now active
> déc. 05 11:33:07 dipankar lvm[1178]:   debian: autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1222]:   device-mapper: reload ioctl on
> (253:0) failed: Périphérique ou ressource occupé
> déc. 05 11:33:07 dipankar lvm[1222]:   Failed to suspend
> debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1237]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1237]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1253]:
> device-mapper: reload ioctl on (253:0) failed: Périphérique ou
> ressource occupé déc. 05 11:33:07 dipankar lvm[1253]:   Failed to
> suspend debian/deb-racine. déc. 05 11:33:07 dipankar lvm[1182]:
> debian: refresh before autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1182]:   Cannot activate LVs in VG
> debian while PVs appear on duplicate devices.
> déc. 05 11:33:07 dipankar lvm[1182]:   Cannot activate LVs in VG
> debian while PVs appear on duplicate devices.
> déc. 05 11:33:07 dipankar lvm[1182]:   1 logical volume(s) in volume
> group "debian" now active
> déc. 05 11:33:07 dipankar lvm[1182]:   debian: autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1222]:   debian: refresh before
> autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1222]:   Cannot activate LVs in VG
> debian while PVs appear on duplicate devices.
> déc. 05 11:33:07 dipankar lvm[1222]:   1 logical volume(s) in volume
> group "debian" now active
> déc. 05 11:33:07 dipankar lvm[1222]:   debian: autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1237]:   debian: refresh before
> autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1237]:   Cannot activate LVs in VG
> debian while PVs appear on duplicate devices.
> déc. 05 11:33:07 dipankar lvm[1237]:   1 logical volume(s) in volume
> group "debian" now active
> déc. 05 11:33:07 dipankar lvm[1237]:   debian: autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1253]:   debian: refresh before
> autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1253]:   Cannot activate LVs in VG
> debian while PVs appear on duplicate devices.
> déc. 05 11:33:07 dipankar lvm[1253]:   1 logical volume(s) in volume
> group "debian" now active
> déc. 05 11:33:07 dipankar lvm[1253]:   debian: autoactivation failed.
> déc. 05 11:33:07 dipankar lvm[1178]:   2 logical volume(s) in volume
> group "annexes" now active
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:127.service: Main
> process exited, code=exited, status=5/NOTINSTALLED
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:127.service:
> Failed with result 'exit-code'.
> -- Subject: L'unité (unit) lvm2-pvscan@9:127.service a échoué
> -- L'unité (unit) lvm2-pvscan@9:127.service a échoué, avec le résultat
> failed.
> déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=lvm2-pvscan@9:127 comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=failed' déc. 05 11:33:07 dipankar lvm[1222]:   2 logical
> volume(s) in volume group "annexes" now active
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:11.service: Main
> process exited, code=exited, status=5/NOTINSTALLED
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:11.service: Failed
> with result 'exit-code'.
> -- Subject: L'unité (unit) lvm2-pvscan@9:11.service a échoué
> -- L'unité (unit) lvm2-pvscan@9:11.service a échoué, avec le résultat
> failed.
> déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=lvm2-pvscan@9:11 comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=failed' déc. 05 11:33:07 dipankar lvm[1182]:   2 logical
> volume(s) in volume group "annexes" now active
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:4.service: Main
> process exited, code=exited, status=5/NOTINSTALLED
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:4.service: Failed
> with result 'exit-code'.
> -- Subject: L'unité (unit) lvm2-pvscan@9:4.service a échoué
> -- L'unité (unit) lvm2-pvscan@9:4.service a échoué, avec le résultat
> failed. déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=lvm2-pvscan@9:4 comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=failed' déc. 05 11:33:07 dipankar lvm[1237]:   2 logical
> volume(s) in volume group "annexes" now active
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:5.service: Main
> process exited, code=exited, status=5/NOTINSTALLED
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:5.service: Failed
> with result 'exit-code'.
> -- Subject: L'unité (unit) lvm2-pvscan@9:5.service a échoué
> -- L'unité (unit) lvm2-pvscan@9:5.service a échoué, avec le résultat
> failed. déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=lvm2-pvscan@9:5 comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=failed' déc. 05 11:33:07 dipankar lvm[1253]:   2 logical
> volume(s) in volume group "annexes" now active
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:1.service: Main
> process exited, code=exited, status=5/NOTINSTALLED
> déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:1.service: Failed
> with result 'exit-code'.
> -- Subject: L'unité (unit) lvm2-pvscan@9:1.service a échoué
> -- L'unité (unit) lvm2-pvscan@9:1.service a échoué, avec le résultat
> failed. déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=lvm2-pvscan@9:1 comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=failed'
>
> All the boot log (result of journalctl -xb) can be seen here:
>
> http://www.mi.parisdescartes.fr/~patte/journal
>
> I hope that someone could help me.
>
> Thank you.

I just took a quick look at the journal output, and this line jumped
out at me.

dipankar kernel: Command line:
BOOT_IMAGE=/vmlinuz-4.19.5-300.fc29.x86_64
root=/dev/mapper/debian-deb--racine ro
rd.md.uuid=95c11201:1509169a:860a8b84:c49f865c
rd.lvm.lv=debian/deb-racine
rd.md.uuid=eb8b5efe:5a8f9369:e940a0f3:83d63ad1

I see debian in there.  I'm not familiar enough to say if that is a
problem or not, but it seems strange that the kernel from fedora would
be booting a debian root partition.  Or did you just reuse a debian lvm
for fedora?

The other thing is that 
/dev/mapper/debian-deb--racine
seems to be different than 
debian/deb-racine

Is there a typo?  Should they both be debian/deb-racine?

Relevant systemd errors.

-- L'unité (unit) systemd-modules-load.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1178]:   2 logical volume(s) in volume group "fedora" now active
déc. 05 11:33:06 dipankar systemd-modules-load[1238]: Failed to find module 'vboxdrv'
déc. 05 11:33:06 dipankar systemd-modules-load[1238]: Failed to find module 'vboxnetflt'
déc. 05 11:33:06 dipankar systemd-modules-load[1238]: Failed to find module 'vboxnetadp'
déc. 05 11:33:06 dipankar systemd-modules-load[1238]: Failed to find module 'vboxpci'
déc. 05 11:33:06 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
déc. 05 11:33:06 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
déc. 05 11:33:06 dipankar systemd[1]: Failed to start Load Kernel Modules.
-- Subject: L'unité (unit) systemd-modules-load.service a échoué
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[Samuel Sieb]

On 12/5/18 4:03 AM, François Patte wrote:
> 1- déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> Main process exited, code=exited, status=1/FAILURE
> déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> Failed with result 'exit-code'.
> déc. 05 11:33:05 dipankar systemd[1]: Failed to start Load Kernel Modules.
> -- Subject: L'unité (unit) systemd-modules-load.service a échoué
>
> This error occurs several times during the boot process.

You can ignore this.  I think I get these messages on all systems.
> 2- A lot of errors about lvm also occur:
>
> déc. 05 11:33:06 dipankar lvm[1178]:   3 logical volume(s) in volume
> group "systeme" now active
> déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Device mismatch detected
> for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
> déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
> (253:0) failed: Périphérique ou ressource occupé<---- busy
> déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend debian/deb-racine.
> déc. 05 11:33:06 dipankar kernel: device-mapper: table: 253:0: linear:
> Device lookup failed
> déc. 05 11:33:06 dipankar kernel: device-mapper: ioctl: error adding
> target to table

This is where the problem is.  Someone ran into a similar problem at 
work.  I think it has to do with the RAID metadata type.  lvm is 
detecting the volumes on the partition before the RAID is setup, so lvm 
tries to use the partition.  Then it finds duplicates on the other RAID 
partition and doesn't like that.

Since all your lvm volumes are only on RAID volumes, you could try 
modifying the /etc/lvm/lvm.conf file.  Find the global_filter option and 
add the following line:
global_filter = [ "r|sd|" ]

Does it work if you boot one of the F28 kernels from the boot menu?  If 
not, you will need to use an F28 (or earlier) live boot to modify the 
file.  I expect you will also need to regenerate the initramfs.  I would 
suggest using the network install image in rescue mode as that makes it 
easier to chroot and work on the installed system.  Be aware that if you 
do this, it will automatically cause an selinux relabel of the entire 
filesystem on next boot.  You can avoid this by deleting the 
/.autorelabel file, but make sure you didn't modify any file labels.

[François Patte]

Le 05/12/2018 à 20:13, stan a écrit :
> On Wed, 5 Dec 2018 13:03:19 +0100
> François Patte  wrote:
> > Bonjour,
> >
> > Yesterday I upgraded my system from f28 to f29 and the result is not
> > what I expected! I can't get my "new" system working correctly: no
> > graphic interface, a lot of errors in the logs....
> >
> > I previously upgraded this system from f25 to f27, then from f27 to
> > f28 without any problems...
> >
> > This system uses raid 1 + lvm: here is the result of lsblk
> >
> > NAME                      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
> > sda                         8:0    0 111,8G  0 disk
> > ├─sda1                      8:1    0     1G  0 part
> > │ └─md2                     9:2    0     1G  0 raid1 /boot
> > ├─sda2                      8:2    0    60G  0 part
> > │ └─md127                   9:127  0    60G  0 raid1
> > │   └─debian-deb--racine  253:0    0  29,3G  0 lvm   /
> > ├─sda3                      8:3    0     1G  0 part
> > └─sda4                      8:4    0  49,8G  0 part
> >   └─md11                    9:11   0  49,8G  0 raid1
> >     ├─fedora-racine       253:2    0     2G  0 lvm
> >     └─fedora-usr          253:3    0    28G  0 lvm
> > sdb                         8:16   0 111,8G  0 disk
> > ├─sdb1                      8:17   0     1G  0 part
> > │ └─md2                     9:2    0     1G  0 raid1 /boot
> > ├─sdb2                      8:18   0    60G  0 part
> > │ └─md127                   9:127  0    60G  0 raid1
> > │   └─debian-deb--racine  253:0    0  29,3G  0 lvm   /

<snip>
> > Don't pay attention to the names (debian or fedora) these are the
> > names I gave a long time ago and I did not change the labels for some
> > volumes.

<snip>
> dipankar kernel: Command line:
> BOOT_IMAGE=/vmlinuz-4.19.5-300.fc29.x86_64
> root=/dev/mapper/debian-deb--racine ro
> rd.md.uuid=95c11201:1509169a:860a8b84:c49f865c
> rd.lvm.lv=debian/deb-racine
> rd.md.uuid=eb8b5efe:5a8f9369:e940a0f3:83d63ad1
>
> I see debian in there.  I'm not familiar enough to say if that is a
> problem or not, but it seems strange that the kernel from fedora would
> be booting a debian root partition.  Or did you just reuse a debian lvm
> for fedora?

As I said: these are only labels for the volumes because I did not
change them when I installed fedora after a previous debian installation.

[François Patte]

Le 05/12/2018 à 21:43, Samuel Sieb a écrit :
> On 12/5/18 4:03 AM, François Patte wrote:
> > 1- déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> > Main process exited, code=exited, status=1/FAILURE
> > déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> > Failed with result 'exit-code'.
> > déc. 05 11:33:05 dipankar systemd[1]: Failed to start Load Kernel
> > Modules.
> > -- Subject: L'unité (unit) systemd-modules-load.service a échoué
> >
> > This error occurs several times during the boot process.
>
> You can ignore this.  I think I get these messages on all systems.
> > 2- A lot of errors about lvm also occur:
> >
> > déc. 05 11:33:06 dipankar lvm[1178]:   3 logical volume(s) in volume
> > group "systeme" now active
> > déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Device mismatch detected
> > for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
> > déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
> > (253:0) failed: Périphérique ou ressource occupé<---- busy
> > déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend
> > debian/deb-racine.
> > déc. 05 11:33:06 dipankar kernel: device-mapper: table: 253:0: linear:
> > Device lookup failed
> > déc. 05 11:33:06 dipankar kernel: device-mapper: ioctl: error adding
> > target to table
>
> This is where the problem is.  Someone ran into a similar problem at
> work.  I think it has to do with the RAID metadata type.  lvm is
> detecting the volumes on the partition before the RAID is setup, so lvm
> tries to use the partition.  Then it finds duplicates on the other RAID
> partition and doesn't like that.

Thank you for your answer.

I could have my system up after understanding that the main problem was
my /opt partition: I commented the line about this partition in the
fstab and the system went up (some other problems remain but I'll try to
solve later).

Here are the error messages about /opt:

<----------------
déc. 05 11:34:35 dipankar systemd[1]:
dev-mapper-debian\x2ddeb\x2d\x2dopt.device: Job
dev-mapper-debian\x2ddeb\x2d\x2dopt.device/start timed out.
déc. 05 11:34:35 dipankar systemd[1]: Timed out waiting for device
dev-mapper-debian\x2ddeb\x2d\x2dopt.device.
-- Subject: L'unité (unit) dev-mapper-debian\x2ddeb\x2d\x2dopt.device a
échoué
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[François Patte]

Le 05/12/2018 à 21:43, Samuel Sieb a écrit :
> On 12/5/18 4:03 AM, François Patte wrote:
> > 1- déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> > Main process exited, code=exited, status=1/FAILURE
> > déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
> > Failed with result 'exit-code'.
> > déc. 05 11:33:05 dipankar systemd[1]: Failed to start Load Kernel
> > Modules.
> > -- Subject: L'unité (unit) systemd-modules-load.service a échoué
> >
> > This error occurs several times during the boot process.
>
> You can ignore this.  I think I get these messages on all systems.
> > 2- A lot of errors about lvm also occur:
> >
> > déc. 05 11:33:06 dipankar lvm[1178]:   3 logical volume(s) in volume
> > group "systeme" now active
> > déc. 05 11:33:06 dipankar lvm[1178]:   WARNING: Device mismatch detected
> > for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
> > déc. 05 11:33:06 dipankar lvm[1178]:   device-mapper: reload ioctl on
> > (253:0) failed: Périphérique ou ressource occupé<---- busy
> > déc. 05 11:33:06 dipankar lvm[1178]:   Failed to suspend
> > debian/deb-racine.
> > déc. 05 11:33:06 dipankar kernel: device-mapper: table: 253:0: linear:
> > Device lookup failed
> > déc. 05 11:33:06 dipankar kernel: device-mapper: ioctl: error adding
> > target to table
>
> This is where the problem is.  Someone ran into a similar problem at
> work.  I think it has to do with the RAID metadata type.  lvm is
> detecting the volumes on the partition before the RAID is setup, so lvm
> tries to use the partition.  Then it finds duplicates on the other RAID
> partition and doesn't like that.
>
> Since all your lvm volumes are only on RAID volumes, you could try
> modifying the /etc/lvm/lvm.conf file.  Find the global_filter option and
> add the following line:
> global_filter = [ "r|sd|" ]

Magic! This is a magic filter: everything went fine --- including the
/opt partition --- after adding this line in the /etc/lvm/lvm.conf file.

I don't understand why... but my system works again.

Thank you.

[Samuel Sieb]

On 12/7/18 7:57 AM, François Patte wrote:
> Le 05/12/2018 à 21:43, Samuel Sieb a écrit :
> > Since all your lvm volumes are only on RAID volumes, you could try
> > modifying the /etc/lvm/lvm.conf file.  Find the global_filter option and
> > add the following line:
> > global_filter = [ "r|sd|" ]
>
> Magic! This is a magic filter: everything went fine --- including the
> /opt partition --- after adding this line in the /etc/lvm/lvm.conf file.
>
> I don't understand why... but my system works again.

This option tells lvm not to find any volumes on the raw hard drive 
partitions.  So it will wait until the RAID is up to find the volumes there.

[Gordon Messmer]

On 12/7/18 9:41 AM, Samuel Sieb wrote:
> This option tells lvm not to find any volumes on the raw hard drive 
> partitions.  So it will wait until the RAID is up to find the volumes 
> there.

This bug also affects RHEL and CentOS 7.6.  It's tracked here:
https://bugzilla.redhat.com/show_bug.cgi?id=1656424

The problem only affects LVM on software RAID whose metadata is 0.90 
version.  Since 0.90 can't checkpoint a recovery action, one (admittedly 
very risky) option is to replace the RAID metadata.

mdadm --stop /dev/md/md-name
mdadm --create /dev/md/md-name --run --level=1 --raid-devices=2 
--metadata=1.0 --assume-clean /dev/sdc1 /dev/sdd1

The set would get a new UUID, so you may need to adjust kernel arguments 
after doing so.  As always: make backups before doing risky things.