Weird ATA errors on Linux?

[Zairker]

Hello,
recently I installed Ubuntu 19.04, and I noticed random temporary (15 seconds or so) system lockups. After launching dmesg in the terminal I came upon this:

About 15 times this message

[14298.730325] ata1.00: exception Emask 0x0 SAct 0xffffffff SErr 0x50000 action 0x6 frozen
[14298.730334] ata1: SError: { PHYRdyChg CommWake }
[14298.730338] ata1.00: failed command: READ FPDMA QUEUED
[14298.730347] ata1.00: cmd 60/08:00:c8:11:40/00:00:14:00:00/40 tag 0 ncq dma 4096 in
                        res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[14298.730350] ata1.00: status: { DRDY }
[14298.730353] ata1.00: failed command: READ FPDMA QUEUED
[14298.730359] ata1.00: cmd 60/08:08:d0:11:40/00:00:14:00:00/40 tag 1 ncq dma 4096 in
                        res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

(about 10 times, then)

[14298.730707] ata1: hard resetting link
[14299.045180] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[14299.046672] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[14299.048815] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[14299.049229] ata1.00: configured for UDMA/133

[14299.061943] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14299.061950] sd 0:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[14299.061953] sd 0:0:0:0: [sda] tag#0 Add. Sense: Unaligned write command
[14299.061958] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 14 40 11 c8 00 00 08 00
[14299.061962] print_req_error: I/O error, dev sda, sector 339743176 flags 80700
[14299.061995] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14299.061997] sd 0:0:0:0: [sda] tag#1 Sense Key : Illegal Request [current] 
[14299.062000] sd 0:0:0:0: [sda] tag#1 Add. Sense: Unaligned write command
[14299.062003] sd 0:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 14 40 11 d0 00 00 08 00
[14299.062005] print_req_error: I/O error, dev sda, sector 339743184 flags 80700

(about 10 times too.)

Looking on various forums the apparent issue is the HDD connection.
BUT, this issue started after installing Ubuntu 19.04. Could this be a kernel issue? If so, how could I fix this? Kernel version is 5.0.0-13-generic.

Thanks in advance.
(Also, sorry for the potential bad English)

[Bad 💀 Motha]

Run diagnostics on all your drives firstly

[Zairker]

Diagnostics runs smoothly, no issue except the HDD temperature sensor (been broken in past but fixed). Any other ideas?

[Bad 💀 Motha]

Try a different Linux maybe, such as MINT and see if that also produces similar issues. As it could be Linux in general doesn't like your motherboard, it's chipset, sata, etc...

[Talby]

aside from the usual bad drive / bad cable problems - have seen some strange things like a single sata port flaking out on board and also PSUs that have low voltages / maybe starting to fail or can't handle the latest component upgrade etc. so swapping out the sata port and even the PSU (or at least check the usual ATX spec voltages)

[Bad 💀 Motha]

What are the full pc specs, and also include a all drive specs too, along with where the drives are connected.

Easiest thing I can suggest so far is trying different sata cables and/or ports

[Zairker]

Bad 💀 Motha님이 먼저 게시:

What are the full pc specs, and also include a all drive specs too, along with where the drives are connected.

The thing is, before installing Ubuntu 19.04 everything was as smooth as ever. I don't know why with this new kernel this issue occurs.

Btw I'm on a laptop, the HP EliteBook 2570p.

CPU : Intel Core i3-3110M (2.40 Ghz)
Integrated GPU : Intel HD Graphics 4000
RAM : 4GB DDR3-1600
HDD : 250 GB + External 1TB for my stuff.

Talby님이 먼저 게시:

aside from the usual bad drive / bad cable problems - have seen some strange things like a single sata port flaking out on board and also PSUs that have low voltages / maybe starting to fail or can't handle the latest component upgrade etc. so swapping out the sata port and even the PSU (or at least check the usual ATX spec voltages)

Can't check that being on a laptop, and again, there were no issues before installing Ubuntu 19.04. Maybe getting an older kernel version would fix it? If I remember correctly Ubuntu 18.04 had kernel version 4.15.

[Bad 💀 Motha]

It's terribly old specs for one thing, stick to an older build perhaps if that ran fine.

[Zairker]

Bad 💀 Motha님이 먼저 게시:

It's terribly old specs for one thing, stick to an older build perhaps if that ran fine.

I know dude, I'm planning on building a new PC soon enough. Thanks for the advice tho.

[Bad 💀 Motha]

Was there any real reason to upgrade to a newer os build?

[Zairker]

Kind of? I always install the newest Ubuntu version at its final release because after a while the system starts running slow and having a fresh install helps a lot. I didn't install Ubuntu 18.10 because I had web connection issues and I thought "well, let's just skip to 19.04", so I don't know if 18.10 would have caused me this error.

[Zairker]

Zairwolf님이 먼저 게시:

I always install the newest Ubuntu version at its final release because after a while the system starts running slow and having a fresh install helps a lot.

No, I'm not joking here, but that's actually what happens. Even if I won't install any application after about 3-4 months the system runs slower.

Rogue님이 먼저 게시:

if your Linux install starts running slow, that's probably because something is wrong. And usually it's something you can fix without resorting to the nuclear option.

Interesting, I may need more advice. What could make my system run slower?

Rogue님이 먼저 게시:

"Currently, Steam for Linux is only supported on the most recent version of Ubuntu LTS with the Unity, Gnome, or KDE desktops."

So if someone has Xubuntu, Lubuntu or Ubuntu MATE Steam isn't supported?

[Zairker]

PuertoRicanStripeHeadedTanager님이 먼저 게시:

Please tell me you don't plan to game on linux?

Yes, I do. Why?

[Zairker]

Yup, in fact, I was using Lubuntu 18.04 and now i'm using Xubuntu 19.04, I knew Ubuntu was too much for my PC. Since the 17.10 release it requires waaay more than the old versions.

And coming back to the original question, I noticed those errors come out when :
-I suspend the system
-I turn on the PC
-I use it after putting it in standby.

I don't have any errors when I'm using the system, e.g. using Firefox, writing on LibreOffice, Gaming ecc, so it's not a critical error.