Re: how to test disk for bad sector
- To: debian-user@lists.debian.org
- Subject: Re: how to test disk for bad sector
- From: David Wright <deblis@lionunicorn.co.uk>
- Date: Mon, 7 Sep 2020 23:27:15 -0500
- Message-id: <[🔎] 20200908042715.GD2304@axis.corp>
- Reply-to: debian-user@lists.debian.org
- In-reply-to: <CAMPXz=qgx6CfNCWcn=58+LezrhtywPTdzREqfEsnwDpZ6ssXGQ@mail.gmail.com>
- References: <537557110.32145.1598669993940.ref@mail.yahoo.com> <537557110.32145.1598669993940@mail.yahoo.com> <20200828203531.0330af5c@debian9> <1889267699.46556.1598680012554@mail.yahoo.com> <CAMPXz=oNFp21C==7i+G_nzV4-d5mFOVkHqhgv7qxFVO6hD4fOA@mail.gmail.com> <934603234.72291.1598694646179@mail.yahoo.com> <CAMPXz=qgx6CfNCWcn=58+LezrhtywPTdzREqfEsnwDpZ6ssXGQ@mail.gmail.com>
On Sun 30 Aug 2020 at 08:02:24 (+1000), David wrote:
> On Sat, 29 Aug 2020 at 19:51, Long Wind <longwind2@yahoo.com> wrote:
>
> > sudo smartctl -A /dev/sda1
> [...]
> > 188 Command_Timeout 0x0032 100 068 000 Old_age Always - 403733086445
>
> That result does not look good. It should be a low number.
I wouldn't take that number at face value. First, convert it into hex
and take another look. I've seen several postings on the web with
>>> hex(4295032833)
'0x1 0001 0001' ← I added the spaces
and I have a drive with
188 Command_Timeout -O--CK 100 099 000 - 12885098499
>>> hex(12885098499)
'0x3 0003 0003'
and another with
188 Command_Timeout -O--CK 100 096 000 - 137441116198
>>> hex(137441116198)
'0x20 0021 0026'
so the OP should look at
>>> hex(403733086445)
'0x5e 005e 00ed'
and ponder what they could mean.
Moral: always see what very large numbers look like in hex.
Cheers,
David.
Reply to: