[Solved] Disk2 in the array does not work, smart command failed, device disabled

[Teza]

After installing unraid (first time user) disk 2 had a bad file system and it's 4GB capacity was not counted in the array.
Parity read/check had 968081081 errors after 1h 3m.

 

After a reboot, I formatted disk 2 and it became part of the array, and the array capacity increased to 12 TB.
Everything looked ok.

 

Then I tried to run a new parity-check, which I canceled after 160276490 errors, and because disk 2 status is now "Device is disabled, contents emulated".

 

Searched the forum and did a diagnostics test that gave me the following info on disk 2:

Quote

 

smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

filserver-diagnostics-20191120-1252.zip

 

Not sure how to proceed?

 

 

Unraid 6.7.2

 

Hardware setup:

Chieftec 19" 4U UNC-410F-B-OP
Corsair AX 1200i, 1200W PSU
ASUS Z9PE-D8 WS, 2xSocket-2011
2 ea Intel® Xeon® Processor E5-2660, 8-Core, 2.2GHz, 20MB
64 GB - Corsair Dominator DDR3 1600MHz
2 ea Intel® High Performance Liquid Cooling
3 ea ASUS GeForce GTX TITAN 6GB PhysX CUDA, 837MHz, 384bit
Plextor PX-B950SA Blue-Ray writer

2 ea Chieftec Backplane CMR-2131 SAS (2x 5,25" bays for 3x SATA/SAS HDDs/SSDs) (NEW)
5 ea Seagate IronWolf 4TB 3.5" NAS HDD (NEW)
Samsung SSD 860 EVO 500GB
Kingston MicroDuo USB 3.0 16GB (NEW)

 

Edited November 21, 2019 by Teza
Solved

[trurl]

On mobile now so haven't looked at Diagnostics yet.

 

Bad connections are much more common than bad disks. 

 

Check all connections, power and SATA, both ends, including any power splitters. 

 

Then post new Diagnostics. 

[JorgeB]

Don't use the onboard Marvell controller (4 grey ports), it's dropping disks, and they are known to do that, all 4 disks with errors are connected there.

[Teza]

3 minutes ago, johnnie.black said:

Don't use the onboard Marvell controller (4 grey ports), it's dropping disks, and they are known to do that, all 4 disks with errors are connected there.

What controller would be recommended for this setup?

[JorgeB]

Depends on how many extra ports you need after using the 6 Intel ones, for 2 extra ports get an Asmedia based controller, for 8 ports get an LSI HBA.

[Teza]

Intel ones is 3.0 Gb/s while the grey ones is 6.0 Gb/s.

Not sure if that matters with the cache drive?
 

 

[JorgeB]

You have 2 Intel SATA3 ports and 4 Intel SATA2 ports, connect any SSD to the SATA3 ports, for disks SATA2 is enough.

[JorgeB]

5 minutes ago, johnnie.black said:

4 Intel SATA2 ports

Correction, 8 Intel SATA2 ports, so you can use up to 10 devices with any additional controller.

[Teza]

1. Stop the array

2. Set disk 2 to no device

3. Start the array

4. Stop the array

5. Set disk 2 to...

6. Start the array

7. The disk will rebuild.

Followed this to get the drive back into the array.

Is it normal to use 6h 30m on this process with empty disks, or does it not matter how much that is stored, as all calculations must be redone anyway?

 

What testing should i do before storing data onto the array, when rebuilt?

 

[JorgeB]

32 minutes ago, Teza said:

or does it not matter how much that is stored, as all calculations must be redone anyway?

This.

 

 

[JorgeB]

32 minutes ago, Teza said:

What testing should i do before storing data onto the array, when rebuilt?

Copy some data and run a couple of parity checks, there should be always 0 sync errors.

[trurl]

2 hours ago, Teza said:

Is it normal to use 6h 30m

That seems a little faster than I might expect for rebuilding 4TB. Possibly it will take longer than the current estimate shown. I usually estimate 2-3 hours per TB.

[Teza]

It took 7 hours and 27 minutes.

Transferred 220 GB to the array and did a parity-check with no reported errors.

 

Thank you for fast help!