-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get Volume group to activate at boot #172
Comments
You can possibly try to enable debuging and syslogging all debug output to your journal - and examine why the auto activation was possibly rejected or non-functional. See lvm.conf log { syslog=1 level 7 } |
Look at journalctrl for lvm-related messages: some from pvscan when each PV appears ("PV /dev/foo online"), and some related to the VG after all PVs have appeared, e.g. a service named lvm-activate- should appear in the logs. |
I did some more tests in fedora 40, updating lvm2 past 2.03.23-1.fc40 causes my system to ;no longer mount /home, blacklisting lvm2 at least lets me use it again, i'll reach out to fedora, hopefully we can fix it |
Are you using 'devicesfile' ? - or lvm.conf filter to select 'visible' devices as PVs ? |
I have a Volumegroup that I can't get activated at boot (on fedora 41), I can however activate it with lvchange -a y all_storage Unsure how to further resolve this, any pointers are appresiated (I have a backup but I'd rather understand the issue prior to rebuilding the raid
The text was updated successfully, but these errors were encountered: