Jump to content

Unraid no longer see's a drive?


mrfixit

Recommended Posts

I am stumped and I hope someone can shed some light on this odd situation.  I shut down my server (Unraid 6) to move it to a new location, did a proper shut down no smart errors or warnings before stopping the array and shutting it down.  When I got done moving it and booted back up I was greeted by an error that one of my 4tb red drives is missing.

 

I tested all of the cables and ports and they are fine, threw in a spare disk and it recognized the spare using the same sata port/cable and power cables (array is currently rebuilding).  When I put the drive the unraid is saying it is unable to see on an external dock on my windows 10 PC, windows see's it immediately through disk manager. I was able to reformat it and see it, ran the WD data lifeguard tools both the quick test and the extended text and it passed both. 

 

Does anyone have any idea why unraid is refusing to see the drive as attached or available?

 

I have attached my smart report form the unraid logs for anyone who wants the full smart file, otherwise here is the smart attributes.  Any help would be appreciated.

 

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      0

  3 Spin_Up_Time            0x0027  183  176  021    Pre-fail  Always      -      7850

  4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      719

  5 Reallocated_Sector_Ct  0x0033  200  200  140    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x002e  100  253  000    Old_age  Always      -      0

  9 Power_On_Hours          0x0032  090  090  000    Old_age  Always      -      7734

10 Spin_Retry_Count        0x0032  100  100  000    Old_age  Always      -      0

11 Calibration_Retry_Count 0x0032  100  100  000    Old_age  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      167

192 Power-Off_Retract_Count 0x0032  200  200  000    Old_age  Always      -      44

193 Load_Cycle_Count        0x0032  193  193  000    Old_age  Always      -      21302

194 Temperature_Celsius    0x0022  117  110  000    Old_age  Always      -      35

196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0030  100  253  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x0032  200  179  000    Old_age  Always      -      3806

200 Multi_Zone_Error_Rate  0x0008  100  253  000    Old_age  Offline      -      0

 

 

WDC_WD40EFRX-68WT0N0_WD-WCC4E0318421.txt

Link to comment

unRaid is seeing the 4TB WD drive

 

Nov 27 21:30:54 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E0318421 (sde) 3907018584

 

unRaid would have wound up disabling the drive initially after the move, so in order to get it working again, you've got to stop the array, set the disk to be "no device", start the array, stop the array, set the disk to be the WD disk, then start the array, so that the system will rebuild back onto itself

 

Link to comment

Ahh I didn't try selecting no device and then starting the array, and then stopping the array and reselecting it.  Once my rebuild with my spare disk is done I will test to see if unraid will detect the disk on a spare SATA port. 

 

Any idea why unraid disabled the device in the first place or what causes this issue?

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...