errors with (S)ATA recognition/booting up after Grub

[DevelOpsMan]

Hello,

this year I wanted to get unchained from Windows. So I first started with dual boot systems on three different devices. When the systems run stable I removed the Win system from my media machine and my server machine. Finally my working laptop still runs in issues booting.

The error was on all machines and remained on my laptop:
"ata6: COMRESET failed (errno=-32)"
This message confuses me, because there are two SDDs connected via PCIE (and I was able to boot several times before from both SDDs, before the final configuration).

My EFI shows 4 empty slots for SATA. That is correct, so the question is why the error now occurs and why I can't boot any longer from the PCIE SSD.

Has anyone an idea how to fix this?

 

[osprey]

Hello,

this year I wanted to get unchained from Windows. So I first started with dual boot systems on three different devices. When the systems run stable I removed the Win system from my media machine and my server machine. Finally my working laptop still runs in issues booting.

The error was on all machines and remained on my laptop:
"ata6: COMRESET failed (errno=-32)"
This message confuses me, because there are two SDDs connected via PCIE (and I was able to boot several times before from both SDDs, before the final configuration).

My EFI shows 4 empty slots for SATA. That is correct, so the question is why the error now occurs and why I can't boot any longer from the PCIE SSD.

Has anyone an idea how to fix this?

The expression from post #1: "I was able to boot several times before from both SDDs, before the final configuration)", may suggest that the software was okay. In that case it may be worth checking the hardware fairly thoroughly. For example, making sure that all the connections and connectors are clean and firmly making accurate contact with their respective sockets. Normally this can be enhanced with an alcohol based contact cleaner to dislodge deposits of one sort or another.

The error message quoted is not entirely clear because of the "-" before the number 32. Error messages with numbers in the include files such as /usr/include/asm-generic/errno.h, have positive integers. Nevertheless, taking the particular error 32, one finds the following:

$ errno -l | grep ' 32'
EPIPE 32 Broken pipe

A broken pipe is consistent with a hardware failure to communicate between two items, so again, the hardware is worth a check. That's what it looks like to me at the moment.

 

[Brickwizard]

I assume you have checked the boot order in the BIOS/UEFI

 

[DevelOpsMan]

$ errno -l | grep ' 32'
EPIPE 32 Broken pipe

A broken pipe is consistent with a hardware failure to communicate between two items, so again, the hardware is worth a check. That's what it looks like to me at the moment.

Thank you for your answer. On computers it could only be soft or hardware. I would not believe in an hardware error while I can boot to Windows and use the disk without failure. You will know when you have unclean, broken or whatever contacts. As I build up my devices for myself I double check the hardware before, to hinder the computer to boot EFI/BIOS.
Then it is more than just an unavailable disk with read/write errors and all this stuff.

I'm answering from this machine's Windows partition from the same disk, throwing the errno-32 error after booting kubuntu from grub2. The same errors come sometimes on recovery. So @Brickwizard, it has nothing to do with the boot order. From time to time I have access and can boot to Kubuntu, but after restart the erro comes back.
It is the second iteration of OS installs after I moved the OSs to the new disk. All boot order problem were solved in this step. The Kubuntu disk is the efi boot disk too. (On another device I had he first time an issue with this when killing the efi boot partition from the first disk. So I can exclude it here.)
I started with the kubuntu-22.04.2-desktop-amd64.iso, the error appeared after some Kernel upgrade. Meanwhile it made some issues too with my USB plugged docking station. But even unplugged it's not bootable any more.

From my view, when it is an hardware error and windows can ignore it, it is an advance to keep it.

 

[osprey]

Thank you for your answer. On computers it could only be soft or hardware. I would not believe in an hardware error while I can boot to Windows and use the disk without failure. You will know when you have unclean, broken or whatever contacts. As I build up my devices for myself I double check the hardware before, to hinder the computer to boot EFI/BIOS.
Then it is more than just an unavailable disk with read/write errors and all this stuff.

I'm answering from this machine's Windows partition from the same disk, throwing the errno-32 error after booting kubuntu from grub2. The same errors come sometimes on recovery. So @Brickwizard, it has nothing to do with the boot order. From time to time I have access and can boot to Kubuntu, but after restart the erro comes back.
It is the second iteration of OS installs after I moved the OSs to the new disk. All boot order problem were solved in this step. The Kubuntu disk is the efi boot disk too. (On another device I had he first time an issue with this when killing the efi boot partition from the first disk. So I can exclude it here.)
I started with the kubuntu-22.04.2-desktop-amd64.iso, the error appeared after some Kernel upgrade. Meanwhile it made some issues too with my USB plugged docking station. But even unplugged it's not bootable any more.

From my view, when it is an hardware error and windows can ignore it, it is an advance to keep it.

Thanks for that information. It wasn't clear to me from your post #1 that things worked in MS.

That kernel error message has been an indicator of hardware problems for some users which were resolved by reseating some components. The COMRESET failure appears to be a failure in communication between the kernel and some hardware, such as a failure to initialise the disk, and hence make it available for use. The "broken pipe" can be software or hardware since pipes can be involved in both.

Since a hardware problem looks to be discounted now from your account, the next approach is really to upgrade to a later kernel, or to the latest kernel to give your machine the best chance of moving on from the issue. Briefly researching the issue more now, certainly some users have resolved the issue in that way.