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]

Date:	Wed, 26 Aug 2009 21:37:21 -0400
From:	"Andrei Tanas" <andrei@...as.ca>
To:	"'Mark Lord'" <liml@....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?

> I suggest you try this:
> 
>     hdparm --read-sector 1953519935 /dev/sdb
> 
> If that succeeds, then the sector is good at the drive.

It succeeds.

> 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.

The drive never did report any media errors. It just mysteriously times out once in every few hundred hours while writing the raid superblock in that sector.


--
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/