Sstrhsrtj

during early boot, I get following error message:

[sdb] No Caching mode page found

[sdb] Assuming drive cache: write through

If I understand correctly, this is actually just a harmless info message and not an actual error. sdb is my USB disk, and it does not use caching .

The problem is, I have intentionally set kernel loglevel to 4, to get rid of these kind of useless info messages.

Why then do I still get this info message?

The reason why it's bothering me is, that it interferes with my password prompt (for decrypting my LUKS disk)

Is there a way to get rid of this message ?

Hard disks have a small amount of RAM cache to speed up write operations. The system can write a chunk of data to the disk cache without actually waiting for it to be written to the disk. This is sometimes called "write-back" mode.
If there is no cache on the disk, data is directly written to it in "write-through" mode.
The Asking for cache data failed warning usually occurs with devices such as USB flash drives, USB card readers, etc. which present themselves as SCSI devices to the system (sdX), but have no cache.
The system asks the device: "Do you have a cache?" and gets no response. So it assumes there is no cache and puts it in "write-through" mode.

You may try to go to:

/etc/modules

and on top of the modules list add the line

usb_storage

It should 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

This is how I solved a similar problem.

Let me know what happened.

Yes. You can get rid of such messages by executing following command:

echo 0 > /proc/sys/kernel/printk

This will suppress almost all the kernel messages and will display only Emergency messages

See this link for more info

This is probably a warn message (maybe the driver considers it important enough to mention). You did not specify which driver your USB hard drive is using so I can't point to the source line to verify this. More info on log levels here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/linux/kern_levels.h?id=HEAD

The easiest fix would be adding "quiet" to your kernel arguments via the bootloader, whether it's GRUB/LILO/etc.

Change your usb boot method while changing the usb as a bootable device use power iso tool to make your usb bootable device it'll work 100% with out fail ...

I had this problem with a new Arch Linux UEFI installation where I was using a UEFI Live USB to load the bootloader on the ESP.

The solution was to fix the setup with an EFI Boot Manager.

• From Windows an easy solution is easyuefi




• From Linux use efibootmgr & set a timeout value

If you use GRUB & not an EFISTUB to boot Linux you do NOT need to add any crypt kernel commands to the efibootmgr commands.

I have the exact same boot up messages on ubuntu 18.04

I have an external 1TB disk using USB port.
Both Ubuntu Desktop and Server are installed side-by-side on the external USB drive.
I have Windows 10 installed on the desktop HD. I use ESC to "BIOS choose" Ubuntu or Windows Boot Device. Then Boot Manager launches for Ubuntu or Windows UEFI choices. Then GRUB launches to choose between Desktop or Server. These boot options are fine with me.

Windows launches fast. Ubuntu choice ends up with the annoying message being displayed for a good 10-15 seconds then finally User Name.

The following efibootmgr page is vey helpful reading for both boot order and timeout options: https://linux.die.net/man/8/efibootmgr

Changing boot order does nothing for me:
-o | --bootorder XXXX,YYYY,ZZZZ
(Explicitly set BootOrder (hex))

Setting timeout with -t or -T does nothing for me:
-t | --timeout seconds
(Boot Manager timeout, in seconds.)
-T | --delete-timeout
(Delete Timeout variable.)

I continue to have the same boot message:"No Caching mode page found”. I will watch this thread. I prefer not to just supress messages that could be important.

The addition of usb_storage to /etc/modules also did not work for me.