[arch-general] systemd
First of all I 'm new user of these distribution list and I do not know if this is the correct place to post my problem and ask for help. If not my apology and please refer me to to the correct place. I' m using Arch now for several years on a desktop and a laptob without severe problems. Few days ago I changed to systemd both on the laptop and desktop. For the laptop all went fine and I' m able to boot using systemd and the system is up and running as before. The only difference between laptop and desktop is that the /home partition on the desktop is on a SW raid My problem: When booting with init=/bin/systemd I have the following phenomenon: Job dev-mapper-nvidia_cjjcaiiep1.device/start timed out and booting stops and I'm in a rescue shell. my /home partition is not mounted. /dev/mapper/nvidia_cjjcaiiep1 exists. Systemctl start dev-mapper-nvidia_cjjcaiiep1.device gives the same result timeout. and my /home is not mounted When I do a manual mount of the /home partition mount /dev/mapper/nvidia_cjjcaiiep1 /home /home is mounted Systemctl default my system resumes booting and finally comes online. I 'm new to systemd so if someone can be so kind to give me some hints how / where to start searching for the problem or maybe the problem is already known ... Thanks in advance. Fred
On Wed, Aug 15, 2012 at 01:50:01PM +0200, Fred Verschueren wrote:
My problem: When booting with init=/bin/systemd I have the following phenomenon:
Job dev-mapper-nvidia_cjjcaiiep1.device/start timed out and booting stops and I'm in a rescue shell. my /home partition is not mounted.
/dev/mapper/nvidia_cjjcaiiep1 exists.
Systemctl start dev-mapper-nvidia_cjjcaiiep1.device gives the same result timeout.
and my /home is not mounted
When I do a manual mount of the /home partition mount /dev/mapper/nvidia_cjjcaiiep1 /home /home is mounted
Systemctl default
my system resumes booting and finally comes online.
I have the exact same problem with systemd-188-2, downgrading back to systemd-187-4 makes it work again.
On Wed, Aug 15, 2012 at 11:12 AM, Mikael Eriksson <mikael_eriksson@miffe.org> wrote:
On Wed, Aug 15, 2012 at 01:50:01PM +0200, Fred Verschueren wrote:
My problem: When booting with init=/bin/systemd I have the following phenomenon:
Job dev-mapper-nvidia_cjjcaiiep1.device/start timed out and booting stops and I'm in a rescue shell. my /home partition is not mounted.
/dev/mapper/nvidia_cjjcaiiep1 exists.
Systemctl start dev-mapper-nvidia_cjjcaiiep1.device gives the same result timeout.
and my /home is not mounted
When I do a manual mount of the /home partition mount /dev/mapper/nvidia_cjjcaiiep1 /home /home is mounted
Systemctl default
my system resumes booting and finally comes online.
I have the exact same problem with systemd-188-2, downgrading back to systemd-187-4 makes it work again.
Be sure to report a bug in Arch's flyspray. Lots of developers don't read arch-general anymore (we should all thank the polite conversations of last days...) -- A: Because it obfuscates the reading. Q: Why is top posting so bad? For more information, please read: http://idallen.com/topposting.html ------------------------------------------- Denis A. Altoe Falqueto Linux user #524555 -------------------------------------------
Op 15-08-12 18:49, Denis A. Altoé Falqueto schreef:
On Wed, Aug 15, 2012 at 11:12 AM, Mikael Eriksson <mikael_eriksson@miffe.org> wrote:
On Wed, Aug 15, 2012 at 01:50:01PM +0200, Fred Verschueren wrote:
My problem: When booting with init=/bin/systemd I have the following phenomenon:
Job dev-mapper-nvidia_cjjcaiiep1.device/start timed out and booting stops and I'm in a rescue shell. my /home partition is not mounted.
/dev/mapper/nvidia_cjjcaiiep1 exists.
Systemctl start dev-mapper-nvidia_cjjcaiiep1.device gives the same result timeout.
and my /home is not mounted
When I do a manual mount of the /home partition mount /dev/mapper/nvidia_cjjcaiiep1 /home /home is mounted
Systemctl default
my system resumes booting and finally comes online. I have the exact same problem with systemd-188-2, downgrading back to systemd-187-4 makes it work again. Be sure to report a bug in Arch's flyspray. Lots of developers don't read arch-general anymore (we should all thank the polite conversations of last days...)
I downgraded to systemd-187-4 but have still the same problem. Any hints where to start searching? Fred
On 08/16/12 08:59, Fred Verschueren wrote:
Op 15-08-12 18:49, Denis A. Altoé Falqueto schreef:
On Wed, Aug 15, 2012 at 11:12 AM, Mikael Eriksson <mikael_eriksson@miffe.org> wrote:
On Wed, Aug 15, 2012 at 01:50:01PM +0200, Fred Verschueren wrote:
My problem: When booting with init=/bin/systemd I have the following phenomenon:
Job dev-mapper-nvidia_cjjcaiiep1.device/start timed out and booting stops and I'm in a rescue shell. my /home partition is not mounted.
/dev/mapper/nvidia_cjjcaiiep1 exists.
Systemctl start dev-mapper-nvidia_cjjcaiiep1.device gives the same result timeout.
and my /home is not mounted
When I do a manual mount of the /home partition mount /dev/mapper/nvidia_cjjcaiiep1 /home /home is mounted
Systemctl default
my system resumes booting and finally comes online. I have the exact same problem with systemd-188-2, downgrading back to systemd-187-4 makes it work again. Be sure to report a bug in Arch's flyspray. Lots of developers don't read arch-general anymore (we should all thank the polite conversations of last days...)
I downgraded to systemd-187-4 but have still the same problem.
Any hints where to start searching? Fred
I found a work around: if I replace in fstab /dev/mapper/nvidia_cjjcaiiep1 /home ext3 defaults,acl 0 1 by /dev/dm-7 /home ext3 defaults,acl 0 1 the system is booting without problem. Kind regards, Fred
Am 17.08.2012 17:28, schrieb Fred Verschueren:
I downgraded to systemd-187-4 but have still the same problem.
Any hints where to start searching? Fred
I found a work around:
if I replace in fstab /dev/mapper/nvidia_cjjcaiiep1 /home ext3 defaults,acl 0 1 by /dev/dm-7 /home ext3 defaults,acl 0 1
the system is booting without problem.
This is extremely dangerous! The name "dm-7" is not persistent at all, it may change at will. What you describe here suggests a problem with the device-mapper and its udev interaction. Udev is supposed to create the symlink /dev/mapper/nvidia_cjjcaiiep1 -> ../dm-7, but it doesn't do so, or doesn't do so in time. This problem lies somewhere in the device mapper library, or in the way the dmraid tool uses it. To be more precise: When activating dmraid, the tool is supposed to wait until udev successfully created the missing symlink. So either dmraid is not configured to do that, or systemd doesn't wait until dmraid finishes, or systemd doesn't know to call dmraid at all. I don't understand enough about systemd to fix this right now, sorry. I am forwarding this to Tom and Dave, who probably don't follow arch-general anymore, but can surely shed some light on the situation.
participants (4)
-
Denis A. Altoé Falqueto
-
Fred Verschueren
-
Mikael Eriksson
-
Thomas Bächler