Ata7.00: revalidation failed (errno=-5)

In order to use a m.2 ssd which got windows :face_vomiting: installed on it I’m using a pcie x 1 adapter but now booting up takes more then 1 minute:

╭─chomsky@EndeavourOS ~
╰─➤  systemd-analyze
Startup finished in 1min 562ms (firmware) + 1.767s (loader) + 3.805s (kernel) + 1.584s (userspace) = 1min 7.720s
graphical.target reached after 1.147s in userspace

And I get the following error in my journalctl:

╭─chomsky@EndeavourOS ~
╰─➤  journalctl -b -1 | grep ata7
dec 21 07:25:12 EndeavourOS kernel: ata7: SATA max UDMA/133 abar m512@0xf7d10000 port 0xf7d10100 irq 29
dec 21 07:25:12 EndeavourOS kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 21 07:25:12 EndeavourOS kernel: ata7.00: ATA-9: HFS128G39TND-N210A, 30001P10, max UDMA/133
dec 21 07:25:12 EndeavourOS kernel: ata7.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 32), AA
dec 21 07:25:12 EndeavourOS kernel: ata7.00: Features: Dev-Sleep
dec 21 07:25:12 EndeavourOS kernel: ata7.00: configured for UDMA/133
dec 21 07:25:12 EndeavourOS kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 21 07:25:12 EndeavourOS kernel: ata7.00: configured for UDMA/133
dec 21 07:25:12 EndeavourOS kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 21 07:25:12 EndeavourOS kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
dec 21 07:25:12 EndeavourOS kernel: ata7.00: revalidation failed (errno=-5)
dec 21 07:25:12 EndeavourOS kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 21 07:25:12 EndeavourOS kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
dec 21 07:25:12 EndeavourOS kernel: ata7.00: revalidation failed (errno=-5)
dec 21 07:25:12 EndeavourOS kernel: ata7: limiting SATA link speed to 3.0 Gbps
dec 21 07:25:12 EndeavourOS kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
dec 21 07:25:12 EndeavourOS kernel: ata7.00: configured for UDMA/133

The pcie card I use :

03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: ASMedia Technology Inc. Device 1060
	Flags: bus master, fast devsel, latency 0, IRQ 18
	I/O ports at d050 [size=8]
	I/O ports at d040 [size=4]
	I/O ports at d030 [size=8]
	I/O ports at d020 [size=4]
	I/O ports at d000 [size=32]
	Memory at f7d10000 (32-bit, non-prefetchable) [size=512]
	Expansion ROM at f7d00000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: ahci

Now when I add pci=nomsi to my kernel parameters the error disappears but booting up still takes over a minute.
The ssd works fine (healthy according to smartctl) and I can boot into windows using grub without any issues.

My question is if I can somehow reduce the boot time and if the kernel parameter pci=nomsi is a good idea or should I just remove the ssd and only insert it when I need windows which happens maybe once a month.

Thanks in advance!

My inxi output:
https://clbin.com/z2DfI

@chomsky
It looks like it’s using the correct module.

I see this controller has only recently have support in the kernel.

https://bbs.archlinux.org/viewtopic.php?id=271095

Is it wise to run the pci=nomsi kernel parameter do you reckon? Does it make the system less stable or can it cause any other issues? I can live with the slow boot time that doesnt bother me much.

According to the documentation it disables MSI interrupts system wide. You could try pci=noaer which disables pci-e advanced error reporting. Kernel parameters either work or cause more issues or problems so you can try it and see. It may cause issues or not or be better? :man_shrugging:

1 Like

Thanks I’ll give it a shot.

With pci=naer the error returns. I think I’ll just remove the kernel parameter and live with the error for now. All I can do is hope that my OCD doesn’t keep me up at night.

What error returns?

Edit: Did you check sudo dmesg and look at what it shows?

This error:

dec 21 13:29:28 EndeavourOS kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
dec 21 13:29:28 EndeavourOS kernel: ata7.00: revalidation failed (errno=-5)

In dmesg it shows the same error and limits the SATA link speed to 3.0 Gbps

[    0.693865] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.715231] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[    6.417196] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    6.528217] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[    6.528225] ata7: limiting SATA link speed to 3.0 Gbps
[   11.907194] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   11.908937] ata7.00: ATA-9: HFS128G39TND-N210A, 30001P10, max UDMA/133
[   11.909058] ata7.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 32), AA
[   11.909411] ata7.00: Features: Dev-Sleep
[   11.910069] ata7.00: configured for UDMA/133
[   11.910228] scsi 6:0:0:0: Direct-Access     ATA      HFS128G39TND-N21 1P10 PQ: 0 ANSI: 5

Does this adapter still use a standard SATA cable?

Edit: If so i would try a new cable.

Doesnt use a sata cable. The m.2 ssd is inserted in the pcie card, no cable required.

Okay… just checking. There is some info regarding this error relating to cables.

1 Like

This normally means it’s waiting in the UEFI - possibly the system doesn’t like the PCIe adapter you’re using, or it should be in a different slot, … ?

But the card is recognized and works as intended so I dont understand why it takes a minute before the actual boot proces begins.

What is the make and model of the pcie card? It might have firmware embedded that is taking time to initialize.

1 Like

According to lspci it’s an ASMedia Technology Inc. ASM1062 and now I notice that it was sold as an ASM1061, a difference in version. That probably explains the delayed initialization and error message.

Got the card from Aliexpress for about $8 including shipping so I cant complain.