NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN316 - Corrupt Files
Not sure this got posted. I can't seem to find ir. Two 316 ReadyNAS boxes. One Producrion, One Backup. Same firmware: 6.10.2 Prod box has WD Red Pro 6 6TB drives. Backup Box has WD Red 6TB dr...
I received an email from Netgear asking if my problem is solved. I haven't heard from anyone after following Stephen's reco so the answer is "no".
What I've done is the interim is:
Verified the files on my Backup NAS. 600,000+ files. 2 were corrupt. I had gotten the segfault on that box as well. The corrupt files were from 2012 so I'm discounting those since they could have been corrupt for 8 years.
I reinstalled the OS. No improvement.
I ran a memory test. 7 passes (8 hours). No errors.
Last night I ran a disk test. I'm not sure were to find the results of that in the log but thing seem fine. Production box booted up fine after the disk test, No obvious errors on the 6 disks.
Here's I did be between each of the above steps:
I found a folder (artist) with 21 sub-folders (albums) with 592 files (songs).
Before the test 63 of 592 files were corrupt. I deleted those and copied from backup after verifying the backup files were okay. After that copy 63/592 were bad with just a straight copy.
Then I did the same after the memory test: 51/592 were bad. Again just a straight copy.
After the Disk test I did the same and 45/592 were bad.
I was thinking thinking the results would always be the same. Silly me.
What causes "good" files to be corrupt after a simple copy???
I would think my next step(s) would be:
Test the drives with WD Lifeguard -or-
Factory reset
I surely would like for Netgear to give me some direction here. The data is bad but perhaps there's something that needs to be studied/corrected before I spends hours doing anything else.
Any ideas?
Dave-
Mook2 wrote:
I surely would like for Netgear to give me some direction here. The data is bad but perhaps there's something that needs to be studied/corrected before I spends hours doing anything else.
This is a community forum, and not Netgear support. One option is for you to send JohnCM_S or Marc_V (Netgear mods) a downloadable link to your full log zip file, and ask them to analyze it. Do that with a private message (PM) by clicking on the envelope link in the upper right of the forum.
You could also use paid support via my.netgear.com.
Mook2 wrote:
I was thinking thinking the results would always be the same. Silly me.
What causes "good" files to be corrupt after a simple copy???
You could test using a utility like teracopy, which has a verify option. One question here is whether the issue is related to your network or with the NAS.
I am also thinking that you might want to create a fresh test share, and see if you get the same results when you copy to the test share.
But to answer your question, there are lots of causes, including:
- a corrupted file system
- bad memory in the NAS
- network issues
- failing disks
Mook2 wrote:
Test the drives with WD Lifeguard -or-
Factory reset
This could also be -and-
Powering down the NAS and doing the long non-destructive test on each disk in Lifeguard is reasonable (though time consuming).
I'd look at pending sector counts and reallocated sector counts in disk_info.log, and for any disk or btrfs errors you see in kernel.log or system.log.
Hi Stephen, thanks for your reply.
I did as you suggested and sent the logs and a PM to one of the contacts you listed.
I do understand this is a user forum and appreciate all the support given here, I wanted to make that clear. I'm just a tad frustrated. I have limted tech knowledge and that can be difficult for any user. Plus the amount of time it takes to do all these tests is, well, time-consuming. :)
Right now I am backing up my backup in case my backup box has issues.
I also didn't know I can get paid support. That's news to me and is an option I'll explore if necessary.
As to your new suggestions. I didn't think of creating a new share and copying to that. I'll give that a shot.
I also looked in the logs you recommended after my disk test.
In the system log I found no errors.
In the kernel log I see this message:
Feb 05 19:14:29 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55441, rd 212, flush 0, corrupt 0, gen 0
(wr continues to 55450)
Plus other btrfs errors:
Feb 05 20:09:22 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55571, rd 212, flush 0, corrupt 0, gen 0
Feb 05 20:30:41 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55583, rd 212, flush 0, corrupt 0, gen 0
Feb 05 20:44:00 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55713, rd 212, flush 0, corrupt 0, gen 0
Feb 05 20:44:05 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55731, rd 212, flush 0, corrupt 0, gen 0
Feb 05 20:44:16 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55751, rd 212, flush 0, corrupt 0, gen 0
Feb 05 20:44:43 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55778, rd 212, flush 0, corrupt 0, gen 0
Feb 05 20:44:55 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55790, rd 212, flush 0, corrupt 0, gen 0
Feb 05 20:46:04 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55819, rd 212, flush 0, corrupt 0, gen 0I'm not sure what this all means and now I'm unsure how to proceed.
Ideas, anyone?
I did read this thread about BTRFS:
and this one:
Mook2 wrote:
Hi Stephen, thanks for your reply.
I did as you suggested and sent the logs and a PM to one of the contacts you listed.
I do understand this is a user forum and appreciate all the support given here, I wanted to make that clear. I'm just a tad frustrated. I have limted tech knowledge and that can be difficult for any user. Plus the amount of time it takes to do all these tests is, well, time-consuming. :)
Right now I am backing up my backup in case my backup box has issues.
I also didn't know I can get paid support. That's news to me and is an option I'll explore if necessary.
As to your new suggestions. I didn't think of creating a new share and copying to that. I'll give that a shot.
I also looked in the logs you recommended after my disk test.
In the system log I found no errors.
In the kernel log I see this message:
Feb 05 20:09:22 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55571, rd 212, flush 0, corrupt 0, gen 0 Feb 05 20:30:41 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55583, rd 212, flush 0, corrupt 0, gen 0 Feb 05 20:44:00 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55713, rd 212, flush 0, corrupt 0, gen 0 Feb 05 20:44:05 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55731, rd 212, flush 0, corrupt 0, gen 0 Feb 05 20:44:16 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55751, rd 212, flush 0, corrupt 0, gen 0 Feb 05 20:44:43 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55778, rd 212, flush 0, corrupt 0, gen 0 Feb 05 20:44:55 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55790, rd 212, flush 0, corrupt 0, gen 0 Feb 05 20:46:04 316-PROD kernel: BTRFS error (device md126): bdev /dev/md127 errs: wr 55819, rd 212, flush 0, corrupt 0, gen 0
I haven't seen this particular error here before, but it looks to me like the the wr counts are btrfs write error counts (which are increasing).
That is consistent with the corrupted files you are seeing when you write to the NAS.
You aren't seeing any disk errors? Just these BTRFS ones?
Correct, No disk errors shown in the logs.
I have a question.
If this corruption is caused by the way BTRFS "works" should I just do a factory reset and begin all over again? I have no issue with that. I'm concerned that this was a blip on the way the file system is handed and not a hardware problem at all.
Is that a valid assumption?
In addition, is this a forseeable problem on that specific NAS or just a screw up that can happen on any NAS at any time?
Dave-
Mook2 wrote:
should I just do a factory reset and begin all over again? I have no issue with that. I'm concerned that this was a blip on the way the file system is handed and not a hardware problem at all.
I have seen BTRFS errors occur when the underlying disks have problems, and I've also seen file system corruption when the system is unexpectedly shut down (due to lost writes). I haven't seen this particular symptom before - either posted here or on my own systems.
So it would be good to have Netgear review the logs, and see if they can explain what happened.
However, as far as recovery goes, I would test the disks and then do a factory reset. That would ensure that you have a clean file system.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
