- Le plus récent
- Le plus de votes
- La plupart des commentaires
Is the problem that any LVM commands like pvdisplay
or vgs
etc. always come back with an error of the form Devices file sys_wwid nvme.1d0f-[big_long_random_string] PVID [shorter_random_string] last seen on /dev/sdb not found.
? I hope it is, because that's the behaviour I've managed to replicate :-)
Not sure whether to call this a fix, or a workaround, or a hack, but anyway what you need to do ensure use_devicesfile = 0 is present in /etc/lvm/lvm.conf on the instance from which the AMI is created, and then create a fresh AMI with this entry in place.
sed -i 's/# use_devicesfile = 0/use_devicesfile = 0/' /etc/lvm/lvm.conf
See comment #8 of https://bugzilla.redhat.com/show_bug.cgi?id=2072201
I tested with an entry in /etc/fstab for an filesystem on an LVM volume, and it mounts the first time a new EC2 is booted from the AMI, with no manual intervention required.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
^^^ this is pure gold. I had multiple lvm modules in my fstab and that was fine on the instance I made them on. When I made an AMI from that instance, the new ec2 would not stand up and this was the fix for that. many thanks