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
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 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 >
Robert Moskowitz 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?Make sure the cables and power supply are ok. Try the drive in another machine that has a different controller to see if there is an incompatibility between the drive and the controller. You could make a btrfs file system on the whole device: that should say that a trim operation is performed for the whole device. Maybe that helps. If the errors persist, replace the drive. I?d use Intel SSDs because they seam to have the least problems with broken firmwares. Do not use SSDs with hardware RAID controllers unless the SSDs were designed for this application.
To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on a couple of systems and it corrupted pretty quickly. I'd stick with xfs/ext4 if you manage to get the drive working again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Aug 9, 2017 at 1:48 PM, hw <hw at gc-24.de> wrote:> Robert Moskowitz 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? >> > > Make sure the cables and power supply are ok. Try the drive in another > machine > that has a different controller to see if there is an incompatibility > between > the drive and the controller. > > You could make a btrfs file system on the whole device: that should say > that > a trim operation is performed for the whole device. Maybe that helps. > > If the errors persist, replace the drive. I? use Intel SSDs because they > seam to have the least problems with broken firmwares. Do not use SSDs > with > hardware RAID controllers unless the SSDs were designed for this > application. > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > >-- [image: photo] Mark Haney Network Engineer at NeoNova 919-460-3330 <(919)%20460-3330> (opt 1) ? mark.haney at neonova.net www.neonova.net <https://neonova.net/> <https://www.facebook.com/NeoNovaNNS/> <https://twitter.com/NeoNova_NNS> <http://www.linkedin.com/company/neonova-network-services>
I have yet to see a SSD read\write error which wasn't related to disk issues like a bad sector but the controller might have an issue with the drive. To verify it you will need to burn some read\write IOPS of the drive but if it's under warranty then it's better to verify it now then later. Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: eliezer at ngtech.co.il -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Robert Moskowitz Sent: Wednesday, August 9, 2017 17:03 To: CentOS mailing list <centos at centos.org> Subject: [CentOS] Errors on an SSD drive 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
mad.scientist.at.large at tutanota.com
2017-Aug-10 02:44 UTC
[CentOS] Errors on an SSD drive
what file system are you using?? ssd drives have different characteristics that need to be accomadated (including a relatively slow write process which is obvious as soon as the buffer is full), and never, never put a swap partition on it, the high activity will wear it out rather quickly.? might also check cables, often a problem particularly if they are older sata cables being run at a possibly higher than rated speed.? in any case, reformating it might not be a bad idea, and you can always use the command line program badblocks to exercise and test it.? keep in mind the drive will invisibly remap any bad sectors if possible.? if the reported size of the drive is smaller than it should be the drive has run out of spare blocks and dying blocks are being removed from the storage place with no replacements. -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 9. Aug 2017 18:44 by eliezer at ngtech.co.il:> I have yet to see a SSD read\write error which wasn't related to disk issues > like a bad sector but the controller might have an issue with the drive. > To verify it you will need to burn some read\write IOPS of the drive but if > it's under warranty then it's better to verify it now then later. > > Eliezer > > ---- > Eliezer Croitoru > Linux System Administrator > Mobile: +972-5-28704261 > Email: > eliezer at ngtech.co.il > > > > -----Original Message----- > From: CentOS [> mailto:centos-bounces at centos.org> ] On Behalf Of Robert > Moskowitz > Sent: Wednesday, August 9, 2017 17:03 > To: CentOS mailing list <> centos at centos.org> > > Subject: [CentOS] Errors on an SSD drive > > 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
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 >
On 08/09/2017 01:48 PM, hw wrote:> Robert Moskowitz 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? > > Make sure the cables and power supply are ok. Try the drive in > another machine > that has a different controller to see if there is an incompatibility > between > the drive and the controller. > > You could make a btrfs file system on the whole device: that should > say that > a trim operation is performed for the whole device. Maybe that helps.This is a Centos7-armv7hl install which is done by dd the provided image onto a drive, so really can't alter the provided file systems much other than to resize them. What I have is: Model: ATA KINGSTON SV300S3 (scsi) Disk /dev/sda: 240GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 1075MB 1074MB primary ext3 2 1075MB 2149MB 1074MB primary linux-swap(v1) 3 2149MB 240GB 238GB primary ext4> > If the errors persist, replace the drive. I?d use Intel SSDs because > they > seam to have the least problems with broken firmwares. Do not use > SSDs with > hardware RAID controllers unless the SSDs were designed for this > application.