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

[trinidad]

How do I find out what is associated with ata2?

Again, try to save a file from Linux Lite to the backup drive. The backup drive initialization file was Windows EFI which is no longer there as I expalined before.
TC

[emil]

OK, I thought the SD card reader might be associated with ata2.

How do I find out what is associated with ata2?

[trinidad]

You have a couple things going on. The seagate backup disk is GPT because it's 2TB. The installed LL system 300GB onboard drive is DOS. The backup drive is looking for a Windows UEFI entry that isn't there anymore. As far as I know you can't run that backup drive in its current state after installing a Linux OS because it still needs a Windows boot manager. The missing ata initializing file for that drive is gone. Linux will still recognize the drive but it may or may not work for data storage. It is normally not considered Linux compatilbe. I would unplug the backup drive and REMOVE any BIOS entry noting or listing it, then reinstall Linux Lite to the onboard drive without the backup drive plugged in. That should properly designate the Linux drive as sda not sdb. "Possibly" making the backup drive Linux compatible will involve some other steps but that's not worth doing until you get the Linux system installed without the backup drive present.

But... BEFORE you do any of the above see if you can store and then retrieve a Linux file to and from the backup drive. If you can do that you may want to leave it as is. I doubt you will be able to, but it's worth trying. If the data partition is FAT32 and not NTFS it may still work. You may even be able partition a space on it for Linux.

By the way you may still be able to edit the backup drive EFI partition and boot windows from it if there is a full backup on it. (Windows live ent disk should work or even bcedit)
TC     

[stevef]

OK, I thought the SD card reader might be associated with ata2.

[emil]

Have you noticed if booting with/without a card in the SD slot makes a difference to the error message ?

If the error message appears to be associated with either state of a card being in or out, repeat several times to check if it is consistent.

It makes no difference, always the same message.

[stevef]

Have you noticed if booting with/without a card in the SD slot makes a difference to the error message ?

If the error message appears to be associated with either state of a card being in or out, repeat several times to check if it is consistent.

[emil]

For ata2, it tries a few times, then tries at a slower speed and then gives up but doesn't appear to log the port as down.

Does your system support removable media in any way ?

Yes, I use an external USB hard drive without any problems.

There's no CD/DVD drive being identified - does the system have one ?

No, this laptop does not have a CD/DVD drive.

Does the system have a slot for a memory card perhaps ?

Yes, SD card, and it's working.

From what you've told us so far, I don't think this is anything to worry about but it would be interesting to find out what's going on.

I really appreciate the info.
Yes, I agree... it would be nice to be able to understand what's going on, but apparently it's something complex.

[stevef]

During boot up the system is checking for devices connected by ATA.
The Hitachi drive is found on ata1.
ata4 and ata5 appear to be unused.

For ata2, it tries a few times, then tries at a slower speed and then gives up but doesn't appear to log the port as down.

Does your system support removable media in any way ?
There's no CD/DVD drive being identified - does the system have one ?
Does the system have a slot for a memory card perhaps ?

From what you've told us so far, I don't think this is anything to worry about but it would be interesting to find out what's going on.

[emil]

After any BIOS display, most new installs usually hide all the linux boot up messages with a splash screen.   If the splash screen is disabled there will be many messages scrolling past.

When exactly does the message you report appear ?

The message appears just before starting LL.

Code: [Select]

journalctl -b | grep ata2

Did you find something here? The message, if not identical, is very similar to this one.

 mfm  ~  journalctl -b | grep ata2
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: SATA max UDMA/133 abar [email protected] port 0xc0507180 irq 24
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: link is slow to respond, please be patient (ready=0)
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: COMRESET failed (errno=-16)
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: link is slow to respond, please be patient (ready=0)
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: COMRESET failed (errno=-16)
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: link is slow to respond, please be patient (ready=0)
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: COMRESET failed (errno=-16)
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: limiting SATA link speed to 1.5 Gbps
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: COMRESET failed (errno=-16)
dez 22 21:41:10 mfm-Aspire-S3 kernel: ata2: reset failed, giving up

