Disk 3 in my array is disabled. It's a relatively new array, with new drives, and SMART shows them all to be healthy- although the SMART Extended test seems to end within secs of me starting, I'm not sure why. It could be the controller, I'm not sure.

 

The Unassigned Devices are in a USB Mediasonic drive bay I intend on copying over, I don't think that would cause a problem but the bay isn't always recognized by the array on reboot for some reason. 

monster-diagnostics-20221101-0721.zip

Nov  1 07:13:07 Monster kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov  1 07:13:10 Monster kernel: ata2: SATA link down (SStatus 0 SControl 300)
Nov  1 07:13:16 Monster kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov  1 07:13:16 Monster kernel: ata3: link is slow to respond, please be patient (ready=0)
Nov  1 07:13:20 Monster kernel: ata3: COMRESET failed (errno=-16)
Nov  1 07:13:20 Monster kernel: ata2: COMRESET failed (errno=-16)
Nov  1 07:13:21 Monster kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov  1 07:13:21 Monster kernel: ata2.00: supports DRM functions and may not be fully accessible
Nov  1 07:13:21 Monster kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov  1 07:13:21 Monster kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Nov  1 07:13:21 Monster kernel: ata3.00: configured for UDMA/133
Nov  1 07:13:21 Monster kernel: ata2.00: supports DRM functions and may not be fully accessible
Nov  1 07:13:21 Monster kernel: ata2.00: configured for UDMA/133

Also having issues with disks 1 and 2, do they share anything in common other than the controller, like a power splitter?

9 minutes ago, JorgeB said:

Nov  1 07:13:07 Monster kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov  1 07:13:10 Monster kernel: ata2: SATA link down (SStatus 0 SControl 300)
Nov  1 07:13:16 Monster kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov  1 07:13:16 Monster kernel: ata3: link is slow to respond, please be patient (ready=0)
Nov  1 07:13:20 Monster kernel: ata3: COMRESET failed (errno=-16)
Nov  1 07:13:20 Monster kernel: ata2: COMRESET failed (errno=-16)
Nov  1 07:13:21 Monster kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov  1 07:13:21 Monster kernel: ata2.00: supports DRM functions and may not be fully accessible
Nov  1 07:13:21 Monster kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov  1 07:13:21 Monster kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Nov  1 07:13:21 Monster kernel: ata3.00: configured for UDMA/133
Nov  1 07:13:21 Monster kernel: ata2.00: supports DRM functions and may not be fully accessible
Nov  1 07:13:21 Monster kernel: ata2.00: configured for UDMA/133

Also having issues with disks 1 and 2, do they share anything in common other than the controller, like a power splitter?

 

I noticed that. I think it's just the tower in general. Old Lenovo setup- I upgraded to a Seasonic 650W PS which should be more than enough for 4 drives and I run them right off the PS. I'll recheck, I don't think I'm splitting them. It's possible those drives are on the same power cable. I don't expect there is anything wrong with the drives. 

 

It might have something to do with the SATA/USB controller- it takes forever for the system to post when the USB bay is plugged in. 

 

Extended SMART self test on the drive seem to be working now so I'm running it. 

 

I'm going to upgrade my main PC eventually and migrate my Unraid array to my old one. 

Smart extended test seemed to be OK. I disconnected the Mediasonic external drive bay, rebooted, and now everything looks good. I suspect it's the USB controller. It's been a bit flakey and as I said it takes forever to boot/shutdown with the drive bay connected.

 

The disabled drive is empty, all of my data is still on Disk 1, it's not even full yet.  Should I reconstruct the array anyways? What's the best way to re-enable the drive?

monster-diagnostics-20221101-1548.zip

Edited November 1, 20223 yr by HDGuy

Yes, re-enabling the drive is the recommended way forward:

 

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself