Stuck with 6.14.0-37 kernel

roger-19 · May 21, 2026, 8:58am

Hi! I’m writing my first message here (and first ever on a tech support board) as for the first time in many years I can’t seem to resolve this problem and starting to get worried about the safety of a system running on an outdated kernel.

Problem Description:
None of the kernels after 6.14.0-37 have been able to boot. I kept reverting to 6.14.0-37 the whole time (by editing the grub file) but over the years I was usually able to skip one kernel version that is not working and then the next one would work normally.

If it is of any relevance, all the kernel updates between 6.14.0-37 and the current one, 6.17.0-29, have resulted in CapsLock button blinking when trying to boot, and then it would just result in a restart right after the blinking stops. This current kernel 6.17.0-29 just ends up in a blank screen with no CapsLock blinking and it does not restart unless I do it manually.

Also currently journalctl -b -1 -p err just returns – No entries – after going through a failed boot with 6.17.0-29.

What I’ve Tried:
The past three months I have been going through all the posts on different boards/forums related to this issue, trying different types of fixes and none seemed to fix the issue my laptop is having.

I’m not sure where to look next at this point so any help would be greatly appreciated!

Ubuntu Version:
24.04.4 LTS

Relevant System Information:

lshw -short output

H/W path Device Class Description

                                  system         81VV (LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL)

/0 bus LNVNB161216
/0/0 memory 128KiB BIOS
/0/4 processor Intel(R) Core™ i5-1035G1 CPU @ 1.00GHz
/0/4/6 memory 128KiB L1 cache
/0/4/7 memory 2MiB L2 cache
/0/4/8 memory 6MiB L3 cache
/0/5 memory 192KiB L1 cache
/0/26 memory 8GiB System Memory
/0/26/0 memory 4GiB SODIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/26/1 memory 4GiB SODIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/100 bridge Ice Lake-LP Processor Host Bridge/DRAM Registers
/0/100/2 /dev/fb0 display Iris Plus Graphics G1 (Ice Lake)
/0/100/4 generic Processor Power and Thermal Controller
/0/100/14 bus Ice Lake-LP USB 3.1 xHCI Host Controller
/0/100/14/0 usb1 bus xHCI Host Controller
/0/100/14/0/6 multimedia Integrated Camera
/0/100/14/0/a communication Bluetooth 9460/9560 Jefferson Peak (JfP)
/0/100/14/1 usb2 bus xHCI Host Controller
/0/100/14.2 memory RAM memory
/0/100/14.3 wlp0s20f3 network Ice Lake-LP PCH CNVi WiFi
/0/100/14.5 mmc1 bus Ice Lake-LP SD Controller
/0/100/15 bus Ice Lake-LP Serial IO I2C Controller #0
/0/100/15.1 bus Ice Lake-LP Serial IO I2C Controller #1
/0/100/15.2 bus Ice Lake-LP Serial IO I2C Controller #2
/0/100/16 communication Ice Lake-LP Management Engine
/0/100/17 storage Ice Lake-LP SATA Controller [AHCI mode]
/0/100/1a mmc2 bus Ice Lake-LP SD Host Controller
/0/100/1d bridge Ice Lake-LP PCI Express Root Port #9
/0/100/1d/0 mmc0 bus RTS522A PCI Express Card Reader
/0/100/1d.4 bridge Ice Lake-LP PCIe Port #13
/0/100/1d.4/0 /dev/nvme0 storage SAMSUNG MZVLB1T0HBLR-000L2
/0/100/1d.4/0/0 hwmon2 disk NVMe disk
/0/100/1d.4/0/2 /dev/ng0n1 disk NVMe disk
/0/100/1d.4/0/1 /dev/nvme0n1 disk 1024GB NVMe disk
/0/100/1d.4/0/1/1 /dev/nvme0n1p1 volume 1074MiB Windows FAT volume
/0/100/1d.4/0/1/2 /dev/nvme0n1p2 volume 2GiB EXT4 volume
/0/100/1d.4/0/1/3 /dev/nvme0n1p3 volume 950GiB EFI partition
/0/100/1f bridge Ice Lake-LP LPC Controller
/0/100/1f/0 system PnP device PNP0c02
/0/100/1f/1 system PnP device PNP0b00
/0/100/1f/2 input PnP device PNP0303
/0/100/1f/3 system PnP device PNP0c02
/0/100/1f/4 system PnP device PNP0c02
/0/100/1f/5 system PnP device PNP0c02
/0/100/1f/6 system PnP device PNP0c02
/0/100/1f/7 input10 input Ideapad extra buttons
/0/100/1f.3 card0 multimedia Ice Lake-LP Smart Sound Technology Audio Controller
/0/100/1f.3/0 input12 input HDA Intel PCH Mic
/0/100/1f.3/1 input13 input HDA Intel PCH Headphone
/0/100/1f.3/2 input14 input HDA Intel PCH HDMI/DP,pcm=3
/0/100/1f.3/3 input15 input HDA Intel PCH HDMI/DP,pcm=7
/0/100/1f.3/4 input16 input HDA Intel PCH HDMI/DP,pcm=8
/0/100/1f.3/5 input17 input HDA Intel PCH HDMI/DP,pcm=9
/0/100/1f.4 bus Ice Lake-LP SMBus Controller
/0/100/1f.5 bus Ice Lake-LP SPI Controller
/1 power CRB Battery 0
/2 power OEM Define 5
/3 input0 input Lid Switch
/4 input1 input Power Button
/5 input11 input Video Bus
/6 input2 input Power Button
/7 input3 input AT Translated Set 2 keyboard
/8 input7 input MSFT0004:01 06CB:7F28 Mouse
/9 input8 input MSFT0004:01 06CB:7F28 Touchpad

tea-for-one · May 21, 2026, 12:28pm

/dev/nvme0n1p3 looks unusual - Why is it displaying EFI partition?

Can you boot into your working kernel, open a terminal and enter:-

lsblk -e 7 -o name,size,pttype,type,fstype,fsuse%,fsavail,mountpoint

Please paste the output within code tags

roger-19 · May 21, 2026, 2:16pm

I’m unsure myself why is it displaying EFI partition, it’s a good question.

The output for lsblk -e 7 -o name,size,pttype,type,fstype,fsuse%,fsavail,mountpointis the following:

NAME SIZE PTTYPE TYPE FSTYPE FSUSE% FSAVAIL MOUNTPOIN
nvme0n1 953.9G gpt disk
├─nvme0n1p1 1G gpt part vfat 1% 1G /boot/efi
├─nvme0n1p2 2G gpt part ext4 12% 1.6G /boot
└─nvme0n1p3 950.8G gpt part crypto_LUKS
└─dm_crypt-0 950.8G crypt LVM2_member
└─ubuntu–vg-ubuntu–lv 950.8G lvm ext4 4% 848.5G /

tea-for-one · May 21, 2026, 2:45pm

The output from lsblk command looks OK.
Previously, there was incomplete info about /dev/nvme0n1p3

Can you access the UEFI settings and disable the following (if present):-

Secure Boot
TPM (Trusted Platform Module)
TCG (Trusted Computing Group)
PTT (Platform Trust Technology)
FTPM (Firmware Trusted Platform Module)
TPT (Trust Platform Technology)
PSP (Platform Security Processor)
Device Guard (some Lenovo devices)
OS Optimised Defaults (some Lenovo devices)
Lock UEFI BIOS Settings
Boot Order Lock

Any luck?

ogra · May 21, 2026, 3:16pm

If this is a HP device, blinking caps indicates usually a hardware issue (with different blink codes for different HW parts apparently)

EDIT: oops, blind me, ignore that, I see this is a lenovo …

peterwhite23 · May 21, 2026, 3:17pm

Welcome to Ubuntu Discourse!

You don’t need to edit anything; older kernels are available in the grub menu. Just hit Esc or hold Shift during boot after the BIOS/UEFI splash screen.

roger-19:

H/W path Device Class Description
                                  system         81VV (LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL)
/0 bus LNVNB161216
/0/0 memory 128KiB BIOS
/0/4 processor Intel(R) Core™ i5-1035G1 CPU @ 1.00GHz

Please use pre-formatted text / code blocks (the </> in the editor) for such output; the formatting is all messed up.

peterwhite23 · May 21, 2026, 3:20pm

But I think your instincts are correct, for I seem to remember that blinking LED’s can (be made to) indicate a kernel panic, too.

ogra · May 21, 2026, 3:21pm

Yup, they can, but I don’t think this is on in any of our generic kernels, must come from the UEFI …

peterwhite23 · May 21, 2026, 4:39pm

To recap, we see a LUKS2 container erroneously marked as ESP while there is another plain vFAT partition, which looks to be the actual ESP.

I’m wondering if someone or something altered the GPT (GUID partition table) or if this is just the tools (lshw, lsblk) getting it wrong.

