Jump to content

Freaking out!!! Parity Rebuild Problem


jonathansayeb

Recommended Posts

Hello all,

Here is my issue: Just followed this guide to replace my WD RED 6tb parity drive to a bigger one HGST NAS 8tb.

I started the parity sync and everything was rebuilding nicely at average 140 mb/s until few hours ago where it just went to 84.4 kb/s, yes that's not a typo i mean KB. The estimated finish sayd 935 days, 20 hours, 2 minutes!!!!!! (See attached screenshot)

Something definitely went wrong so i checked the log and it seems that my data drive number 4 has read errors which i think might be the cause of the problem.

Please tell me there is a solution without losing my datas.

 

Screen Shot 2017-07-04 at 2.19.43 PM.png

Screen Shot 2017-07-04 at 2.19.51 PM.png

Screen Shot 2017-07-04 at 2.20.21 PM.png

Screen Shot 2017-07-04 at 2.21.41 PM.png

Link to comment

Hello Is it what you are talking about?

 

ATA Error Count: 56 (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 56 occurred at disk power-on lifetime: 10591 hours (441 days + 7 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 28 72 11 e4  Error: UNC at LBA = 0x04117228 = 68252200

  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 78 5f 06 e4 08   4d+11:03:13.274  READ DMA
  c8 00 18 60 5f 06 e4 08   4d+11:03:13.229  READ DMA
  c8 00 08 58 5f 06 e4 08   4d+11:03:13.229  READ DMA
  c8 00 08 50 5f 06 e4 08   4d+11:03:13.228  READ DMA
  c8 00 08 48 5f 06 e4 08   4d+11:03:13.228  READ DMA

Error 55 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 f0 4b 3a e9  Error: UNC at LBA = 0x093a4bf0 = 154815472

  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 88 98 49 3a e9 08      03:38:57.548  READ DMA
  c8 00 58 40 49 3a e9 08      03:38:57.548  READ DMA
  c8 00 58 e8 48 3a e9 08      03:38:57.548  READ DMA
  c8 00 20 c8 48 3a e9 08      03:38:57.548  READ DMA
  c8 00 20 a8 48 3a e9 08      03:38:57.548  READ DMA

Error 54 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 90 61 2d e9  Error: UNC at LBA = 0x092d6190 = 153969040

  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 c0 68 4b 2d e9 08      03:38:26.231  READ DMA
  c8 00 90 d8 4a 2d e9 08      03:38:26.230  READ DMA
  c8 00 58 80 4a 2d e9 08      03:38:26.230  READ DMA
  c8 00 70 10 4a 2d e9 08      03:38:26.230  READ DMA
  c8 00 38 d8 49 2d e9 08      03:38:26.230  READ DMA

Error 53 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 20 a8 07 e9  Error: UNC at LBA = 0x0907a820 = 151496736

  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 28 60 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 40 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 20 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 00 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 e0 91 07 e9 08      03:37:05.098  READ DMA

Error 52 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 b0 83 03 e9  Error: UNC at LBA = 0x090383b0 = 151225264

  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 10 38 78 03 e9 08      03:36:48.641  READ DMA
  c8 00 18 20 78 03 e9 08      03:36:48.641  READ DMA
  c8 00 08 18 78 03 e9 08      03:36:48.641  READ DMA
  c8 00 20 f8 77 03 e9 08      03:36:48.641  READ DMA
  c8 00 10 e8 77 03 e9 08      03:36:48.641  READ DMA
Link to comment

would it be doable to stop the parity rebuild, leave the newly installed Hgst 8tb as parity drive, unassigned the disk 4 which seems to be faulty, power off, remove the faulty drive, replace with the previous parity drive ihad in the machine before (wd red 6tb), power on, rebuild the parity?

Link to comment

I would relax about possible data loss. I don't think you are at high risk at this point. Just don't do anything foolish!

 

What you posted is the very bottom of the smart report. Post the rest of it. Posting the diagnostics file is best. It will contain the smart reports.

 

So far what I am seeing is very consistent with a bad or lose cable. Do you have drive cages? Without them this is very very common.

 

If this is indeed a calling issue, and should cancel the rebuild, power down the server, secure the drive cables, and boot. You should be able to retry the parity update.

Link to comment

Thank you for your replies. It makes me worry less.

Here is the smart report downloaded.

 

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Purple
Device Model:     WDC WD10PURX-64E5EY0
Serial Number:    WD-WCC4J3SVAHE9
LU WWN Device Id: 5 0014ee 20c35fcc1
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Jul  4 19:20:37 2017 ICT
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:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
Total time to complete Offline 
data collection:         (13500) 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:      ( 154) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x303d)    SCT Status supported.
                    SCT Error Recovery Control 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   177   177   051    Pre-fail  Always       -       39801
  3 Spin_Up_Time            0x0027   133   132   021    Pre-fail  Always       -       4333
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       752
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       10601
 10 Spin_Retry_Count        0x0032   100   100   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       -       68
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       36
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       715
194 Temperature_Celsius     0x0022   113   094   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   189   182   000    Old_age   Always       -       1916
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: 56 (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 56 occurred at disk power-on lifetime: 10591 hours (441 days + 7 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 28 72 11 e4  Error: UNC at LBA = 0x04117228 = 68252200

  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 78 5f 06 e4 08   4d+11:03:13.274  READ DMA
  c8 00 18 60 5f 06 e4 08   4d+11:03:13.229  READ DMA
  c8 00 08 58 5f 06 e4 08   4d+11:03:13.229  READ DMA
  c8 00 08 50 5f 06 e4 08   4d+11:03:13.228  READ DMA
  c8 00 08 48 5f 06 e4 08   4d+11:03:13.228  READ DMA

Error 55 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 f0 4b 3a e9  Error: UNC at LBA = 0x093a4bf0 = 154815472

  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 88 98 49 3a e9 08      03:38:57.548  READ DMA
  c8 00 58 40 49 3a e9 08      03:38:57.548  READ DMA
  c8 00 58 e8 48 3a e9 08      03:38:57.548  READ DMA
  c8 00 20 c8 48 3a e9 08      03:38:57.548  READ DMA
  c8 00 20 a8 48 3a e9 08      03:38:57.548  READ DMA

Error 54 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 90 61 2d e9  Error: UNC at LBA = 0x092d6190 = 153969040

  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 c0 68 4b 2d e9 08      03:38:26.231  READ DMA
  c8 00 90 d8 4a 2d e9 08      03:38:26.230  READ DMA
  c8 00 58 80 4a 2d e9 08      03:38:26.230  READ DMA
  c8 00 70 10 4a 2d e9 08      03:38:26.230  READ DMA
  c8 00 38 d8 49 2d e9 08      03:38:26.230  READ DMA

Error 53 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 20 a8 07 e9  Error: UNC at LBA = 0x0907a820 = 151496736

  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 28 60 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 40 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 20 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 00 92 07 e9 08      03:37:05.098  READ DMA
  c8 00 20 e0 91 07 e9 08      03:37:05.098  READ DMA

Error 52 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 b0 83 03 e9  Error: UNC at LBA = 0x090383b0 = 151225264

  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 10 38 78 03 e9 08      03:36:48.641  READ DMA
  c8 00 18 20 78 03 e9 08      03:36:48.641  READ DMA
  c8 00 08 18 78 03 e9 08      03:36:48.641  READ DMA
  c8 00 20 f8 77 03 e9 08      03:36:48.641  READ DMA
  c8 00 10 e8 77 03 e9 08      03:36:48.641  READ DMA

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

Link to comment

The current pending sector count has incremented to over 1900. Indeed a very bad sign for that disk.

 

Before doing a disk or parity upgrade, it is a good idea to do a parity check, and examine the smart attributes to make sure the drives are healthy before the upgrade. The parity check generates a similar amount of system stress as a rebuild.

Link to comment

Thank you Johnie. Here is the diagnostic file.

I have just realized reading the report that the failing disk has almost no data in it and that most files have been written to the other 3 data disks. Just used krusader to see what are the files in that "disk4" and they are not that important since i have backups on an external drive.

 

Just to make sure of the process to not do anything foolish.

1- cancel the parity rebuild

2- stop the array

3- power off

4- replace disk4 with my old partity drive WD RED 6TB (the one before the 8tb hgst i've just installed)

5- power on

(6- should i preclear the wd red 6tb that comes in place of the failing disk)

7- rebuild the parity sync.

 

Thank you in advance for your help

 

 

 

ecserver-diagnostics-20170704-1930.zip

Link to comment

If there's no important data on disk4 you can do that.

 

On step 4 you'll need to do a new config:

Tools -> New Config -> Retain All

 

Then select assign old parity to disk4 and start the array to begin the parity sync.

Don't see a need to preclear old parity, you'll just need to format it after array start.

Link to comment

Archived

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

×
×
  • Create New...