NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS RN316 showing Volume Is read-only
Can someone please help. My RN316 is showing "Volume is read-only". i've tried replacing 3 of the 6 disks, only 1 of which had shown any errors in the "ATA error" item when you hover the mous...
craigat wrote:
Hi,
The RN316 seems fine... its just read-only.. I can copy files off it, I can play videos from it.
Is there anything I can do? or just destroy it?
Thanks,
Craig
The best strategy is to do a factory reset, set up the NAS again, and restore the data from a backup.
Which is why I keep asking if you've made a backup.
craigat wrote:
My RN316 is showing "Volume is read-only".
Its getting to expensive to just replace disks for the "heck of it".
Read-only is usually triggered by a problem with the BTRFS file system, not the disk drives.
You could try downloading the full log zip file from the NAS, and looking in there for details. There is a lot of info there, I could help you analyze it if you like. (Don't post a link to the logs publicly, as there is some information leakage when you do that).
craigat wrote:
If I copy all the data off, what do I do to resolve this?
Do a factory default (either from the boot menu or system->settings->update in the admin web ui). Then reconfigure the NAS (recreating shares, etc) and copy the data back.
What you have been doing is may create more issues, it won't solve the problem. The volume has gone read-only to prevent you from doing further damage before you back up the files, so take the hint.
You should be able to save the configuration and restore it again later rather than completely re-configure manually. Note that you do need to use the same volume name for that to work. You likely can also just destroy and re-create the data volume.
If your NAS set-up is pretty standard without a lot of users, it won't matter much. Note that you will need to restore apps in either case, which now takes extra effort.
Hi
Thanks guys for the reply.
10+ yrs ago I spent time in the u*ix/l*ix space but dont know brfs at all. I did download the logs & in dmesg.log I see:
NTFSJ support included
Hfs+J support included
Build_for__Netgear_RN314_x86_64_k4.1.16_2016-04-19_lke_9.6.4_b635
[Wed Sep 11 17:18:28 2024] ufsd: PAGE_SIZE=4K, THREAD_SIZE=16k
[Wed Sep 11 17:18:28 2024] ufsd: Can't open /proc/config.gz
[Wed Sep 11 17:18:28 2024] ufsd: Kernel .config hash: original unknown, current can't check.
[Wed Sep 11 17:18:28 2024] ufsd: Kernel .config hash: original unknown, current can't check
[Wed Sep 11 17:18:31 2024] ufsd: "mount" (sdh2): is mounted as NTFS(rw) at 2024-09-11 07:18:31
[Wed Sep 11 17:18:32 2024] nfsd: last server has exited, flushing export cache
[Wed Sep 11 17:18:32 2024] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[Wed Sep 11 17:18:32 2024] NFSD: starting 90-second grace period (net ffffffff88d782c0)
[Wed Sep 11 17:18:37 2024] nfsd: last server has exited, flushing export cache
[Wed Sep 11 17:18:37 2024] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[Wed Sep 11 17:18:37 2024] NFSD: starting 90-second grace period (net ffffffff88d782c0)
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS: error (device md127) in btrfs_commit_transaction:2249: errno=-5 IO failure (Error while writing out transaction)
[Wed Sep 11 17:30:57 2024] BTRFS info (device md127): forced readonly
[Wed Sep 11 17:30:57 2024] BTRFS warning (device md127): Skipping commit of aborted transaction.
[Wed Sep 11 17:30:57 2024] BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure
[Wed Sep 11 17:30:57 2024] BTRFS info (device md127): delayed_refs has NO entry
[Thu Sep 12 08:55:14 2024] md: md127: recovery done.
[Thu Sep 12 08:55:17 2024] RAID conf printout:
[Thu Sep 12 08:55:17 2024] --- level:5 rd:6 wd:6
[Thu Sep 12 08:55:17 2024] disk 0, o:1, dev:sda3
[Thu Sep 12 08:55:17 2024] disk 1, o:1, dev:sdb3
[Thu Sep 12 08:55:17 2024] disk 2, o:1, dev:sdc3
[Thu Sep 12 08:55:17 2024] disk 3, o:1, dev:sdd3
[Thu Sep 12 08:55:17 2024] disk 4, o:1, dev:sde3
[Thu Sep 12 08:55:17 2024] disk 5, o:1, dev:sdf3
[Thu Sep 12 09:36:30 2024] BTRFS error (device md127): Remounting read-write after error is not allowed
[Thu Sep 12 09:36:53 2024] BTRFS error (device md127): Remounting read-write after error is not allowed
[Thu Sep 12 10:16:39 2024] BTRFS error (device md127): Remounting read-write after error is not allowed
[Thu Sep 12 17:36:38 2024] BTRFS error (device md127): Remounting read-write after error is not allowedTrusting the RAID5 too much, I did think replacing the erroring disk (4 ATA erros, but not enough for the RN316 to change it to status RED) would help, but clearly not.
craigat wrote:
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS error (device md127): bdev /dev/md127 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
[Wed Sep 11 17:30:57 2024] BTRFS: error (device md127) in btrfs_commit_transaction:2249: errno=-5 IO failure (Error while writing out transaction)5 writes to the volume failed. Can you check other logs (system.log, kernel.log, systemd-journal.log) for errors at this time?
Since you do have read access, you should
- immediately back up the files to other storage
- do NOT reboot the NAS, as that might result in losing access altogether.
Hi
Thanks guys. I've been spending ages trying to backup as you suggested.
kernel.log only showing me things that I cant see how to make changes to rectify like:
-- Logs begin at Wed 2024-09-11 18:06:55 AEST, end at Mon 2024-09-16 17:58:47 AEST. --
Sep 12 08:55:13 rn316 kernel: md: md127: recovery done.
Sep 12 08:55:15 rn316 kernel: RAID conf printout:
Sep 12 08:55:15 rn316 kernel: --- level:5 rd:6 wd:6
Sep 12 08:55:15 rn316 kernel: disk 0, o:1, dev:sda3
Sep 12 08:55:15 rn316 kernel: disk 1, o:1, dev:sdb3
Sep 12 08:55:15 rn316 kernel: disk 2, o:1, dev:sdc3
Sep 12 08:55:15 rn316 kernel: disk 3, o:1, dev:sdd3
Sep 12 08:55:15 rn316 kernel: disk 4, o:1, dev:sde3
Sep 12 08:55:15 rn316 kernel: disk 5, o:1, dev:sdf3
Sep 12 09:36:28 rn316 kernel: BTRFS error (device md127): Remounting read-write after error is not allowed
Sep 12 09:36:51 rn316 kernel: BTRFS error (device md127): Remounting read-write after error is not allowed
Sep 12 10:16:37 rn316 kernel: BTRFS error (device md127): Remounting read-write after error is not allowed
Sep 12 17:36:35 rn316 kernel: BTRFS error (device md127): Remounting read-write after error is not allowed
Sep 12 19:06:47 rn316 kernel: nr_pdflush_threads exported in /proc is scheduled for removal
Sep 12 19:21:24 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379596075008
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379588964352
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379515039744
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379586244608
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379405758464
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379406938112
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379406118912
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379406151680
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379405725696
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379405332480
Sep 12 19:22:11 rn316 kernel: BTRFS error (device md127): bad tree block start 7611175298055105740 33379404939264
Sep 12 19:22:17 rn316 kernel: btree_readpage_end_io_hook: 4 callbacks suppressedsystem.log showing
Sep 16 16:17:01 rn316 CRON[28088]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 16 16:17:01 rn316 CRON[28089]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 16 16:17:01 rn316 CRON[28088]: pam_unix(cron:session): session closed for user root
Sep 16 16:26:21 rn316 connmand[3002]: ntp: adjust (slew): +0.002224 sec
Sep 16 16:43:26 rn316 connmand[3002]: ntp: adjust (slew): -0.000354 sec
Sep 16 17:00:31 rn316 connmand[3002]: ntp: adjust (slew): -0.001583 sec
Sep 16 17:17:01 rn316 CRON[28536]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 16 17:17:01 rn316 CRON[28537]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 16 17:17:01 rn316 CRON[28536]: pam_unix(cron:session): session closed for user root
Sep 16 17:17:36 rn316 connmand[3002]: ntp: adjust (slew): -0.000665 sec
Sep 16 17:18:02 rn316 connmand[3002]: ntp: adjust (slew): -0.001093 sec
Sep 16 17:35:06 rn316 connmand[3002]: ntp: adjust (slew): -0.000356 sec
Sep 16 17:52:11 rn316 connmand[3002]: ntp: adjust (slew): +0.002863 sec
Sep 16 17:58:10 rn316 apache_access[4507]: 192.168.1.108 "GET /admin/ HTTP/1.1" 401
Sep 16 17:58:18 rn316 apache_access[4507]: Admin session started from 192.168.1.108
Sep 16 17:58:20 rn316 apache_access[4507]: 192.168.1.108 "POST /dbbroker HTTP/1.1" 401
Sep 16 17:58:47 rn316 dbus[2993]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Sep 16 17:58:47 rn316 dbus[2993]: [system] Successfully activated service 'org.opensuse.Snapper'
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Pictures errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Videos errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Music errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Documents errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Backup errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Sync errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Training errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/eBooks errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failed
Sep 16 17:58:47 rn316 snapperd[29280]: THROW: open failed path:/data/Games errno:2 (No such file or directory)
Sep 16 17:58:47 rn316 snapperd[29280]: reading failedI dont even have a share called "Pictures" !
So is my only option to "Destroy" the Raid5 & re-start from scratch ?
Thanks,
Craig
Australia
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
