system initialization with error: ata2: COMRESET failed (errno=-16)

[emil]

Hello from Braizil.
Newbe, here.

When starting the system, the following messages appear:
[ 12.455142] ata2: COMRESET failed (errno=-16)
[ 22.487141] ata2: COMRESET failed (errno=-16)
[ 57.539126] ata2: COMRESET failed (errno=-16)
[ 62.591133] ata2: COMRESET failed (errno=-16)
[ 62.592391] ata2: reset failed, giving up

Is it possible to arrange?

[stevef]

Difficult to say what's going on with the information provided.
Has this symptom recently started on a previously working system ?
Could be a hardware error but need more information.

[emil]

Difficult to say what's going on with the information provided.
Has this symptom recently started on a previously working system ?
Could be a hardware error but need more information.

I noticed this only after installing some system updates.
But that was the same day I installed lite.
But before, when I was using UBUNTU, it also happened right after updating the system to install Inkscape.

[stevef]

Does the system halt (fail to complete boot) when you get these messages ?

Can you boot off another media to try to work out what ata2 might be referring to and run some disk checks ?
Try installing LL 5.8 perhaps ?

[trinidad]

I noticed this only after installing some system updates

when I was using UBUNTU, it also happened

Taking a swing here, your profile says kernel 6 on an i5. I doubt this involves disk failure. It's probably because ata firmware is involved and the kernel can't address the disk features correctly. It is a rare but old time issue with Ubuntu when upgrading kernels after an existing install. Just my opinion, but if you're going to play with new kernels and don't understand things like pre-seeding firmware results will be unpredictable.

TC   

[emil]

Does the system halt (fail to complete boot) when you get these messages ?

Can you boot off another media to try to work out what ata2 might be referring to and run some disk checks ?
Try installing LL 5.8 perhaps ?

No problem with the system, it boots up "normally.

I can check the disk with the command "fsck". But the tutorial say "unmount the drive you want to check". Can you tell me how can I found that?

Terminal:
 mfm  ~  sudo lsblk
[sudo] password for mfm:
NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda      8:0    0  1,8T  0 disk
├─sda1  8:1    0  200M  0 part
└─sda2  8:2    0  1,8T  0 part
sdb      8:16  0 298,1G  0 disk
├─sdb1  8:17  0  512M  0 part
├─sdb2  8:18  0  513M  0 part /boot/efi
├─sdb3  8:19  0    1K  0 part
└─sdb5  8:21  0 297,1G  0 part /

[emil]

I noticed this only after installing some system updates

when I was using UBUNTU, it also happened

Taking a swing here, your profile says kernel 6 on an i5. I doubt this involves disk failure. It's probably because ata firmware is involved and the kernel can't address the disk features correctly. It is a rare but old time issue with Ubuntu when upgrading kernels after an existing install. Just my opinion, but if you're going to play with new kernels and don't understand things like pre-seeding firmware results will be unpredictable.

TC 

Sorry, I just checked, my kernel version is 5.15.0-56-generic

I really don't understand any of this, I am completely nub with linux.
Could you give me some tips?

[stevef]

No problem with the system, it boots up "normally.

OK, that's good.  How did you notice these messages ?
What exactly is the problem you are trying to solve here ?

In order to properly test your disks you need to boot from another media, like a USB stick but if your system boots ok you can run these commands to find if the ata2 message is referring to one of your disks.

Code:

udevadm info -q path -n /dev/sda

Code:

udevadm info -q path -n /dev/sdb

[trinidad]

Looks like Linux Lite / is on sdb5. What is on sda1? Are you dual booting? Are you using an external or USB disk? If the Linux Lite system is booting and running the ata error messages may just be informative rather than consequential i/e a device may not be immediately connectable in the initial boot order but does connect later on. Do you have fast boot disabled in the UEFI settings if this computer was originally Windows?
TC

[emil]

OK, that's good.  How did you notice these messages ?
What exactly is the problem you are trying to solve here ?

I thought that those error messages were wrong and that it would be good to fix them. The messages appear at boot, they are the only messages I can see at boot.

Code:

udevadm info -q path -n /dev/sda

/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host1/target1:0:0/1:0:0:0/block/sda

Code:

udevadm info -q path -n /dev/sdb

/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sdb