Code: [Select]

lsblk -o NAME,Model,HCTL

mfm  ~  lsblk -o NAME,Model,HCTL
NAME        MODEL                   HCTL
sda         Hitachi HTS543232A7A384 0:0:0:0
├─sda1                             
├─sda2                             
├─sda3                             
└─sda5                             
mmcblk0                             
└─mmcblk0p1 

[stevef]

emil

If you are still getting similar messages please post the result of

Code: [Select]

journalctl -b | grep ata2

Code: [Select]

lsblk -o NAME,Model,HCTL
After any BIOS display, most new installs usually hide all the linux boot up messages with a splash screen.   If the splash screen is disabled there will be many messages scrolling past.

When exactly does the message you report appear ?

[emil]

@emil

hhhm - ok good stuff - thinking it in another direction from @stevef  which hopefully helps in his direction..

With the USB disconnected and you reboot - Do you receive the error message still?
Also, if you do either the lsblk or fdisk, does the hitachi (internal disk) now show as sda?

My thought...
Perhaps with USB connected and it having an EFI directory, perhaps its cycling/reading taking a moment and generating the error....
If the error persists - perhaps not ...

Unfortunately still receive the same message.

mfm  ~  127  sudo fdisk -l
[sudo] password for mfm:
Disk /dev/sda: 298,09 GiB, 320072933376 bytes, 625142448 sectors
Disk model: Hitachi HTS54323
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0b75e36e

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sda1          2048   1050623   1048576   512M  b W95 FAT32
/dev/sda2  *    1050624   2101247   1050624   513M ef EFI (FAT-12/16/32)
/dev/sda3       2103294 625141759 623038466 297,1G  5 Extended
/dev/sda5       2103296 625141759 623038464 297,1G 83 Linux

[firenice03]

@emil


hhhm - ok good stuff - thinking it in another direction from @stevef  which hopefully helps in his direction..


With the USB disconnected and you reboot - Do you receive the error message still?
Also, if you do either the lsblk or fdisk, does the hitachi (internal disk) now show as sda?


My thought...
Perhaps with USB connected and it having an EFI directory, perhaps its cycling/reading taking a moment and generating the error....
If the error persists - perhaps not ...

[emil]

Code: [Select]

