December 8, 200916 yr Hey all, I'm trying to push over 100+GB to my unRAID server and I've been having problems where the Windows says that the location is no longer available. I checked the systemlog and there are a lot of errors... I am copying this to a new 1.5TB hard drive that I pre-cleared with Joe's script. What do all these errors means? I had to use Mega upload as my systemlog is too large for the forum: http://www.megaupload.com/?d=MJRWNHEJ Thank you, Mike
December 8, 200916 yr Hey all, I'm trying to push over 100+GB to my unRAID server and I've been having problems where the Windows says that the location is no longer available. I checked the systemlog and there are a lot of errors... I am copying this to a new 1.5TB hard drive that I pre-cleared with Joe's script. What do all these errors means? I had to use Mega upload as my systemlog is too large for the forum: http://www.megaupload.com/?d=MJRWNHEJ Thank you, Mike The errors start here with the drive /dev/sdc not being accessible. The "read stripe" errors are just the result of not being able to communicate with the drive. Dec 8 17:01:32 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 Dec 8 17:01:32 Tower kernel: ata3.00: irq_stat 0x40000008 Dec 8 17:01:32 Tower kernel: ata3.00: cmd 60/90:00:f7:96:e9/03:00:8c:00:00/40 tag 0 ncq 466944 in Dec 8 17:01:32 Tower kernel: res 51/40:e9:9e:98:e9/00:01:8c:00:00/40 Emask 0x409 (media error) <F> Dec 8 17:01:32 Tower kernel: ata3.00: status: { DRDY ERR } Dec 8 17:01:32 Tower kernel: ata3.00: error: { UNC } Dec 8 17:01:32 Tower kernel: ata3.00: configured for UDMA/133 Dec 8 17:01:32 Tower kernel: ata3: EH complete Dec 8 17:01:32 Tower kernel: sd 3:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Dec 8 17:01:32 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Dec 8 17:01:32 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Dec 8 17:01:32 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 8 17:01:34 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Dec 8 17:01:34 Tower kernel: ata3.00: irq_stat 0x40000008 Dec 8 17:01:34 Tower kernel: ata3.00: cmd 60/90:08:f7:96:e9/03:00:8c:00:00/40 tag 1 ncq 466944 in Dec 8 17:01:34 Tower kernel: res 41/40:f1:96:98:e9/8a:01:8c:00:00/40 Emask 0x409 (media error) <F> Dec 8 17:01:34 Tower kernel: ata3.00: status: { DRDY ERR } Dec 8 17:01:34 Tower kernel: ata3.00: error: { UNC } Dec 8 17:01:34 Tower kernel: ata3.00: configured for UDMA/133 Dec 8 17:01:34 Tower kernel: ata3: EH complete Dec 8 17:01:34 Tower kernel: sd 3:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Dec 8 17:01:34 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Dec 8 17:01:34 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Dec 8 17:01:34 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 8 17:01:37 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Dec 8 17:01:37 Tower kernel: ata3.00: irq_stat 0x40000008 Dec 8 17:01:37 Tower kernel: ata3.00: cmd 60/90:08:f7:96:e9/03:00:8c:00:00/40 tag 1 ncq 466944 in Dec 8 17:01:37 Tower kernel: res 41/40:f1:96:98:e9/8a:01:8c:00:00/40 Emask 0x409 (media error) <F> Dec 8 17:01:37 Tower kernel: ata3.00: status: { DRDY ERR } Dec 8 17:01:37 Tower kernel: ata3.00: error: { UNC } Dec 8 17:01:37 Tower kernel: ata3.00: configured for UDMA/133 Dec 8 17:01:37 Tower kernel: ata3: EH complete Dec 8 17:01:37 Tower kernel: sd 3:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Dec 8 17:01:37 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Dec 8 17:01:37 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Dec 8 17:01:37 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 8 17:01:40 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Dec 8 17:01:40 Tower kernel: ata3.00: irq_stat 0x40000008 Dec 8 17:01:40 Tower kernel: ata3.00: cmd 60/90:08:f7:96:e9/03:00:8c:00:00/40 tag 1 ncq 466944 in Dec 8 17:01:40 Tower kernel: res 41/40:f1:96:98:e9/8a:01:8c:00:00/40 Emask 0x409 (media error) <F> Dec 8 17:01:40 Tower kernel: ata3.00: status: { DRDY ERR } Dec 8 17:01:40 Tower kernel: ata3.00: error: { UNC } Dec 8 17:01:40 Tower kernel: ata3.00: configured for UDMA/133 Dec 8 17:01:40 Tower kernel: ata3: EH complete Dec 8 17:01:40 Tower kernel: sd 3:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Dec 8 17:01:40 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Dec 8 17:01:40 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Dec 8 17:01:40 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 8 17:01:42 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Dec 8 17:01:42 Tower kernel: ata3.00: irq_stat 0x40000008 Dec 8 17:01:42 Tower kernel: ata3.00: cmd 60/90:08:f7:96:e9/03:00:8c:00:00/40 tag 1 ncq 466944 in Dec 8 17:01:42 Tower kernel: res 41/40:f1:96:98:e9/8a:01:8c:00:00/40 Emask 0x409 (media error) <F> Dec 8 17:01:42 Tower kernel: ata3.00: status: { DRDY ERR } Dec 8 17:01:42 Tower kernel: ata3.00: error: { UNC } Dec 8 17:01:42 Tower kernel: ata3.00: configured for UDMA/133 Dec 8 17:01:42 Tower kernel: ata3: EH complete Dec 8 17:01:42 Tower kernel: sd 3:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Dec 8 17:01:42 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Dec 8 17:01:42 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Dec 8 17:01:42 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 8 17:01:45 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Dec 8 17:01:45 Tower kernel: ata3.00: irq_stat 0x40000008 Dec 8 17:01:45 Tower kernel: ata3.00: cmd 60/90:08:f7:96:e9/03:00:8c:00:00/40 tag 1 ncq 466944 in Dec 8 17:01:45 Tower kernel: res 41/40:e9:9e:98:e9/8a:01:8c:00:00/40 Emask 0x409 (media error) <F> Dec 8 17:01:45 Tower kernel: ata3.00: status: { DRDY ERR } Dec 8 17:01:45 Tower kernel: ata3.00: error: { UNC } Dec 8 17:01:45 Tower kernel: ata3.00: configured for UDMA/133 Dec 8 17:01:45 Tower kernel: sd 3:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Dec 8 17:01:45 Tower kernel: sd 3:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor] Dec 8 17:01:45 Tower kernel: Descriptor sense data with sense descriptors (in hex): Dec 8 17:01:45 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 8 17:01:45 Tower kernel: 00 e9 98 9e Dec 8 17:01:45 Tower kernel: sd 3:0:0:0: [sdc] ASC=0x11 ASCQ=0x4 Dec 8 17:01:45 Tower kernel: end_request: I/O error, dev sdc, sector 2364118775 Dec 8 17:01:45 Tower kernel: ata3: EH complete Dec 8 17:01:45 Tower kernel: sd 3:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Dec 8 17:01:45 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Dec 8 17:01:45 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Dec 8 17:01:45 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118712/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118720/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118728/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118736/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118744/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118752/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118760/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118768/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118776/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118784/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118792/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118800/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118808/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118816/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118824/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118832/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118840/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118848/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118856/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118864/0, count: 1 Dec 8 17:01:45 Tower kernel: md0: read error! Dec 8 17:01:45 Tower kernel: handle_stripe read error: 2364118872/0, count: 1 This drive (/dev/sdc) is apparently assigned as your parity drive. It either has has a connector to it come loose, or a cable/drive-controler-port has gone bad, or it has some other internal failure. It is listed in your syslog as: Dec 7 17:02:33 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 (sdc) ata-SAMSUNG_HD154UI_S1XWJ1LS806374 You can attempt to see if you can run a smart status report on /dev/sdc. I don't think the new drive (/dev/sdk) has anything to do with this, other than you might have dislodged something connected to /dev/sdc when installing it. To get a smart report, type: smartctl -a -d ata /dev/sdc Joe L.
December 8, 200916 yr Author Tower login: root Linux 2.6.24.4-unRAID. root@Tower:~# smartctl -a -d ata /dev/sdc smartctl version 5.36 [i486-slackware-linux-gnu] Copyright © 2002-6 Bruce Alle n Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD154UI Serial Number: S1XWJ1LS806374 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Not recognized. Minor revision code: 0x52 Local Time is: Tue Dec 8 18:47:07 2009 GMT+8 ==> 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: (18704) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: ( 33) minutes. 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 099 099 051 Pre-fail Always - 7130 3 Spin_Up_Time 0x0007 066 066 011 Pre-fail Always - 10860 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 58 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 27 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 12461 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 767 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 - 30 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 7103 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 7257 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 190 Unknown_Attribute 0x0022 075 072 000 Old_age Always - 420675609 194 Temperature_Celsius 0x0022 073 070 000 Old_age Always - 27 (Lifetime Min/Max 0/7442) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 31767203 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 27 197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 13 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 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 085 085 000 Old_age Always - 657 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 without error 00% 407 - 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.
December 8, 200916 yr Run a long test on the drive and see if the numbers above change. Check here on example on how to use smartctl
December 8, 200916 yr Author It's weird... I've been trying to run the short and long test, but this is all that I get... It won't actually do any test... hrmm. Statistics for /dev/sdc SAMSUNG_HD154UI_S1XWJ1LS806374 smartctl version 5.36 [i486-slackware-linux-gnu] Copyright © 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD154UI Serial Number: S1XWJ1LS806374 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Not recognized. Minor revision code: 0x52 Local Time is: Tue Dec 8 19:08:05 2009 GMT+8 ==> 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: (18704) 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: ( 33) minutes. 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 099 099 051 Pre-fail Always - 7130 3 Spin_Up_Time 0x0007 066 066 011 Pre-fail Always - 10860 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 58 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 27 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 12461 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 768 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 - 30 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 7103 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 7257 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 190 Unknown_Attribute 0x0022 075 072 000 Old_age Always - 420675609 194 Temperature_Celsius 0x0022 073 070 000 Old_age Always - 27 (Lifetime Min/Max 0/7442) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 31767203 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 27 197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 13 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 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 085 085 000 Old_age Always - 657 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 without error 00% 407 - 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.
December 8, 200916 yr What command (exactly) are you typing to run the "long" test? Are you thinking it is not running because the command prompt is immediately returned? The smartctl "long" command only "starts" a test running, you'll need to wait 255 minutes (or more) before it will be completed and then issue a smartctl command once more to see the results. as far as the smart report you are posting, it shows 27 re-allocated sectors 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 27 and also shows 13 more sectors pending re-allocation. (They were un-readable and should be re-allocated when they are next written to.) 197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 13 The "long" test should tell you more. If the number of sectors pending re-allocation increases by a bunch, odds are it is time to RMA the drive. Since this is a parity drive, the only way to write to it to get it to re-allocate the un-readable sectors is to perform a full parity calculation. (not a parity check, as that only reads the drive, but you can start with that, and if the sector is un-readable then unRAID may write it to correct it. Certainly worth a try.) Oh yes, you'll need to disable the spin-down of the parity drive while doing the long test. (Or make it much longer than the 4.25 hours run time it estimates to run the tests ) Joe L.
December 8, 200916 yr Author Joe - I was running the long test from unMenu I guess I just have to be patient. I will disable spindown now! THANK YOU
December 8, 200916 yr Joe - I was running the long test from unMenu I guess I just have to be patient. I will disable spindown now! THANK YOU I think you'll need to run it on the command line at a telnet prompt. I saw no evidence of it running in your subsequent SMART report. That feature was reported by one user as broken in some versions of unMENU. (actually, it needs lightly different syntax with some controller/sata drive combinations, but... I just now figured that out my array was mostly all older IDE drives, so I never noticed the issue... I never ran the "long" test on the two SATA drives in the array) Disable spin-down, then, either at the console, or at a telnet prompt type: smartctl -t long -d ata /dev/sdc Wait about 4 1/2 hours, then get a new smartctl report. I just tried it on my own parity drive. I got this: root@Tower:/boot/unmenu_final# smartctl -t long /dev/sdf smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ SMART Disabled. Use option -s with argument 'on' to enable it. I tried smartctl -s on /dev/sdf and it said it could not enable SMART. Argh..... It appears I must add an additional argument to the command to get the long test to run (and it appears I need to fix unMENU too) Instead of typing smartctl -t long /dev/sdf I must instead type smartctl -t long -d ata /dev/sdf It then output this: root@Tower:/boot/unmenu# smartctl -t long -d ata /dev/sdf smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Extended self-test routine immediately in off-line mode". Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 219 minutes for test to complete. Test will complete after Tue Dec 8 17:51:11 2009 So... with that in mind, you need to type smartctl -t long -d ata /dev/sdc and then it should start the long report process. Joe L.
December 9, 200916 yr Author well here is the smart report: It seems that it is stuck at 90% and is having read errors.... RMA this puppy? Statistics for /dev/sdc SAMSUNG_HD154UI_S1XWJ1LS806374 smartctl version 5.36 [i486-slackware-linux-gnu] Copyright © 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD154UI Serial Number: S1XWJ1LS806374 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Not recognized. Minor revision code: 0x52 Local Time is: Wed Dec 9 04:17:59 2009 GMT+8 ==> 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (18704) 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: ( 33) minutes. 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 099 099 051 Pre-fail Always - 7131 3 Spin_Up_Time 0x0007 066 066 011 Pre-fail Always - 10860 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 58 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 27 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 11543 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 777 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 - 30 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 7104 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 7258 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 190 Unknown_Attribute 0x0022 075 072 000 Old_age Always - 454230041 194 Temperature_Celsius 0x0022 074 070 000 Old_age Always - 26 (Lifetime Min/Max 0/7442) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 31767203 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 27 197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 13 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 085 085 000 Old_age Always - 658 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 90% 770 2367490183 # 2 Extended offline Completed without error 00% 407 - 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.
December 9, 200916 yr well here is the smart report: It seems that it is stuck at 90% and is having read errors.... RMA this puppy? That would be what I'd be thinking...
December 10, 200916 yr Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 770 2367490183 # 2 Extended offline Completed without error 00% 407 - Having seen a number of these, I think for many drives, perhaps with Seagate firmware, that 'Remaining' is only updated each 10%. When the test is complete ("Completed:"), I think they don't even bother to update 'Remaining', so it remains at 90% and should be ignored. The more important item is that it no longer says the test is running, but says it is 'Completed'. This test is certainly not very impressive, as after all that testing, it only indicates "Completed without error" or "Completed: read failure" plus the LBA of the first bad sector. It does not tell us how many bad sectors it found in this test, or where they all are, or try to recover or remap them, which is rather unhelpful. We can still determine how many it found by comparing before and after SMART reports, but seems as if they could produce a more comprehensive listing and accounting. I think we need to emphasize getting SMART reports before and after any SMART tests, and check to see what numbers increase. I think in this case and in some others recently, that the drive has just experienced a few bad sectors, and once resolved, will be fine for quite a while to come. We really need a tool to resolve these, to clear Pending to zero. I would like to see a SpinRite-like tool that tests all drive sectors, and works as hard as necessary to recover all marginal sectors, but either fully clears them or remaps them (then tests the remapped sector too), and never leaves any as Pending.
Archived
This topic is now archived and is closed to further replies.