The blinking LED suggests that UEFI might be failing to find a boot loader in the faux ESP, and, as someone else on this Discourse recently pointed out, multiple ESP’s are undefined behavior. Still no idea why it works with older kernels, though.

roger-19 · May 21, 2026, 5:05pm

Thank you for the suggestion! I checked the UEFI settings and Secure Boot is disabled.

I additionally disabled the following:

Intel Trust Technology
OS Optimised Defaults

There is no change unfortunately.

roger-19 · May 21, 2026, 5:07pm

Thanks for the tip, I was using the preformatted text for the outputs but somehow they still turned out messed up, will try to get it right next time!

roger-19 · May 21, 2026, 5:11pm

Six or so months ago I did a clean OS installation on this laptop and did not mess with partitioning, nor there is a dual-boot situation going on.

peterwhite23 · May 21, 2026, 5:12pm

You may need to click that button before pasting.

peterwhite23 · May 21, 2026, 7:09pm

Still unsure, if it’s just a detection issue, so this should provide a definitive answer:

$ sudo fdisk -l /dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594
Disk /dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SAMSUNG MZVLB512HBJQ-000L7
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: 4DA337FE-0D65-4324-83C5-FF91F226EB8C

Device                                                                 Start        End   Sectors   Size Type
/dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part1    2048    1050623   1048576   512M EFI System
/dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part2 1050624    2549759   1499136   732M Linux filesystem
/dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part3 2549760 1000214527 997664768 475,7G Linux filesystem

You need to adjust the actual path in /dev/disk/by-id to match your device; this example output is from mine to illustrate the naming scheme. See this Redhat documentation article as to why it’s imporant to not use /dev/nvme* directly; TLDR: the names in /dev aren’t persistent across restarts.

peterwhite23 · May 21, 2026, 7:43pm

FWIW, what I just wrote above, can actually be responsible for funny boot issues, because pointing GRUB or /etc/fstab to such legacy device names can have the effect that the actual device gets a different name and thus the kernel tries to mount the wrong one and panics. This is why UUID’s are how it’s done these days, and have been for a long time.

IOW, what is the output of these commands:

cat /proc/cmdline

sudo awk '$1~/linux/' /boot/grub/grub.cfg

cat /etc/fstab

roger-19 · May 21, 2026, 7:54pm

Thank you for the hint, I’m looking into how to change the path and will ask if I get lost, which might happen.

The output for cat /proc/cmdline

BOOT_IMAGE=/vmlinuz-6.14.0-37-generic root=/dev/mapper/ubuntu–vg-ubuntu–lv ro quiet splash

For sudo awk ‘$1~/linux/’ /boot/grub/grub.cfg it is

	linux	/vmlinuz-6.17.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro  quiet splash $vt_handoff
		linux	/vmlinuz-6.17.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro  quiet splash $vt_handoff
		linux	/vmlinuz-6.17.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro recovery nomodeset dis_ucode_ldr 
		linux	/vmlinuz-6.14.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro  quiet splash $vt_handoff
		linux	/vmlinuz-6.14.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro recovery nomodeset dis_ucode_ldr 
        linux    /memtest86+x64.efi
        linux   /memtest86+x64.efi console=ttyS0,115200

And for cat /etc/fstab it’s

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-MA8mRjEyVjnR27HFITcaj2bT68jA9H6kYveUz3XNNiPPz7ZCRHo27e3GJ6lJd8N8 / ext4 defaults 0 1
# /boot was on /dev/nvme0n1p2 during curtin installation
/dev/disk/by-uuid/89b00d12-d7ef-4dc7-8b24-6ed6f0f43fc2 /boot ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/653C-25A9 /boot/efi vfat defaults 0 1
/swap.img	none	swap	sw	0	0

tea-for-one · May 21, 2026, 8:10pm

This is quite unusual - only one bootable kernel?

Can you download Ubuntu 26.04, make a bootable USB and see if you can reach a “Try Ubuntu” live session?
It uses kernel 7.0.0-14-generic

peterwhite23 · May 21, 2026, 8:46pm

As you can see in the grub.cfg there is a menu entry for 6.14.0-37-generic. And seeing it like that makes me think this may actually be an issue with 6.17 on your hardware.

In a modification of @tea-for-one’s suggestion, I’d suggest using the 24.04.4 live installer in “Try Ubuntu” mode, which should be using the 6.17 kernel, if I’m not mistaken. You can double-check that inside the live session by running this in a terminal:

