manny

Members
  • Posts

    55
  • Joined

  • Last visited

Posts posted by manny

  1. Hi, I have unRaid Server Plus license and was running 8 drives without any cache drive. I was using a modest build and most was using to store my Blu ray rips and was playing them via Popcorn hour media player. The old config was,

    - Asus P8B75-M LE Mobo , Intel i3 2100T CPU, Corsair CX500 builder series, - G.Skill RipjawsX DDR3 8 GB (2 x 4 GB) PC RAM (F3-12800CL9D-8GBXL) 

     

    I recently moved to a different country and in the hurry i just brought only the hard drives and my unRaid USB drive. If I build a new setup and add these drives along with unRaid USB will it create any problem? 

     

    Also I need some suggestions on building a new systems, this time I would add Plex with max 2 streams and probably 1 VM (Linux) and NO gaming. Overall budget around $1000. 

     

    Has someone has any build in this price range? 

     

    Thanks a lot for your suggestions and input....

     

     

  2. My 3TB drive is precleared and I had to do swap-disable since my current parity is only 2TB. I have been reading the manuals and this is what i think I should do, please correct me if I am wrong.

     

    1. Currently one drive is disabled and drive has been marked as red

    2. Select the faulty drive and assign to no-device

    3. Stop the array

    4. Restart the array

    4. Change the current parity from the old parity drive and assign the new 3TB parity drive (sdf)

    5. Change the disabled drive - assign the old parity drive

    6. Start the array

     

    Is this good enough?

  3. I just completed the second preclear cycle and have Current_Pending_Sector = 2 and Raw_Read_Error_Rate=8, as per the explanation from RobJ above i think this should be ok right? I am planning to replace this drive as the Parity drive. Should I run one more cycle just to be on the safe side?

     

    The "Raw_Read_Error_Rate=8" is not a problem, because the raw value for that attribute is meaningless.  What's important is the VALUE for it, 200, which is perfect.

     

    What IS a problem is the "Current_Pending_Sector = 2".  As was stated above, that HAS to be zero.  If this SMART report occurred right after a Preclear then that is a bad sign.  Preclear it again, and if Current_Pending_Sector stays non-zero, I would not use that drive, it can't be trusted.

     

    Just completed the 3rd round of preclear, Current_Pending_Sector has become zero :-) Shall iI go ahead and use this drive?

     

    
    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       -       8
      3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1
      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       -       100
    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       -       1
    192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
    193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       7
    194 Temperature_Celsius     0x0022   119   118   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       -       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: 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.
    

     

    This was the final output from preclear

     

    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdf
    =               cycle 1 of 1, partition start on sector 1
    = Disk Pre-Clear-Read completed                                 DONE
    = Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
    = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
    = Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
    = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
    = Step 5 of 10 - Clearing MBR code area                         DONE
    = Step 6 of 10 - Setting MBR signature bytes                    DONE
    = Step 7 of 10 - Setting partition 1 to precleared state        DONE
    = Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
    = Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
    = Step 10 of 10 - Verifying if the MBR is cleared.              DONE
    = Disk Post-Clear-Read completed                                DONE
    Disk Temperature: 31C, Elapsed Time:  32:43:31
    ========================================================================1.15
    == WDCWD30EFRX-68EUZN0   
    == Disk /dev/sdf has been successfully precleared
    == with a starting sector of 1
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Temperature_Celsius =   119     120            0        ok          31
    No SMART attributes are FAILING_NOW
    
    2 sectors were pending re-allocation before the start of the preclear.
    2 sectors were pending re-allocation after pre-read in cycle 1 of 1.
    0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
    0 sectors are pending re-allocation at the end of the preclear,
        a change of -2 in the number of sectors pending re-allocation.
    0 sectors had been re-allocated before the start of the preclear.
    0 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.
    
    

  4. I just completed the second preclear cycle and have Current_Pending_Sector = 2 and Raw_Read_Error_Rate=8, as per the explanation from RobJ above i think this should be ok right? I am planning to replace this drive as the Parity drive. Should I run one more cycle just to be on the safe side?

    Disk: /dev/sdf
    smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build)
    Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Western Digital Red (AF)
    Device Model:     WDC WD30EFRX-68EUZN0
    LU WWN Device Id: 5 0014ee 6b002b183
    Firmware Version: 82.00A82
    User Capacity:    3,000,592,982,016 bytes [3.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: 3.0 Gb/s)
    Local Time is:    Tue Apr 28 08:28:42 2015 IST
    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: 		(41760) 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: 	 ( 418) minutes.
    Conveyance self-test routine
    recommended polling time: 	 (   5) minutes.
    SCT capabilities: 	       (0x703d)	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   200   200   051    Pre-fail  Always       -       8
      3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1
      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       -       66
    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       -       1
    192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
    193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       4
    194 Temperature_Celsius     0x0022   120   119   000    Old_age   Always       -       30
    196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
    197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       2
    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
    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.
    
    
    
    

  5. Hi All, I am trying to add a 3TB WD Red Drive to my array and the first preclear run just got completed, can someone check and let me know if this is fine? also how many preclear cycle should I run, 20 cycles might take lot of time:-) what would be the minimum safe number of runs?

     

    I got this one line in the final summary, is this a issue? : 1 sector was pending re-allocation after pre-read in cycle 1 of 1.

     

    I started the preclear with this command : preclear_disk.sh -A -M 4 /dev/sdf

    Summary.txt

    preclear_finish_2015-04-26.txt

  6. Sorry guys one last question. Currently I have 3 data disks and 1 Parity and all of them are 2TB WD Red. While shopping I found some good discount on the 3TB drives. I browsed the forum and found that I can replace the current faulty disk with the parity drive and replace the parity with higher capacity 3TB HDD using "swap-disable". I am running version 5.0.5. Is it ok if I do this? currently the failed disk is showing in Red dot.

     

    If get a 3TB drive and put that in the current parity drive slot and take the parity and put it in the failed disk slot and power up the unit , will it work? Will unRaid identify this change automatically and rebuild the parity and array automatically or do I have to do something.

     

    Thanks again for your inputs.

  7. Thanks all your reply. So I will initiate the RMA process. I don't have another drive to rebuild the array but guess i will buy one since i am almost 80% full in the current 3 data drives.

     

    One question, do you think i need to replace the power and SATA cable as well?

     

    Also i paid premium for WD Red drives hoping that they will last long guess this time will stick with WD green drives? any suggestions on the HDD?

     

     

     

     

  8. Hi, I am unraid noob so please excuse if there are any basic questions. I have been using unRaid for a while and its been great. I generally don't keep my server on and switch on only when needed. After a long time (72 days) I ran parity checked yesterday. Before running the parity check i copied some files to one of disks. During parity check there was lot of read and write errors in one of the HDD and unRaid moved it to disabled state. I checked the cables and restarted the array but it is still in disabled state.

     

    I ran both short and long smart test, I am attaching the syslog taken before the reboot and the smart status report. Can someone please look into it and see if this HDD needs replacement? This is 2 TB WD Red NAS drive and it is just 2 and half years old. I ran preclear when I purchased these HDD.

     

    Thanks a lot for your inputs and help.

     

    Statistics for /dev/sdd WDC_WD20EFRX-68AX9N0_WD-WMC300130454
    smartctl -a -d ata /dev/sdd
    smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build)
    Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Western Digital Red (AF)
    Device Model:     WDC WD20EFRX-68AX9N0
    LU WWN Device Id: 5 0014ee 058c461e8
    Firmware Version: 80.00A80
    User Capacity:    2,000,398,934,016 bytes [2.00 TB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    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: 3.0 Gb/s)
    Local Time is:    Wed Apr 15 09:40:53 2015 IST
    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:      ( 118)	The previous self-test completed having
    				the read element of the test failed.
    Total time to complete Offline 
    data collection: 		(25980) 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: 	 ( 263) minutes.
    Conveyance self-test routine
    recommended polling time: 	 (   5) minutes.
    SCT capabilities: 	       (0x70bd)	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   200   200   051    Pre-fail  Always       -       6
      3 Spin_Up_Time            0x0027   199   176   021    Pre-fail  Always       -       3050
      4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       821
      5 Reallocated_Sector_Ct   0x0033   199   199   140    Pre-fail  Always       -       30
      7 Seek_Error_Rate         0x002e   196   194   000    Old_age   Always       -       43
      9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       1868
    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       -       419
    192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       67
    193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       753
    194 Temperature_Celsius     0x0022   115   106   000    Old_age   Always       -       32
    196 Reallocated_Event_Count 0x0032   170   170   000    Old_age   Always       -       30
    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   200   200   000    Old_age   Offline      -       1
    
    SMART Error Log Version: 1
    No Errors Logged
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Extended offline    Completed: read failure       60%      1860         1724653656
    # 2  Short offline       Completed without error       00%      1858         -
    # 3  Extended offline    Completed without error       00%       410         -
    # 4  Short offline       Completed without error       00%        91         -
    
    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.
    

    syslog.zip

  9. Hi, I just added my 4th drive to the array and completed the 3rd round of preclear, can you please let me know if everything is fine with this disk? I am attaching the preclear finish report. Also having a one more issue, this disk is not showing in the device list and hence not able to add to the array....I had the trail version and recently purchased the plus revision...These are the few reference i see in syslog for the new HDD (SDD)

     

    Feb 18 08:35:47 Manitower kernel: scsi 4:0:0:0: Direct-Access     ATA      WDC WD20EFRX-68E 80.0 PQ: 0 ANSI: 5 (Drive related)
    Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related)
    Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] 4096-byte physical blocks (Drive related)
    Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Write Protect is off (Drive related)
    Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00 (Drive related)
    Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
    Feb 18 08:35:47 Manitower kernel:  sdd: sdd1 (Drive related)
    Feb 18 08:35:47 Manitower kernel:  sdc: sdc1 (Drive related)
    Feb 18 08:35:47 Manitower kernel: sd 2:0:0:0: [sdc] Attached SCSI disk (Drive related)
    Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Attached SCSI disk (Drive related)

     

    [EDIT] Attaching the syslog

    preclear_finish_WD-WCC4M1568296_2014-02-18.txt

    syslog-2014-02-18.zip

  10. Thanks a lot RobJ, this is very informative, thank you for taking time to write such a detailed explanation. Meanwhile I took HDD out of the array and dropped it in my windows 7 PC and ran HD tune. Not sure if this is a good idea but as you predicated it showed bunch of bad sectors at the very beginning. It has around 0.6% of damaged blocks as per HD tune. Should I go ahead and RMA the drive or run zero pass preclear?.....