Too much random read errors?


Recommended Posts

It's my second or third post about my server read errors.

 

I have had errors related to controllers on the motherboard (marvell), had errors also on intel scu controllers, related to discs (replaced), have tried two kind of supermicro server motherboards, replaced sata cables, etc  but the errors return.

The truth is that I don't know what else to try to not get errors evey 15 days.

 

Yesterday I got 32 read errors on one of my discs. (When I got home will attach diagnostic file.)

 

What is the exact procedure to follow after those errors?

 

Is still the parity disc valid?

 

Do I have to rebuild my disc everytime I got a read error?

 

Thankyou

Gus

 

 

 

 

 

 

Link to comment

Here is the "diagnostics" file.

 

And the drive with those errors was this:

 

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD40EFRX-68WT0N0
Serial Number:    WD-WCC4E4CLFP20
LU WWN Device Id: 5 0014ee 20cf990a2
Firmware Version: 82.00A82
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Jul 14 21:42:10 2017 CEST
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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		(52860) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 529) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   185   178   021    Pre-fail  Always       -       7741
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       855
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       8958
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       108
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       66
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1982
194 Temperature_Celsius     0x0022   112   103   000    Old_age   Always       -       40
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 24 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 24 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 45 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 45 00 00 00 a0 00      00:23:12.221  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:23:12.221  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 00      00:23:06.180  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:23:06.179  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:23:06.179  IDENTIFY DEVICE

Error 23 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 45 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 45 00 00 00 a0 00      00:23:06.179  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:23:06.179  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 00      00:23:00.809  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:23:00.809  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:23:00.808  IDENTIFY DEVICE

Error 22 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 45 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 45 00 00 00 a0 00      00:23:00.809  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:23:00.808  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:23:00.632  READ DMA
  ec 00 00 00 00 00 a0 00      00:22:00.709  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:22:00.709  SET FEATURES [Set transfer mode]

Error 21 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 08 00 00 00 e0  Device Fault; Error: ABRT 8 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:23:00.632  READ DMA
  ec 00 00 00 00 00 a0 00      00:22:00.709  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:22:00.709  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:22:00.708  IDENTIFY DEVICE

Error 20 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 00      00:22:00.709  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:22:00.708  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 00      00:21:29.508  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:21:29.508  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

 

unraid-media-diagnostics-20170714-2142.zip

Link to comment
2 hours ago, Frank1940 said:

Try replacing the SATA data cables on the disks in question. 

 

Also, do NOT bundle SATA cables tightly together for 'neatness'.  (This can cause "crosstalk" between the cables!)  

 

Also, if you are using WD disks, you should read this article on the use of latching/locking SATA cables on some of their drives.

 

   https://support.wdc.com/knowledgebase/answer.aspx?ID=10477

 

Thankyou @Frank1940

 

The truth is that I'm using those cables that are pretty near:

https://www.amazon.es/CableDeconn-Speed-6Gbps-Quality-Server/dp/B00VI3MFMO/ref=sr_1_2?ie=UTF8&qid=1500127291&sr=8-2&keywords=sata+cable+1m

 

Can this be the problem?

 

Gus

 

 

sata_cable.jpg

Link to comment

If the SATA data cables are going to be bundled, they should be made with shielded wire.  If you notice there are two groups-- each group consisting of a pair of twisted wires for each connector.  Normally if you want to bundle the cables, each one of these twisted-pair groups should have grounded shielding around them.  Normally, this will make each group round rather than flat.  These look to be flat.  Plus, they are one meter in length.  Obliviously, the longer the length, the more coupling between wires you will have.

 

(98% of all SATA cables are NOT shielded!!!  You really have to look for the shielded ones.  And they are usually expensive.) 

Link to comment

I would try running an extended self test on the drive. I am not sure what those ABRT errors are in the smart log. They are not triggering any SMART attribute issues, but if you are seeing read errors, and these align with those errors, something is happening that the drive is reporting. And if the drive is reporting it, it is very likely a problem with the drive.

Link to comment
4 hours ago, bjp999 said:

I would try running an extended self test on the drive. I am not sure what those ABRT errors are in the smart log. They are not triggering any SMART attribute issues, but if you are seeing read errors, and these align with those errors, something is happening that the drive is reporting. And if the drive is reporting it, it is very likely a problem with the drive.

 

