You are not logged in.

#1 2021-11-14 10:39:56

Vizitor
Member
Registered: 2015-01-05
Posts: 62

[SOLVED] ata5.00: Read log page 0x08 failed after upgrade

Hi,
today after update to 5.15.2-arch1-1, i noticed the very first boot messages with errors:

sudo dmesg | grep failed
[    1.864916] ata5.00: Read log page 0x08 failed, Emask 0x1
[    1.876376] ata5.00: Read log page 0x08 failed, Emask 0x1
[    2.349558] ata6.00: Read log page 0x08 failed, Emask 0x1
[    2.352287] ata6.00: Read log page 0x08 failed, Emask 0x1
[   14.691450] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
sudo journalctl -b | grep failed
Nov 14 11:26:52 bprime kernel: ata5.00: Read log page 0x08 failed, Emask 0x1
Nov 14 11:26:52 bprime kernel: ata5.00: Read log page 0x08 failed, Emask 0x1
Nov 14 11:26:52 bprime kernel: ata6.00: Read log page 0x08 failed, Emask 0x1
Nov 14 11:26:52 bprime kernel: ata6.00: Read log page 0x08 failed, Emask 0x1
Nov 14 11:26:52 bprime kernel: vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Nov 14 11:26:58 bprime dbus-daemon[727]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Nov 14 11:26:58 bprime dbus-daemon[727]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Nov 14 11:26:58 bprime audit[798]: CRED_ACQ pid=798 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="v" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 14 11:26:58 bprime kernel: audit: type=1103 audit(1636885618.180:44): pid=798 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="v" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 14 11:26:58 bprime dbus-daemon[727]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Nov 14 11:32:06 bprime dbus-daemon[727]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.

I am using full disk encryption (simple dm-crypt - meaning without LVM), and efistub booting (ESP is not encrypted).
(EDIT: those messages are seen before entering encryption password)
So far I didn't noticed any strange behaviour of the system, and VBox is running OK.
So, are those errors something to be worry or more a cosmetic ones?

Last edited by Vizitor (2021-11-14 21:40:19)

Offline

#2 2021-11-14 19:29:02

RetroThief
Member
Registered: 2021-02-01
Posts: 4

Re: [SOLVED] ata5.00: Read log page 0x08 failed after upgrade

I'm receiving the same exact error after upgrading yesterday. I'm running on a regular Arch machine without encryption. I noticed that when looking at the hard drive that it's corresponding to, it's error'ing on my drive that has Windows installed. I do have dual boot enabled through Grub so I can choose between Windows and Arch at boot.

$ journalctl -p 3 -b
Nov 14 14:18:09 alex kernel: ata3.00: Read log page 0x08 failed, Emask 0x1
Nov 14 14:18:09 alex kernel: ata3.00: Read log page 0x08 failed, Emask 0x1

The dmesg logs:

# dmesg | grep ata3.00
[    1.521770] ata3.00: ATA-8: WDC WD2500AAKX-75U6AA0, 19.01H19, max UDMA/133
[    1.522116] ata3.00: Read log page 0x08 failed, Emask 0x1
[    1.522117] ata3.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.524171] ata3.00: Read log page 0x08 failed, Emask 0x1
[    1.524175] ata3.00: configured for UDMA/133

The corresponding hard drive using fdisk:

# fdisk -l
Disk /dev/sdb: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC WD2500AAKX-7
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: gpt
Disk identifier: D74088BB-7055-4E98-8A7F-ECF0B2AD49DB

Device     Start       End   Sectors   Size Type
/dev/sdb1     34     32767     32734    16M Microsoft reserved
/dev/sdb2  32768 488394751 488361984 232.9G Microsoft basic data

Last edited by RetroThief (2021-11-14 19:49:05)

Offline

#3 2021-11-14 20:53:50

Vizitor
Member
Registered: 2015-01-05
Posts: 62

Re: [SOLVED] ata5.00: Read log page 0x08 failed after upgrade

I have dual boot too, with win10 and arch, both on nvme (which is not appearing in error messages).
I do not have grub installed, but selecting OS through "F8" key at boot time (automatic booting in arch, and pressing F8 only if I have to go in win10 which is once a month)

My ata5 is this SSD:

ata5.00: ATA-8: KINGSTON SHFS37A120G, 60AABBF0, max UDMA/133

fdisk:

Disk /dev/sdc: 111.79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SHFS37A

which is empty, unformatted;
And ata6 is this HDD:

ata6.00: ATA-8: WDC WD10EALX-009BA0, 15.01H15, max UDMA/133

fdisk:

Disk /dev/sdd: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EALX-009

There are other disks too, see full fdisk output

Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WDS100T2B0C-00PXH0                  
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: gpt
Disk identifier: 64FDA67F-1A41-4BF5-87E4-EC4F4EE78F59

Device              Start        End    Sectors  Size Type
/dev/nvme0n1p1       2048     526335     524288  256M EFI System
/dev/nvme0n1p2     526336     559103      32768   16M Microsoft reserved
/dev/nvme0n1p3     559104  169838928  169279825 80.7G Microsoft basic data
/dev/nvme0n1p4  169840640  170946559    1105920  540M Windows recovery environment
/dev/nvme0n1p5  170946560 1848668159 1677721600  800G Microsoft basic data
/dev/nvme0n1p6 1848668160 1953523711  104855552   50G Linux filesystem


Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: MKNSSDTR480GB   
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: 9045494E-B54B-46D6-8A31-36F61E6FE4D0

Device     Start       End   Sectors   Size Type
/dev/sda1   2048 937701375 937699328 447.1G Microsoft basic data


Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: ADATA SU650     
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: gpt
Disk identifier: 960E7B1E-D652-484B-902C-4537E8F8535A

Device     Start       End   Sectors   Size Type
/dev/sdb1   2048 937701375 937699328 447.1G Linux filesystem


Disk /dev/sdc: 111.79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SHFS37A
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: gpt
Disk identifier: CDEA042D-5055-4B95-99B8-A9B08045E1EA


Disk /dev/sdd: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EALX-009
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: gpt
Disk identifier: 9614A55F-A973-4447-8599-1CAC80B048D2

Device          Start        End    Sectors  Size Type
/dev/sdd1        2048 1887438847 1887436800  900G Microsoft basic data
/dev/sdd2  1887438848 1953523711   66084864 31.5G Linux filesystem


Disk /dev/mapper/cryptroot: 49.98 GiB, 53669265408 bytes, 104822784 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

and so far I have no problems accessing them.

Also I have another machine with very similar hardware, and there are those errors too.

Offline

#4 2021-11-14 21:05:51

loqs
Member
Registered: 2014-03-06
Posts: 14,243

Re: [SOLVED] ata5.00: Read log page 0x08 failed after upgrade

See https://github.com/torvalds/linux/commi … f8a8f49501 warning was upgraded to an error.

Offline

#5 2021-11-14 21:38:18

Vizitor
Member
Registered: 2015-01-05
Posts: 62

Re: [SOLVED] ata5.00: Read log page 0x08 failed after upgrade

Ty loqs, so

Since READ LOG PAGE DMA EXT is an optional command,
this warning is not at all important but may be scary for the user.

and as I understand will be fixed in the future.

Offline

#6 2021-11-15 00:16:43

loqs
Member
Registered: 2014-03-06
Posts: 14,243

Re: [SOLVED] ata5.00: Read log page 0x08 failed after upgrade

Vizitor wrote:

and as I understand will be fixed in the future.

I thought the fix was to replace one/two warning messages with an error message.
The error message is still produced using 5.16-rc1.

Offline

Board footer

Powered by FluxBB