I'm building my second UnRAID server with two brand new 18TB drives (one parity) and one is saying "Device Is Disabled, Contents Emulated".  I ran tests on it and the drive seems totally fine.  Is there a way to re-add it to the array and disable the error?  I even tried running the two drives on a completely different machine and still got the error, so it's not a cable, SATA port, etc.

 

Also, is there a log I can post to help diagnose?  

Thanks for the help.

attach diagnostics to your NEXT post in this thread

Sorry about that.  Here you go...and thank you!

unraid-diagnostics-20220307-1647.zip

Sorry I didn't get back to this till now, surprised nobody else did.

 

15 hours ago, RGB0b said:

ran tests on it

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        59         -
# 2  Extended offline    Aborted by host               90%        59         -
# 3  Extended offline    Aborted by host               90%        58         -

You will have to disable spindown on the disk to get the extended test to complete.

 

SMART attributes for the disk look fine, though, except

199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    1

which is a connection problem. You should see a SMART warning for that one on the Dashboard page. Click on that warning and Acknowledge, it will warn again if the count increases.

 

Since you rebooted after the disk became disabled can't really see what caused it in syslog, but as noted connection problem.

 

Unraid disables a disk when a write to it fails. After it is disabled, the disk isn't accessed again because it is no longer in sync with parity. Instead, the contents of the disk are emulated from the parity calculation by reading all other disks. The data for the emulated disk can be read, and even written by updating parity, but the physical disk itself isn't used, only the results of the parity calculation.

 

The initial failed write, and any subsequent writes, can be recovered from the emulated disk by rebuilding the disk. Nothing you have tried will get the disk back in sync, you have to rebuild it.

 

Emulated disk1 mounts and has plenty of data. Its SMART looks good, so should be fine to rebuild to the same disk.

 

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

 

Since you have been unplugging and plugging the disks possibly you have fixed whatever connection problem you had.

 

During rebuild, on Main - Array Devices, you should see lots of writing to the rebuilding disk, lots of reading from all other array disks, and zero in the Errors column for all disks.

 

Thanks so much for the detailed response...and thanks for pointing me to the dashboard page to look for the thumb's down!  I think I looked everywhere else for it but there.  Once I hit that, I followed the rest of your instructions and its rebuilding now.

 

I think I know what caused it:  I was testing one of those low-end multi-drive eSATA enclosures with a cheap port multiplying eSATA PCIe card.  Not only was it slow, it would randomly only boot with one drive showing.  A reboot would then show two...and after one of the reboots, I got this error.  I'm never using one of those things again, unless it's single drive only!

 

If this ever happens to me (or anyone else) in the future, is there a way to try and skip rebuilding?  Essentially, the drive was untouched.