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.

[Update] Preclear crashing server

Featured Replies

I recently had a redball and the smart report showed the drive throwing off a ton of errors and problems so I decided to replace it. I purchased 2 new WD green 2TB drives and began preclearing. For both cases about 12-15 hours preclear crashes and unraid becomes unresponsive. For both drives the smart reports were showing some problems.

 

I use 2 Supermicro AOC-SAT2-MV8 8-port SATA Controllers and have tried running the preclear off them and directly off the motherboard. I have tried a variety of different sata cables and connectors.

 

PSU: Corsair TX 750

 

Attached are the smart report and syslog after running preclear for about 15minutes:

 

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

  3 Spin_Up_Time            0x0027  171  169  021    Pre-fail  Always      -      6416

  4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      171

  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  100  100  000    Old_age  Always      -      16

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      -      169

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

193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      48

194 Temperature_Celsius    0x0022  116  116  000    Old_age  Always      -      34

196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      13

198 Offline_Uncorrectable  0x0030  100  253  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x0008  100  253  000    Old_age  Offline      -      0

 

My server has been unprotected for some time now and im quite worried I have a major issue here. Any help would be much appreciated .

syslog-2012-06-24.txt

Disk /dev/sdj is filling your syslog with media errors.  probably eventually running out of free memory, and crashing the server.

Jun 24 18:51:36 Tower emhttp: pci-0000:00:1f.5-scsi-1:0:0:0 host20 (sdj) WDC_WD20EARX-00PASB0_WD-WMAZA910041

 

Jun 24 19:03:06 Tower kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Jun 24 19:03:06 Tower kernel: ata20.00: BMDMA stat 0x25

Jun 24 19:03:06 Tower kernel: ata20.00: failed command: READ DMA

Jun 24 19:03:06 Tower kernel: ata20.00: cmd c8/00:00:88:20:eb/00:00:00:00:00/e4 tag 0 dma 131072 in

Jun 24 19:03:06 Tower kernel:          res 51/40:0f:70:21:eb/00:00:00:00:00/e4 Emask 0x9 (media error)

Jun 24 19:03:06 Tower kernel: ata20.00: status: { DRDY ERR }

Jun 24 19:03:06 Tower kernel: ata20.00: error: { UNC }

Jun 24 19:03:06 Tower kernel: ata20.00: configured for UDMA/133

Jun 24 19:03:06 Tower kernel: sd 20:0:0:0: [sdj] Unhandled sense code

Jun 24 19:03:06 Tower kernel: sd 20:0:0:0: [sdj] Result: hostbyte=0x00 driverbyte=0x08

Jun 24 19:03:06 Tower kernel: sd 20:0:0:0: [sdj] Sense Key : 0x3 [current] [descriptor]

Jun 24 19:03:06 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Jun 24 19:03:06 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Jun 24 19:03:06 Tower kernel:        04 eb 21 70

Jun 24 19:03:06 Tower kernel: sd 20:0:0:0: [sdj] ASC=0x11 ASCQ=0x4

Jun 24 19:03:06 Tower kernel: sd 20:0:0:0: [sdj] CDB: cdb[0]=0x28: 28 00 04 eb 20 88 00 01 00 00

  • Author

Any idea why that is happening? What can I do?

 

EDIT: Does this just mean I got incredibly unlucky with 2 DOA drives?

Any idea why that is happening? What can I do?

 

EDIT: Does this just mean I got incredibly unlucky with 2 DOA drives?

what does the smart report for WDC_WD20EARX-00PASB0_WD-WMAZA910041 show?

 

Yes, with as many drives as you have, odds are high to experience disk failures.

  • Author

I'm not particularly good at reading these but It doesn't look good :P

 

SMART status Info for /dev/sdj

 

smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Device Model:    WDC WD20EARX-00PASB0

Serial Number:    WD-WMAZA9100414

Firmware Version: 51.0AB51

User Capacity:    2,000,398,934,016 bytes

Device is:        Not in smartctl database [for details use: -P showall]

ATA Version is:  8

ATA Standard is:  Exact ATA specification draft version not indicated

Local Time is:    Mon Jun 25 11:10:54 2012 MDT

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

 

General SMART Values:

Offline data collection status:  (0x80) Offline data collection activity

was never started.

Auto Offline Data Collection: Enabled.

Self-test execution status:      ( 121) The previous self-test completed having

the read element of the test failed.

Total time to complete Offline

data collection: (37560) seconds.

Offline data collection

