Bug 13151 - core175: An configured lvm volume did not start after an reboot.
Summary: core175: An configured lvm volume did not start after an reboot.
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: Will affect almost no one Major Usability
Assignee: Adolf Belka
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-14 12:42 UTC by Daniel Weismüller
Modified: 2023-07-12 09:42 UTC (History)
2 users (show)

See Also:


Attachments
the modified rules file which seems to work (3.03 KB, text/plain)
2023-06-15 11:23 UTC, Daniel Weismüller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Weismüller 2023-06-14 12:42:05 UTC
After upgrading to core175 my configured lvm volume did not start. I have to activate it manually after every reboot.

It seems that the old udev rules weren't deleted and the new once try to use systemd.
Comment 1 Michael Tremer 2023-06-14 16:36:01 UTC
@Adolf: Would you like to work with Daniel on this?

The problem seems to be as follows: The old udev rules are still present blocking the new set from being executed at all. But if the old set is being deleted, the new rules try to wrap an LVM command in systemd-run which we don't have. So that part of the command simply needs to be removed. That should fix the problem.

> https://sourceware.org/git/?p=lvm2.git;a=blob;f=udev/69-dm-lvm.rules.in;h=ff15681456403f52c9743e54901372c9fafa0e54;hb=HEAD
Comment 2 Adolf Belka 2023-06-14 19:34:16 UTC
Yes, I will pick this up. I did the last update on lvm anyway so I must have missed something so it makes sense for me to find out what I missed and fix it so I know for the future.
Comment 3 Daniel Weismüller 2023-06-15 11:22:58 UTC
(In reply to Adolf Belka from comment #2)
> Yes, I will pick this up. I did the last update on lvm anyway so I must have
> missed something so it makes sense for me to find out what I missed and fix
> it so I know for the future.

Is it helpful if I add my actual 69-dm-lvm.rules?
Comment 4 Daniel Weismüller 2023-06-15 11:23:51 UTC
Created attachment 1194 [details]
the modified rules file which seems to work
Comment 5 Adolf Belka 2023-06-15 12:03:57 UTC
Thanks very much Daniel. That helps a lot, especially as you are using it and therefore can confirm that it functions correctly correctly.

It looks like the lvm stuff has come from RedHat and they have moved to systemd and with one of the recent updates they have removed all the non systemd stuff from the udev rules.

I will take your udev rules file as the example to create with the IPFire build.

Need to also find why the old 69-dm-lvm-metad.rules file is still present. It was removed from the rootfile.

Maybe it needed to be removed from installations with the update.sh script to remove it from existing installations, like removing old library files.
Comment 6 Adolf Belka 2023-06-18 18:04:43 UTC
Patch submitted to development mailing list and patchwork

https://lists.ipfire.org/pipermail/development/2023-June/016058.html
https://patchwork.ipfire.org/project/ipfire/list/?series=3686
Comment 9 Adolf Belka 2023-07-12 09:42:13 UTC
Core Update 176 released

https://blog.ipfire.org/post/ipfire-2-27-core-update-176-released