File corruption

bburns · December 29, 2013

I appear to be experiencing file corruption on my Unraid server:( I have noticed that many of my mkv files will stop playing periodically. It is almost like there is a bad spot in the file, if I skip over the place that it stops prematurely it will play fine?!?! Since it has been happening more and more frequently, I have started debugging it some. BTW I use XBMC to play my video stuff. If I play a failing file with VLC it seems to play fine. I have several XBMC machines and a failing file seems to fail on all machines at the same point, which lead me to believe that there must be something wrong with the file.

So first I ran a memory check for 12 hours and it did not find any memory problems.

I then performed a binary file compare on a failing file, which I had a backup copy on another machines. There was indeed file corruption:( Now I am extremely worried about other files on my system being corrupt.

It doesn't happen all the time or at least I don't think so (maybe some corruption goes undetected).

The problem seemed to start about the time that I upgraded my Unraid motherboard to a GIGABYTE GA-F2A85XM-D3H. Also at that time I upgraded UNRAID for 4.7 to 5.0 rc? and now I am running the released version of 5.0. This was around April.

So where is the problem?

- Motherboard?

- UNRAID 5.0?

- Network issue?

Any Ideas on how to narrow down where the problem is?

B2

garycase · December 29, 2013

Since you've identified that there IS some corruption, I'd do the following:

(a) Compare the rest of your files with your backups to see just how widespread the corruption is.

(b) Replace all of the corrupted files from your backups.

© Use a checksum utility to generate checksums for all your files, so you can easily check them in the future without having to pull out your backups. [i use Corz' excellent checksum utility to do this from Windows: http://corz.org/windows/software/checksum/ ]

That resolves the corrupted files; but doesn't identify HOW they were corrupted. You've already run a fairly thorough memory diagnostic; so that can reasonably be eliminated (not 100%, but with fairly high confidence).

Do you always verify your writes to the array? [e.g. using TeraCopy or by comparing the file on the array with the source?] This would catch network issues.

It's not likely an UnRAID issue ... that would have been noticed long before now

What are the specifics of your system? Motherboard make/model; memory; disk complement; power supply make/model; etc. If you have marginal power and/or poorly seated SATA cables that could explain issues on the disks ... although you should be seeing reported disk errors in the Web GUI if that is the case.

kristisdad · December 29, 2013

I noticed that I was getting the "Tower kernel: mce: [Hardware Error]: Machine check events logged (Errors)" on my Syslog quite often. I noticed that the common denominator for these errors was that I was writing directly to my drives from makeMKV, i, like you, was worried about data corruption. It took me awhile to figure where these errors where coming from. I have been extensively writing to my drives with Handbrake in the past 30 hours and have not had any errors during the writes. I notice that Handbrake log shows that it writes to the capability of the CPU. I've ripped about 30 DVD in that time period. No errors.

I believe that makeMKV may be at the root of the problem. I used to write to an external drive with makeMKV and copy to unRaid, and this provided no errors, but I didn't like the time involved of doing the job twice.

I'm going to try some other tweaks during the week, upgrade my mobo bios, add drivers for my eth0 to stop some packet drops, but for the most part I think I've got it tacked down.

Try the Handbrake, I think you'll find it more unRaid friendly, doesn't cost anything to try...

bburns · December 29, 2013

So I just checked the syslog and I see the following. Should I be concerned about the page errors or the ata error?

Dec 28 12:54:10 Ungol kernel: [mem 0x00000000-0x000fffff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x37800000-0x379fffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x34000000-0x377fffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x00100000-0x001fffff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20130117/tbfadt-599) (Minor Issues)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata16: end_device-2:3: dev error handler (Errors)

Dec 28 12:54:11 Ungol avahi-daemon[1396]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! (Minor Issues)

Dec 28 12:54:16 Ungol emhttp: shcmd (56): killall -HUP smbd (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: cd+++++++++ Movies/CouchPotato/Machete Kills (2013)/ (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013) (Minor Issues)

bburns · December 29, 2013

My system is:

MB: GIGABYTE GA-F2A85XM-D3H

Processor: AMD A4-5300 APU with Radeon HD Graphics

Memory: 8G

Total disk: 8 2TB Data Disks + 1 2TB Parity disk + 500GB Cache Drive

Just did another test. I copied a 4GB file to my unraid with Teracopy. The file was written to my cache drive. I then used Tearacopy to verify it and it was corrupt on the cache drive. So it must be getting corrupted on the initial write.

dgaschk · December 29, 2013

So I just checked the syslog and I see the following. Should I be concerned about the page errors or the ata error?

Dec 28 12:54:10 Ungol kernel: [mem 0x00000000-0x000fffff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x37800000-0x379fffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x34000000-0x377fffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x00100000-0x001fffff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20130117/tbfadt-599) (Minor Issues)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata16: end_device-2:3: dev error handler (Errors)

Dec 28 12:54:11 Ungol avahi-daemon[1396]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! (Minor Issues)

Dec 28 12:54:16 Ungol emhttp: shcmd (56): killall -HUP smbd (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: cd+++++++++ Movies/CouchPotato/Machete Kills (2013)/ (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013) (Minor Issues)

None of these are errors. Updating menu should fix some of them.

dgaschk · December 29, 2013

My system is:

MB: GIGABYTE GA-F2A85XM-D3H

Processor: AMD A4-5300 APU with Radeon HD Graphics

Memory: 8G

Total disk: 8 2TB Data Disks + 1 2TB Parity disk + 500GB Cache Drive

Just did another test. I copied a 4GB file to my unraid with Teracopy. The file was written to my cache drive. I then used Tearacopy to verify it and it was corrupt on the cache drive. So it must be getting corrupted on the initial write.

Any SATA cards?

bburns · December 29, 2013

I have an 8 port SATA card: Supermicro AOC-SASLP-MV8

dgaschk · December 30, 2013

Zip and attach the syslog.

Joe L. · December 30, 2013

So I just checked the syslog and I see the following. Should I be concerned about the page errors or the ata error?

Dec 28 12:54:10 Ungol kernel: [mem 0x00000000-0x000fffff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x37800000-0x379fffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x34000000-0x377fffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x00100000-0x001fffff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors)

Dec 28 12:54:10 Ungol kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors)

Dec 28 12:54:10 Ungol kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20130117/tbfadt-599) (Minor Issues)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors)

Dec 28 12:54:10 Ungol kernel: sas: ata16: end_device-2:3: dev error handler (Errors)

Dec 28 12:54:11 Ungol avahi-daemon[1396]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! (Minor Issues)

Dec 28 12:54:16 Ungol emhttp: shcmd (56): killall -HUP smbd (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: cd+++++++++ Movies/CouchPotato/Machete Kills (2013)/ (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues)

Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues)

Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues)

Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013) (Minor Issues)

