| View previous topic :: View next topic |
| Author |
Message |
mr-simon
Guru
Joined: 22 Nov 2002
Posts: 367
Location: Leamington Spa, Warks, UK
|
 Posted: Thu Jan 22, 2015 3:23 pm Post subject: [solved] systemd and I are fighting over a mount point |
 |
|
I have two partitions on a fakeraid device that I want to mount on my system. My root partition is on an SSD, but the fakeraid contains a large volume on magnetic disks, containing an ntfs partition and an ext4 partition.
I have the following entries at the end of my fstab:
| Code: | /dev/mapper/isw_dgjjicdjij_SSTOR1 /home/simon/sstor ntfs uid=1000,gid=1000,dmask=027,fmask=137,noauto 0 2
/dev/mapper/isw_dgjjicdjij_SSTOR2 /home/simon/spinny ext4 noatime,noauto 0 2
|
NOTE: This problem still occurs if I attempt to mount by UUID. Either way, the device nodes are there, and always the same.
So, the problem is that when I mount one of the above entries, systemd goes ahead and unmounts it again immediately (it /very/ briefly appears in Nautilus's sidebar, and then disappears again)
| Code: |
stargazer ~ # mount /home/simon/spinny
stargazer ~ # tail -n 1 /var/log/messages
Jan 22 15:07:24 stargazer kernel: EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
stargazer ~ # journalctl -n 5
Jan 22 15:07:18 stargazer.cubbington.eu.widgit.com su[9066]: + /dev/pts/0 root:root
Jan 22 15:07:18 stargazer.cubbington.eu.widgit.com su[9066]: pam_unix(su:session): session opened for user root by simon
Jan 22 15:07:24 stargazer.cubbington.eu.widgit.com gnome-session[5196]: libmediaart-Message: Mount:'spinny' with UUID:'9aed12cbee36b384afe4ca92714d75ae' now unmounted from:'/home/simon/spinny'
Jan 22 15:07:24 stargazer.cubbington.eu.widgit.com kernel: EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jan 22 15:07:24 stargazer.cubbington.eu.widgit.com systemd[1]: Unit home-simon-spinny.mount entered failed state.
|
Systemd can tell me a few things about the failed device...
| Code: |
stargazer ~ # systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● home-simon-spinny.mount loaded failed failed /home/simon/spinny
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
|
| Code: |
stargazer ~ # systemctl show home-simon-spinny.mount
Where=/home/simon/spinny
What=/dev/mapper/isw_dgjjicdjij_SSTOR2
Options=noatime,noauto
Type=ext4
TimeoutUSec=1min 30s
ControlPID=0
DirectoryMode=0755
SloppyOptions=no
Result=exit-code
ExecUnmount={ path=/bin/umount ; argv[]=/bin/umount -n /home/simon/spinny ; ignore_errors=no ; start_time=[Thu 2015-01-22 15:07:24 GMT] ; stop_time=[Thu 2015-01-22 15:07:24 GMT] ; pid=9076 ; code=exited ; status=0 }
Slice=system.slice
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=(null)
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
UMask=0022
LimitCPU=18446744073709551615
|
It definitely does mount successfully, albeit temporarily:
| Code: | stargazer ~ # mount -v /home/simon/spinny && ls /home/simon/spinny
mount: /dev/mapper/isw_dgjjicdjij_SSTOR2 mounted on /home/simon/spinny.
home.tar.gz lost+found vmware
stargazer ~ # ls /home/simon/spinny
stargazer ~ #
|
If I don't set noauto on the entries the system dies during boot and I'm given a rescue shell, where the same problem I'm describing here occurs.
I'm new to systemd, and I've run out of things to google about this. Any ideas? I can't seem to find any log about what actually failed.
_________________
"Pokey, are you drunk on love?"
"Yes. Also whiskey. But mostly love... and whiskey."
Last edited by mr-simon on Thu Jan 22, 2015 4:11 pm; edited 1 time in total |
|
| Back to top |
|
 |
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Thu Jan 22, 2015 3:59 pm Post subject: |
|
|
systemd mounting is a mess.
Perhaps it helps to switch it off for your device by disabling the mount point: | Code: | ln -s /dev/null /etc/systemd/system/home-simon-astor.mount
ln -s /dev/null /etc/systemd/system/home-simon-spinny.mount |
|
|
| Back to top |
|
|
mr-simon
Guru
Joined: 22 Nov 2002
Posts: 367
Location: Leamington Spa, Warks, UK
|
| Posted: Thu Jan 22, 2015 4:04 pm Post subject: |
|
|
| mv wrote: | systemd mounting is a mess.
Perhaps it helps to switch it off for your device by disabling the mount point: |
Edit: The information below is nonsense. A reboot fixed it, after your recommended change.
Many thanks for your help. 
| Quote: |
Alas, that didn't help. 
| Code: | simon@stargazer:16:01:57 ruby-2.2.0 [~]
-> ls -l /etc/systemd/system/home-simon-spinny.mount
lrwxrwxrwx 1 root root 9 Jan 22 16:01 /etc/systemd/system/home-simon-spinny.mount -> /dev/null
simon@stargazer:16:02:30 ruby-2.2.0 [~]
-> sudo mount -v /home/simon/spinny && ls /home/simon/spinny
mount: /dev/mapper/isw_dgjjicdjij_SSTOR2 mounted on /home/simon/spinny.
home.tar.gz lost+found vmware
simon@stargazer:16:02:37 ruby-2.2.0 [~]
-> ls /home/simon/spinny
simon@stargazer:16:02:46 ruby-2.2.0 [~]
->
|
|
_________________
"Pokey, are you drunk on love?"
"Yes. Also whiskey. But mostly love... and whiskey." |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Sat Feb 21, 2015 7:44 am Post subject: |
|
|
With systemd-219, they boycotted the workaround.
Only solution: Dump systemd, switch to a sane init system which does not have the intention to spoon-feed the user.
Edit: I now found the topic where I asked concerning this problem for the first time: You might want to continue discussion in that topic. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
