February 25, 201115 yr Hi, i ran an unmenu verify but don't correct over night, and it's returned 0 errors, but has spat out 48 disk errors on the parity drive. Now from what i can tell from the system log it looks as though the errors occurred towards the end for the drive, so I'm guessing it's not a cable problem? I'd imagine if it was the cable the errors would of been more frequent then just a few dozen blocks near the end together. So i'm guessing it's physical? Anyway before i get to carried swapping cables, i'll check what you experts say. I've attached the system log starting from last night, would be too big to attach the whole thing as it's been up for a few weeks. if more is needed let me know. Thanks abridged_syslog.txt
February 25, 201115 yr Author What does SMART for sdh report? Statistics for /dev/sdh SAMSUNG_HD154UI_S1XWJ9ASB00115 smartctl -a -d ata /dev/sdh smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD154UI Serial Number: S1XWJ9ASB00115 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Fri Feb 25 11:23:58 2011 EST ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (19417) 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: ( 34) minutes. SCT capabilities: (0x003f) 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 0x000f 100 099 051 Pre-fail Always - 16 3 Spin_Up_Time 0x0007 072 072 011 Pre-fail Always - 9320 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 727 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 42 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 095 095 015 Pre-fail Offline - 16876 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 9406 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 78 13 Read_Soft_Error_Rate 0x000e 100 099 000 Old_age Always - 16 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 19 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 055 000 Old_age Always - 30 (Lifetime Min/Max 26/33) 194 Temperature_Celsius 0x0022 070 053 000 Old_age Always - 30 (Lifetime Min/Max 24/36) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1150713847 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 42 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 099 000 Old_age Always - 60 201 Soft_Read_Error_Rate 0x000a 099 099 000 Old_age Always - 3 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% 9406 - # 2 Short offline Aborted by host 10% 4293 - # 3 Short offline Completed without error 00% 2732 - 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.
February 25, 201115 yr do a long test? Before you do a long test, disable any spin-down-dimer for that disk. It will abort the test otherwise when you ask the drive to spin down in the middle. that disk has 47 reallocated sectors. Nothing too bad, but watch it in the future and if the number increases, constantly, replace the drive. After the long test, get another SMART report. Joe L.
February 25, 201115 yr Author do a long test? that disk has 47 reallocated sectors. Nothing too bad, but watch it in the future and if the number increases, constantly, replace the drive. Joe L. as in bad sectors? have pulled the server out and hooked upto my monitor, and ran the samsung diag tools just ran the short test, i'll do a full surface scan on it tonight when i goto bed, but it passed the quick test. on another topic from yesterday about the hpa thing, i updated the bios and it gave the option to disable it, plus i did a save cmos to bios thing.. so hoping that fixes the part about it coming back in the event of battery going flat that was commented about
February 25, 201115 yr Make sure that you resolve the HPA issue fully. If your board does not turn off HPA by default then the problem will reoccur when CMOS is reset for any reason, e.g., the CMOS battery dies. Having the option to disable it is not good enough; the board must default to the off setting. Sometimes a BIOS update will fix the problem. Although, others have replaced their MB due to this problem. Motherboards the have HPA enabled by default are not suitable for unRAID. You don't want to be surprised by HPA in the future.
February 26, 201115 yr Author Make sure that you resolve the HPA issue fully. If your board does not turn off HPA by default then the problem will reoccur when CMOS is reset for any reason, e.g., the CMOS battery dies. Having the option to disable it is not good enough; the board must default to the off setting. Sometimes a BIOS update will fix the problem. Although, others have replaced their MB due to this problem. Motherboards the have HPA enabled by default are not suitable for unRAID. You don't want to be surprised by HPA in the future. Well I just tested this, connected a couple more power and sata cables, getting everything prepped for the new drives this afternooon. And while i was doing all that i pulled the battery and turned the power off, to simulate what would happen. When i turned it back I, i was hit by the gigabyte logo thing which is normal disabled... so first thought was buggar, but then after that it presented a menu with something like cmos error (can't remember exactly what it said but anyway), it had a list of default and last known good config, and a few others that you could save, in the save cmos to bios thing that i did. It was defaulted at last known good with 15sec count down.. let it go and bam restarted with all the previous settings, with all the extras that i have disabled, re-disabled. So i'm not going to have to sacrifice the good asus board in my main I also ran the full surface scan on the parity drive using the samsung utiltiy last night.. and it came back clean.. so hopefully it was just a glitch.
Archived
This topic is now archived and is closed to further replies.