You are not logged in.
Pages: 1
Before systemd started handling local fs mounts, I used to mount my local filesystems using fstab and give local user access. My fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fcf7b1d7-a025-4842-b016-ae6f43de485b LABEL=arch
/dev/sda4 /mnt/win8 ntfs-3g defaults,noatime 0 0
/dev/sda5 / ext4 rw,relatime,data=ordered 0 1
/dev/sda10 /home ext4 defaults 0 0
/dev/sda11 /var reiserfs defaults 0 0
/dev/sda6 none swap defaults 0 0
/dev/sda7 /mnt/data exfat rw,suid,users,dev,exec,uid=user,gid=users 0 0
/dev/sda8 /mnt/media ntfs-3g rw,suid,users,dev,exec 0 0
#/dev/sda8 /mnt/media ntfs-3g rw,suid,users,dev,exec,uid=user,gid=users 0 0
/dev/sda9 /mnt/dump ntfs-3g defaults,rw,uid=user,gid=users 0 0Now with systemd intervening with the mounts, when my local fs partitions (sda7,sda8 and sda9) get mounted in ro mode since systemd ignores the options specified here.
I share this partitions with a windows installations, thus requiring manual mounting. Since fstab entrie take precedence over systemd mount units what should I specify here to pass parameters to systemd to mount these local fs in rw mode.
Also if I write mount units within /etc which would override fstab entries, where could I obtain a format for the mount unit and specifically what option must be passed for rw mode for local fs giving local users access to it.
Reards,
Offline
systemd has nothing to do with that.
If you share your partitions with windows installations, you must ensure that they are not hibernating and that fast boot on the Windows' side is disabled and that the windows side wasn't in an "updating system" condition.
Try to manually mount one of the partitions, ntfs-3g should issue a warning that the partition has been found in an inconsistent state and it opens it up in ro mode to prevent damage.
Offline
systemd has nothing to do with that.
If you share your partitions with windows installations, you must ensure that they are not hibernating and that fast boot on the Windows' side is disabled and that the windows side wasn't in an "updating system" condition.
Try to manually mount one of the partitions, ntfs-3g should issue a warning that the partition has been found in an inconsistent state and it opens it up in ro mode to prevent damage.
Thank you for the reminder.
Seems windows had updated without my knowledge and turned fast boot on. I presumed incorrectly that systemd was interfering.
Offline
Please mark as [SOLVED] by editing the thread title in your initial post.
Offline
Pages: 1