GoChris Posted March 9, 2009 Share Posted March 9, 2009 Hi all, I'm new to unraid, so far I like it, and everything is working pretty good. I have a problem with a drive, I have 4 drives as part of my raid, but this problem existed last week and I only had 3 on the free version. I have a drive that sounds like it's trying to power up, I'm not sure I would say it's the same sound as a dead drive. If I power down the system, and turn it back on, it's fine. I ran the computer at least all day yesterday, started a transfer last night (still trying to migrate data), when I got up this morning, the transfer was not done by the looks of it (but the transfer dialog was gone). I "stopped" the array, but that never really finished so I just powered it down. I suspect when I get home tonight and power it on, it will be fine, probably for many many hours until it happens again. So, long story short (too late?), how do I tell which drive it is? Would I be able to determine from the SMART stats at all? I suspect it's my 1.5TB parity drive or a refurb 750gb. (The other drive I had in there before is a 500gb, I also added another 1.5TB this weekend). I just want to know asap before I move more data overl. If it's the 1.5tb I have enough free space I can use the new 1.5 as the parity I think, or if it's the 750 I just put a 500gb in the case which I haven't added to the array yet. (since the drive isn't dead is there a wiki on how to "ghost" the drive so it doesn't have to rebuild?) Thanks in advance for the help. I know there is huge community support, part of the reason I went with unRaid so I'm not worried. Quote Link to comment
Joe L. Posted March 9, 2009 Share Posted March 9, 2009 Hi all, I'm new to unraid, so far I like it, and everything is working pretty good. I have a problem with a drive, I have 4 drives as part of my raid, but this problem existed last week and I only had 3 on the free version. I have a drive that sounds like it's trying to power up, I'm not sure I would say it's the same sound as a dead drive. If I power down the system, and turn it back on, it's fine. I ran the computer at least all day yesterday, started a transfer last night (still trying to migrate data), when I got up this morning, the transfer was not done by the looks of it (but the transfer dialog was gone). I "stopped" the array, but that never really finished so I just powered it down. I suspect when I get home tonight and power it on, it will be fine, probably for many many hours until it happens again. So, long story short (too late?), how do I tell which drive it is? Would I be able to determine from the SMART stats at all? I suspect it's my 1.5TB parity drive or a refurb 750gb. (The other drive I had in there before is a 500gb, I also added another 1.5TB this weekend). I just want to know asap before I move more data overl. If it's the 1.5tb I have enough free space I can use the new 1.5 as the parity I think, or if it's the 750 I just put a 500gb in the case which I haven't added to the array yet. (since the drive isn't dead is there a wiki on how to "ghost" the drive so it doesn't have to rebuild?) Thanks in advance for the help. I know there is huge community support, part of the reason I went with unRaid so I'm not worried. Post a syslog. Very likely it will give the clues needed to determine the defective drive. Instructions are in the wiki under troubleshooting. (link in my sig) Joe L. Quote Link to comment
bubbaQ Posted March 9, 2009 Share Posted March 9, 2009 Run smartctl -H on each one ... this is one of the symptoms that will often produce a FAILED health status in smartctl. Quote Link to comment
GoChris Posted March 9, 2009 Author Share Posted March 9, 2009 thanks, I will do both of those suggestions as soon as I get home tonight. I installed unMenu so that will make the syslog part super easy (unmenu rocks btw), and wow, super fast replies guys, thanks. Quote Link to comment
Joe L. Posted March 9, 2009 Share Posted March 9, 2009 thanks, I will do both of those suggestions as soon as I get home tonight. I installed unMenu so that will make the syslog part super easy (unmenu rocks btw), and wow, super fast replies guys, thanks. unMENU has the smartctl report built in too. Look for the button labeled "Smart Status" on the disk-management page. Joe L. Quote Link to comment
GoChris Posted March 9, 2009 Author Share Posted March 9, 2009 Using "Smart Statistics" on the Disk Mgmt screen. === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS082L1 Firmware Version: CC1H User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 9 16:00:06 2009 GMT+8 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: ( 609) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 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 115 099 006 Pre-fail Always - 96054377 3 Spin_Up_Time 0x0003 100 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 97 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3906201 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1236 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 184 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 3 189 High_Fly_Writes 0x003a 048 048 000 Old_age Always - 52 190 Airflow_Temperature_Cel 0x0022 076 052 045 Old_age Always - 24 (Lifetime Min/Max 23/24) 194 Temperature_Celsius 0x0022 024 048 000 Old_age Always - 24 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 052 030 000 Old_age Always - 96054377 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 191074505065381 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 881705840 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 384087824 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. === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 Device Model: ST3750330AS Serial Number: 5QK01SEZ Firmware Version: AD14 User Capacity: 750,156,374,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 9 16:05:23 2009 GMT+8 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: ( 25) The self-test routine was aborted by the host. Total time to complete Offline data collection: ( 634) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 171) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 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 119 100 006 Pre-fail Always - 209788967 3 Spin_Up_Time 0x0003 094 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 63 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 4300497694 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 256 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 51 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 099 000 Old_age Always - 8590065667 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 075 059 045 Old_age Always - 25 (Lifetime Min/Max 20/25) 194 Temperature_Celsius 0x0022 025 042 000 Old_age Always - 25 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 047 036 000 Old_age Always - 209788967 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 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): === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630AS Serial Number: 9QG2V7BY Firmware Version: 3.AAE User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Mar 9 16:08:26 2009 GMT+8 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: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 163) minutes. SMART Attributes Data Structure revision number: 10 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 117 089 006 Pre-fail Always - 149624972 3 Spin_Up_Time 0x0003 098 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 691 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 247955503 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 7087 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 311 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 071 049 045 Old_age Always - 29 (Lifetime Min/Max 29/29) 194 Temperature_Celsius 0x0022 029 051 000 Old_age Always - 29 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 097 055 000 Old_age Always - 233684308 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 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): === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS0ZZLS Firmware Version: CC1H User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 9 16:12:31 2009 GMT+8 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: ( 617) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 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 111 100 006 Pre-fail Always - 32170619 3 Spin_Up_Time 0x0003 096 096 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 19 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 1925693 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 34 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 7 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 055 055 000 Old_age Always - 45 190 Airflow_Temperature_Cel 0x0022 072 068 045 Old_age Always - 28 (Lifetime Min/Max 20/28) 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 045 045 000 Old_age Always - 32170619 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 266893562740765 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 110247548 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 181214449 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): (4th drive is the one I just added). I'm not really sure yet how to decipher the smart values. It's clicking once every 10-20 seconds pretty much since I turned it on a few minutes ago. On another note, my parity check is going crap slow, before it was 60+MB/s, all 4 array drives are on the mobo. I was going to get the syslog but...now I don't get a connection to the web server. Quote Link to comment
RobJ Posted March 10, 2009 Share Posted March 10, 2009 You have 6 drives installed, so we need to see the SMART reports for the other 2 also. The 4 reports above do not seem bad at all. They all seem to me to have a Seek_Error_Rate that is a little worse than you would like, should be monitored, but otherwise are fine. The 500GB has one 'oddity', its Hardware_ECC_Recovered RAW_VALUE is about 55% higher than the Raw_Read_Error_Rate RAW_VALUE. They normally are exactly the same for Seagates. The syslog is showing (the increasingly common) frozen/timeout errors, for the parity drive first, and then Disk 2. What is odd is that they were occurring just over a minute apart, and once Disk 2 decided to join the parity drive in these errors, the errors occurred simultaneously for both drives. That would seem to point to a system problem, not a cable or drive problem. Both eventually resulted in the drives being slowed to UDMA/33 speed, which accounts for your very slow parity check speed. Unfortunately, this kind of error is really frustrating, has been occurring more often with the recent Linux kernels, and tells me almost nothing as to what the real problem is. I can't say for sure whether it is a problem with the drive, the cable, or the disk controller it is connected to, or a driver problem. However, I am thinking more and more that we will find out in a future Linux kernel release that it was a software problem, or at least was fixable in software. I've been waiting to test the new kernel in v4.5-beta2, Linux kernel release 2.6.28.4. Since there is some evidence that this behavior changes with the version of kernel, you may want to test this, by dropping back to unRAID v4.2.4 or v4.3.3, or jumping ahead to v4.5-beta2. Other things to try are reconnecting to different SATA ports, and/or changing the BIOS settings for the onboard SATA ports, to run in AHCI mode, which will cause them to use a different driver. Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 the other 2 drives are not part of the array yet so that's why I didn't post them. 1 I was going to add but this problem arose, the 2nd will be my cache drive. I am not sure where to get older versions, so I will try the beta release and see how that goes. I will check the bios, but I don't think this one does AHCI, I have the option for enhanced or combined, or..something for sata options. I'll probably have to hard power down now, console says "Kernel Panic - not syncing: Out of memory and no killable processes" Edit: I see now there are some old versions for download, I will just try the 4.5 now. Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 Alright, change one connection that fed the power to the 1.5 and (i think) the 500, was getting power off a fan molex, but now its from a direct rail, into a 2 sata power cable. anyway, its up and running, just for 2 minutes so far. version: 4.5-beta2 Total size: 1,465,138,552 KB Current position: 10,629,892 (0.7%) Estimated speed: 61,641 KB/sec Estimated finish: 393.2 minutes Sync errors: 128 edit: hmm, few write errors. prob should rma this drive? which is easy as I have instant replacement so I can just go to the store and over the counter exchange it. Model / Serial No. Temperature Size Free Reads Writes Errors parity ata-ST31500341AS_9VS082L1 33°C 1,465,138,552 - 209,697 51 67 Quote Link to comment
RobJ Posted March 10, 2009 Share Posted March 10, 2009 the other 2 drives are not part of the array yet so that's why I didn't post them. You were trying to find out which of the installed drives is clicking, right? Any drive that is running in the computer could be the clicker, and that has nothing to do with the array. Or perhaps I misunderstood you? You really should try to get a SMART report for each of the other 2 drives. I believe you can also use UnMENU to get SMART reports for the other 2 drives, that are not in the array (sda and sdb). Both are older drives, and therefore more likely to be clicking. Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 the other 2 drives are not part of the array yet so that's why I didn't post them. You were trying to find out which of the installed drives is clicking, right? Any drive that is running in the computer could be the clicker, and that has nothing to do with the array. Or perhaps I misunderstood you? You really should try to get a SMART report for each of the other 2 drives. I believe you can also use UnMENU to get SMART reports for the other 2 drives, that are not in the array (sda and sdb). Both are older drives, and therefore more likely to be clicking. I was pretty sure the clicking happened once last week, before the other 2 drives where added. I would post the info on them right now however I do not see how I can get it via UnMenu since they are not part of the array. The array/system becomes quite unresponsive, and actually hung earlier due to the clicking, so I assumed it was a member drive. This could be a wrong assumption. Quote Link to comment
SSD Posted March 10, 2009 Share Posted March 10, 2009 Alright, change one connection that fed the power to the 1.5 and (i think) the 500, was getting power off a fan molex, but now its from a direct rail, into a 2 sata power cable. anyway, its up and running, just for 2 minutes so far. version: 4.5-beta2 Total size: 1,465,138,552 KB Current position: 10,629,892 (0.7%) Estimated speed: 61,641 KB/sec Estimated finish: 393.2 minutes Sync errors: 128 edit: hmm, few write errors. prob should rma this drive? which is easy as I have instant replacement so I can just go to the store and over the counter exchange it. Model / Serial No. Temperature Size Free Reads Writes Errors parity ata-ST31500341AS_9VS082L1 33°C 1,465,138,552 - 209,697 51 67 Unless the drive's graphic (far left) has turned red, there have been no write errors. Write errors cause unRAID to kick a drive from the array which cause the graphic to turn red. When unRAID encounters a read error, it will calculate what it was not able to read by examining the corresponding sector of each of the other drives and reconstructing the bad sector. It will then write the data back to the source drive. Using the magic of SMART, this should force a sector remap with the net result of correcting the error. One of these in a blue moon is somewhat to be expected. 67 of them is not a good sign. I just looked below at your prior smart report on this drive. There is 1 reallocated sector at that time. My experience with bad sectors has been pretty bad. Even 1 likely means you have a problem that will only get worse. Some drives, however, have a few bad sectors and the number stays constant and does not grow. If you have one of these situations, there is nothing to worry about. Again my experience with 300G and smaller drives has been that 1 or 2 bad sectors is not a big problem. But with 500G+ drives, I've noticed that frequently even a single reallocated sector will quickly grow to dozens, and ultimately failure, in a very short time. Pull another smart report on the parity disk. You should see about 67 (or so) remapped sectors (or perhaps some remapped and some pending remap). Either way, if you see this in the smartctl report, you know it is a drive issue. If, however, the smart report still shows only 1 reallocated sector, this would point to a bad cable. My guess is it is the drive, though. Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 Pull another smart report on the parity disk. You should see about 67 (or so) remapped sectors (or perhaps some remapped and some pending remap). Either way, if you see this in the smartctl report, you know it is a drive issue. If, however, the smart report still shows only 1 reallocated sector, this would point to a bad cable. My guess is it is the drive, though. Thanks for the lesson, that was some information I didn't know. Red circle...bad heh Updated info ata-ST31500341AS_9VS082L1 30°C 1,465,138,552 - 1,669,676 69 169 === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS082L1 Firmware Version: CC1H User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 9 20:49:08 2009 GMT+8 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: ( 609) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 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 119 099 006 Pre-fail Always - 213748855 3 Spin_Up_Time 0x0003 100 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 183 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3908619 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1239 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 273 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 076 076 000 Old_age Always - 24 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 3 189 High_Fly_Writes 0x003a 048 048 000 Old_age Always - 52 190 Airflow_Temperature_Cel 0x0022 070 052 045 Old_age Always - 30 (Lifetime Min/Max 28/33) 194 Temperature_Celsius 0x0022 030 048 000 Old_age Always - 30 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 055 030 000 Old_age Always - 213748855 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 142597209195431 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 881727511 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1125710762 SMART Error Log Version: 1 ATA Error Count: 24 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 24 occurred at disk power-on lifetime: 1238 hours (51 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:17:15.838 READ DMA EXT 27 00 00 00 00 00 e0 00 01:17:15.776 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 02 01:17:15.736 IDENTIFY DEVICE ef 03 46 00 00 00 a0 02 01:17:15.718 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 01:17:15.596 READ NATIVE MAX ADDRESS EXT Error 23 occurred at disk power-on lifetime: 1238 hours (51 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:17:12.863 READ DMA EXT 27 00 00 00 00 00 e0 00 01:17:12.801 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 02 01:17:12.781 IDENTIFY DEVICE ef 03 46 00 00 00 a0 02 01:17:12.762 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 01:17:12.711 READ NATIVE MAX ADDRESS EXT Error 22 occurred at disk power-on lifetime: 1238 hours (51 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:17:09.878 READ DMA EXT 27 00 00 00 00 00 e0 00 01:17:09.816 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 02 01:17:09.776 IDENTIFY DEVICE ef 03 46 00 00 00 a0 02 01:17:09.761 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 01:17:09.646 READ NATIVE MAX ADDRESS EXT Error 21 occurred at disk power-on lifetime: 1238 hours (51 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:17:06.883 READ DMA EXT 27 00 00 00 00 00 e0 00 01:17:06.821 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 02 01:17:06.801 IDENTIFY DEVICE ef 03 46 00 00 00 a0 02 01:17:06.782 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 01:17:06.731 READ NATIVE MAX ADDRESS EXT Error 20 occurred at disk power-on lifetime: 1238 hours (51 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:17:03.868 READ DMA EXT 27 00 00 00 00 00 e0 00 01:17:03.786 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 02 01:17:03.705 IDENTIFY DEVICE ef 03 46 00 00 00 a0 02 01:17:03.673 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 01:17:03.645 READ NATIVE MAX ADDRESS EXT 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. Quote Link to comment
SSD Posted March 10, 2009 Share Posted March 10, 2009 Bad guess. You have a cabling problem to this drive. Try replacing the data cable with a fresh one. If you are using backplanes or docks, it could be that is the source of the bad connection. You might try connecting the drive directly to the SATA port with a known good SATA data cable. Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 Bad guess. You have a cabling problem to this drive. Try replacing the data cable with a fresh one. If you are using backplanes or docks, it could be that is the source of the bad connection. You might try connecting the drive directly to the SATA port with a known good SATA data cable. I am connecting right to the motherboard. I will replace a cable with another one, hopefully I can find a previously unused cable and this week I will buy some new ones. Can I stop the parity check, replace the cable, and will it start where it left off? Or should I let it finish first? Quote Link to comment
SSD Posted March 10, 2009 Share Posted March 10, 2009 Bad guess. You have a cabling problem to this drive. Try replacing the data cable with a fresh one. If you are using backplanes or docks, it could be that is the source of the bad connection. You might try connecting the drive directly to the SATA port with a known good SATA data cable. I am connecting right to the motherboard. I will replace a cable with another one, hopefully I can find a previously unused cable and this week I will buy some new ones. Can I stop the parity check, replace the cable, and will it start where it left off? Or should I let it finish first? I would just stop it. If you don't have a fresh cable handy, you might just unplug and replug (securely) both ends of the cable that is there. (Obviously completely power down first!) There is no way to resume a parity check - you'd just have to start it over. Note that when you rerun the parity check, you might get some sync errors. Do not be overly concerned, so long as you aren't getting drive errors and so long as your smartctl report continues to look good. After running 1 parity check, you should soon afterwards run another one. That second one should be flawless. Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 Alright, found a brand new, sealed, unused cable. I will power down, replace and start up again. It's just before bedtime so the parity check should be done by morning. Thanks, I'll report back after. Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 Well it's morning, no clicking, parity check done, and no errors. Parity disk, looks like the bad sector count is still just one. right? SMART Attributes Data Structure revision number: 10 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 117 099 006 Pre-fail Always - 148466845 3 Spin_Up_Time 0x0003 099 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 185 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3912674 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1249 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 274 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 076 076 000 Old_age Always - 24 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 3 189 High_Fly_Writes 0x003a 048 048 000 Old_age Always - 52 190 Airflow_Temperature_Cel 0x0022 079 052 045 Old_age Always - 21 (Lifetime Min/Max 21/34) 194 Temperature_Celsius 0x0022 021 048 000 Old_age Always - 21 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 056 030 000 Old_age Always - 148466845 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 96344706384813 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 881728175 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 60491478 Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 Also right before I left for work, I noticed the front case fans weren't working (no leds). I opened the case, touched the connector, and voila they turned on. So obviously the connection on that splitter wasn't very good, which was the old one used for 2 drives. Should have known better to use that in the first place. Thanks for the help guys. Quote Link to comment
Joe L. Posted March 10, 2009 Share Posted March 10, 2009 Also right before I left for work, I noticed the front case fans weren't working (no leds). I opened the case, touched the connector, and voila they turned on. So obviously the connection on that splitter wasn't very good, which was the old one used for 2 drives. Should have known better to use that in the first place. Thanks for the help guys. That is exactly the issue I ran into with two of my splitters... The drives they were feeding "occasionally" had errors that would crash the server. Funny how the drives like to have a continuous source of power while they are running. Equally funny is how I eventually found the issue.. I had taken a picture of my server to share with another member, and looking at it closely, I could see the fan blades on one of the fans... It was not spinning either... just like yours... for the same reason. I replaced two of the old 2-way splitters with a single 4-way splitter. The new splitter was a 4-way and cost all of $2.99. It is much higher quality and heavier gauge wire too. Search here for what I purchased: http://www.intrex.com/parts/parts.aspx (Search for part number: ADA-POWYX2) Hope it all works out for you. Joe L. Picture showing the small fan in added card-cage at the bottom of my array not spinning New 4 way splitter vs. old intermittent splitters. (I purchased a spare too, it is still in the bag) Quote Link to comment
lionelhutz Posted March 10, 2009 Share Posted March 10, 2009 I've read about clicking most commonly with Seagate drives and it seems they often work OK with the clicking for a while and then just die very quickly. You could power each one up individually and see if one clicks because it's reported the clicking always happens even if not being read. Try one drive at a time and just booting to the BIOS. Even remove the flash if you want. I'm a little concerned about your need for a parity check after each shut down and the errors you posted. I don't think you're using the proper shutdown. You have to use the web interface and stop the array and then use the power down button that appears. The syslog is showing (the increasingly common) frozen/timeout errors, for the parity drive first, and then Disk 2. What is odd is that they were occurring just over a minute apart, and once Disk 2 decided to join the parity drive in these errors, the errors occurred simultaneously for both drives. That would seem to point to a system problem, not a cable or drive problem. Both eventually resulted in the drives being slowed to UDMA/33 speed, which accounts for your very slow parity check speed. Unfortunately, this kind of error is really frustrating, has been occurring more often with the recent Linux kernels, and tells me almost nothing as to what the real problem is. I can't say for sure whether it is a problem with the drive, the cable, or the disk controller it is connected to, or a driver problem. However, I am thinking more and more that we will find out in a future Linux kernel release that it was a software problem, or at least was fixable in software. I've been waiting to test the new kernel in v4.5-beta2, Linux kernel release 2.6.28.4. I was seeing that with my 1T Seagate drives every now and then. I updated the firmware and haven't seen it again yet. Once again, it has been reported that the Seagate drives will momentarily hang at times with the 1.5T drives being the worst culprits because they would hang long enough to cause a RAID card to flag them as bad with the end result being either a degrade or loss of the array. I suspect this is unRAID recovering from this type of drive hang. Peter Quote Link to comment
GoChris Posted March 10, 2009 Author Share Posted March 10, 2009 I've read about clicking most commonly with Seagate drives and it seems they often work OK with the clicking for a while and then just die very quickly. You could power each one up individually and see if one clicks because it's reported the clicking always happens even if not being read. Try one drive at a time and just booting to the BIOS. Even remove the flash if you want. I'm a little concerned about your need for a parity check after each shut down and the errors you posted. I don't think you're using the proper shutdown. You have to use the web interface and stop the array and then use the power down button that appears. Peter The parity check wasn't needed each time. Just the other day (yesterday, sunday..don't remember) since the system hung from the clicking drive. I started the check manually last night because I had manually stopped the one it was doing as a result of the hard shutdown in order to replace the sata cable and subsequently changed the power splitter. I am stopping the array via the gui and using the power down button when turning it off. But thanks for the heads up. Quote Link to comment
GoChris Posted March 11, 2009 Author Share Posted March 11, 2009 didn't want to start another thread, but this is unrelated. I tried the pre_clear script on a 500gb I was going to add, what does this tell me? ============================================================================ == == Disk /dev/sdb has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 50c50 < 1 Raw_Read_Error_Rate 0x000f 118 089 006 Pre-fail Always - 186204900 --- > 1 Raw_Read_Error_Rate 0x000f 118 089 006 Pre-fail Always - 0 54c54 < 7 Seek_Error_Rate 0x000f 064 054 030 Pre-fail Always - 283637411448 --- > 7 Seek_Error_Rate 0x000f 064 054 030 Pre-fail Always - 283639711502 59,60c59,60 < 190 Airflow_Temperature_Cel 0x0022 070 053 045 Old_age Always - 30 (Lifetime Min/Max 21/30) < 195 Hardware_ECC_Recovered 0x001a 072 054 000 Old_age Always --- > 190 Airflow_Temperature_Cel 0x0022 068 053 045 Old_age Always - 32 (Lifetime Min/Max 21/34) > 195 Hardware_ECC_Recovered 0x001a 070 054 000 Old_age Always ============================================================================ here is the the rest for that drive # smartctl -a /dev/sdb smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630AS Serial Number: 6QG0VL1N Firmware Version: 3.AAK User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Mar 11 16:52:55 2009 GMT+8 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: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 163) minutes. SMART Attributes Data Structure revision number: 10 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 111 089 006 Pre-fail Always - 193125213 3 Spin_Up_Time 0x0003 096 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 691 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 6 7 Seek_Error_Rate 0x000f 064 054 030 Pre-fail Always - 283639855424 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 7201 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 214 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 053 045 Old_age Always - 30 (Lifetime Min/Max 21/34) 194 Temperature_Celsius 0x0022 030 047 000 Old_age Always - 30 (0 18 0 0) 195 Hardware_ECC_Recovered 0x001a 062 054 000 Old_age Always - 201774066 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 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. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.