NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN316 Corrupting files on write
I have a similar issue to RN316-Corrupt-Files (1855098#M39773) and want to avoid factory resetting the NAS. Random files written to the NAS seem to be getting corrupted when re-checking them after transfer (via SMB/LAN).
dmesg logs show
[21217.880559] BTRFS error (device md126): bdev /dev/md126 errs: wr 185, rd 744, flush 0, corrupt 92, gen 0 [21217.881008] BTRFS error (device md126): bdev /dev/md126 errs: wr 186, rd 744, flush 0, corrupt 92, gen 0 [21244.145426] BTRFS error (device md126): bdev /dev/md126 errs: wr 187, rd 744, flush 0, corrupt 92, gen 0 [21244.351290] BTRFS error (device md126): bdev /dev/md126 errs: wr 188, rd 744, flush 0, corrupt 92, gen 0 [21244.593259] BTRFS error (device md126): bdev /dev/md126 errs: wr 189, rd 744, flush 0, corrupt 92, gen 0
confirmed with kernal.log
Jun 20 02:38:19 NAS kernel: BTRFS error (device md126): bdev /dev/md126 errs: wr 182, rd 744, flush 0, corrupt 92, gen 0 Jun 20 02:38:20 NAS kernel: BTRFS error (device md126): bdev /dev/md126 errs: wr 183, rd 744, flush 0, corrupt 92, gen 0 Jun 20 02:38:20 NAS kernel: BTRFS error (device md126): bdev /dev/md126 errs: wr 184, rd 744, flush 0, corrupt 92, gen 0 Jun 20 02:38:24 NAS kernel: BTRFS error (device md126): bdev /dev/md126 errs: wr 185, rd 744, flush 0, corrupt 92, gen 0 Jun 20 02:38:24 NAS kernel: BTRFS error (device md126): bdev /dev/md126 errs: wr 186, rd 744, flush 0, corrupt 92, gen 0
I noticed OS 6.10.2 is out, but this NAS is on OS 6.9.6 - trying to do a frontview firmware update ("Check for Update"), I get "Your system is currently running the latest firmware. Your system does not need a firmware update." message instead.
I'm using WD Red 6x8TB drives - i believe based on WD the 8+ TB red's are usingCMR, so don't suffer from SMR issues. Only 1 of the RaidX config'ed drives shows smart log errors from a while ago due to a UPS battery/power outage issue.
Would it be safe to perahaps
1) Manually update the OS to 6.10.2, to stablise BTRFS - or does it make no difference on the RN316? (update listed models say "Improved BTRFS stability on ARM units (102/104/2120/202/204/212/214)" - but not 316?
2) Is there any other way to stablize the FS before it gets so bad I have to start using another NAS system?
12 Replies
Current firmware is actually 6.10.5, but there are some issues with it - so I don't recommend upgrading to it.
q3d wrote:
1) Manually update the OS to 6.10.2, to stablise BTRFS - or does it make no difference on the RN316? (update listed models say "Improved BTRFS stability on ARM units (102/104/2120/202/204/212/214)" - but not 316?
If you use rsync "push" backups (remote destination), then avoid 6.10.4 and 6.10.5.
There is a login loop in 6.10.5 that blocks admin access for some users. That seems to be linked to using http to access the web ui (instead of https). But that is new information, so I wouldn't risk upgrading to it just yet. But you could safely update to 6.10.2 or 6.10.3.
I don't think it will resolve your problem, but it would do no harm to try.
The write errors appear to be slowly climbing. Have you tried testing the disks (using the test on the volume settings wheel)?
No issues found on the Disk Test and Scrub (unless there is a detailed log somewhere else other than Frontview?)
Jun 24, 2021 01:55:40 AM Volume: Disk test completed for volume data. Jun 23, 2021 10:10:17 PM Volume: Disk test is in process for Volume 'data'. Jun 23, 2021 08:14:05 PM Volume: Scrub completed for volume data'. Jun 20, 2021 01:43:55 AM Volume: Scrub started for volume data.
I'll do an firmware update to 6.10.2 at least (I don't use rsync backups so I can even do 10.5)
I also read somewhere, that scrubbing disk by disk (rather than raid level) was required for BTRFS, however I'm not sure how Netgear have implemented BTRFS on RAID 5 with the RN315/OS6?
Would it be safe and of any benefit to do a disk by disk scrub on the RN316? ....at lease read only to start with, something like:
btrfs scrub start -r /dev/sda
btrfs scrub start -r /dev/sdb
btrfs scrub start -r /dev/sdc
btrfs scrub start -r /dev/sdd
btrfs scrub start -r /dev/sde
btrfs scrub start -r /dev/sdfThen if any errors, without the -r (read only)?
Drives are listed as:
# fdisk -l | grep "^Disk /dev/sd" Partition 2 does not start on physical sector boundary. Disk /dev/sda: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors Disk /dev/sdd: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors Disk /dev/sde: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors Disk /dev/sdf: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors ......
q3d wrote:
(unless there is a detailed log somewhere else other than Frontview?)
Download the log zip file from the web ui's log page- there is a lot more in there.
q3d wrote:
I also read somewhere, that scrubbing disk by disk (rather than raid level) was required for BTRFS, however I'm not sure how Netgear have implemented BTRFS on RAID 5 with the RN315/OS6?
Not sure where you read that, but its not the case with the ReadyNAS. MDADM is used to create a virtual disk, then the BTRFS file system is created on top of that.
The scrub you already ran includes both a RAID scrub and a BTRFS scrub. Though it did complete, I suggest looking in btrfs.log, system.log, and kernel.log for file system related errors (btrfs and disk). Perhaps also look at the smart stats in disk_info.log.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
