[Solved] ata4.00: Read log page 0x08 failed, Emask 0x1

TheProf

Gold Member
Gold Supporter
Joined
Jun 15, 2021
Messages
189
Reaction score
147
Credits
1,664
I've come across an interesting error a few days ago after doing some kernel upgrades. The error I am getting:

ata4.00: Read log page 0x08 failed, Emask 0x1

Not sure if other folks on Arch saw this error, but based on the link here, it seems I am not the only one.

I dont have any issues with my hard drives, everything works well, just that I see this error and it is kind of annoying.

Anyone else experience this?
 


brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
1,239
Reaction score
957
Credits
9,359
@TheProf .... are you on Arch or derivative? there are several reports of this error on the net
 

brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
1,239
Reaction score
957
Credits
9,359
I am on a derivative of Arch
yes its a strange one, I know little of Arch based distributions, but if its working ok [ its a harddrive connection fault] I can only assume that there is a bug in the update of the reporting system
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
3,893
Reaction score
2,633
Credits
28,122
I'm not getting that error.
 

brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
1,239
Reaction score
957
Credits
9,359
@f33dm3bits hi pal, its reporting an error on ATA and SATTA drive connections
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
3,893
Reaction score
2,633
Credits
28,122
@f33dm3bits hi pal, its reporting an error on ATA and SATTA drive connections
I'm multitasking it didn't register, but that make sense that I'm not getting it since I only have an nvme ssd in this system.
 
OP
TheProf

TheProf

Gold Member
Gold Supporter
Joined
Jun 15, 2021
Messages
189
Reaction score
147
Credits
1,664
Its odd, because I have 3 SATA SSDs and 1 drive as an NVME... this seems to only effect one drive.
 

brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
1,239
Reaction score
957
Credits
9,359
this seems to only effect one drive.
Is that drive working OK? if it is i would leave it alone.. if not you could always try disconnecting the cables to the MB and re- connecting them [ you may have developed a dry joint] but as its appears to be a common fault, my suspicions are still on a programming bug in the update
 
OP
TheProf

TheProf

Gold Member
Gold Supporter
Joined
Jun 15, 2021
Messages
189
Reaction score
147
Credits
1,664
Everything works fine, no issues, just curious as to why this happened.

Either way, what I realized is that from time to time new kernel updates introduce some errors and then at a later point with other kernel updates, these errors get resolved.

I had this happen with USB ports. Now it’s the SATA drive.
 
OP
TheProf

TheProf

Gold Member
Gold Supporter
Joined
Jun 15, 2021
Messages
189
Reaction score
147
Credits
1,664
So as I mentioned above, after a kernel update, I now have a completely different error, no longer getting the ata errors lol.. I should learn to just ignore these.
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!


Top