[arch-general] System doesn't load LVM volumes when booting in single user mode
Like the subject says, when I boot directly into single user mode, system doesn't load my LVM volumes. So the only way I can realistically use single user mode (since many of my key files are on LVM volumes) is to boot the system to multi-user mode, and the "telinit s" to drop back down to single user.
This seems like an error, and that systemd should be starting LVM volumes even in single user mode. Anyone have any idea what the problem might be and/or a workaround?
Thanks,
DR
Am 12.11.2012 16:28, schrieb David Rosenstrauch:
Like the subject says, when I boot directly into single user mode, system doesn't load my LVM volumes. So the only way I can realistically use single user mode (since many of my key files are on LVM volumes) is to boot the system to multi-user mode, and the "telinit s" to drop back down to single user.
This seems like an error, and that systemd should be starting LVM volumes even in single user mode. Anyone have any idea what the problem might be and/or a workaround?
Thanks,
Please test with testing/lvm2. I hope that LVM activation will only be done as it is done in this package in the future (one bug that I don't understand has been reported, but other than that it's working just fine).
On 11/12/2012 10:33 AM, Thomas Bächler wrote:
Am 12.11.2012 16:28, schrieb David Rosenstrauch:
Like the subject says, when I boot directly into single user mode, system doesn't load my LVM volumes. So the only way I can realistically use single user mode (since many of my key files are on LVM volumes) is to boot the system to multi-user mode, and the "telinit s" to drop back down to single user.
This seems like an error, and that systemd should be starting LVM volumes even in single user mode. Anyone have any idea what the problem might be and/or a workaround?
Thanks,
Please test with testing/lvm2. I hope that LVM activation will only be done as it is done in this package in the future (one bug that I don't understand has been reported, but other than that it's working just fine).
I just upgraded to the latest version (2.02.98-3) of lvm2. But I'm still having the same issue: when I boot into single user mode, my lvm volumes aren't seen and so any mounts time out.
Any idea what the problem might be or a fix/workaround?
Thanks,
DR
Am 12.02.2013 15:38, schrieb David Rosenstrauch:
I just upgraded to the latest version (2.02.98-3) of lvm2. But I'm still having the same issue: when I boot into single user mode, my lvm volumes aren't seen and so any mounts time out.
Any idea what the problem might be or a fix/workaround?
The problem in the new setup is that lvmetad.socket and dmeventd.socket are required by sockets.target, which is pulled in by basic.target, but not by sysinit.target. As rescue.target (which is activated by the 'single' option) only depends on sysinit.target, LVM will not be activated.
A solution would be to to add lvmetad.socket and dmeventd.socket to sysinit.target.wants instead of sockets.target.wants. In fact, this is probably the correct thing to do to make rescue.target work.
On 02/12/2013 10:05 AM, Thomas Bächler wrote:
Am 12.02.2013 15:38, schrieb David Rosenstrauch:
I just upgraded to the latest version (2.02.98-3) of lvm2. But I'm still having the same issue: when I boot into single user mode, my lvm volumes aren't seen and so any mounts time out.
Any idea what the problem might be or a fix/workaround?
The problem in the new setup is that lvmetad.socket and dmeventd.socket are required by sockets.target, which is pulled in by basic.target, but not by sysinit.target. As rescue.target (which is activated by the 'single' option) only depends on sysinit.target, LVM will not be activated.
A solution would be to to add lvmetad.socket and dmeventd.socket to sysinit.target.wants instead of sockets.target.wants. In fact, this is probably the correct thing to do to make rescue.target work.
Is this a change I would need to make locally, or something that's planned to get included into the next lvm2 package release?
Thanks,
DR
Am 12.02.2013 16:22, schrieb David Rosenstrauch:
On 02/12/2013 10:05 AM, Thomas Bächler wrote:
Am 12.02.2013 15:38, schrieb David Rosenstrauch:
I just upgraded to the latest version (2.02.98-3) of lvm2. But I'm still having the same issue: when I boot into single user mode, my lvm volumes aren't seen and so any mounts time out.
Any idea what the problem might be or a fix/workaround?
The problem in the new setup is that lvmetad.socket and dmeventd.socket are required by sockets.target, which is pulled in by basic.target, but not by sysinit.target. As rescue.target (which is activated by the 'single' option) only depends on sysinit.target, LVM will not be activated.
A solution would be to to add lvmetad.socket and dmeventd.socket to sysinit.target.wants instead of sockets.target.wants. In fact, this is probably the correct thing to do to make rescue.target work.
Is this a change I would need to make locally, or something that's planned to get included into the next lvm2 package release?
Well, both. First, you could test it locally. This would suffice:
mkdir -p /etc/systemd/system/sysinit.target.wants/ ln -s /usr/lib/systemd/system/{lvmetad.socket,dmeventd.socket} /etc/systemd/system/sysinit.target.wants/
(The changes you made in /etc/ above concern your machine and expand what the package does, pacman never interferes here.)
Then, we could include it in a future package, if that indeed solves the problem.
On 02/12/2013 10:29 AM, Thomas Bächler wrote:
Am 12.02.2013 16:22, schrieb David Rosenstrauch:
On 02/12/2013 10:05 AM, Thomas Bächler wrote:
Am 12.02.2013 15:38, schrieb David Rosenstrauch:
I just upgraded to the latest version (2.02.98-3) of lvm2. But I'm still having the same issue: when I boot into single user mode, my lvm volumes aren't seen and so any mounts time out.
Any idea what the problem might be or a fix/workaround?
The problem in the new setup is that lvmetad.socket and dmeventd.socket are required by sockets.target, which is pulled in by basic.target, but not by sysinit.target. As rescue.target (which is activated by the 'single' option) only depends on sysinit.target, LVM will not be activated.
A solution would be to to add lvmetad.socket and dmeventd.socket to sysinit.target.wants instead of sockets.target.wants. In fact, this is probably the correct thing to do to make rescue.target work.
Is this a change I would need to make locally, or something that's planned to get included into the next lvm2 package release?
Well, both. First, you could test it locally. This would suffice:
mkdir -p /etc/systemd/system/sysinit.target.wants/ ln -s /usr/lib/systemd/system/{lvmetad.socket,dmeventd.socket} /etc/systemd/system/sysinit.target.wants/
(The changes you made in /etc/ above concern your machine and expand what the package does, pacman never interferes here.)
Then, we could include it in a future package, if that indeed solves the problem.
OK. Will test this out (probably not until tonight) and report back.
Thanks,
DR
On 02/12/2013 10:29 AM, Thomas Bächler wrote:
Am 12.02.2013 16:22, schrieb David Rosenstrauch:
On 02/12/2013 10:05 AM, Thomas Bächler wrote:
Am 12.02.2013 15:38, schrieb David Rosenstrauch:
I just upgraded to the latest version (2.02.98-3) of lvm2. But I'm still having the same issue: when I boot into single user mode, my lvm volumes aren't seen and so any mounts time out.
Any idea what the problem might be or a fix/workaround?
A solution would be to to add lvmetad.socket and dmeventd.socket to sysinit.target.wants instead of sockets.target.wants. In fact, this is probably the correct thing to do to make rescue.target work.
Is this a change I would need to make locally, or something that's planned to get included into the next lvm2 package release?
Well, both. First, you could test it locally. This would suffice:
mkdir -p /etc/systemd/system/sysinit.target.wants/ ln -s /usr/lib/systemd/system/{lvmetad.socket,dmeventd.socket} /etc/systemd/system/sysinit.target.wants/
(The changes you made in /etc/ above concern your machine and expand what the package does, pacman never interferes here.)
Then, we could include it in a future package, if that indeed solves the problem.
Worked!!!
Thanks much for the fix!
DR
Am 13.02.2013 06:16, schrieb David Rosenstrauch:
Well, both. First, you could test it locally. This would suffice:
mkdir -p /etc/systemd/system/sysinit.target.wants/ ln -s /usr/lib/systemd/system/{lvmetad.socket,dmeventd.socket} /etc/systemd/system/sysinit.target.wants/
(The changes you made in /etc/ above concern your machine and expand what the package does, pacman never interferes here.)
Then, we could include it in a future package, if that indeed solves the problem.
Worked!!!
Thanks much for the fix!
DR
Time to fix the lvm package then.
participants (2)
-
David Rosenstrauch
-
Thomas Bächler