If it's a bad sector problem, you'd write to sector 17066160 and see if the
drive complies or spits back a write error. It looks like a bad sector in
that the same LBA is reported each time but I've only ever seen this with
both a read error and a UNC error. So I'm not sure it's a bad sector.
What is DID_BAD_TARGET?
And what do you get for
smartctl -x <dev>
Chris Murphy
On Wed, Aug 9, 2017, 8:03 AM Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
> I am building a new system using an Kingston 240GB SSD drive I pulled
> from my notebook (when I had to upgrade to a 500GB SSD drive). Centos
> install went fine and ran for a couple days then got errors on the
> console. Here is an example:
>
> [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0
> 00 00 08 00
> [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160
> [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> [168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 b0
> 00 00 08 00
> [168487.551206] blk_update_request: I/O error, dev sda, sector 17066160
> [168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> [168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 b0
> 00 00 08 00
> [168787.830544] blk_update_request: I/O error, dev sda, sector 17066160
>
> Eventually, I could not do anything on the system. Not even a
> 'reboot'. I had to do a cold power cycle to bring things back.
>
> Is there anything to do about this or trash the drive and start anew?
>
> Thanks
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
