View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001274 | channel: kernel/el9 | kernel-ml | public | 2022-10-04 07:08 | 2023-07-02 15:27 |
| Reporter | JoshuaPK | Assigned To | burakkucat | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | x86_64 | OS | AlmaLinux | OS Version | 9 |
| Summary | 0001274: kernel-ml package may require config change of lvm.conf | ||||
| Description | This is an informational bug only since I determined how to fix this. Installing kernel-ml on my main laptop (AlmaLinux 9) this morning. Went to reboot it and the boot failed; the LVM device for my /home directory could not be found. When I ran pvscan and lvcan, the specific error was: Devices file sys_wwid eml.xxxxxxxxxxxxxxxxx PVID xxxxxxxxxxxxxxxxxxxxx no matching physical volume found. Rebooting back into the previous kernel (normal EL9 5.14 kernel) worked fine. I verified that the devices file under /etc/lvm/devices did, in fact, have the correct GUID. I then queried Google and found the article linked below. There is a setting in /etc/lvm/lvm.conf called use_devicesfile; if you set this to 0 (or just uncomment the commented line with the same setting) then this problem goes away. I verified that solution worked. | ||||
| Steps To Reproduce | On an AlmaLinux 9 system that uses LVM for at least one of its mounts do the following: 1. Install kernel-ml (at this time it is 6.0.0-1) 2. Reboot 3. Observe that the system drops to an emergency login prompt 4. Login using the root password 5. Run 'pvscan' 6. Observe that pvscan reports an error similar to what is noted above. | ||||
| Additional Information | I have two logical volumes, one mounted under /home and one mounted under /root. The volume mounted under /root did not have this problem, but the /root LV did not have a corresponding PV in the 'devices' file. | ||||
| Tags | No tags attached. | ||||
|
|
Thank you for the report, and your workaround. From reading the lvmdevices manpage, I guess the other solution would have been to add the missing device with lvmdevices --adddev if you did want to use the devices file. Just wondering / trying to understand why you would see this issue with kernel-ml, but not with your distro kernel. |
|
|
When I have some time later tonight (I'm in EDT timezone) I can look at this and see if there is additional configuration that might need to be done when installing or updating kernel-ml. Here is the StackOverflow question: https://serverfault.com/questions/1093110/linux-lvm-pvid-last-seen-on |
|
|
Closing due to inactivity. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-10-04 07:08 | JoshuaPK | New Issue | |
| 2022-10-04 07:42 | pperry | Assigned To | => burakkucat |
| 2022-10-04 07:42 | pperry | Status | new => assigned |
| 2022-10-04 08:12 | pperry | Note Added: 0008682 | |
| 2022-10-04 09:09 | JoshuaPK | Note Added: 0008683 | |
| 2023-07-02 15:27 | toracat | Status | assigned => closed |
| 2023-07-02 15:27 | toracat | Resolution | open => no change required |
| 2023-07-02 15:27 | toracat | Note Added: 0009252 |
