On 08/09/2017 10:44 PM, mad.scientist.at.large@xxxxxxxxxxxx wrote:
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.
When working with a Cubieboard SoC (or most of the other armv7 boards),
you tend to have everything hanging out:
http://medon.htt-consult.com/~rgm/cubieboard/cubietower-2.JPG
I have checked the cables and they are all tight.
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.
I will have to look into that.
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@xxxxxxxxxxxx:
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@xxxxxxxxxxxx
-----Original Message-----
From: CentOS [> mailto:centos-bounces@xxxxxxxxxx> ] On Behalf Of Robert
Moskowitz
Sent: Wednesday, August 9, 2017 17:03
To: CentOS mailing list <> centos@xxxxxxxxxx> >
Subject: 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@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
