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 -- -- L'unité (unit) dev-mapper-debian\x2ddeb\x2d\x2dopt.device a échoué, avec le résultat timeout. déc. 05 11:34:35 dipankar systemd[1]: Dependency failed for File System Check on /dev/mapper/debian-deb--opt. -- Subject: L'unité (unit) systemd-fsck@dev-mapper-debian\x2ddeb\x2d\x2dopt.service a échoué -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- L'unité (unit) systemd-fsck@dev-mapper-debian\x2ddeb\x2d\x2dopt.service a échoué, avec le résultat dependency. déc. 05 11:34:35 dipankar systemd[1]: Dependency failed for /opt. -- Subject: L'unité (unit) opt.mount a échoué -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- L'unité (unit) opt.mount a échoué, avec le résultat dependency. déc. 05 11:34:35 dipankar systemd[1]: Dependency failed for Local File Systems. -- Subject: L'unité (unit) local-fs.target a échoué -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- L'unité (unit) local-fs.target a échoué, avec le résultat dependency. déc. 05 11:34:35 dipankar systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. déc. 05 11:34:35 dipankar systemd[1]: local-fs.target: Triggering OnFailure= dependencies. déc. 05 11:34:35 dipankar systemd[1]: opt.mount: Job opt.mount/start failed with result 'dependency'. déc. 05 11:34:35 dipankar systemd[1]: systemd-fsck@dev-mapper-debian\x2ddeb\x2d\x2dopt.service: Job systemd-fsck@dev-mapper-debian\x2ddeb\x2d\x2dopt.service/start failed with result 'dependency'. 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 failed with result 'timeout'. <------------------------------------ strangely, I can't see the /dev/mapper/debian-deb--opt which does exist, as I can see using lvscan: # lvscan WARNING: found device with duplicate /dev/sdb2 WARNING: found device with duplicate /dev/md127 WARNING: Disabling lvmetad cache which does not support duplicate PVs. WARNING: Scan found duplicate PVs. WARNING: Not using lvmetad because cache update failed. WARNING: Not using device /dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG. WARNING: Not using device /dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG. WARNING: PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because of previous preference. WARNING: PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because of previous preference. ACTIVE '/dev/fedora/racine' [2,00 GiB] inherit ACTIVE '/dev/fedora/usr' [28,00 GiB] inherit ACTIVE '/dev/data/home' [500,00 GiB] inherit ACTIVE '/dev/systeme/swap' [4,00 GiB] inherit ACTIVE '/dev/systeme/var' [15,00 GiB] inherit ACTIVE '/dev/systeme/chiffre' [15,00 GiB] inherit WARNING: Device mismatch detected for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2. ACTIVE '/dev/debian/deb-racine' [29,33 GiB] inherit inactive '/dev/debian/deb-opt' [<30,67 GiB] inherit ACTIVE '/dev/annexes/data' [260,00 GiB] inherit ACTIVE '/dev/annexes/sauvegardes' [205,00 GiB] inherit BTW I don't know what to do with these warnings.... > > 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|" ] I will try this. Thank you. -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)6 7892 5822 http://www.math-info.univ-paris5.fr/~patte
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
