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 drvies (Not Pro)
Both boxes used for media files.
Prod box is missing FLAC files. When I open a file with MP3tag the file (song) shows as a FLAC file with no tag (only filename). It will not play. Foobar gives this message:
Unable to open item for playback (Unsupported format or corrupted file):
"\\316-prod\db-prod\DB-BLs\Beach Boys\- Goodbye Surfing Hello God - CD 1.5\01 - Hi We're The Beach Boys - Beach Boys.flac"
There is no file there but the 316 Production box thinks there is. It shows as a file.
Same file plays fine on the Backup box.
I'm going to call these unplayable files "ghost" files.
My first step was to delete the ghost files from the 316 Production box and restore the same file from the Backup box. The copy works fine BUT the copied file now on the Production box doesn't necessarily play. It's another ghost file. Some play, some do not.
The MAIN share is Music. In Music there are 10 sub-shares by category. In the sub-share I'm working there are 40 sub-shares (Artist). In all there are 9500 files (songs).
Of those 9500 there are 154 ghost files.
There are no log file alert messages. The system indicates it's healhty. BUT when I select Diagnotics on Raidar I get this message:
Successfully completed diagnostics
System
No errors found.
Logs
2020-01-23 18:46:01: raidard[2978]: segfault at 7ffedc880000 ip 0000000000401d20 sp 00007ffedc87dab8 error 4 in raidard[400000+6000]
I'm stumped. Is this a drive error or memory area? Searching online gives an answer whic is above my pay grade. Why doesn't the system place a message in the log file area?
Questions:
How do I determine what the real issue is? (Bad disks? How do I know? Can I fix?)
What's the best way to attack this issue? (I'll assume a full restore from Backup but I MUST solve the issue first?)
Finally, what should I NOT do?
Dave-
13 Replies
I suggest that you download the full log zip file from the production NAS. Put the zip into cloud storage (google drive, dropbox, etc), and send a download link to the mods ( JohnCM_S or Marc_V ) and ask them to analyze them.
Don't post the link publicly. Instead use the private message (PM) facility in the forum. You send a PM by clicking on the envelope icon in the upper right of the forum page.
Note that if you purchased the NAS new between 1 June 2014 and 31 May 2016, you have lifetime chat support at my.netgear.com. You could also use that.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
