NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Read-only
3 Topics
Shares goes read-only after a while after upgrade to 6.8.0
Hi, After upgrading to 6.8.0 I have a strange behavior. After every boot, everything is fine for some time (up to half an hour) and then file system goes read only. After boot: root@NasSebUltra6:/# mount | grep -v snapshot | grep '(ro' tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) After some time: root@NasSebUltra6:/# mount | grep -v snapshot | grep '(ro' tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) /dev/md127 on /data type btrfs (ro,noatime,nodiratime,nospace_cache,subvolid=5,subvol=/) /dev/md127 on /home type btrfs (ro,noatime,nodiratime,nospace_cache,subvolid=256,subvol=/home) /dev/md127 on /apps type btrfs (ro,noatime,nodiratime,nospace_cache,subvolid=257,subvol=/.apps) /dev/md127 on /run/nfs4/home type btrfs (ro,noatime,nodiratime,nospace_cache,subvolid=256,subvol=/home) Strange thing is, there no new entry in system logs. It juste goes in readonly until next reboot. I launched a scrub just in case, but I don't really believe it will chance anything. Does anyone have some idea about how to solve this ?Solved1.5KViews0likes3Comments
1002030001 - Commit Failed #27399265
ReadyNas 312. Current Firmware (6.7.4). For the second time in under a month, this ReadyNAS has become 'Read Only'. The first time was after a firmware upgrade and I was also setting up access rights for ReadyNas Remote and so I thought I'd caused the issue. This time is after a power fail and restart of the NAS drive. I've checked the logs and there's no report of disk errors or problems. However, the share is read-only (when accessed from user PCs) and when I try and change any of the security setttings via the Admin page I get the error: 100203001 Commit Failed. I can't create a new share (same error) or create or rename folders in this share (no error via Admin page / disk full error via PC). I have tried to run the backup manually (there's an overnight backup to USB as well as a continuous backup to ReadyVault) but the backup to USB job status remains as 'In Queue'. I have the data secure and I know I can restore to factory settings, set it up again and copy all the data back as that's what I did last time. However I need to know it's not going to happen again.I'm guessing there could be some underlying hardware issue (disk error?) but there's nothing I can see in the logs. Is there any way of running a check or test?Currently all users can access the files they need and are saving changes to their local PCs and will copy back once the NAS is working again, and it's Friday, so I have a day or two to resolve this. Any help or advise would be greatly appreciated.Solved10KViews0likes14Comments
