If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#21
|
|||
|
|||
A dying very old HDD confirmed?
"Rod Speed" writes:
Ant wrote Rod Speed wrote Ant wrote Those results look bad? Not too bad if they don't keep increasing. Really? Yeah, a few reallocated sectors are no big deal on a drive that old. Some of those older drives don't handle mains failure that well and can produce a bad sector that way and then just reallocate that bad sector. Disks are so cheap there's no reason not to replace them at first sign of trouble. -- Måns Rullgård |
#22
|
|||
|
|||
A dying very old HDD confirmed?
On 04/22/14 07:59, Måns Rullgård wrote:
"Rod Speed" writes: Ant wrote Rod Speed wrote Ant wrote Those results look bad? Not too bad if they don't keep increasing. Really? Yeah, a few reallocated sectors are no big deal on a drive that old. Some of those older drives don't handle mains failure that well and can produce a bad sector that way and then just reallocate that bad sector. Disks are so cheap there's no reason not to replace them at first sign of trouble. +1 to that! Any disk, over 3 years old and under 250 GB, just replace it at first sight of problems. |
#23
|
|||
|
|||
A dying very old HDD confirmed?
"Ant" wrote in message m... On 4/21/2014 5:56 AM PT, Robert Nichols typed: All it depends on is a version of debugfs that is compatible with the filesystem, and that's just to identify the file (if any) that is currently using the bad sector. Note that the "LBA_of_first_error" reported by the offline test may not be precise. It could be just the start of a block that contained the bad sector. You can use "hdparm --read-sector ..." to try to pin that down. # debugfs -V debugfs 1.42.5 (29-Jul-2012) Using EXT2FS Library version 1.42.5 That looks kind of old? Hmm. I hope Debian stable gives me the correct version for all of its disk utility packages to be compatible when I need to run it. So far, I haven't gotten any new SMART e-mails about new issues. Original e-mail said it was supposed to be daily? I guess, it is stable for now? Although, I noticed smartctl's Reallocated_Sector_Ct went from 6 to 7 when I checked the old HDD's SMART datas. Is that going up too fast within two/2 days, Rod? See below for the latest smartctl results: Nar, that's fine. One of the offline uncorrectable or pending sectors has been reallocated so in fact the total number of bads has gone down by one. 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail - 7 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age ne - 0 |
#24
|
|||
|
|||
A dying very old HDD confirmed?
"Ant" wrote in message m... On 4/21/2014 4:31 PM PT, Pascal Hambourg typed: Although, I noticed smartctl's Reallocated_Sector_Ct went from 6 to 7 when I checked the old HDD's SMART datas. Is that going up too fast within two/2 days, Rod? See below for the latest smartctl results: [...] 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 7 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Apparently it is only the previously pending unreadable sector which eventually got reallocated, so no new error. Oh. So, how should I be reading its results to see if it is getting worse quickly or not? That one isnt getting worse, just the detail has changed, the sector has been reallocated, because something wrote to it. I am confused. The drive is still fine for a drive that old. |
#25
|
|||
|
|||
A dying very old HDD confirmed?
Måns Rullgård wrote
Rod Speed wrote Ant wrote Rod Speed wrote Ant wrote Those results look bad? Not too bad if they don't keep increasing. Really? Yeah, a few reallocated sectors are no big deal on a drive that old. Some of those older drives don't handle mains failure that well and can produce a bad sector that way and then just reallocate that bad sector. Disks are so cheap there's no reason not to replace them at first sign of trouble. I don't bother and it works fine. |
#26
|
|||
|
|||
A dying very old HDD confirmed?
"Vic RR Garcia" wrote in message ... On 04/22/14 07:59, Måns Rullgård wrote: "Rod Speed" writes: Ant wrote Rod Speed wrote Ant wrote Those results look bad? Not too bad if they don't keep increasing. Really? Yeah, a few reallocated sectors are no big deal on a drive that old. Some of those older drives don't handle mains failure that well and can produce a bad sector that way and then just reallocate that bad sector. Disks are so cheap there's no reason not to replace them at first sign of trouble. +1 to that! Any disk, over 3 years old and under 250 GB, just replace it at first sight of problems. I don’t bother with drives that small and it works fine to keep using drives which only have a few reallocated sectors. |
#27
|
|||
|
|||
A dying very old HDD confirmed?
"Rod Speed" writes:
"Vic RR Garcia" wrote in message ... On 04/22/14 07:59, Måns Rullgård wrote: "Rod Speed" writes: Ant wrote Rod Speed wrote Ant wrote Those results look bad? Not too bad if they don't keep increasing. Really? Yeah, a few reallocated sectors are no big deal on a drive that old. Some of those older drives don't handle mains failure that well and can produce a bad sector that way and then just reallocate that bad sector. Disks are so cheap there's no reason not to replace them at first sign of trouble. +1 to that! Any disk, over 3 years old and under 250 GB, just replace it at first sight of problems. I don’t bother with drives that small and it works fine to keep using drives which only have a few reallocated sectors. Drives work fine until they don't. -- Måns Rullgård |
#28
|
|||
|
|||
A dying very old HDD confirmed?
That one isnt getting worse, just the detail has changed, the
sector has been reallocated, because something wrote to it. I meant for future. I remember it said 6 and then it was 7. I am confused. The drive is still fine for a drive that old. OK. FYI just in case (nothing changed drastically I assume): # smartctl -a /dev/sda smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus Device Model: ST380011A Serial Number: 4JV5P7LN Firmware Version: 8.01 User Capacity: 80,026,361,856 bytes [80.0 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2 Local Time is: Tue Apr 22 17:02:52 2014 PDT 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: ( 118) The previous self-test completed having the read element of the test failed. 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: ( 58) 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 057 053 006 Pre-fail Always - 140973423 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 0 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 7 7 Seek_Error_Rate 0x000f 089 060 030 Pre-fail Always - 936370500 9 Power_On_Hours 0x0032 019 019 000 Old_age Always - 71113 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 362 194 Temperature_Celsius 0x0022 035 053 000 Old_age Always - 35 195 Hardware_ECC_Recovered 0x001a 057 053 000 Old_age Always - 140973423 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 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 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 Extended offline Completed: read failure 60% 5502 67691664 # 2 Extended offline Completed: read failure 60% 5501 67691664 # 3 Short offline Completed without error 00% 5501 - # 4 Short offline Completed without error 00% 5501 - # 5 Extended offline Completed: read failure 60% 5501 67691664 # 6 Short offline Completed without error 00% 5501 - # 7 Extended offline Completed: read failure 60% 5499 67691664 # 8 Extended offline Completed without error 00% 3165 - # 9 Extended offline Completed without error 00% 48483 - #10 Extended offline Completed without error 00% 43207 - #11 Extended offline Interrupted (host reset) 90% 43201 - #12 Extended offline Completed without error 00% 39844 - #13 Extended offline Interrupted (host reset) 20% 38502 - #14 Extended offline Completed without error 00% 35555 - #15 Extended offline Completed without error 00% 31886 - #16 Extended offline Completed without error 00% 22233 - #17 Extended offline Completed without error 00% 18951 - #18 Extended offline Completed without error 00% 18674 - #19 Extended offline Completed without error 00% 15957 - #20 Extended offline Completed without error 00% 14448 - 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 of the Week: "Where there is sugar, there are bound to be ants." --Malay Proverb /\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site) / /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ / Please nuke ANT if replying by e-mail. If crediting, ( ) then please kindly use Ant nickname and AQFL URL/link. |
#29
|
|||
|
|||
A dying very old HDD confirmed?
"Måns Rullgård" wrote in message ... "Rod Speed" writes: "Vic RR Garcia" wrote in message ... On 04/22/14 07:59, Måns Rullgård wrote: "Rod Speed" writes: Ant wrote Rod Speed wrote Ant wrote Those results look bad? Not too bad if they don't keep increasing. Really? Yeah, a few reallocated sectors are no big deal on a drive that old. Some of those older drives don't handle mains failure that well and can produce a bad sector that way and then just reallocate that bad sector. Disks are so cheap there's no reason not to replace them at first sign of trouble. +1 to that! Any disk, over 3 years old and under 250 GB, just replace it at first sight of problems. I don’t bother with drives that small and it works fine to keep using drives which only have a few reallocated sectors. Drives work fine until they don't. Hardly any of mine have ever died. They mostly get replaced because they are too small. |
#30
|
|||
|
|||
A dying very old HDD confirmed?
Ant wrote
That one isnt getting worse, just the detail has changed, the sector has been reallocated, because something wrote to it. I meant for future. I remember it said 6 and then it was 7. Because the offline uncorrectable was written to and became a reallocated sector. The pending sector turned out to be fine. I am confused. The drive is still fine for a drive that old. OK. FYI just in case (nothing changed drastically I assume): Yes, see above for what happened. Interesting that the read failures are still there and that blows a great hole in Bob Nichols' claim that the test just stopped when it got to the offline uncorrectable sector. # smartctl -a /dev/sda smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus Device Model: ST380011A Serial Number: 4JV5P7LN Firmware Version: 8.01 User Capacity: 80,026,361,856 bytes [80.0 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2 Local Time is: Tue Apr 22 17:02:52 2014 PDT 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: ( 118) The previous self-test completed having the read element of the test failed. 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: ( 58) 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 057 053 006 Pre-fail Always - 140973423 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 0 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 7 7 Seek_Error_Rate 0x000f 089 060 030 Pre-fail Always - 936370500 9 Power_On_Hours 0x0032 019 019 000 Old_age Always - 71113 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 362 194 Temperature_Celsius 0x0022 035 053 000 Old_age Always - 35 195 Hardware_ECC_Recovered 0x001a 057 053 000 Old_age Always - 140973423 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 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 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 Extended offline Completed: read failure 60% 5502 67691664 # 2 Extended offline Completed: read failure 60% 5501 67691664 # 3 Short offline Completed without error 00% 5501 - # 4 Short offline Completed without error 00% 5501 - # 5 Extended offline Completed: read failure 60% 5501 67691664 # 6 Short offline Completed without error 00% 5501 - # 7 Extended offline Completed: read failure 60% 5499 67691664 # 8 Extended offline Completed without error 00% 3165 - # 9 Extended offline Completed without error 00% 48483 - #10 Extended offline Completed without error 00% 43207 - #11 Extended offline Interrupted (host reset) 90% 43201 - #12 Extended offline Completed without error 00% 39844 - #13 Extended offline Interrupted (host reset) 20% 38502 - #14 Extended offline Completed without error 00% 35555 - #15 Extended offline Completed without error 00% 31886 - #16 Extended offline Completed without error 00% 22233 - #17 Extended offline Completed without error 00% 18951 - #18 Extended offline Completed without error 00% 18674 - #19 Extended offline Completed without error 00% 15957 - #20 Extended offline Completed without error 00% 14448 - 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. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
confirmed: AMD will buy ATI for $5.4 billion | AirRaid Mach 2.5 | Ati Videocards | 2 | July 27th 06 11:59 PM |
confirmed: AMD will buy ATI for $5.4 billion | AirRaid Mach 2.5 | AMD x86-64 Processors | 1 | July 24th 06 11:14 AM |
confirmed: AMD will buy ATI for $5.4 billion | AirRaid Mach 2.5 | Overclocking AMD Processors | 1 | July 24th 06 11:14 AM |
confirmed: AMD will buy ATI for $5.4 billion | AirRaid Mach 2.5 | Nvidia Videocards | 1 | July 24th 06 11:14 AM |
Yamhill confirmed? | Derek Baker | General | 15 | January 6th 04 09:14 PM |