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 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?
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 / partition:
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 / Solaris
/dev/sda3 4196352 468862127 232332888 83 Linux
But I don't know where it is in relation to the way the drive was
formatted in my notebook. I think it would have been in the / partition.
> And what do you get for
> smartctl -x <dev>
About 17KB of output? I don't know how to read what it is saying, but
noted in the beginning:
Write SCT (Get) XXX Error Recovery Control Command failed: scsi error
badly formed scsi parameters
Don't know what this means...
BTW, the system is a Cubieboard2 armv7 SoC running Centos7-armv7hl. This
is the first time I have used an SSD on a Cubie, but I know it is
frequently done. I would have to ask on the Cubie forum what others
experience with SSDs have been.
>
> Chris Murphy
>
> On Wed, Aug 9, 2017, 8:03 AM Robert Moskowitz <rgm at htt-consult.com> 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 at centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>