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.
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 allowed
Trusting 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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
