Data partitions mounted read only

Hi,
I am having problems with my fstab and mounting my internal disk data partitions, they are all read only
I did this after the AL installation (I was being conservative), NOT during it.

I first used gnome-disks to edit mount options of these two partitions (work and Documents)

Then I used the fstab that I saved from my (all working perfectly) previous AL instalation

Same problem

I have the following in fstab:

LABEL=Documents /run/media/leigh/Documents auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=984 0 0
LABEL=Work /run/media/leigh/Work auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=984 0 0
leigh@archlabs ~ % whoami
leigh
leigh@archlabs ~ % id leigh
uid=1000(leigh) gid=984(users) groups=984(users),19(log),998(wheel),985(video),982(rfkill)

Any ideas?
should I put a rw option in? But I dont understand why this wasnt needed in my previous installation

leigh@archlabs ~ % mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=5833424k,nr_inodes=1458356,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/sdb2 on / type ext4 (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=300)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
none on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576,inode64)
/dev/sdb3 on /run/media/leigh/Work type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,x-gvfs-show)
/dev/sda6 on /run/media/leigh/Documents type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,x-gvfs-show)
/dev/sdb1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1168848k,nr_inodes=292212,mode=700,uid=1000,gid=984,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=984)

@leigh

If it helps you this is my installation of AL yesterday and I’ll pass you my /etc/fstab:

3 Likes

Thanks @judd
but that bit of my fstab is working fine - its the extra lines to mount my separate data partitions that is the problem

I tried putting a ,rw in but it messed up my boot and didn’t work anyway

1 Like

Was that at exaclty the way @judd did above @leigh

1 Like

This is my full fstab:

leigh@archlabs ~ % cat  /etc/fstab
# /dev/sdb2
UUID=e39d8e26-bfbc-4b98-82aa-b9f517273ad2	/         	ext4      	rw,relatime	0 1

# /dev/sdb1
UUID=CC47-FF0C      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/sda5
UUID=d06f9174-8e6f-46d0-a610-295cc5bd817a	none      	swap      	defaults  	0 0

LABEL=Documents /run/media/leigh/Documents auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=984 0 0
LABEL=Work /run/media/leigh/Work auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=984 0 0

You can also try to set just defaults and see if that works…

2 Likes

These are data partitions are ntfs formatted?

1 Like

Might need to change ownership. Partitions created as root?

1 Like

DOH!
Yes they are …
EDIT but shouldnt auto deal with this?

could be, I made them using the EOS live USB
then copied the data over from a backup in Windows

Oh, I see why @leigh ; here s what you did

rw , relatime

It should be that way instead at every added rw that you did add to your fstab edits;

rw, relatime

Basically rw COMMA Space relatime

2 Likes

You can also work graphically with the gnome-disk-utility

1 Like

thats the way I did it originally - I am lazy :smiley:

1 Like

not sure about this, no spaces there, and you are looking at sdb1 and sdb2 I think - I havent showed where I did it for Work and Documents partitions

Maybe not.

Take a look at @sammiev last post in this thread. Using ntfs3 (need to be running kernel 5.15 or higher). Change the uid and gid for your system.

3 Likes

Yep, only on those 2 first partitions , namely sdb2 & sdb1 as you stated above.

The comma needs to be exactly after rw then space & relatime , the way I posted it above, just try copy & paste from my post above & check what it will do.

rw, relatime

2 Likes

Cheers @altman
This didnt work for Work and Documents partitions, nor putting rw at end
And it gave me doot errors

# /dev/sdb2
UUID=e39d8e26-bfbc-4b98-82aa-b9f517273ad2       /               ext4           >

# /dev/sdb1
UUID=CC47-FF0C          /boot           vfat            rw,relatime,fmask=0022,>

# /dev/sda5
UUID=d06f9174-8e6f-46d0-a610-295cc5bd817a       none            swap           >

LABEL=Documents /run/media/leigh/Documents auto rw,nosuid,nodev,nofail,x-gvfs-s>
LABEL=Work /run/media/leigh/Work auto rw,nosuid,nodev,nofail,x-gvfs-show,uid=10>

ntfs and vfat don’t have the permissions rules like Linux file systems.

Edit - although copying the files back and forth can change ownership of the actual files. Always something to check.

3 Likes

Good tip and often effective.

3 Likes

True.

But I meant to change it over so he isn’t using @sammiev uid and gid - thinking more along the lines of a cut-and-paste error.

3 Likes