On Tue, May 08, 2018 at 12:04:58PM -0700, Samuel Sieb wrote: > On 05/03/2018 06:35 PM, Jim Simmons wrote: > >In journalctl, I see this and I think it is the problem: > > > > WARNING: PV W0e1Cx-ByMA-iRX6-OGxr-KfWC-zaUP-YXWgW5 on /dev/sdb8 was > > already found on sda8. > > WARNING: PV W0e1Cx-ByMA-iRX6-OGxr-KfWC-zaUP-YXWgW5 on /dev/md127 was > > already found on sda8. > > WARNING: PV W0e1Cx-ByMA-iRX6-OGxr-KfWC-zaUP-YXWgW5 prefers device > > /dev/sda8 because device was seen first. > > WARNING: PV W0e1Cx-ByMA-iRX6-OGxr-KfWC-zaUP-YXWgW5 prefers device > > /dev/md127 because device size is correct. > > Yes, this is the problem. Someone was having a very similar problem > at work recently with multipath. The problem is that LVM is > checking for volumes before raid has finished checking. The raid > device is getting created, but it's too late, LVM has already found > the PV on the raw disk. I think if the raid version was different, > LVM wouldn't be able to see the PV, but it would be difficult to > change that now. If you only have LVM volumes on the raid, then add > the following line to your /etc/lvm/lvm.conf in the devices section: > filter = [ "r/sd.*/" ] > > Then you will need to regenerate the initramfs by running: > dracut -f --kver kernel-version > "kernel-version" is the full name of the kernel. e.g. The latest > kernel package I have installed is "kernel-4.15.7-300.fc27.x86_64", > so I would run: > dracut -f --kver 4.15.7-300.fc27.x86_64 > You can remove the dracut-config-generic package to go back to > smaller files if you want. I tried multiple settings for filter - just enable /dev/md.* and disable everything else and others. Nothing helped. I also experimented with various lvm commands from the emergency shell - passing the filter and/or global_filter options on the command line - nothing helped. I could boot from the Fedora 28 i386 xfce live image, though, and it saw raid volumes and volume group without problems. In checking things, this system was originally installed with Red Hat 7.3 in 2012 and the md device was created then. It had 0.90 version metadata. I forced it to 1.0 using the live image but that didn't work, either. I used the F28 live image to install to disk again, telling it to reformat /, /boot, etc. It installed ok but still wouldn't boot - same exact symptoms. Finally I backed /home and the other filesystems in the volume group, went into the live cd and manually deleted the volume group and both md mirrors, then recreated them by hand, rebooted the live image and did another install to disk. This time it worked and it has been happy since. I still don't know what the issue was but hopefully this info may be useful for someone else if they happen to have a 16 year old system they're trying to keep running :-) I'm guessing it was related to the age of the mirror - I have several other systems (64-bit, though) using a similar configuration and they upgraded and run fine. Thanks, Jim _______________________________________________ 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/message/GCMW4KO5RET6TVUQGKWKD7QVC4IEFLVK/
