You are not logged in.
Hey all,
Let me preface all of this by noting that my drives are set up with LVM on LUKS. About half a year ago, I had a hard drive fail in my desktop - it would work intermittently, but most of the time it was dead.
That drive was part of one of my LVM VGs, and for the longest time I couldn't get that VG and any of its LVs to mount. At one point I managed to get it to mount with the failing drive working at the time, so I quickly moved any extents off of that PV, removed it from the VG, and unplugged it for good. Now, I see different behaviors depending on my system configuration.
1. The failed drive is unplugged, but It still has an entry in /etc/crypttab.initramfs. In this case, during boot, systemd waits for 1m30s for the drive to become available. The job eventually fails, but the VG the drive was formerly a member of activates just fine.
2. The failed drive is unplugged, and I remove (comment out) its entry in /etc/crypttab.initramfs. Now there is no job hanging during boot, but the VG the drive was formerly a member of does not activate - I can manually activate and mount the VG, but it does not happen automatically on boot.
3. The failed drive is plugged in, and I keep its entry in /etc/crypttab.initramfs. The boot process does not wait during cryptsetup, and only sometimes needs to wait for LVM VGs, but the VG the drive was formerly a member of does not activate. I have not tried manual activation.
I'm stumped here. I've tried following the advice here but I just get "Volume group "[My VG name]" is already consistent", suggesting that all should be fine.
TL;DR With LVM on LUKS, had an LVM PV fail. Removed it from the VG, but now I have to either wait for its cryptsetup job to fail on boot (VG activates) or remove it from crypttab and manually activate/mount its former VG.
Offline