[Solved] TrueNas Error: [Errno 30] Read-only file system

My knowledge of zfs and linux is limited but I have an issue where my volumes are mounted in a read only state. I was running out of storage so I created a replication task to copy the data onto an external 14 TiB drive. I then ended up reinstalling truenas due to other issues but I ultimately went down a raidz level to get more space. I first setup the voulume with the disks and then set the replication tasks to copy the datasets into it. That all worked, and so far all my data is intact on both volumes. Hover when I try to write data to it, I get the error in the title " Error: [Errno 30] Read-only file system".

When I run the mount command I can see that the drives are mounted as read only.

Warning: settings changed through the CLI are not written to
the configuration database and will be reset on reboot.

root@freenas[~]# mount
boot-pool/ROOT/default on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)tmpfs on /etc (tmpfs, local)
tmpfs on /mnt (tmpfs, local)
tmpfs on /var (tmpfs, local)
fdescfs on /dev/fd (fdescfs)vol1 on /mnt/vol1 (zfs, local, nfsv4acls)
vol1/ds4 on /mnt/vol1/ds4 (zfs, local, read-only, nfsv4acls)
vol1/ds2 on /mnt/vol1/ds2 (zfs, local, read-only, nfsv4acls)
vol1/ds1 on /mnt/vol1/ds1 (zfs, local, read-only, nfsv4acls)
vol2 on /mnt/vol2 (zfs, local, read-only, nfsv4acls)
vol2/ds1 on /mnt/vol2/ds1 (zfs, local, read-only, nfsv4acls)
vol2/ds4 on /mnt/vol2/ds4 (zfs, local, read-only, nfsv4acls)
vol2/iocage on /mnt/vol2/iocage (zfs, local, read-only, nfsv4acls)
vol2/ds2 on /mnt/vol2/ds2 (zfs, local, read-only, nfsv4acls)
vol2/iocage/jails on /mnt/vol2/iocage/jails (zfs, local, read-only, nfsv4acls)
vol2/iocage/releases on /mnt/vol2/iocage/releases (zfs, local, read-only, nfsv4aroot@freenas[~]# mount
boot-pool/ROOT/default on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
tmpfs on /etc (tmpfs, local)tmpfs on /mnt (tmpfs, local)
tmpfs on /var (tmpfs, local)fdescfs on /dev/fd (fdescfs)
vol1 on /mnt/vol1 (zfs, local, nfsv4acls)
vol1/ds4 on /mnt/vol1/ds4 (zfs, local, read-only, nfsv4acls)
vol1/ds2 on /mnt/vol1/ds2 (zfs, local, read-only, nfsv4acls)
vol1/ds1 on /mnt/vol1/ds1 (zfs, local, read-only, nfsv4acls)vol2 on /mnt/vol2 (zfs, local, read-only, nfsv4acls)
vol2/ds1 on /mnt/vol2/ds1 (zfs, local, read-only, nfsv4acls)vol2/ds4 on /mnt/vol2/ds4 (zfs, local, read-only, nfsv4acls)
vol2/iocage on /mnt/vol2/iocage (zfs, local, read-only, nfsv4acls)vol2/ds2 on /mnt/vol2/ds2 (zfs, local, read-only, nfsv4acls)
vol2/iocage/jails on /mnt/vol2/iocage/jails (zfs, local, read-only, nfsv4acls)
vol2/iocage/releases on /mnt/vol2/iocage/releases (zfs, local, read-only, nfsv4a
cls)
vol2/iocage/images on /mnt/vol2/iocage/images (zfs, local, read-only, nfsv4acls)
vol2/iocage/log on /mnt/vol2/iocage/log (zfs, local, read-only, nfsv4acls)
vol2/iocage/templates on /mnt/vol2/iocage/templates (zfs, local, read-only, nfsv
4acls)
vol2/iocage/download on /mnt/vol2/iocage/download (zfs, local, read-only, nfsv4acls)
vol1/.system on /var/db/system (zfs, local, nfsv4acls)
vol1/.system/cores on /var/db/system/cores (zfs, local, nfsv4acls)
vol1/.system/samba4 on /var/db/system/samba4 (zfs, local, nfsv4acls)
vol1/.system/syslog-7bdf26d378f44463a02df9c5bc4d0ea3 on /var/db/system/syslog-7bdf26d378f44463a02df9c5bc4d0ea3 (zfs, local, nfsv4acls)
vol1/.system/rrd-7bdf26d378f44463a02df9c5bc4d0ea3 on /var/db/system/rrd-7bdf26d378f44463a02df9c5bc4d0e

What I would like to know is how to remount them into a rw state. Its great that the data is safe, but not useful with it being read only.

I was able to solve this issue. After doing some more reading I was able to find a flag in the gui when you ‘edit options’ of the data set. Under advanced options there is a read-only dropdown. I changed this to ‘off’ and saved my changes. I then removed and re-created my shares. This worked and I can now write to the volumes/datasets.

3 Likes

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.