Rebuilt parity disk multiple times with success then a day or so later get parity disk disabled (Unraid 6.5.2)


Recommended Posts

I've tried researching the error codes I'm getting on google and the unraid forum but the various posts I've found seem to be slightly different situations then what I have. I've attached my diagnostics log and smart report for the parity drive that I'm having issues with (I have 2 drive parity, its parity 1 that I'm having the issue with, not parity 2).

 

The drive in question doesn't show any SMART errors, at least I don't think it is if I'm reading it correctly. All the drives in the array are 8TB WD easystore drives and I haven't had them for too terribly long maybe 2-3 months. But only started using them 2 months ago, only been using Unraid for 1 month. Everything went well the first 3 weeks I was using Unraid with no issues on the array. But here recently I started having a strange problem where the parity disk will get marked as disabled. Then Ill google some of the messages and not find anything that leads me to believe that the drive is bad. So then Ill stop the array, turn it back on and tell it to rebuild the parity on the same 8TB parity disk. The parity rebuild will eventually succeed and not find any issues. then later on maybe 12-24 hours later, the parity disk will end up getting marked disabled again. 

 

I thought the maybe the parity disk was being marked as disabled during times when I might have otherwise been tinkering with stuff around the servers and perhaps I bumped a wire. So I wanted to rule that out before I posted on the forum so I made sure all the connections were firm on the drives and kicked off the parity rebuild which succeeded again. Then the issue happened again where 12-24 hours later the parity disk was marked as disabled. Finally, I thought that maybe I messed up something a week prior to all this when I had previously added in a 3TB, 5TB, and 8TB disk to the server. So decided I would just restart everything with a new config via the Tools > New Config option. I did that and told it to rebuilt both parity 1 and parity 2 disk. Then after the parity was rebuilt, the same thing happened, 12-24 hours later the parity 1 was marked as disabled.

 

Please note, every time the parity 1 disk is getting disabled, the parity 2 disk has always remained healthy without any issues.

 

So now I'm just confused. I'm pretty sure the parity disk is good because I dont see errors on the SMART report. When I try googling the error messages that are happening during the problem I didn't have much luck in helping my problem. So hoping one of you can review and assist.

 

To help you find the applicable times quickly in the error reports, here is the message in the upper right corner of Unraid:

unRAID Parity disk error: 04-06-2018 03:02 Alert [VMUNRAID] - Parity disk in error state (disk dsbl) WDC_WD80EMAZ-00WJTA0_7SGHEGHC (sdk)


Details about setup:
Unraid Version: 6.5.2

 

Plugins installed:
Dynamix SSD TRIM
Statistics
rclone
CA Cleanup Appdata
File Activity
User Scripts
Dynamix Cache Directories
CA Mover Tuning
Fix Common Problems
Tips and Tweaks
Preclear Disks
Community Applications
Unassigned Devices
ControlR
unBALANCE
openVMTools_auto

Dockers installed:
cadvisor
dupeGuru
Ombi
Plex
Tautulli
Duplicati
Jackett

 

Server Specs
Dell Precision T7610 Tower Workstation
2 x Intel Xeon CPU E5-2650 v2 @ 2.60GHz
128 GB Ram 

 

Server OS: VMWare ESXi version: 6.5.0 (Unraid runs as a VM on my ESXi host. Unraid still runs off USB)
ESXi build number: 7388607

 

Unraid has the following allocated to it:

12 vCpus

20 GB of memory

 

 

 

Jun  4 01:31:22 VMUnraid kernel: mdcmd (81): spindown 1
Jun  4 03:01:06 VMUnraid kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00)
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 4b 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467449688
Jun  4 03:01:06 VMUnraid kernel: md: disk0 write error, sector=2467449624
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 4f 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467450712
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 0
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#2 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#2 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#2 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 53 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467451736
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 57 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467452760
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 5b 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467453784
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 5f 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467454808
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 63 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467455832
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 67 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467456856
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 Sense Key : 0x2 [current] 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 
Jun  4 03:01:06 VMUnraid kernel: sd 34:0:6:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 93 12 6b 58 00 00 04 00 00 00
Jun  4 03:01:06 VMUnraid kernel: print_req_error: I/O error, dev sdk, sector 2467457880
Jun  4 03:01:06 VMUnraid kernel: md: disk0 write error, sector=2467449632
Jun  4 03:01:06 VMUnraid kernel: md: disk0 write error, sector=2467449640
Jun  4 03:01:06 VMUnraid kernel: md: disk0 write error, sector=2467449648
Jun  4 03:01:06 VMUnraid kernel: md: disk0 write error, sector=2467449656
Jun  4 03:01:06 VMUnraid kernel: md: disk0 write error, sector=2467449664

 

There are 2,048 of these "disk0 write error, sector=" errors.  See attachments for full list.

 

Everyone's help is very much greatly appreciated.

 

 

 

 

Edited by ispaydeu
Link to comment
5 hours ago, trurl said:

 

Do you mean you have shucked these external drives, or do you mean you are trying to use USB connected external drives for the array?

They are all shucked drives.

 

