One end of the cable is angled and makes contact with the side panel. So I guess there was the issue.
I have ordered new completely straightened cables online. Let's see if those are any better.
2 Likes
I get the straight ones with tabs that lock it to the ssd. works awsome
A little update: I made a mistake here, ata5 doesn't correspond to my SSD, but rather my CD drive. Don't know if these error messages still are the cause of the freezes, but when the replacement SATA cables arrive, I hope they'll fix the connection issues for good, both on my CD drive and my SSD, just to be sure.
1 Like
Good news and bad news.
Good news: The new SATA cables arrived and the cable connected to my SSD isn't touching the side panel anymore. So I hope I can rule out an issue with the cable here.
Bad news: The new cable on my CD drive didn't fix the speed limit loop issue. Even after connecting it to an entirely different cable to a different SATA port on my motherboard, it wouldn't fix it. It would only maintain a connection after whacking my PC a little. So perhaps something may be broken in the CD drive internally. Ah well, I wasn't using that thing much anyway. I'll just leave it disconnected, in the hopes that it won't cause any problems in the future. If I still get crashes, I'll let you know. I also will keep a Terminal window with journalctl -f open, in the hopes of it revealing the source of the crashes.
1 Like
No freezes for 15 days straight... until now. Again when the PC is idle. However, when I launched a game and lag spikes occured, I noticed this in journalctl -f:
Jul 28 23:46:59 (...) kernel: ata2.00: limiting speed to UDMA/33:PIO4
Jul 28 23:46:59 (...) kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
Jul 28 23:46:59 (...) kernel: ata2.00: irq_stat 0x00000040, connection status changed
Jul 28 23:46:59 (...) kernel: ata2: SError: { PHYRdyChg CommWake DevExch }
Jul 28 23:46:59 (...) kernel: ata2.00: failed command: READ DMA EXT
Jul 28 23:46:59 (...) kernel: ata2.00: cmd 25/00:48:10:8f:25/00:05:5a:01:00/e0 tag 22 dma 692224 in
res 50/00:00:1f:c4:25/00:00:5a:01:00/e0 Emask 0x10 (ATA bus error)
Jul 28 23:46:59 (...) kernel: ata2.00: status: { DRDY }
Jul 28 23:46:59 (...) kernel: ata2: hard resetting link
Jul 28 23:47:00 (...) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 28 23:47:00 (...) kernel: ata2.00: failed to set xfermode (err_mask=0x40)
Jul 28 23:47:05 (...) kernel: ata2: hard resetting link
Jul 28 23:47:06 (...) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 28 23:47:06 (...) kernel: ata2.00: configured for UDMA/33
Jul 28 23:47:06 (...) kernel: sd 1:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
Jul 28 23:47:06 (...) kernel: sd 1:0:0:0: [sda] tag#22 Sense Key : Aborted Command [current]
Jul 28 23:47:06 (...) kernel: sd 1:0:0:0: [sda] tag#22 Add. Sense: No additional sense information
Jul 28 23:47:06 (...) kernel: sd 1:0:0:0: [sda] tag#22 CDB: Read(16) 88 00 00 00 00 01 5a 25 8f 10 00 00 05 48 00 00
Jul 28 23:47:06 (...) kernel: I/O error, dev sda, sector 5807378192 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 2
Jul 28 23:47:06 (...) kernel: ata2: EH complete
Jul 28 23:47:06 (...) kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
Jul 28 23:47:06 (...) kernel: ata2.00: irq_stat 0x00000040, connection status changed
Jul 28 23:47:06 (...) kernel: ata2: SError: { PHYRdyChg CommWake DevExch }
Jul 28 23:47:06 (...) kernel: ata2.00: failed command: READ DMA EXT
Jul 28 23:47:06 (...) kernel: ata2.00: cmd 25/00:50:28:31:23/00:06:4a:01:00/e0 tag 23 dma 827392 in
res 50/00:00:27:31:23/00:00:4a:01:00/e0 Emask 0x10 (ATA bus error)
Jul 28 23:47:06 (...) kernel: ata2.00: status: { DRDY }
Jul 28 23:47:06 (...) kernel: ata2: hard resetting link
Jul 28 23:47:07 (...) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 28 23:47:07 (...) kernel: ata2.00: failed to set xfermode (err_mask=0x40)
Jul 28 23:47:12 (...) kernel: ata2: hard resetting link
Jul 28 23:47:13 (...) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 28 23:47:13 (...) kernel: ata2.00: configured for UDMA/33
Jul 28 23:47:13 (...) kernel: sd 1:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
Jul 28 23:47:13 (...) kernel: sd 1:0:0:0: [sda] tag#23 Sense Key : Aborted Command [current]
Jul 28 23:47:13 (...) kernel: sd 1:0:0:0: [sda] tag#23 Add. Sense: No additional sense information
Jul 28 23:47:13 (...) kernel: sd 1:0:0:0: [sda] tag#23 CDB: Read(16) 88 00 00 00 00 01 4a 23 31 28 00 00 06 50 00 00
Jul 28 23:47:13 (...) kernel: I/O error, dev sda, sector 5538787624 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 2
Jul 28 23:47:13 (...) kernel: ata2: EH complete
Jul 28 23:47:13 (...) kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
Jul 28 23:47:13 (...) kernel: ata2.00: irq_stat 0x00000040, connection status changed
Jul 28 23:47:13 (...) kernel: ata2: SError: { PHYRdyChg CommWake DevExch }
Jul 28 23:47:13 (...) kernel: ata2.00: failed command: READ DMA EXT
Jul 28 23:47:13 (...) kernel: ata2.00: cmd 25/00:f0:10:bd:51/00:07:4a:01:00/e0 tag 14 dma 1040384 in
res 50/00:00:0f:bd:51/00:00:4a:01:00/e0 Emask 0x10 (ATA bus error)
Jul 28 23:47:13 (...) kernel: ata2.00: status: { DRDY }
Jul 28 23:47:13 (...) kernel: ata2: hard resetting link
Jul 28 23:47:14 (...) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 28 23:47:14 (...) kernel: ata2.00: failed to set xfermode (err_mask=0x40)
Jul 28 23:47:19 (...) kernel: ata2: hard resetting link
Jul 28 23:47:20 (...) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 28 23:47:20 (...) kernel: ata2.00: configured for UDMA/33
Jul 28 23:47:20 (...) kernel: sd 1:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
Jul 28 23:47:20 (...) kernel: sd 1:0:0:0: [sda] tag#14 Sense Key : Aborted Command [current]
Jul 28 23:47:20 (...) kernel: sd 1:0:0:0: [sda] tag#14 Add. Sense: No additional sense information
Jul 28 23:47:20 (...) kernel: sd 1:0:0:0: [sda] tag#14 CDB: Read(16) 88 00 00 00 00 01 4a 51 bd 10 00 00 07 f0 00 00
Jul 28 23:47:20 (...) kernel: I/O error, dev sda, sector 5541838096 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 2
Jul 28 23:47:20 (...) kernel: ata2: EH complete
ata2 corresponds to my HDD, where I put my Games on. There is nothing on there that's related to booting. I'll have it open for a while again, to see if something happens with my SSD.
Zorin 18 is telling you, "Ewe, there is a mechanical hard drive on this computer. I am going to freeze!"
I am typing this on a 1 TB mechanical hard drive, the laptop was built for Windows 10. It was stalling so much I went to Zorin 17, and it still stalled.
Windows 10, 11, Zorin 17, 18 hate mechanical hard drives. I went backwards, I am using Zorin 16.3 on this computer, and my other computer with a Mechanical hard drive I am using Windows 8.1, with Zorin 16.3 Lite and Core in the VirtualBox.
Not that I can say exactly what is happening, yet these newer OS's hate mechanical hard drives.
If i remember correct the mechanical drives tryed to get a speed boost with the introduction of sata connections got some but not alot....soon after the first series sata ssds appeared making accessing the ssd way faster..550 mbs vs 150mbs now we have nvme drives which are becoming the industry standard started seeing these when the pcie 3.0 came out now we at pcie 5.0 i have a pcie 4.0 board and the nvmes are nearly instantaneous now Most folks use the old spinup drives as a storage drive mostly not on operating systems