uname -r

That should tell us, if it’s really related to the kernel version, which I’m having a hard time to believe. There could be something missing in your installation or something failing. So how about we force the recreation of the initial ramdisk from scratch?

sudo update-initrams -c -k 6.17.0-29-generic

This should not be run in the live session but on the proper installation, which has the issue.

You also forgot the output of fdisk -l ....

peterwhite23 · May 21, 2026, 8:51pm

Caution! I’ve just updated the update-initramfs command. The previous iteration was targeting the old kernel, when it should have been the new one.

roger-19 · May 22, 2026, 6:01am

I have been suspecting a hardware failure of sorts for a while but couldn’t put my finger on it.

Before I try out the live installer, here is the long output of fdisk -l

sudo fdisk -l
Disk /dev/loop0: 4 KiB, 4096 bytes, 8 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


Disk /dev/loop1: 13.43 MiB, 14086144 bytes, 27512 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


Disk /dev/loop2: 13.46 MiB, 14118912 bytes, 27576 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


Disk /dev/loop3: 8.33 MiB, 8736768 bytes, 17064 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


Disk /dev/loop4: 63.78 MiB, 66875392 bytes, 130616 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


Disk /dev/loop5: 63.78 MiB, 66879488 bytes, 130624 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


Disk /dev/loop6: 7.27 MiB, 7626752 bytes, 14896 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


Disk /dev/loop7: 73.95 MiB, 77545472 bytes, 151456 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


Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SAMSUNG MZVLB1T0HBLR-000L2              
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: 8E6561F5-4592-44F2-8DD0-2F99DB555330

Device           Start        End    Sectors   Size Type
/dev/nvme0n1p1    2048    2203647    2201600     1G EFI System
/dev/nvme0n1p2 2203648    6397951    4194304     2G Linux filesystem
/dev/nvme0n1p3 6397952 2000406527 1994008576 950.8G Linux filesystem


Disk /dev/mapper/dm_crypt-0: 950.8 GiB, 1020915613696 bytes, 1993975808 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


Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 950.8 GiB, 1020914565120 bytes, 1993973760 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


Disk /dev/loop8: 73.98 MiB, 77574144 bytes, 151512 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


Disk /dev/loop9: 66.85 MiB, 70094848 bytes, 136904 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


Disk /dev/loop10: 66.8 MiB, 70049792 bytes, 136816 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


Disk /dev/loop11: 120.63 MiB, 126492672 bytes, 247056 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


Disk /dev/loop14: 120.63 MiB, 126492672 bytes, 247056 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


Disk /dev/loop12: 246.63 MiB, 258609152 bytes, 505096 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


Disk /dev/loop13: 247.52 MiB, 259538944 bytes, 506912 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


Disk /dev/loop15: 16.45 MiB, 17248256 bytes, 33688 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


Disk /dev/loop16: 16.5 MiB, 17301504 bytes, 33792 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


Disk /dev/loop17: 516.01 MiB, 541073408 bytes, 1056784 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


Disk /dev/loop19: 606.08 MiB, 635518976 bytes, 1241248 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


Disk /dev/loop18: 531.38 MiB, 557187072 bytes, 1088256 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


Disk /dev/loop21: 91.69 MiB, 96141312 bytes, 187776 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


Disk /dev/loop22: 10.35 MiB, 10854400 bytes, 21200 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


Disk /dev/loop20: 10.36 MiB, 10858496 bytes, 21208 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


Disk /dev/loop24: 154.27 MiB, 161763328 bytes, 315944 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


Disk /dev/loop25: 154.07 MiB, 161554432 bytes, 315536 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


Disk /dev/loop23: 394.98 MiB, 414167040 bytes, 808920 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


Disk /dev/loop27: 15.69 MiB, 16449536 bytes, 32128 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


Disk /dev/loop29: 49.26 MiB, 51654656 bytes, 100888 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


Disk /dev/loop28: 48.37 MiB, 50716672 bytes, 99056 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


Disk /dev/loop26: 15.57 MiB, 16326656 bytes, 31888 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


Disk /dev/loop30: 580 KiB, 593920 bytes, 1160 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


Disk /dev/loop31: 580 KiB, 593920 bytes, 1160 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


Disk /dev/loop32: 82.59 MiB, 86601728 bytes, 169144 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


Disk /dev/loop34: 193.18 MiB, 202567680 bytes, 395640 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


Disk /dev/loop35: 197 MiB, 206573568 bytes, 403464 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