Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Rod Speed" Newsgroups: comp.os.linux.hardware,comp.sys.ibm.pc.hardware.storage,alt.comp.periphs.hdd Subject: Re: A dying very old HDD confirmed? Date: Thu, 24 Apr 2014 06:32:42 +1000 Lines: 38 Message-ID: References: <1OGdnVOCGsDgqcjOnZ2dnUVZ_j2dnZ2d@earthlink.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response Content-Transfer-Encoding: 8bit X-Trace: individual.net bQqjsCEQa+H3a+O8+ajJngvK00b/19uQyHXQ6JhQihLNL8Q5Y= Cancel-Lock: sha1:8mPFRpGt2IfH9dzGBT95ibf1qFs= In-Reply-To: X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 Xref: csiph.com comp.os.linux.hardware:2345 comp.sys.ibm.pc.hardware.storage:5427 Robert Nichols wrote > Ant wrote >> 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% >> 5583 - >> # 2 Short offline Completed without error 00% >> 5583 - > # 5 Short offline Completed without error 00% > 5501 - >> # 3 Extended offline Completed: read failure 60% 5502 >> 67691664 >> # 4 Extended offline Completed: read failure 60% 5501 >> 67691664 > [SNIP] >> That was interesting to see automatic reallocation made the tests work >> again. I guess I should use the disk again if I see reallocation issues >> again? > There's no "great hole" in my theory, Rod. You were looking at the > history of tests that were run _before_ the bad sector was reallocated. Dunno, his original list, which still had the offline uncorrectable showing, had got quite a few extended tests that had completed without error, and your story about why the extended tests did sometimes abort with a read error doesn’t explain why those didn’t. > It's a bit hard to see that, as the "hours" numbers in the self-test > log are apparently recorded as 16-bit numbers and you have to add 65536 to > the recent ones to get values that align with the > Power_On_Hours in the SMART attributes table. Still doesn’t explain the above unless I am having a massive brain fart.