Jump to content

4.7 Pro Slow Parity Rebuild


ajgoyt

Recommended Posts

Hey guys running 4.7 Pro for well over a year and have not done any transferring or addons of any kind for well over 2 months, I went to rebuild parity the other day and noticed the parity is super slow @ 46 kb/sec minutes are crazy like 69,5279 left.  When i let it try to rebuild most of the day today it only got to 1.1% and disk1 had some errors.

 

All disks show green even disk1 with the errors! But if i refresh the page they (all disks except parity) are all blinking like they are asleep!

 

I have looked through the syslog and I saw some spindowns events, So i naturally changed the spindown to 9.0hours and it took.. But changing the spindown has no effect on speeding up the parity check.

 

Any ideas on what's happening?  I have attached the syslog

 

fyi - I can view all my shares from my win 7 machine....

 

Thanks

Aj

syslog-2012-01-21.txt

Link to comment

Ok tried to stop parity and it's super slow to react (per it had lots of errors on disk 1) and refreshing the webpage doesn't seem to help, finally tried another and now cannot get to the tower page.

 

also cannot see the server through the network, Hardrive LED is still solid...

 

appears to be a disk1 issue causing the slowness or maybe something to do with the spinup-down script!!!!!!

 

see the capture after tried to stop the parity I sat for 20 minutes waiting for all disks to unmount so i can shut it down properly. still will not shutdown properly (finally got the server shutdown after waiting along time)

 

question - can I disconnect disk1 and the try another parity check or?

 

Capture.PNG.b12e32d440288e0f7fbc5a5a62518cd9.PNG

Link to comment

Sorry for the late reply was traveling - This is a short smart test on disk1 - Looks like a sector errors.....

 

Kind of scared to start parity again. Just started a long smart test on drive 1, will be done in 4+ hours

 

Please advise?

 

 

=== START OF INFORMATION SECTION ===

Device Model:    Hitachi HDS723020BLA642

Serial Number:    MN1220F31JXH2D

Firmware Version: MN6OA5C0

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:  ATA-8-ACS revision 4

Local Time is:    Sat Jan 28 06:37:16 2012 PST

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: FAILED!

Drive failure expected in less than 24 hours. SAVE ALL DATA.

See vendor-specific Attribute list for failed Attributes.

 

General SMART Values:

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

was aborted by an interrupting command from host.

Auto Offline Data Collection: Enabled.

Self-test execution status:      ( 249) Self-test routine in progress...

90% of test remaining.

Total time to complete Offline

data collection: (18096) seconds.

Offline data collection

capabilities: (0x5b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

No 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: (  1) minutes.

Extended self-test routine

recommended polling time: ( 255) minutes.

SCT capabilities:       (0x003d) 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    0x000b  041  041  016    Pre-fail  Always      -      47540

  2 Throughput_Performance  0x0005  135  135  054    Pre-fail  Offline      -      84

  3 Spin_Up_Time            0x0007  253  253  024    Pre-fail  Always      -      65 (Average 216)

  4 Start_Stop_Count        0x0012  100  100  000    Old_age  Always      -      332

  5 Reallocated_Sector_Ct  0x0033  001  001  005    Pre-fail  Always  FAILING_NOW 2005

  7 Seek_Error_Rate        0x000b  100  100  067    Pre-fail  Always      -      0

  8 Seek_Time_Performance  0x0005  135  135  020    Pre-fail  Offline      -      26

  9 Power_On_Hours          0x0012  100  100  000    Old_age  Always      -      1288

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

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      156

192 Power-Off_Retract_Count 0x0032  100  100  000    Old_age  Always      -      336

193 Load_Cycle_Count        0x0012  100  100  000    Old_age  Always      -      336

194 Temperature_Celsius    0x0002  253  253  000    Old_age  Always      -      23 (Lifetime Min/Max 16/43)

196 Reallocated_Event_Count 0x0032  001  001  000    Old_age  Always      -      2352

197 Current_Pending_Sector  0x0022  100  100  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0008  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x000a  200  200  000    Old_age  Always      -      0

 

SMART Error Log Version: 1

No Errors Logged

 

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

Your disk has already failed. RMA it.

 

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

SMART overall-health self-assessment test result: FAILED!

Drive failure expected in less than 24 hours. SAVE ALL DATA.

5 Reallocated_Sector_Ct  0x0033  001  001  005    Pre-fail  Always  FAILING_NOW 2005

Link to comment

Probably not on the nocorrect, The good if you call it was there really wasn't anything on that drive.

 

Question - for now i would like to thrown in a smaller drive in disk1 - and then make a full parity check to back up all the other drives, Is this possible or do i have to use the same size disk or?

Link to comment

Probably not on the nocorrect, The good if you call it was there really wasn't anything on that drive.

 

Question - for now i would like to thrown in a smaller drive in disk1 - and then make a full parity check to back up all the other drives, Is this possible or do i have to use the same size disk or?

You can only use a smaller disk if you stop the array, set a new initial disk configuration, which immediately invalidates parity.  Then, completely re-calculate parity on the new disk configuration.

 

You'll be without parity protection until it completes the new parity calculation.

Link to comment

Archived

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

×
×
  • Create New...