no, they are not errors.

For BOTH classes of lines marked as "errors", apparently you've not checked for updates in unMENU for many months, since those specific messages "kernel: [mem ...." error are no longer falsely matched since Mid July..

-- The first set is showing how memory is being allocated)

-- The others contain the string of letters "error" somewhere on the line so marked. (They are telling you which error handler will be used if there is an error on that disk device)

If you use the Check-for-updates/Install Updates buttons on the user-scripts page, both will no longer be marked as "errors" in the syslog viewer of unMENU.

Joe L.

bburns · December 30, 2013

I removed my cache drive completely and copied the same file again. This time Teracopy verified the file correctly. So I guess my problem is with the cache drive. Although one test is not very definitive:) Should I run SMART on the cache drive? Is their a tool that I can use on a Windows PC to check the drive with?

B2

dgaschk · December 30, 2013

Run a long SMART test.

bburns · December 31, 2013

So after I removed my cache drive, I now am getting a disk space full error when I try to copy a file to one of my shares. My share settings are:

Name: TV

Comments:

Allocation method: High-water

Min. free space:

Split level: 0

Included disk(s): disk6, disk7

Excluded disk(s): disk1,disk2,disk3,disk4,disk5,disk8

Share empty? No

The disks 6 & 7 are 2TB and roughly 50% free each.

I tried using a new disk for cache drive to see if the problem would go away, no joy:(

I then tried changing some of the share setting, like Allocation Method and Min free space, but the changes don't seem to take effect?!?!?

What is going on?

dgaschk · December 31, 2013

Attach the syslog. Note the time of the failed transfer.

bburns · December 31, 2013

Run a long SMART test.

Here is the results: It seems okay to me?

SMART status Info for /dev/sdm

Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===

Model Family: Seagate Barracuda 7200.10 family

Device Model: ST3500630AS

Serial Number: 9QG3W646

Firmware Version: 3.AAK

User Capacity: 500,107,862,016 bytes

Device is: In smartctl database [for details use: -P show]

ATA Version is: 7

ATA Standard is: Exact ATA specification draft version not indicated

Local Time is: Tue Dec 31 11:45:10 2013 EST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

General SMART Values:

Offline data collection status: (0x82) Offline data collection activity

was completed without error.

Auto Offline Data Collection: Enabled.

Self-test execution status: ( 0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: ( 430) seconds.

Offline data collection

capabilities: (0x5b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

No Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 1) minutes.

Extended self-test routine

recommended polling time: ( 163) minutes.

SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x000f 108 097 006 Pre-fail Always - 30787889

3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0

4 Start_Stop_Count 0x0032 096 096 020 Old_age Always - 4890

5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0

7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail Always - 520025772

9 Power_On_Hours 0x0032 054 054 000 Old_age Always - 40611

10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0

12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 480

187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0

189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0

190 Airflow_Temperature_Cel 0x0022 069 052 045 Old_age Always - 31 (Lifetime Min/Max 22/38)

194 Temperature_Celsius 0x0022 031 048 000 Old_age Always - 31 (0 11 0 0)

195 Hardware_ECC_Recovered 0x001a 063 056 000 Old_age Always - 240790440

197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0

198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 17

200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0

202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0

SMART Error Log Version: 1

No Errors Logged

SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Extended offline Completed without error 00% 40602 -

# 2 Extended offline Completed without error 00% 18731 -

SMART Selective self-test log data structure revision number 1

SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

1 0 0 Not_testing

2 0 0 Not_testing

3 0 0 Not_testing

4 0 0 Not_testing

5 0 0 Not_testing

Selective self-test flags (0x0):

After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

bburns · January 4, 2014

So I removed the cache drive and I did more moving of large video files, but this time I used teracopy and verified each copy. I had about a 50% success rate of the first copy not having any errors:( So how should I go about debugging this? Is there a chkdsk program for unraid to see if there are bad sectors on the drives? Does the long SMART test identify bad sectors?

dgaschk · January 4, 2014

Run memtest overnight.

bburns · January 4, 2014

I have already run it for 12 hours with no failures. I would think that at the rate that I'm seeing file corruption that memtest would have seen it very quickly.

bburns · January 5, 2014

I ran the "File System Check" from unmenu and it found two corruptions:

Comparing bitmaps..Checking Semantic tree:

finished

2 found corruptions can be fixed when running with --fix-fixable

###########

I am now running the fix file system. Hopefully that fixes my problem.

Joe L. · January 5, 2014

The SMART report also lists a number of CRC errors. That is usually noise pickup on the SATA cables from adjacent power or SATA cables.

199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 17

Do you have the cables to the drives tie-wrapped together? If so, cut the tie-wraps and get some distance between the cables.

File corruption

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation