[prev in list] [next in list] [prev in thread] [next in thread] 

List:       smartmontools-support
Subject:    Re: [smartmontools-support] LBA->file
From:       Bruce Allen <ballen () gravity ! phys ! uwm ! edu>
Date:       2008-09-18 6:13:38
Message-ID: Pine.LNX.4.64.0809180111300.26103 () gc ! phys ! uwm ! edu
[Download RAW message or body]

Ben: thanks for the good news.  This is the 'raison d'etre' for 
smartmontools: you've been able to understand (and then fix) what was 
going wrong with your hard disk.

Justin: thanks for helping out Ben!

cheers,
 	Bruce


On Wed, 17 Sep 2008, ben@bcchang.com wrote:

> Hi, just wanted to make sure I said "thanks"!  as far as I can tell
> this in fact worked; I had to do it about ten times, and it was
> interesting to see that indeed the long selftest picks up errors that
> the short selftest misses.  eventually the OFFLINE_UNCORRECTABLE
> reduced down to 0, and now the drive reports clean from smartctl,
> badblocks, and fsck.  :)
>
> It's also interesting to see that it's possible to have blocks that
> are so bad in some way that badblocks will die trying to see if
> they're bad.  but this trick fixed it.  oh, and for my original
> question, I found that, I just wasn't reading the smartmon website
> carefully enough.
>
> thanks,
>
> --ben
>
> Quoting Justin Piszcz <jpiszcz@lucidpixels.com>:
>
>>
>>
>> On Tue, 9 Sep 2008, ben@bcchang.com wrote:
>>
>>> In the man page, it says that there's information on how to figure out
>>> which file is at a particular LBA; but I'm having a hard time finding
>>> it :)
>>>
>>> I just discovered smartmontools, which I installed of course -after- I
>>> think I have a problem (namely: fsck freezes).
>>>
>>> overall health is "PASSED", but the short test gives me this:
>>>
>>> Num  Test_Description    Status                  Remaining
>>> LifeTime(hours)  LBA_of_first_error
>>> # 1  Short offline       Completed: read failure       90%      4258
>>>      92246636
>>>
>>> my last five errors are "READ FPDMA QUEUED" and "WRITE FPDMA QUEUED".
>>>
>>> how do i know if it's a failing drive, or just a bad block?
>>>
>>> thanks,
>>>
>>> --ben
>>>
>>
>> I had the same problem recently, if you run a dd across read/write +
>> badblocks + smart long,short,offline over the disk, it will usually go
>> away after that.
>>
>> You can also use smartctl to test the specific LBA of the error as well
>> btw, check smartctl's manpage.
>>
>> Justin.
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Smartmontools-support mailing list
> Smartmontools-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
[prev in list] [next in list] [prev in thread] [next in thread]