Jump to content

cwr

Members
  • Content Count

    105
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cwr

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. replaced the 'faulty' drive with a new drive, in the same port, using the same cable, psu etc and everything is fine interesting that preclear didn't pickup a problem with the drive, will run it in a test box and see if that has any issues
  2. unraid 4.7, norco 4020 case, 19 drives, its a 1.1kw psu of some description doing a drive rebuild now onto a new drive it was probably 3 or 4 months between the time the drive first had a red dot, then i replaced it (array had no issues during this time) and putting the drive back in after thinking it was ok
  3. A while back my parity drive (2TB WDC Green) went into DISK_DSBL, so I replaced it and all was well I saw it sitting on the shelf a couple of days ago and decided to check it out. no smart errors, and the preclear for the drive came back fine. i ran preclear again, and again it came back fine put it into the array and all was well. i get home from work, my unRAID crashed and the drive was in DISK_DSBL again I've also run the western digital data lifeguard tool over it, and that reported no errors either. it was in a new slot in my unraid array with different cables etc. anyone have any ideas? smart report: Statistics for /dev/sdo 00P_WD-WCAZA6667485 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-WCAZA6667485 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 Jan 7 17:59:45 2013 EST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: (37680) 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 - 0 3 Spin_Up_Time 0x0027 172 169 021 Pre-fail Always - 6375 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 250 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 085 085 000 Old_age Always - 11275 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 - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 192 192 000 Old_age Always - 25937 194 Temperature_Celsius 0x0022 107 103 000 Old_age Always - 43 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 200 200 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 - 0 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 Short offline Completed without error 00% 11275 - 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.
  4. sweet. thanks for the quick reply!
  5. i have a weird question i couldnt find answered anywhere else, so hoping somebody has the answer. one of my drives died today, so i kicked off a rebuild and all is going well. while refreshing the unraid web interface I noticed the Writes count was going up for a separate (working fine) drive, which as it turns out was being caused by my wife using the WDTV player to watch tv would this be affecting the parity or the data being restored to drive being rebuilt? i imagine yes simply because a write on a drive == write on the parity drive?
  6. thats good to know. if we're running non-jumpered EARS drives, we have to live with the performance hit? lame
  7. so if i have some 4K drives without a jumper, i could just set the 4K alignment option, unassign + reassign drives to the same slot, rebuild from parity and everything should be fine?
  8. do not use wdidle3. people on other forums have contacted WD about this utility and been told using it would void the warranty on their drives
  9. -B doesnt work with the WD EARS drives, -S0 doesn't disable it totally, but seems like the best way to slow it down
  10. -S doesnt exactly stop it, however it slows it to about 8/hour from what my drives are showing other people seem to be running -B 255 which disables APM for the drive
  11. http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=5357 Disable Advanced power management using standard ATA command (Uses more power as turns off all low power modes but results in no load/unload cycles) Linux users add following (hdparm -B 255 /dev/sdX where X is your hard drive device). ATA users can disable APM usually controlled via BIOS and/or OS.
  12. Unless you are writing lots of small files odds are you would not notice at all. oh sweet! thanks
  13. out of curiosity, do any of the other advanced format/4K sector drives have the ability to be jumpered? every store i've called (in my city) is out of stock of the WD drives and won't have any more in for around 3-4 weeks. without paying the postage of about ~$40 my only other option is to use either a seagate or samsung. running a 4K sector drive as a parity drive will be painfully slow i imagine
  14. so, there will be no issues in the future if i have an advanced format drive now as my parity drive with a jumper?