linux-kernel - Re: MD/RAID: what's wrong with sector 1953519935?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A95CE31.80404@rtr.ca>
Date:	Wed, 26 Aug 2009 20:07:13 -0400
From:	Mark Lord <liml@....ca>
To:	Andrei Tanas <andrei@...as.ca>
Cc:	Ric Wheeler <rwheeler@...hat.com>, NeilBrown <neilb@...e.de>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: MD/RAID: what's wrong with sector 1953519935?

Andrei Tanas wrote:
> On Wed, 26 Aug 2009 11:39:38 -0400, Ric Wheeler <rwheeler@...hat.com>
> wrote:
>> On 08/26/2009 10:46 AM, Andrei Tanas wrote:
>>> On Wed, 26 Aug 2009 06:34:14 -0400, Ric Wheeler<rwheeler@...hat.com>
>>> wrote:
>>>> On 08/25/2009 11:45 PM, Andrei Tanas wrote:
>>>>>>>> I would suggest that Andrei might try to write and clear the IO
>>>>>> error
>>>>>>>> at that
>>>>>>>> offset. You can use Mark Lord's hdparm to clear a specific sector
..
> [90318.370625] end_request: I/O error, dev sdb, sector 1953519935
..

I suggest you try this:

    hdparm --read-sector 1953519935 /dev/sdb

If that succeeds, then the sector is good at the drive.
But *If* it fails, then you could check the syslog to ensure
that it didn't fail for some weird reason, and then *fix* it:

    hdparm --write-sector 1953519935 /dev/sdb

This is very different from how 'dd' does writes.

Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/