capabilities: (0x7b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities:            (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability:        (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: (  2) minutes.

Extended self-test routine

recommended polling time: ( 255) minutes.

Conveyance self-test routine

recommended polling time: (  5) minutes.

SCT capabilities:       (0x3035) SCT Status supported.

SCT Feature Control supported.

SCT Data Table supported.

 

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      -      252

  3 Spin_Up_Time            0x0027  173  169  021    Pre-fail  Always      -      6341

  4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      172

  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  100  100  000    Old_age  Always      -      32

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      -      170

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

193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      59

194 Temperature_Celsius    0x0022  119  115  000    Old_age  Always      -      31

196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      47

198 Offline_Uncorrectable  0x0030  100  253  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x0008  100  253  000    Old_age  Offline      -      0

 

SMART Error Log Version: 1

ATA Error Count: 60 (device log contains only the most recent five errors)

CR = Command Register [HEX]

FR = Features Register [HEX]

SC = Sector Count Register [HEX]

SN = Sector Number Register [HEX]

CL = Cylinder Low Register [HEX]

CH = Cylinder High Register [HEX]

DH = Device/Head Register [HEX]

DC = Device Command Register [HEX]

ER = Error register [HEX]

ST = Status register [HEX]

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.

 

Error 60 occurred at disk power-on lifetime: 16 hours (0 days + 16 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 08 d8 1c bd e5  Error: UNC 8 sectors at LBA = 0x05bd1cd8 = 96279768

 

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name

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

  c8 00 08 d8 1c bd e5 08      00:40:23.467  READ DMA

  ec 00 00 00 00 00 a0 08      00:40:23.447  IDENTIFY DEVICE

  ef 03 46 00 00 00 a0 08      00:40:23.447  SET FEATURES [set transfer mode]

 

Error 59 occurred at disk power-on lifetime: 16 hours (0 days + 16 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 08 d8 1c bd e5  Error: UNC 8 sectors at LBA = 0x05bd1cd8 = 96279768

 

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name

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

  c8 00 08 d8 1c bd e5 08      00:40:20.779  READ DMA

  ec 00 00 00 00 00 a0 08      00:40:20.759  IDENTIFY DEVICE

  ef 03 46 00 00 00 a0 08      00:40:20.759  SET FEATURES [set transfer mode]

 

Error 58 occurred at disk power-on lifetime: 16 hours (0 days + 16 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 08 d8 1c bd e5  Error: UNC 8 sectors at LBA = 0x05bd1cd8 = 96279768

 

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name

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

  c8 00 08 d8 1c bd e5 08      00:40:18.092  READ DMA

  ec 00 00 00 00 00 a0 08      00:40:18.071  IDENTIFY DEVICE

  ef 03 46 00 00 00 a0 08      00:40:18.052  SET FEATURES [set transfer mode]

 

Error 57 occurred at disk power-on lifetime: 16 hours (0 days + 16 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 08 d8 1c bd e5  Error: UNC 8 sectors at LBA = 0x05bd1cd8 = 96279768

 

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name

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

  c8 00 08 d8 1c bd e5 08      00:40:15.384  READ DMA

  ec 00 00 00 00 00 a0 08      00:40:15.365  IDENTIFY DEVICE

  ef 03 46 00 00 00 a0 08      00:40:15.365  SET FEATURES [set transfer mode]

 

Error 56 occurred at disk power-on lifetime: 16 hours (0 days + 16 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 08 d8 1c bd e5  Error: UNC 8 sectors at LBA = 0x05bd1cd8 = 96279768

 

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name

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

  c8 00 08 d8 1c bd e5 08      00:40:12.697  READ DMA

  ec 00 00 00 00 00 a0 08      00:40:12.677  IDENTIFY DEVICE

  ef 03 46 00 00 00 a0 08      00:40:12.677  SET FEATURES [set transfer mode]

 

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline      Completed: read failure      90%        32        82518388

# 2  Short offline      Completed: read failure      90%        32        82518388

 

SMART Selective self-test log data structure revision number 1

SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

    1        0        0  Not_testing

    2        0        0  Not_testing

    3        0        0  Not_testing

    4        0        0  Not_testing

    5        0        0  Not_testing

Selective self-test flags (0x0):

  After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

 

 

You are right. 47 sectors pending re-allocation.

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      47

  • Author

Picked up 2 new drives and trying again. 2 hours into preclear and things seem a bit better although I did notice a few errors in my syslog that baffle me.

 

SMART Attributes Data Structure revision number: 16Vendor 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  189  189  021    Pre-fail  Always      -      5516 

4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      11

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  100  100  000    Old_age  Always      -      1

10 Spin_Retry_Count        0x0032  100  253  000    Old_age  Always      -      0

11 Calibration_Retry_Count 0x0032  100  253  000    Old_age  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      8

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

193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      15

194 Temperature_Celsius    0x0022  118  118  000    Old_age  Always      -      32

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  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x0008  100  253  000    Old_age  Offline      -      0

SMART Error Log Version: 1No Errors Logged

syslog-2012-06-25.txt

  • Author

First of the new drives has finished preclear with flying colours. I believe this thread is solved. Thanks Joe!

  • 2 weeks later...
  • Author

Finally got around to running a preclear on the failed drive that caused my problems. I just want to verify this drive is toast:

 

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      -      285

  3 Spin_Up_Time            0x0027  253  163  021    Pre-fail  Always      -      891

  4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      763

  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  071  071  000    Old_age  Always      -      21624

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      -      153

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

193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      763

194 Temperature_Celsius    0x0022  122  108  000    Old_age  Always      -      28

196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      6

198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      6

199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x0008  200  200  000    Old_age  Offline      -      0

 

Syslog attached (filled with errors)

syslog-2012-07-04.zip

  • Author

I hope it's ok that I bump this. Sorry to be a bother everyone

Repeat pre-clear until the pending sectors stays at zero for 2 consecutive runs.

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.