插入特定U盘导致Ubuntu 22.04.03 LTS启动卡顿的问题求助

大家好，我目前在联想L13 Yoga笔记本上运行Ubuntu 22.04.03 LTS，遇到了一个挺奇怪的问题：

如果我在开机前插入某款U盘，系统会在启动序列执行完毕后卡住。这时候拔掉U盘，系统会输出下面这些错误日志（我从启动日志里复制下来的），之后就能正常进入系统了。

这款U盘平时使用完全没问题，换其他品牌/型号的U盘插着开机就一切正常。我试过把它格式化成FAT32和NTFS两种格式，情况都没有改善。

我特意用Grub Customizer加了echo命令，在每个启动步骤后输出提示，确认启动序列已经全部走完，问题是在这之后出现的。现在搜相关问题特别费劲，出来的全是“无法从U盘启动”的内容，但我根本不是要从U盘启动，只是插着U盘开机而已。

如果需要更多排查信息，我随时可以提供！

拔出U盘后出现的错误日志： #

device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: ldm_validate_partition_table(): Disk read failed.
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: Dev sda: unable to read RDB block 0
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >

Update 1: 当前Grub配置片段 #

从grub.cfg里提取的启动序列内容：

recordfail
savedefault
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 5147e4a0-81c2-440a-ba09-ae762f4304fb
echo    'Loading Linux 6.2.0-39-generic ...'
linux   /boot/vmlinuz-6.2.0-39-generic root=UUID=5147e4a0-81c2-440a-ba09-ae762f4304fb ro  quiet splash $vt_handoff
echo    'Loading initial ramdisk ...'
initrd  /boot/initrd.img-6.2.0-39-generic

Update 2: BIOS启动顺序 #

我的BIOS里启动项顺序是：

• Ubuntu
• Windows Boot Manager
• 内置SSD
• Linux固件更新器
• Lenovo Cloud
• 其他所有选项均已设为排除

Update 3: 有无U盘的启动日志对比 #

我对比了带U盘和不带U盘启动时的日志片段，差异很明显：

插U盘时的启动日志片段： #

EXT4-fs (nvme0n1p5): mounted filesystem 5147e4a0-81c2-440a-ba09->
-Gen-2 kernel: scsi 0:0:0:0: Direct-Access     GENERIC  USB FLASH  DISK  7.76 P>
-Gen-2 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
-Gen-2 kernel: sd 0:0:0:0: [sda] 62259200 512-byte logical blocks: (31.9 GB/29.>
-Gen-2 kernel: sd 0:0:0:0: [sda] Write Protect is off
-Gen-2 kernel: sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
-Gen-2 kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, do>
-Gen-2 kernel: usb 4-2: USB disconnect, device number 2
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: ldm_validate_partition_table(): Disk read failed.
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read
-Gen-2 kernel: device offline error, dev sda, sector 0 op 0x0:(READ) flags 0x0 >
-Gen-2 kernel: Buffer I/O error on dev sda, logical block 0, async page read

不插U盘时的启动日志片段： #

EXT4-fs (nvme0n1p5): mounted filesystem 5147e4a0-81c2-440a-ba09->
-Gen-2 systemd[1]: Inserted module 'autofs4'
-Gen-2 systemd[1]: systemd 249.11-0ubuntu3.11 running in system mode (+PAM +AUD>
-Gen-2 systemd[1]: Detected architecture x86-64.
-Gen-2 systemd[1]: Hostname set to <sabaca-ThinkPad-L13-Yoga-Gen-2>.
-Gen-2 kernel: Lockdown: systemd: /dev/mem,kmem,port is restricted; see man ker>
-Gen-2 systemd-crontab-generator[245]: ignoring /etc/cron.d/anacron because it >
-Gen-2 systemd-crontab-generator[245]: ignoring /etc/cron.d/e2scrub_all because>
-Gen-2 systemd[1]: Queued start job for default target Graphical Interface.
-Gen-2 systemd[1]: Created slice Slice /system/modprobe.
-Gen-2 systemd[1]: Created slice Slice /system/postfix.
-Gen-2 systemd[1]: Created slice Slice /system/systemd-fsck.
-Gen-2 systemd[1]: Created slice User and Session Slice.
-Gen-2 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
-Gen-2 systemd[1]: Set up automount Arbitrary Executable File Formats File Syst>
-Gen-2 systemd[1]: Reached target User and Group Name Lookups.
-Gen-2 systemd[1]: Reached target Remote File Systems.
-Gen-2 systemd[1]: Reached target Slice Units.
-Gen-2 systemd[1]: Reached target Mounting snaps.
-Gen-2 systemd[1]: Reached target Local Verity Protected Volumes.
-Gen-2 systemd[1]: Listening on Syslog Socket.
-Gen-2 systemd[1]: Listening on fsck to fsckd communication Socket.
-Gen-2 systemd[1]: Listening on initctl Compatibility Named Pipe.

备注：内容来源于stack exchange，提问作者Sabaca