Chris Murphy wrote:
> On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz <r...@htt-consult.com>
>> On 08/09/2017 10:46 AM, Chris Murphy wrote:
>> > If it's a bad sector problem, you'd write to sector 17066160 and see
>> > drive complies or spits back a write error. It looks like a bad sector
>> > that the same LBA is reported each time but I've only ever seen this
>> > both a read error and a UNC error. So I'm not sure it's a bad sector.
>> > What is DID_BAD_TARGET?
>> I have no experience on how to force a write to a specific sector and
>> not cause other problems. I suspect that this sector is in the /
>> Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 sectors
>> Units = sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk label type: dos
>> Disk identifier: 0x0000c89d
>> Device Boot Start End Blocks Id System
>> /dev/sda1 2048 2099199 1048576 83 Linux
>> /dev/sda2 2099200 4196351 1048576 82 Linux swap /
>> /dev/sda3 4196352 468862127 232332888 83 Linux
> LBA 17066160 would be on sda3.
> dd if=/dev/sda skip=17066160 count=1 2>/dev/null | hexdump -C
> That'll read that sector and display hex and ascii. If you recognize the
> contents, it's probably user data. Otherwise, it's file system metadata or
> a system binary.
Yeah, I was going to suggest you find out what that's part of. Try this link
<https://www.gra2.com/article.php/20041015232512624>, which is about
identifying what an unreadable sector is part of.
CentOS mailing list