Disable lvmetad (in systemctl and by editing lvm.conf to not use metad). I have had lvmetad cause disks to not get detected on boot up on several reboots. Restarting it will fix it sometimes and then doing a vgchange -ay afterwards enabled the lvs. It is easiest to just disable it as I believe I have seen notes indicating lvmetad is being moved away from. On Wed, Jan 2, 2019 at 4:11 AM Giuseppe Vacanti <giuseppe@xxxxxxxxxxx> wrote: > > Hello, > > I have found a solution to the problem, however the problem seems to come back after every reboot. > > I have been put on the good path by the remarks made on this list by John and Gionatan. > > The fix is the following: > > - convince myself that the device has the correct uuid, I used blkid and compared the result with the information in the lvm backup > - run pvck -t on /dev/sdc. Nothing special, all seems OK > - run vgscan --cache. This command brings back knowledge of the VG the PV belongs to > - now pvs lists my PV again, but the LV is inactive > - I activate the LV with lvchange > - all is back, I can mount and use the LV > > After a reboot however the information about the VG is gone again, and I have to repeat the steps above to be able to use the LV. > > I have a running system, but I don't know what is happening. Where can I look to figure this out? > > Regards, Giuseppe > > -- > Giuseppe Vacanti > > > _______________________________________________ > linux-lvm mailing list > linux-lvm@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