Also, they are plugged directly into the 16 port LSI HBA I have which is in PCI pass through from VMWare ESXI to the unraid VM. Everything was running fine for the first 3 weeks so not sure whats going on this last week that after each rebuild its succeeding then later having issues. Especially since I dont see where in my diagnostics that its reporting errors at the time that its occurring but I'm not sure.

 

Thoughts?

Link to comment

I tried a rebuild again this morning and this time it failed a couple hours into the rebuild. Seems to be same issue as before. SMART report doesnt show any errors. Can anyone give some guidance? I've attached the diagnostics from this morning

 

 

 

un  5 11:16:55 VMUnraid ntpd[2322]: receive: Unexpected origin timestamp 0xdec127e7.8a6c7435 does not match aorg 0000000000.00000000 from [email protected] xmt 0xdec127e7.8eb2502f
Jun  5 11:18:20 VMUnraid kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00)
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 Sense Key : 0x2 [current] 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 ASC=0x4 ASCQ=0x0 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c6 69 59 18 00 00 04 00 00 00
Jun  5 11:18:20 VMUnraid kernel: print_req_error: I/O error, dev sdh, sector 3328792856
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792792
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 Sense Key : 0x2 [current] 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 ASC=0x4 ASCQ=0x0 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c6 69 5d 18 00 00 04 00 00 00
Jun  5 11:18:20 VMUnraid kernel: print_req_error: I/O error, dev sdh, sector 3328793880
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 Sense Key : 0x2 [current] 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 ASC=0x4 ASCQ=0x0 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c6 69 61 18 00 00 04 00 00 00
Jun  5 11:18:20 VMUnraid kernel: print_req_error: I/O error, dev sdh, sector 3328794904
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 Sense Key : 0x2 [current] 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 ASC=0x4 ASCQ=0x0 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c6 69 65 18 00 00 04 00 00 00
Jun  5 11:18:20 VMUnraid kernel: print_req_error: I/O error, dev sdh, sector 3328795928
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 Sense Key : 0x2 [current] 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 ASC=0x4 ASCQ=0x0 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c6 69 69 18 00 00 04 00 00 00
Jun  5 11:18:20 VMUnraid kernel: print_req_error: I/O error, dev sdh, sector 3328796952
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 Sense Key : 0x2 [current] 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 ASC=0x4 ASCQ=0x0 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c6 69 6d 18 00 00 04 00 00 00
Jun  5 11:18:20 VMUnraid kernel: print_req_error: I/O error, dev sdh, sector 3328797976
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 Sense Key : 0x2 [current] 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 ASC=0x4 ASCQ=0x0 
Jun  5 11:18:20 VMUnraid kernel: sd 34:0:20:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c6 69 71 18 00 00 02 00 00 00
Jun  5 11:18:20 VMUnraid kernel: print_req_error: I/O error, dev sdh, sector 3328799000
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792800
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792808
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792816
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792824
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792832
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792840
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792848
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792856
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792864
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792872
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792880
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792888
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792896
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792904
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792912
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792920
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792928
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792936
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792944
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792952
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792960
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792968
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792976
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792984
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328792992
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793000
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793008
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793016
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793024
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793032
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793040
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793048
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793056
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793064
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793072
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793080
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793088
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793096
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793104
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793112
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793120
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793128
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793136
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793144
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793152
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793160
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793168
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793176
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793184
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793192
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793200
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793208
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793216
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793224
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793232
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793240
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793248
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793256
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793264
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793272
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793280
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793288
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793296
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793304
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793312
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793320
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793328
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793336
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793344
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793352
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793360
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793368
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793376
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793384
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793392
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793400
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793408
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793416
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793424
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793432
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793440
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793448
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793456
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793464
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793472
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793480
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793488
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793496
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793504
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793512
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793520
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793528
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793536
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793544
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793552
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793560
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793568
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793576
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793584
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793592
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793600
Jun  5 11:18:20 VMUnraid kernel: md: disk0 write error, sector=3328793608

 

Edited by ispaydeu
Link to comment
On 6/5/2018 at 11:47 AM, johnnie.black said:

Connect that disk to a different controller with different cables and try again.

Ok will do. I was starting to think it might be the cable as well since there didn't seem to be any errors on the disk.

 

For now, I decided to switch out that disk all together with a different 8TB drive (Seagate 8TB drive, non SMR, 7200 RPM). So far the array rebuilt just fine. Running a parity check now to see how it goes hopefully all will be ok. On the old 8TB WD Easystore shucked drive its currently still on the old wire it was on but I did remove wire and insert again. I have a 3 pass preclear running on it now to see if it comes up with any errors. If not Ill just put it in as a data drive for the array.

 

Ill report back to let everyone know if the Seagate drive runs into any issues or not.

Link to comment

And yet another failure. The array rebuilt just fine. Again, this time I told it to use an entirely different hard drive for Parity 1, a seagate drive that was already precleared. The array rebuilt just fine, went 12 hours without any issues. Then I decided I better run a parity check to make sure everything is okay, and then in the middle of the parity check the parity drive was disabled.

 

This seagate drive that I'm using is on an entirely different cable then the other one parity drive I had been using. 

 

Diagnostics and smart report attached. 

 

Any other ideas on what is wrong?

 

 

Edited by ispaydeu
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.