Im trying to figure this out, this drive has a few more months of warranty. If anyone can assist that would be great as I'm unsure if this is a real problem or maybe a cable or something?

The drive was disabled by unraid automatically and is showing errors, however smart reports look ok i think other than 9800+ udma crc errors which i suspect are cable related?.

Attached is a screenshot of the 295052 errors on the web gui, I'm also attaching the smart report.

Also, whats the path forward here? I'm leaning towards swapping he cable and wiping out the drive and letting it rebuild.

--

[edit]

replacing the cable seems to have resolved this problem... 16TB takes a while, but everything is working well without issue now.

[/edit]

Edited January 14Jan 14 by Abzstrak

Please post the diagnostics.

2 minutes ago, JorgeB said:

Please post the diagnostics.

sry, just added that

37 minutes ago, Abzstrak said:

sry, just added that

Better to put them in a new post instead of editing old post. Since you did make a new post to tell us, we could tell there was something new in the thread. If you had just edited the old post without making a new post, we wouldn't have known about it and probably would not have visited the thread again.

Disk5 does have 8 reallocated but none pending so that should be fine, except for the obvious problems communicating with the drive. (UDMA...)

Emulated disk5 is mounted so should be OK to rebuild after you fix the connections.

Seems you don't have disks 1,3,4, I guess that is expected? So you have dual parity but only 2 data drives?

33 minutes ago, trurl said:

Disk5 does have 8 reallocated but none pending so that should be fine, except for the obvious problems communicating with the drive. (UDMA...)

Emulated disk5 is mounted so should be OK to rebuild after you fix the connections.

Seems you don't have disks 1,3,4, I guess that is expected? So you have dual parity but only 2 data drives?

Yeah I moved around drives a lot previously (when upgrading from smaller drives), but didn't bother trying to fix the enumeration since it didn't affect anything. This might be a good reason to go ahead and do that.

If you reorder disks you must rebuild parity2 (or remove it). Parity(1) will be valid whatever the order as long as no disks are removed or added.

1 minute ago, trurl said:

reorder disks

I really mean changing slots requires parity2 rebuild. The slot of each assigned disk is part of the parity2 algorithm.

7 minutes ago, trurl said:

Parity(1) will be valid whatever the order as long as no disks are removed or added

And another correction. Parity(1) will be valid whatever the slot of each data disk as long as none are added or removed. Parity2 can be added or removed and parity(1) will remain valid.

yeah the slots dont matter in the long run, ill leave it alone... now i recall why i left it like this
I think I'll just replace the cable, rebuild to it and see what happens.