Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Is this Normal? Unmountable drive during rebuild?

Featured Replies

Hi all.  Some funky stuff happened last night and my disk 8 reported 4 errors.  I noticed it was unmountable.  I am not sure I went about things in the correct order but it's now rebuilding but the FS is unmountable.  It should be XFS.  Is this normal?

 

Rebuilding an unmountable disk just rebuilds a disk that's unmountable! You need to start the array in Maintenance mode and run a file system check on it.

 

EDIT: You'll have to wait until tomorrow when it has finished rebuilding.

 

Rebuilding only does goed when a disk has physically died.. As long as unraid is doing what it is made for it will continuously update parity to reflect the status of all the drives, so if you get some kind of massive file system corruption then parity will be updated to make sure that corruption can be 100% replicated when you do a rebuild..

  • Author

I stopped the rebuild.  repaired xfs and started the rebuild.  does it look normal now?

Yes.

 

  • Community Expert

Your problem is fixed for now, but it was almost certainly caused by these disk errors:

 

 

Device Model:    ST8000AS0002-1NA17Z

Serial Number:    Z840C17N

 

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x000f  105  099  006    Pre-fail  Always      -      7414448

  3 Spin_Up_Time            0x0003  091  091  000    Pre-fail  Always      -      0

  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      10

  5 Reallocated_Sector_Ct  0x0033  100  100  010    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  077  060  030    Pre-fail  Always      -      57660596

  9 Power_On_Hours          0x0032  097  097  000    Old_age  Always      -      3071

10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      9

183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0

184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0

187 Reported_Uncorrect      0x0032  096  096  000    Old_age  Always      -      4

188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0

189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0

190 Airflow_Temperature_Cel 0x0022  072  064  045    Old_age  Always      -      28 (Min/Max 25/28)

191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

192 Power-Off_Retract_Count 0x0032  097  097  000    Old_age  Always      -      6468

193 Load_Cycle_Count        0x0032  094  094  000    Old_age  Always      -      13278

194 Temperature_Celsius    0x0022  028  040  000    Old_age  Always      -      28 (0 9 0 0 0)

195 Hardware_ECC_Recovered  0x001a  105  099  000    Old_age  Always      -      7414448

197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      1662 (217 191 0)

241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      28688252041

242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      154966124013

 

 

Error 4 occurred at disk power-on lifetime: 3066 hours (127 days + 18 hours)

  When the command that caused the error occurred, the device was active or idle.

 

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

 

LBA = 0x0fffffff doesn't looks like a valid sector and since there are no pending sectors it's probably not bad sectors, but it's a disk issue, I would give it a second chance but not a third, if errors re-occur I would consider replacing it.

  • Author

Agreed.  I have a new archive disk on the way.  When it arrives I will pre-clear it.  If it clears, I will replace this disk 8 and send it out for replacement since its still under warranty.

 

 

Your problem is fixed for now, but it was almost certainly caused by these disk errors:

 

 

Device Model:    ST8000AS0002-1NA17Z

Serial Number:    Z840C17N

 

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x000f  105  099  006    Pre-fail  Always      -      7414448

  3 Spin_Up_Time            0x0003  091  091  000    Pre-fail  Always      -      0

  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      10

  5 Reallocated_Sector_Ct  0x0033  100  100  010    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  077  060  030    Pre-fail  Always      -      57660596

  9 Power_On_Hours          0x0032  097  097  000    Old_age  Always      -      3071

10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      9

183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0

184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0

187 Reported_Uncorrect      0x0032  096  096  000    Old_age  Always      -      4

188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0

189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0

190 Airflow_Temperature_Cel 0x0022  072  064  045    Old_age  Always      -      28 (Min/Max 25/28)

191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

192 Power-Off_Retract_Count 0x0032  097  097  000    Old_age  Always      -      6468

193 Load_Cycle_Count        0x0032  094  094  000    Old_age  Always      -      13278

194 Temperature_Celsius    0x0022  028  040  000    Old_age  Always      -      28 (0 9 0 0 0)

195 Hardware_ECC_Recovered  0x001a  105  099  000    Old_age  Always      -      7414448

197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      1662 (217 191 0)

241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      28688252041

242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      154966124013

 

 

Error 4 occurred at disk power-on lifetime: 3066 hours (127 days + 18 hours)

  When the command that caused the error occurred, the device was active or idle.

 

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

 

LBA = 0x0fffffff doesn't looks like a valid sector and since there are no pending sectors it's probably not bad sectors, but it's a disk issue, I would give it a second chance but not a third, if errors re-occur I would consider replacing it.

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.