You are not logged in.
Hello,
Since the update of systemd-tools, the "comment=systemd.automount, or x-systemd.automount" in fstab no longer works. During boot it just says "systemd failed to initialize automounter, no such file or directory". Removing the automount comment mounts all partitions properly.
(Not sure if autofs is needed, never needed it before)
community/autofs 5.0.6-3
core/libsystemd 184-2
core/systemd 184-2
community/systemd-arch-units 20120528-3
core/systemd-tools 184-2
kernel 3.3.7-1-ck.
I'm going to check if the same error occurs with stock kernel.
Edit: Found the error, apparently ONE partition didn't like being automounted, I'll look into that. Bottom line is, there's no problem with the latest update!
Last edited by Glaucous (2012-06-02 09:35:28)
Offline
Something has changed with systemd automounting - my cifs share that automounted faithfully for months will no longer do so. It mounts manually with no problem.
UPDATE: Here's the error I am getting in my system log
mount.cifs: bad UNC (/192.168.1.1/USB_Storage)Last edited by Da_Coynul (2012-06-03 16:02:57)
Offline
Something has changed with systemd automounting - my cifs share that automounted faithfully for months will no longer do so. It mounts manually with no problem.
UPDATE: Here's the error I am getting in my system log
mount.cifs: bad UNC (/192.168.1.1/USB_Storage)
yes, I also noticed this. The problem is that systemd cuts of the first slash when parsing the fstab.
falconindy posted a patch upstream which should fix this. I guess this should make it into the next systemd version.
http://lists.freedesktop.org/archives/s … 05343.html
Offline
yes, I also noticed this. The problem is that systemd cuts of the first slash when parsing the fstab.
falconindy posted a patch upstream which should fix this. I guess this should make it into the next systemd version.
http://lists.freedesktop.org/archives/s … 05343.html
Thanks, 65kid. Funny thing is I noticed the missing slash in the error message and even tried adding an extra one in my fstab but that didn't seem to do anything.
Offline
65kid wrote:yes, I also noticed this. The problem is that systemd cuts of the first slash when parsing the fstab.
falconindy posted a patch upstream which should fix this. I guess this should make it into the next systemd version.
http://lists.freedesktop.org/archives/s … 05343.htmlThanks, 65kid. Funny thing is I noticed the missing slash in the error message and even tried adding an extra one in my fstab but that didn't seem to do anything.
It's persistent enough to strip off any number of "extra" slashes, apparently. You should be able to work around this bug by making an "actual" unit in /etc/systemd/system for the affected mount, which will be used instead of what it thinks it sees in fstab. Look in /run/systemd/generators/ to see what it came up with automatically and use that as a starting point.
Offline