Re: Problems with SSD
On 06/03/2015 03:51 AM, Petter Adsen wrote: On Tue, 2 Jun 2015 18:36:43 +0300 Selim T. Erdoğan se...@alumni.cs.utexas.edu wrote: On Fri, May 29, 2015 at 11:18:35AM +0200, Petter Adsen wrote: This just in: snip [12675.977977] ata5: hard resetting link [12680.979063] ata4: softreset failed (1st FIS failed) [12680.979080] ata4: hard resetting link [12685.976201] ata5: softreset failed (1st FIS failed) You could try forcing the drive to a lower speed to see if taxing the hardware less will avoid triggering the problem. Make a file /etc/modprobe.d/local.conf and put the single line options libata force=1.5G in it. Reboot. If it works, you can then try with 3.0G instead of 1.5G. Thanks, I will try that and see if it helps, but it seems a lot like a hardware problem. This motherboard is getting to be a few years old, and has been working fine up until now, it just started behaving like this a few days ago. I'm investigating new motherboards now, since I heavily suspect that is going to be what I'll end up having to do. The drives/controller are not heavily utilized when this happens, the machine is just churning along with low load. I always have gkrellm open, and there is never any hint that utilization has anything to do with this. You might have your power supply checked as well. With all of those drives, you might be straining for more juice and, as a result, the system appears flakey. Ric -- My father, Victor Moore (Vic) used to say: There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome. R.I.P. Dad. http://linuxcounter.net/user/44256.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/556f65d4.6020...@gmail.com
Re: Problems with SSD
On Tue, 2 Jun 2015 18:36:43 +0300 Selim T. Erdoğan se...@alumni.cs.utexas.edu wrote: On Fri, May 29, 2015 at 11:18:35AM +0200, Petter Adsen wrote: This just in: snip [12675.977977] ata5: hard resetting link [12680.979063] ata4: softreset failed (1st FIS failed) [12680.979080] ata4: hard resetting link [12685.976201] ata5: softreset failed (1st FIS failed) You could try forcing the drive to a lower speed to see if taxing the hardware less will avoid triggering the problem. Make a file /etc/modprobe.d/local.conf and put the single line options libata force=1.5G in it. Reboot. If it works, you can then try with 3.0G instead of 1.5G. Thanks, I will try that and see if it helps, but it seems a lot like a hardware problem. This motherboard is getting to be a few years old, and has been working fine up until now, it just started behaving like this a few days ago. I'm investigating new motherboards now, since I heavily suspect that is going to be what I'll end up having to do. The drives/controller are not heavily utilized when this happens, the machine is just churning along with low load. I always have gkrellm open, and there is never any hint that utilization has anything to do with this. I will try it, though. Petter -- I'm ionized Are you sure? I'm positive. pgp9nMkIqNjO3.pgp Description: OpenPGP digital signature
Re: Problems with SSD
On Tue, 02 Jun 2015 13:46:55 -0400 Gary Dale garyd...@torfree.net wrote: On 30/05/15 02:17 AM, Petter Adsen wrote: On Fri, 29 May 2015 13:18:17 -0600 Bob Proulx b...@proulx.com wrote: Jochen Spieker wrote: Petter Adsen: I'm starting to suspect that it is. Either that, or the controller on the motherboard, which would be even worse. Or just the cable (if we are not talking about a laptop). I got rid of similar errors in the past by replacing the SATA cable. If it were me I would swap cables and move to a different SATA port on the motherboard. I have seen individual SATA ports fail with the rest of the ports okay. I also have the advantage of many different sets of hardware available and so I would mix and match the various parts into different systems. If the problem stays with the system or moves with the moved part is a good diagnostic aid in determining which piece of hardware or software is causing problems. In this case it is 1) the kernel software 2) sata cable 3) sata device 4) motherboard sata controller. At least one of those is the problem. It is a mental game of Mastermind to determine which. From what I can understand of the messages above, it seems the error messages are coming from two different devices, ata4 and ata5 - or am I wrong? To me, that would (unfortunately) indicate the controller... Petter Could potentially be a BIOS setting depending on how the BIOS numbers its drives. The first 4 drives are usually set the same while the last 2 can be set differently. Normally the first 4 should be set to AHCI while the last 2 should be set to the same as the first 4. In my case it's 6 and 2, and all are set to AHCI. Petter -- I'm ionized Are you sure? I'm positive. pgpmAqm6VepYq.pgp Description: OpenPGP digital signature
Re: Problems with SSD
On Fri, May 29, 2015 at 11:18:35AM +0200, Petter Adsen wrote:
This just in:
[12490.684280] ata4.00: exception Emask 0x0 SAct 0x7f007fff SErr 0x0 action
0x6 frozen
[12490.684296] ata4.00: failed command: WRITE FPDMA QUEUED
[12490.684312] ata4.00: cmd 61/b8:00:e8:7d:87/00:00:06:00:00/40 tag 0 ncq
94208 out
res 40/00:01:c8:7f:d5/00:00:1d:00:00/e0 Emask 0x4 (timeout)
[12490.684320] ata4.00: status: { DRDY }
[12490.684326] ata4.00: failed command: READ FPDMA QUEUED
[12490.684338] ata4.00: cmd 60/08:08:80:47:f9/00:00:0d:00:00/40 tag 1 ncq
4096 in
[12545.656751] ata4: limiting SATA link speed to 3.0 Gbps
[12545.656758] ata4: hard resetting link
[12550.657835] ata5: softreset failed (1st FIS failed)
[12550.657850] ata5: hard resetting link
[12550.853737] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[12550.853751] ata4.00: link online but device misclassified
[12555.850872] ata4.00: qc timeout (cmd 0xec)
[12555.850891] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[12555.850898] ata4.00: revalidation failed (errno=-5)
[12555.850909] ata4: hard resetting link
[12605.826168] ata5: softreset failed (1st FIS failed)
[12605.826176] ata5: hard resetting link
[12610.819329] ata4: softreset failed (1st FIS failed)
[12610.819345] ata4: limiting SATA link speed to 1.5 Gbps
[12610.819352] ata4: hard resetting link
[12615.820431] ata5: softreset failed (1st FIS failed)
[12615.820447] ata5: hard resetting link
[12616.004368] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[12616.004381] ata4.00: link online but device misclassified
[12625.998617] ata4.00: qc timeout (cmd 0xec)
[12625.998637] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[12625.998644] ata4.00: revalidation failed (errno=-5)
[12625.998656] ata4: hard resetting link
[12635.996892] ata4: softreset failed (1st FIS failed)
[12635.996907] ata4: hard resetting link
[12645.995158] ata4: softreset failed (1st FIS failed)
[12645.995174] ata4: hard resetting link
[12650.800410] ata5: softreset failed (1st FIS failed)
[12650.800427] ata5: limiting SATA link speed to 1.5 Gbps
[12650.800434] ata5: hard resetting link
[12655.985396] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[12655.985409] ata5.00: link online but device misclassified
[12665.979715] ata5.00: qc timeout (cmd 0xec)
[12665.979735] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[12665.979742] ata5.00: revalidation failed (errno=-5)
[12665.979754] ata5: hard resetting link
[12675.977962] ata5: softreset failed (1st FIS failed)
[12675.977977] ata5: hard resetting link
[12680.979063] ata4: softreset failed (1st FIS failed)
[12680.979080] ata4: hard resetting link
[12685.976201] ata5: softreset failed (1st FIS failed)
You could try forcing the drive to a lower speed to see if taxing the
hardware less will avoid triggering the problem.
Make a file /etc/modprobe.d/local.conf and put the single line
options libata force=1.5G
in it. Reboot. If it works, you can then try with 3.0G instead of 1.5G.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150602153643.GA27845@side
Re: Problems with SSD
On 30/05/15 02:17 AM, Petter Adsen wrote: On Fri, 29 May 2015 13:18:17 -0600 Bob Proulx b...@proulx.com wrote: Jochen Spieker wrote: Petter Adsen: I'm starting to suspect that it is. Either that, or the controller on the motherboard, which would be even worse. Or just the cable (if we are not talking about a laptop). I got rid of similar errors in the past by replacing the SATA cable. If it were me I would swap cables and move to a different SATA port on the motherboard. I have seen individual SATA ports fail with the rest of the ports okay. I also have the advantage of many different sets of hardware available and so I would mix and match the various parts into different systems. If the problem stays with the system or moves with the moved part is a good diagnostic aid in determining which piece of hardware or software is causing problems. In this case it is 1) the kernel software 2) sata cable 3) sata device 4) motherboard sata controller. At least one of those is the problem. It is a mental game of Mastermind to determine which. From what I can understand of the messages above, it seems the error messages are coming from two different devices, ata4 and ata5 - or am I wrong? To me, that would (unfortunately) indicate the controller... Petter Could potentially be a BIOS setting depending on how the BIOS numbers its drives. The first 4 drives are usually set the same while the last 2 can be set differently. Normally the first 4 should be set to AHCI while the last 2 should be set to the same as the first 4. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/556dec0f.8090...@torfree.net
Re: Problems with SSD
On Fri, 29 May 2015 13:18:17 -0600 Bob Proulx b...@proulx.com wrote: Jochen Spieker wrote: Petter Adsen: I'm starting to suspect that it is. Either that, or the controller on the motherboard, which would be even worse. Or just the cable (if we are not talking about a laptop). I got rid of similar errors in the past by replacing the SATA cable. If it were me I would swap cables and move to a different SATA port on the motherboard. I have seen individual SATA ports fail with the rest of the ports okay. I also have the advantage of many different sets of hardware available and so I would mix and match the various parts into different systems. If the problem stays with the system or moves with the moved part is a good diagnostic aid in determining which piece of hardware or software is causing problems. In this case it is 1) the kernel software 2) sata cable 3) sata device 4) motherboard sata controller. At least one of those is the problem. It is a mental game of Mastermind to determine which. From what I can understand of the messages above, it seems the error messages are coming from two different devices, ata4 and ata5 - or am I wrong? To me, that would (unfortunately) indicate the controller... Petter -- I'm ionized Are you sure? I'm positive. pgpDuVNywDlny.pgp Description: OpenPGP digital signature
Re: Problems with SSD
On 29/05/2015 5:08 PM, Petter Adsen pet...@synth.no wrote: When I woke up this morning, one of my boxen had spewed out a ton of errors from one of my SSDs (the root drive), remounted read-only, and went into a kernel panic. After rebooting everything seems fine, though. I've ran a SMART long test, but as I found out the SMART error log is not supported on this drive. Neither do I have the log of what happened, since / was remounted ro. I've included the output of smartctl --all /dev/sdc, but I can't see anything that stands out. Yesterday, I had another kernel panic (that seemed related to systemd), so I suspect the (manually built) kernel to be at fault here. The RAM in this machine is all brand new, and I ran memtest less than two weeks ago, so that should be fine. Can anyone look at this log and tell me if there is anything to worry about? Which of the attributes should I look at, so that I know in the future? (And I did a full backup as recently as yesterday that was tested OK at the time, so data loss is not a concern. Everything important is on other drives anyway.) ---snip--- smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.19.0-18-generic] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: SandForce Driven SSDs Device Model: KINGSTON SV300S37A120G Serial Number:snip LU WWN Device Id: 5 0026b7 74703dbf1 Firmware Version: 525ABBF0 User Capacity:120 034 123 776 bytes [120 GB] Sector Size: 512 bytes logical/physical Rotation Rate:Solid State Device Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS, ACS-2 T13/2015-D revision 3 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Fri May 29 08:50:31 2015 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:(0) seconds. Offline data collection capabilities:(0x79) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 36) minutes. Conveyance self-test routine recommended polling time:( 2) minutes. SCT capabilities: (0x0025) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0033 095 095 050Pre-fail Always - 0/6132927 5 Retired_Block_Count 0x0033 100 100 003Pre-fail Always - 0 9 Power_On_Hours_and_Msec 0x0032 096 096 000Old_age Always - 4237h+54m+09.420s 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 74 171 Program_Fail_Count 0x000a 000 000 000Old_age Always - 0 172 Erase_Fail_Count0x0032 000 000 000Old_age Always - 0 174 Unexpect_Power_Loss_Ct 0x0030 000 000 000Old_age Offline - 65 177 Wear_Range_Delta0x 000 000 000Old_age Offline - 0 181 Program_Fail_Count 0x000a 000 000 000Old_age Always - 0 182 Erase_Fail_Count0x0032 000 000 000Old_age Always -
Re: Problems with SSD
196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0 Reallocated_Event_Count is 0 meaning no bad sectors were ever found. I have a failing drive atm and this number slowly piles up. 201 Unc_Soft_Read_Err_Rate 0x001c 120 120 000Old_age Offline - 0/6132927 The question is if the string above has any meaning in ssd context... Usually one can see more information in dmesg output. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55682494.8040...@biotec.tu-dresden.de
Re: Problems with SSD
On Fri, 2015-05-29 at 09:08 +0200, Petter Adsen wrote: When I woke up this morning, one of my boxen had spewed out a ton of errors from one of my SSDs (the root drive), remounted read-only, and went into a kernel panic. It's probably a good idea to test with the manufacturers own diagnostic tool to make sure nothing is wrong with the disk. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Problems with SSD
When I woke up this morning, one of my boxen had spewed out a ton of errors from one of my SSDs (the root drive), remounted read-only, and went into a kernel panic. After rebooting everything seems fine, though. I've ran a SMART long test, but as I found out the SMART error log is not supported on this drive. Neither do I have the log of what happened, since / was remounted ro. I've included the output of smartctl --all /dev/sdc, but I can't see anything that stands out. Yesterday, I had another kernel panic (that seemed related to systemd), so I suspect the (manually built) kernel to be at fault here. The RAM in this machine is all brand new, and I ran memtest less than two weeks ago, so that should be fine. Can anyone look at this log and tell me if there is anything to worry about? Which of the attributes should I look at, so that I know in the future? (And I did a full backup as recently as yesterday that was tested OK at the time, so data loss is not a concern. Everything important is on other drives anyway.) ---snip--- smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.19.0-18-generic] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: SandForce Driven SSDs Device Model: KINGSTON SV300S37A120G Serial Number:snip LU WWN Device Id: 5 0026b7 74703dbf1 Firmware Version: 525ABBF0 User Capacity:120 034 123 776 bytes [120 GB] Sector Size: 512 bytes logical/physical Rotation Rate:Solid State Device Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS, ACS-2 T13/2015-D revision 3 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Fri May 29 08:50:31 2015 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:(0) seconds. Offline data collection capabilities:(0x79) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 36) minutes. Conveyance self-test routine recommended polling time:( 2) minutes. SCT capabilities: (0x0025) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0033 095 095 050Pre-fail Always - 0/6132927 5 Retired_Block_Count 0x0033 100 100 003Pre-fail Always - 0 9 Power_On_Hours_and_Msec 0x0032 096 096 000Old_age Always - 4237h+54m+09.420s 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 74 171 Program_Fail_Count 0x000a 000 000 000Old_age Always - 0 172 Erase_Fail_Count0x0032 000 000 000Old_age Always - 0 174 Unexpect_Power_Loss_Ct 0x0030 000 000 000Old_age Offline - 65 177 Wear_Range_Delta0x 000 000 000Old_age Offline - 0 181 Program_Fail_Count 0x000a 000 000 000Old_age Always - 0 182 Erase_Fail_Count0x0032 000 000 000Old_age Always - 0 187 Reported_Uncorrect 0x0012 100 100 000Old_age Always - 0 189
Re: Problems with SSD
On Fri, 29 May 2015 11:04:09 +0200
Sven Arvidsson s...@whiz.se wrote:
On Fri, 2015-05-29 at 09:08 +0200, Petter Adsen wrote:
When I woke up this morning, one of my boxen had spewed out a ton of
errors from one of my SSDs (the root drive), remounted read-only,
and went into a kernel panic.
It's probably a good idea to test with the manufacturers own
diagnostic tool to make sure nothing is wrong with the disk.
I'm starting to suspect that it is. Either that, or the controller on
the motherboard, which would be even worse.
This just in:
[12490.684280] ata4.00: exception Emask 0x0 SAct 0x7f007fff SErr 0x0 action 0x6
frozen
[12490.684296] ata4.00: failed command: WRITE FPDMA QUEUED
[12490.684312] ata4.00: cmd 61/b8:00:e8:7d:87/00:00:06:00:00/40 tag 0 ncq 94208
out
res 40/00:01:c8:7f:d5/00:00:1d:00:00/e0 Emask 0x4 (timeout)
[12490.684320] ata4.00: status: { DRDY }
[12490.684326] ata4.00: failed command: READ FPDMA QUEUED
[12490.684338] ata4.00: cmd 60/08:08:80:47:f9/00:00:0d:00:00/40 tag 1 ncq 4096
in
[12545.656751] ata4: limiting SATA link speed to 3.0 Gbps
[12545.656758] ata4: hard resetting link
[12550.657835] ata5: softreset failed (1st FIS failed)
[12550.657850] ata5: hard resetting link
[12550.853737] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[12550.853751] ata4.00: link online but device misclassified
[12555.850872] ata4.00: qc timeout (cmd 0xec)
[12555.850891] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[12555.850898] ata4.00: revalidation failed (errno=-5)
[12555.850909] ata4: hard resetting link
[12605.826168] ata5: softreset failed (1st FIS failed)
[12605.826176] ata5: hard resetting link
[12610.819329] ata4: softreset failed (1st FIS failed)
[12610.819345] ata4: limiting SATA link speed to 1.5 Gbps
[12610.819352] ata4: hard resetting link
[12615.820431] ata5: softreset failed (1st FIS failed)
[12615.820447] ata5: hard resetting link
[12616.004368] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[12616.004381] ata4.00: link online but device misclassified
[12625.998617] ata4.00: qc timeout (cmd 0xec)
[12625.998637] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[12625.998644] ata4.00: revalidation failed (errno=-5)
[12625.998656] ata4: hard resetting link
[12635.996892] ata4: softreset failed (1st FIS failed)
[12635.996907] ata4: hard resetting link
[12645.995158] ata4: softreset failed (1st FIS failed)
[12645.995174] ata4: hard resetting link
[12650.800410] ata5: softreset failed (1st FIS failed)
[12650.800427] ata5: limiting SATA link speed to 1.5 Gbps
[12650.800434] ata5: hard resetting link
[12655.985396] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[12655.985409] ata5.00: link online but device misclassified
[12665.979715] ata5.00: qc timeout (cmd 0xec)
[12665.979735] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[12665.979742] ata5.00: revalidation failed (errno=-5)
[12665.979754] ata5: hard resetting link
[12675.977962] ata5: softreset failed (1st FIS failed)
[12675.977977] ata5: hard resetting link
[12680.979063] ata4: softreset failed (1st FIS failed)
[12680.979080] ata4: hard resetting link
[12685.976201] ata5: softreset failed (1st FIS failed)
Petter
--
I'm ionized
Are you sure?
I'm positive.
pgppHckutK4HF.pgp
Description: OpenPGP digital signature
Re: Problems with SSD
Petter Adsen: On Fri, 29 May 2015 11:04:09 +0200 It's probably a good idea to test with the manufacturers own diagnostic tool to make sure nothing is wrong with the disk. I'm starting to suspect that it is. Either that, or the controller on the motherboard, which would be even worse. Or just the cable (if we are not talking about a laptop). I got rid of similar errors in the past by replacing the SATA cable. J. -- I throw away plastics and think about the discoveries of future archeologists. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Problems with SSD
Jochen Spieker wrote: Petter Adsen: I'm starting to suspect that it is. Either that, or the controller on the motherboard, which would be even worse. Or just the cable (if we are not talking about a laptop). I got rid of similar errors in the past by replacing the SATA cable. If it were me I would swap cables and move to a different SATA port on the motherboard. I have seen individual SATA ports fail with the rest of the ports okay. I also have the advantage of many different sets of hardware available and so I would mix and match the various parts into different systems. If the problem stays with the system or moves with the moved part is a good diagnostic aid in determining which piece of hardware or software is causing problems. In this case it is 1) the kernel software 2) sata cable 3) sata device 4) motherboard sata controller. At least one of those is the problem. It is a mental game of Mastermind to determine which. Bob https://en.wikipedia.org/wiki/Mastermind_(board_game) signature.asc Description: Digital signature
