January 4, 201313 yr A week or so ago I noticed a lot of errors on one of my shitty 3TB drives. Today, I finally got around to pulling out the BRi10 SAS card and replacing with another IBM M1015 card. However, after bringing my unraid server back online, I have a red ball(ed) drive. I've ran the short test via the web UI as well as via smartctl. Pasted below so the result of the smart test (short) and it appears the drive is fine. Next steps? smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EZRX-00MMMB0 Serial Number: WD-WCAWZ2706097 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,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: Fri Jan 4 21:33:20 2013 Local time zone must be set--see zic m 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: (0x85) Offline data collection activity was aborted by an interrupting command from host. 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: (50760) 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 121 118 051 Pre-fail Always - 186223 3 Spin_Up_Time 0x0027 172 150 021 Pre-fail Always - 8391 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 269 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 098 098 000 Old_age Always - 1574 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 - 147 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 146 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 366 194 Temperature_Celsius 0x0022 122 118 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 - 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 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 1574 - # 2 Extended offline Aborted by host 90% 1574 - 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.
January 4, 201313 yr Author I followed the steps outlined on the wiki about re-enabling the drive. I just clicked the Rebuild button and it appears to have started. But the concern I have is that the data rate it says it is rebuilding at is 1.2MB/s, initially it was 700KB/s. That is concerning to me. ;/
January 5, 201313 yr It's hard to tell if the new hardware is causing the problem or a misconfigured or incompatible add-on is the issue. Shut-down and see my sig to disable all add-ons. Reboot and try the rebuild again. If it's still slow then post a new syslog. Why did you change the SATA card?
January 6, 201313 yr Author I swapped out the bri10 because the two drives that were on it were so slow. Stupid slow. But now everything is slow
January 7, 201313 yr Author It's hard to tell if the new hardware is causing the problem or a misconfigured or incompatible add-on is the issue. Shut-down and see my sig to disable all add-ons. Reboot and try the rebuild again. If it's still slow then post a new syslog. Why did you change the SATA card? As per your suggestion, I have disabled all addons and my go script was already at default. I've started the rebuild again and its going just as painfully slow. Total size: 3 TB Current position: 33.03 MB (0%) Estimated speed: 575.49 KB/sec Estimated finish: 86514 minutes Attached is the new syslog although small as I just started: Jan 7 01:24:23 Hoard emhttp: Restart SMB... Jan 7 01:24:23 Hoard emhttp: shcmd (56): killall -HUP smbd Jan 7 01:24:23 Hoard emhttp: shcmd (57): ps axc | grep -q rpc.mountd Jan 7 01:24:23 Hoard emhttp: _shcmd: shcmd (57): exit status: 1 Jan 7 01:24:23 Hoard emhttp: shcmd (58): /usr/local/sbin/emhttp_event svcs_restarted Jan 7 01:24:23 Hoard emhttp_event: svcs_restarted Jan 7 01:24:41 Hoard kernel: mdcmd (41): check NOCORRECT Jan 7 01:24:41 Hoard kernel: md: recovery thread woken up ... Jan 7 01:24:41 Hoard kernel: md: recovery thread rebuilding disk5 ... Jan 7 01:24:41 Hoard kernel: md: using 1536k window, over a total of 2930266532 blocks. * I replaced the SAS card because the IBM Bri10 is overall slower it seems. I believed it to be the reason it was performing so bad to begin with. I have a buddy with 5x2TB 5900 RPM drives and his performs stuff at 30MB/s where as mine has been near 2, 3, 5, etc. Very slow and not sure why. I have all 7200RPM drives except for parity and this one 3TB data drive. I have other drives I could replace them with all together and get all the 5900s out of the box. But getting this thing back to full green is my first priority. It isn't redballed any more, just orange.
January 7, 201313 yr Author Not sure if it matters, but my parity checks would usually progress at about 12-16MB/s. No changes since those parity checks... no new hardware except for the BRi10 replacement with M1015. But, the drive was seeing some errors before (posted in previous post) a few weeks ago. Wonder if its time to preclear another 3TB disk and replace it.
January 7, 201313 yr Author New syslog? Attached. However, I am curious. Considering I am only using a few hundred gig on this disk that is proving to be a pain in my ass, assuming it is in fact the disk's fault... Is it possible to move the data from it, off to another drive on the array and then remove it completely and rebuilt? Or is that pointless? Should I preclear another 3TB drive, stop the array, put it in, add it to the array, remove the existing 3TB disk, start the array and rebuild? Would that be the best solution? syslog.zip
January 7, 201313 yr Author Total size: 3 TB Current position: 20.06 GB (1%) Estimated speed: 609.54 KB/sec Estimated finish: 81179 minutes Its been running for a day or so now, man its so slow..
January 12, 201313 yr Your motherboard BIOS is 4 revisions old: You use BIOS V1.7 01/13/2009 with the latest available being 1.B dated 2010-06-21 The two m1015 are with very old firmware (P10) with P15 available now: mpt2sas0: LSISAS2008: FWVersion(10.00.02.00).
January 12, 201313 yr Author I know my mobo bios is old. Need to flash it. Been lazy. But it was fine prior
Archived
This topic is now archived and is closed to further replies.