Is there any utility in unraid to perform this test?

 

thankyou

gus

Link to comment
5 hours ago, zzgus said:

Is there any utility in unraid to perform this test?

 

Spin up all of the Disks.    'Main'   >>>   ''Array Operation', then click on the 'Spin Up' button.   Click on 'Main'   >>>  'Array Devices'.  Then double click on the Disk you want to test on the "Device" column.   Click on the 'Self-Test' Tab.  Choose the test you want to run.

Link to comment

Did anyone else notice that there were hundreds of lines of errors in @zzgus's syslog that contain repeated errors like this:

Jul 14 02:16:01 UNRAID-MEDIA root: exportfs: Failed to stat /mnt/disks/WDC_WD2002FYPS_01U1B0_WD_WCAVY1003496: Input/output error
Jul 14 02:17:01 UNRAID-MEDIA root: exportfs: Failed to stat /mnt/disks/WDC_WD2002FYPS_01U1B0_WD_WCAVY1003496: Input/output error

and

Jul 14 19:47:44 UNRAID-MEDIA kernel: md: disk5 read error, sector=1419017144
Jul 14 19:47:44 UNRAID-MEDIA kernel: md: disk5 read error, sector=1419017152

and

Jul 14 20:03:02 UNRAID-MEDIA root: exportfs: Failed to stat /mnt/disks/WDC_WD2002FYPS_01U1B0_WD_WCAVY1003496: Input/output error
Jul 14 20:03:02 UNRAID-MEDIA emhttp: err: mdcmd: write: No such file or directory
Jul 14 20:03:02 UNRAID-MEDIA kernel: mdcmd (75): spindown 5
Jul 14 20:03:02 UNRAID-MEDIA kernel: md: do_drive_cmd: lock_bdev error: -2

I am no Guru when it comes to these types of errors but they are probably indicators of some problem(s) with this disk.

Link to comment
On 7/16/2017 at 1:54 AM, zzgus said:

 

Is there any utility in unraid to perform this test?

 

thankyou

gus

 

Click on the disk hyperlink on the main page (e.g.,. "disk1") and scroll down and there is a button to start the extended smart test. You may need to spin up the disk to enable the feature.

Link to comment
  • 1 month later...

Will refloat the thread as new problems have come.

 

@bjp999 @Frank1940 All the errors with my discs were solved with a simple sata cable swaping. I replaced all the cables *show in a post before with normal 1m sata cables. Since then no more errors.

Yesterday I got two power cuts in my house.

It showed my disk 1 as emuled. Re-build this disc and all ok.

 

Some minutes after another time the disc is emulated with 192 errors.

 

What must I do, do I re-rebuild the disc another time?

 

Attach diagnostics.

 

Thankyou

Gus

unraid-media-diagnostics-20170909-1434.zip

Link to comment

See the extract from the log below. Not everyone needs to be an expert syslog reader, but messages like "hard resetting link" are a very good indication of cabling problems! I expect all of these error are related to bad cabling of your drive.

 

You have three drives that are decidedly not happy - ata2, ata4 and ata6. Here is the info about those drives:

 

ata2.00: ATA-9: WDC WD40EFRX-68WT0N0,      WD-WCC4E3PKYRUL, 82.00A82, max UDMA/133 (disk1)

ata4.00: ATA-9: WDC WD40EFRX-68WT0N0,      WD-WCC4E1228876, 80.00A80, max UDMA/133 (disk2)
ata6.00: ATA-9: WDC WD40EFRX-68WT0N0,      WD-WCC4E4CLFP20, 82.00A82, max UDMA/133 (disk5)

 

Looks like disk1 dropped completely offline and then reconnected. I am not sure why it did that. Normally when a drive drops offline it is down for the count.

 

Might want to have @johnnie.black take a look to rule out controller issues. (It does not appear you are using a Marvell controller, so I am doubting it is a disk controller.)

 

