wuqso
June 15, 2026, 12:34pm
1
My laptop (xiaomi notebook 14 pro 2026) has F44 and Win11 installed. Two days ago, the F44 system cannot boot and the screen shows:
unexpected return from initial read: Volume Corrupt, buffersize 1000
Failed to load image \EFI\fedora\grubx64.efi: Volume Corrupt
start_image() returned Volume Corrupt
Failed to open \EFI\fedora\grubx64.efi - Volume Corrupt
Failed to load image \EFI\fedora\grubx64.efi: Volume Corrupt
start_image() returned Volume Corrupt
startimage failed: Volume Corrupt
What’s the problem? What can I do to recover the system booting?
pg-tips
June 15, 2026, 12:37pm
2
Sorry to state the obvious, but it sounds like corruption on the EFI partition.
You could try reinstalling the bootloader from a Fedora Live USB using this documentation .
Do you also have problems booting into Windows? If so, it’s better to repair Windows first, and then fix Fedora second.
gnwiii
June 15, 2026, 1:43pm
3
You should check drive health and free space on the EFI partition. That can be done using the F44 Workstation Live USB with Gnome Disks. I’ve had multiple instances of Windows 11 updates messing with the EFI partition — did the issue start after a Windows update?
wuqso
June 15, 2026, 2:26pm
4
Thank you for your reply. I tried according to the documentation you mentioned but the problem remains.
I do not have problem to boot into Windows.
wuqso
June 15, 2026, 2:31pm
5
It seems this issue start after a Windows update (However, I update F44 almost everyday).
The EFI partition is 273 MB and 186 MB is free as shown in Gnome Disks. When using ‘fdisk -l’ to check the partition, the system shows
Partition table entries are not in disk order.
wuqso
June 15, 2026, 2:56pm
6
Sorry, in trying the steps mention in the documentation, there is error of “tty: ttyname error: No such device” when typing “sudo chroot /mnt”. How can I fix it?
pg-tips
June 15, 2026, 2:59pm
7
I don’t know, but what happens if you use chroot /mnt without sudo? (The docs don’t use sudo.)
wuqso
June 15, 2026, 3:16pm
8
$ chroot /mnt
chroot: cannot change root directory to ‘/mnt’: Operation not permitted
When there is no sudo, even the mount commands cannot be executed.
pg-tips
June 15, 2026, 3:17pm
9
Interesting - which live USB are you using?
wuqso
June 15, 2026, 3:21pm
13
So the packages were not installed in fact.
pg-tips
June 15, 2026, 3:22pm
14
Did you mount all of these?
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
mount -o bind /run /mnt/run
I think I’ve seen that “unable to allocate pty” error in cases where /proc wasn’t mounted.
