Errors after installing 5.15.5

General system Kernel, boot, graphics & hardware
1

Since upgraded to Linux 5.15.5-arch1-1 today, I get the following error while running journalctl:
Nov 27 08:30:22 nuc kernel: sd 1:0:0:0: [sda] Asking for cache data failed
Nov 27 08:30:22 nuc kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Nov 27 08:30:22 nuc kernel: sd 2:0:0:0: [sdb] Asking for cache data failed
Nov 27 08:30:22 nuc kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through

I also upgraded endeavouros on an external ssd drive and I also get the error “Asking for cache data failed”.

Never had this before the upgrade to 5.15.5. What can be done to resolve this please?

2

Could you post the link for the following.

inxi -Faz --no-host | eos-sendlog

3

done ricklinux.

https://clbin.com/ZeMto

4

You can try adding this in

/etc/modules

add this to the top entry

usb_storage

Try it for a sufficient number of boots and see if it makes any difference. If not you can remove it.

File might look something like this

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

usb_storage
lp

Edit: I put it as the top entry. It may or may not work?

5

There isn’t any file called “modules” in /etc ???

6

You can create the file and if it has no effect you can delete it or if it causes any issues.

sudo nano /etc/modules

add

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

usb_storage

ctrl + o enter to save
ctrl + x to exit nano

Doesn’t work or any issues delete the file.

7

Yes I tried by create the file, but the errors are still there
.

8

Just delete the file then. The messages could be coming from any usb drives hooked up or internal card reader posssibly. Did you check

sudo dmesg

9

Hi Ricklinux, I already checked. I only have the usual: cam, printer, mouse and keyboard.
It is interesting that when I log on my LTS 5.10 (old) I do not have this issue. It only happened today after updating the kernel.

10

I wouldn’t get too concerned about it. It may go away with updates.

11

Agreed, it looks like everything is still working. I shall monitor this for the next few days. Thank you for your time.

12

It seems to be a bug related to scsi
Most likely going to be fixed in 5.15.6 or later.

https://bugzilla.kernel.org/show_bug.cgi?id=215137

13

Cool , thank you Ricklinux.

14

Errors like this shouldn’t be ignored.

I would recommend either downgrading to 5.15.4 or using the lts kernel until this is rectified.

15

Thanks otherbarry, presently back using LTS , waiting for a kernel upgrade and then testing it again.

1 Like
16

The kernel prints the message to err on the side of caution; all it means is that the kernel tried to determine the drives’ caches’ characteristics, using an optional feature of the SCSI specification, but the drives don’t support it so the characteristics couldn’t be obtained. There’s nothing to do about it.

1 Like
17

I get the same messages in my virtualbox vm’s as well.

[sda] Asking for cache data failed
[sda] Assuming drive cache: write through

The vm’s have no external usb devices connected except the virtual devices for hard drive and cdrom.

2 Likes
18

My system gets them too as an example here.

Nov 27 10:11:03 eos-kde kernel: sd 0:0:0:0: [sda] Asking for cache data failed
Nov 27 10:11:03 eos-kde kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Nov 27 10:11:03 eos-kde kernel:  sda: sda1 sda2
Nov 27 10:11:03 eos-kde kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Nov 27 10:11:03 eos-kde kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 27 10:11:03 eos-kde kernel: ata2.00: ATA-10: ST4000DM004-2CV104, 0001, max UDMA/133
Nov 27 10:11:03 eos-kde kernel: ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Nov 27 10:11:03 eos-kde kernel: tsc: Refined TSC clocksource calibration: 3900.000 MHz
Nov 27 10:11:03 eos-kde kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x706eb6a54e6, max_idle_ns: 881591026581 ns
Nov 27 10:11:03 eos-kde kernel: clocksource: Switched to clocksource tsc
Nov 27 10:11:03 eos-kde kernel: ata2.00: configured for UDMA/133
Nov 27 10:11:03 eos-kde kernel: scsi 1:0:0:0: Direct-Access     ATA      ST4000DM004-2CV1 0001 PQ: 0 ANSI: 5
Nov 27 10:11:03 eos-kde kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Nov 27 10:11:03 eos-kde kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Nov 27 10:11:03 eos-kde kernel: sd 1:0:0:0: [sdb] Write Protect is off
Nov 27 10:11:03 eos-kde kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Nov 27 10:11:03 eos-kde kernel: sd 1:0:0:0: [sdb] Asking for cache data failed
Nov 27 10:11:03 eos-kde kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
19

@tongri

So here it is for the following output!

Nov 27 11:33:01 eos-kde kernel: scsi 1:0:0:0: Direct-Access     ATA      ST4000DM004-2CV1 0001 PQ: 0 ANSI: 5
Nov 27 11:33:01 eos-kde kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Nov 27 11:33:01 eos-kde kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Nov 27 11:33:01 eos-kde kernel: sd 1:0:0:0: [sdb] Write Protect is off
Nov 27 11:33:01 eos-kde kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Nov 27 11:33:01 eos-kde kernel: sd 1:0:0:0: [sdb] Asking for cache data failed
Nov 27 11:33:01 eos-kde kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through

I have only one informational error message in the boot journal. As you can see it is on sdb which is not an SSD drive. It is a normal 4 TB what i call Hybrid Drive or hard drive. It just reports the information that it can’t get or read cache data from this drive. This drive is internal. I don’t have it mounted or anything. It’s just there … extra. I have no concerns about this info.

2 Likes
20

After upgrading to 5.15.6-arch2-1 those errors are now gone :wink:

4 Likes