[quote author=firenice03 link=topic=9032.msg59901#msg59901 date=1671589924]

Disk /dev/sda: 1,82 TiB, 2000398933504 bytes, 3907029167 sectors
Disk model: Ultra Slim PL   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 9B3432E5-83D6-4B4E-A233-89E34D845695

Device      Start        End    Sectors  Size Type
/dev/sda1      40     409639     409600  200M EFI System
/dev/sda2  411648 3907028991 3906617344  1,8T Microsoft basic data


Disk /dev/sdb: 298,09 GiB, 320072933376 bytes, 625142448 sectors
Disk model: Hitachi HTS54323
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0b75e36e

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdb1          2048   1050623   1048576   512M  b W95 FAT32
/dev/sdb2  *    1050624   2101247   1050624   513M ef EFI (FAT-12/16/32)
/dev/sdb3       2103294 625141759 623038466 297,1G  5 Extended
/dev/sdb5       2103296 625141759 623038464 297,1G 83 Linux

Looking at your fdisk...
LL is running on the Hitachi - assuming the USB drive.
sdb1 - is a left over non needed...
sdb2/3/5 are the EFI and LL "/" partitions
*Most likely as @trinidad mentioned taking a moment to read the disk...

sda1 - EFI partition on the internal hard disk
sda2 - Windows partition; I'd assume C: due to the size... but??

Have you FULLY installed LL on to the computer (using the install process)? or are you still testing the Live Environment - aka booted the iso? or are you using the USB with persistence?
- If you dont know what I mean... Thats ok...
My assumption is you attempted to install LL and inadvertently installed onto the USB drive...

If we think this is the case - no worries we can get you back around and install onto the hard drive.

If you have any files you want to keep - back those up else where.

The Hitachi is the computer's hd. On usb I have Seagate (backup).
Ow .. have a windows partition? But I don't have windows anymore...
Yes, I completely installed the LL, I installed it through .iso with an usb .. but the usb is kept for safety, I read somewhere that it is good to keep it.

Ahhhh, did I install LL on the USB? I just restarted without the external hd (usb) and it started LL normally. What a scare! But no, I did not install the LL on the usb. 

[emil]

Does the system have any other SATA devices - maybe a CD/DVD drive ?

Please can you post the result of

Code: [Select]

journalctl -b | grep ATA

mfm  ~  journalctl -b | grep ATA
dez 21 07:51:02 mfm-Aspire-S3 kernel: NODE_DATA(0) allocated [mem 0x14fdd6000-0x14fdfffff]
dez 21 07:51:02 mfm-Aspire-S3 kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
dez 21 07:51:02 mfm-Aspire-S3 kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
dez 21 07:51:03 mfm-Aspire-S3 kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x1b impl SATA mode
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata1: SATA max UDMA/133 abar [email protected] port 0xc0507100 irq 24
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata2: SATA max UDMA/133 abar [email protected] port 0xc0507180 irq 24
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata4: SATA max UDMA/133 abar [email protected] port 0xc0507280 irq 24
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata5: SATA max UDMA/133 abar [email protected] port 0xc0507300 irq 24
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata1.00: ATA-8: Hitachi HTS543232A7A384, ES2OA90B, max UDMA/133
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata1.00: ATA Identify Device Log not supported
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata1.00: ATA Identify Device Log not supported
dez 21 07:51:03 mfm-Aspire-S3 kernel: scsi 1:0:0:0: Direct-Access     ATA      Hitachi HTS54323 A90B PQ: 0 ANSI: 5
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata2: limiting SATA link speed to 1.5 Gbps
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata4: SATA link down (SStatus 0 SControl 300)
dez 21 07:51:03 mfm-Aspire-S3 kernel: ata5: SATA link down (SStatus 0 SControl 300)

[firenice03]

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

How do I find out what is on sda1?
I am not dual booting, I only have Linux Lite on the laptop. I installed it with an external USB, but I don't need it anymore. Yes, it was windows originally.
I even google to try to find out if I have fast boot disabled in the UEFI, but I didn't find anything very friendly.

Code: [Select]

I don't know if it helps, but I typed sudo fdisk -l and the result:

Disk /dev/sda: 1,82 TiB, 2000398933504 bytes, 3907029167 sectors
Disk model: Ultra Slim PL   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 9B3432E5-83D6-4B4E-A233-89E34D845695

Device      Start        End    Sectors  Size Type
/dev/sda1      40     409639     409600  200M EFI System
/dev/sda2  411648 3907028991 3906617344  1,8T Microsoft basic data


Disk /dev/sdb: 298,09 GiB, 320072933376 bytes, 625142448 sectors
Disk model: Hitachi HTS54323
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0b75e36e

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdb1          2048   1050623   1048576   512M  b W95 FAT32
/dev/sdb2  *    1050624   2101247   1050624   513M ef EFI (FAT-12/16/32)
/dev/sdb3       2103294 625141759 623038466 297,1G  5 Extended
/dev/sdb5       2103296 625141759 623038464 297,1G 83 Linux


Looking at your fdisk...
LL is running on the Hitachi - assuming the USB drive.
sdb1 - is a left over non needed...
sdb2/3/5 are the EFI and LL "/" partitions
*Most likely as @trinidad mentioned taking a moment to read the disk...


sda1 - EFI partition on the internal hard disk
sda2 - Windows partition; I'd assume C: due to the size... but??




Have you FULLY installed LL on to the computer (using the install process)? or are you still testing the Live Environment - aka booted the iso? or are you using the USB with persistence?
- If you dont know what I mean... Thats ok...
My assumption is you attempted to install LL and inadvertently installed onto the USB drive...


If we think this is the case - no worries we can get you back around and install onto the hard drive.




If you have any files you want to keep - back those up else where.