What I strongly suggest is hot-swap cages - like CSE-M35T-1Bs and shorter cables. 1M is rather long. 0.5M (~18 inches) should be plenty long. 0.75M if you need a bit longer. (That's just a general recommendation - not sure if your cable length is a problem).

 

Sep  9 14:21:08 UNRAID-MEDIA kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata4: irq_stat 0x00400040, connection status changed
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata4: SError: { PHYRdyChg 10B8B DevExch }
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata4: hard resetting link
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata6: irq_stat 0x00400040, connection status changed
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata6: SError: { PHYRdyChg 10B8B DevExch }
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata6: hard resetting link
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata3: irq_stat 0x00400040, connection status changed
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata3: SError: { PHYRdyChg 10B8B DevExch }
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata3: hard resetting link
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata5: irq_stat 0x00400040, connection status changed
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata5: SError: { PHYRdyChg 10B8B DevExch }
Sep  9 14:21:08 UNRAID-MEDIA kernel: ata5: hard resetting link
Sep  9 14:21:09 UNRAID-MEDIA kernel: ata4: SATA link down (SStatus 0 SControl 310)
Sep  9 14:21:09 UNRAID-MEDIA kernel: ata4.00: link offline, clearing class 1 to NONE
Sep  9 14:21:09 UNRAID-MEDIA kernel: ata4: hard resetting link
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata4: SATA link down (SStatus 0 SControl 310)
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata4.00: link offline, clearing class 1 to NONE
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata4: hard resetting link
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata5: SATA link down (SStatus 0 SControl 300)
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata5.00: link offline, clearing class 1 to NONE
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata5: hard resetting link
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata2: irq_stat 0x00400040, connection status changed
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata2: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
Sep  9 14:21:10 UNRAID-MEDIA kernel: ata2: hard resetting link
Sep  9 14:21:11 UNRAID-MEDIA kernel: ata5: SATA link down (SStatus 0 SControl 300)
Sep  9 14:21:11 UNRAID-MEDIA kernel: ata5.00: link offline, clearing class 1 to NONE
Sep  9 14:21:11 UNRAID-MEDIA kernel: ata5: limiting SATA link speed to 1.5 Gbps
Sep  9 14:21:11 UNRAID-MEDIA kernel: ata5: hard resetting link
Sep  9 14:21:12 UNRAID-MEDIA kernel: ata2: SATA link down (SStatus 0 SControl 300)
Sep  9 14:21:12 UNRAID-MEDIA kernel: ata2: hard resetting link
Sep  9 14:21:13 UNRAID-MEDIA kernel: ata6: link is slow to respond, please be patient (ready=0)
Sep  9 14:21:13 UNRAID-MEDIA kernel: ata3: link is slow to respond, please be patient (ready=0)
Sep  9 14:21:14 UNRAID-MEDIA kernel: ata2: SATA link down (SStatus 0 SControl 300)
Sep  9 14:21:14 UNRAID-MEDIA kernel: ata2.00: link offline, clearing class 1 to NONE
Sep  9 14:21:14 UNRAID-MEDIA kernel: ata2: limiting SATA link speed to 1.5 Gbps
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2: hard resetting link
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata5.00: configured for UDMA/133
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata5: EH complete
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2: SATA link down (SStatus 0 SControl 310)
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2.00: disabled
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2: EH complete
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2.00: detaching (SCSI 3:0:0:0)
Sep  9 14:21:15 UNRAID-MEDIA kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
Sep  9 14:21:15 UNRAID-MEDIA kernel: sd 3:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Sep  9 14:21:15 UNRAID-MEDIA kernel: sd 3:0:0:0: [sdc] Stopping disk
Sep  9 14:21:15 UNRAID-MEDIA kernel: sd 3:0:0:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849600
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849608
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849616
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849624
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849632
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849640
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849648
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849656
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849664
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849672
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849680
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849688
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849696
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849704
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849712
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849720
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849728
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849736
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849744
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849752
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849760
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849768
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849776
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849784
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849792
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849800
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849808
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849816
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849824
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849832
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849840
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849848
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849856
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849864
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849872
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849880
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849888
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849896
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849904
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849912
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849920
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849928
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849936
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849944
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849952
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849960
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849968
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849976
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849984
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070849992
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850000
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850008
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850016
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850024
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850032
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850040
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850048
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850056
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850064
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850072
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850080
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850088
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850096
Sep  9 14:21:15 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850104
Sep  9 14:21:15 UNRAID-MEDIA rc.diskinfo[7939]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684
Sep  9 14:21:15 UNRAID-MEDIA rc.diskinfo[7939]: SIGHUP received, forcing refresh of disks info.
Sep  9 14:21:15 UNRAID-MEDIA rc.diskinfo[7939]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684
Sep  9 14:21:15 UNRAID-MEDIA rc.diskinfo[7939]: SIGHUP received, forcing refresh of disks info.
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2: irq_stat 0x00000040, connection status changed
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2: SError: { CommWake DevExch }
Sep  9 14:21:15 UNRAID-MEDIA kernel: ata2: hard resetting link
Sep  9 14:21:16 UNRAID-MEDIA kernel: ata4: link is slow to respond, please be patient (ready=0)
Sep  9 14:21:18 UNRAID-MEDIA kernel: ata6: COMRESET failed (errno=-16)
Sep  9 14:21:18 UNRAID-MEDIA kernel: ata6: hard resetting link
Sep  9 14:21:18 UNRAID-MEDIA kernel: ata3: COMRESET failed (errno=-16)
Sep  9 14:21:18 UNRAID-MEDIA kernel: ata3: hard resetting link
Sep  9 14:21:20 UNRAID-MEDIA kernel: ata4: COMRESET failed (errno=-16)
Sep  9 14:21:20 UNRAID-MEDIA kernel: ata4: hard resetting link
Sep  9 14:21:21 UNRAID-MEDIA kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep  9 14:21:21 UNRAID-MEDIA kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata6.00: configured for UDMA/133
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata6: EH complete
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata3.00: configured for UDMA/133
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata3: EH complete
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata4.00: configured for UDMA/133
Sep  9 14:21:22 UNRAID-MEDIA kernel: ata4: EH complete
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849600
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849608
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849616
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849624
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849632
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849640
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849648
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849656
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849664
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849672
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849680
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849688
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849696
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849704
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849712
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849720
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849728
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849736
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849744
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849752
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849760
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849768
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849776
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849784
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849792
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849800
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849808
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849816
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849824
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849832
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849840
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849848
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849856
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849864
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849872
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849880
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849888
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849896
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849904
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849912
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849920
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849928
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849936
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849944
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849952
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849960
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849968
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849976
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849984
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070849992
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850000
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850008
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850016
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850024
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850032
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850040
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850048
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850056
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850064
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850072
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850080
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850088
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850096
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850104
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850112
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850120
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850128
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850136
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850144
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850152
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850160
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850168
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850176
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850184
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850192
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850200
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850208
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850216
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850224
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850232
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850240
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850248
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850256
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850264
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850272
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850280
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850288
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850296
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850304
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850312
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850320
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850328
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850336
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850344
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850352
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 read error, sector=2070850360
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850112
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850120
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850128
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850136
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850144
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850152
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850160
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850168
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850176
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850184
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850192
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850200
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850208
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850216
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850224
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850232
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850240
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850248
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850256
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850264
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850272
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850280
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850288
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850296
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850304
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850312
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850320
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850328
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850336
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850344
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850352
Sep  9 14:21:22 UNRAID-MEDIA kernel: md: disk1 write error, sector=2070850360
Sep  9 14:21:23 UNRAID-MEDIA kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  9 14:21:23 UNRAID-MEDIA kernel: ata2.00: ATA-9: WDC WD40EFRX-68WT0N0,      WD-WCC4E3PKYRUL, 82.00A82, max UDMA/133
Sep  9 14:21:23 UNRAID-MEDIA kernel: ata2.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Sep  9 14:21:23 UNRAID-MEDIA kernel: ata2.00: configured for UDMA/133
Sep  9 14:21:23 UNRAID-MEDIA kernel: ata2: EH complete

 

Link to comment
37 minutes ago, bjp999 said:

Might want to have @johnnie.black take a look to rule out controller issues. (It does not appear you are using a Marvell controller, so I am doubting it is a disk controller.)

 

All disks are using the onboard Intel controller, that's as good as it gets, IMO most probable reasons for connection issues on multiple disks in this case and in order: cables, power supply or a bad controller, in this case the board.

Link to comment

Very annoying all those problems.

 

The truth is that since I replaced all cables I haven't had any problems (almost 2 months without any problem) and all the problems return with the 2 power cuts this saturday.

 

Will re-check cables and if the problems return will have to try an alternative.

 

Thankyou

Gus

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.