Good morning everyone, I am trying to add a new disk (3tb WD Red) to my array. On bootup the disk is listed under the unassigned drives, I choose a slot for it, hit start on the array and after the page refreshes, the disk is not in the assigned slot, nor in the unassigned disks area. It completely disappears from the system until I power it off and on again. What's going on here?

 

 

I'd power down and insert the USB into a Windows computer, and run a chkdsk on it, and correct errors if found. I expect there may be some corruption.

 

Could also be related to the drive is not securely connected and dropping offline. Could be a bad or loose cable.

 

Actually sounds like both problems may be happening.

If the suggested steps do not fix the issue, then post the diagnostics file (obtained via Tools->Diagnostics) so you can get more informed feedback.

I have attache the diagnostics here. Swapping cables and ports on my raid card made no difference. Thanks for the help!

 

 

dolores-diagnostics-20171117-1013.zip

Look like a bad disk:

 

Quote

Nov 17 09:28:59 Dolores kernel: ata9.00: failed to read native max address (err_mask=0x1)
Nov 17 09:28:59 Dolores kernel: ata9.00: HPA support seems broken, skipping HPA handling
Nov 17 09:28:59 Dolores kernel: ata9.00: ATA-9: WDC WD30EFRX-68EUZN0,      WD-WCC4N0ZD1HHH, 82.00A82, max UDMA/133
Nov 17 09:28:59 Dolores kernel: ata9.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Nov 17 09:28:59 Dolores kernel: ata9.00: both IDENTIFYs aborted, assuming NODEV
Nov 17 09:28:59 Dolores kernel: ata9.00: revalidation failed (errno=-2)
Nov 17 09:28:59 Dolores kernel: ata9.00: both IDENTIFYs aborted, assuming NODEV
Nov 17 09:28:59 Dolores kernel: ata9.00: revalidation failed (errno=-2)
Nov 17 09:28:59 Dolores kernel: ata9.00: both IDENTIFYs aborted, assuming NODEV
Nov 17 09:28:59 Dolores kernel: ata9.00: revalidation failed (errno=-2)
Nov 17 09:28:59 Dolores kernel: ata9.00: disabled