In GPT/BIOS, GRUB2 "installs" on BIOS boot partition "core.img" consiting of "diskboot.img", lzma decompressor (lzma_decompress.img) and core.img (IIUC). I assumed that skipping 512 B of diskboot.img, then skipping lzma decompressor (2880 B on SLES), I would get compressed "real" core.img (ending where '00 00' follows). But how to decompress this part? Or, do I do anything wrong? BTW, I can't decompress even /boot/grub2/i386-pc/core.img (on SLES too) while skipping same parts... The goal is to see real "core.img" data to detect a modification...

I'm attempting to run 32 bit linux off of a usb for an old XP machine. There are important files on the computer's base drive, so formatting or partitioning isn't on the cards. So far I've tried AntiX and Debian, and in both cases I was sent straight to grub repair with the error "/boot/grub/i386-pc/normal.mod cannot be found". Using grub rescue I identified the correct partition, and can use ls to see the list of folders to find the /boot folder, however any attempt to ls into the boot folder produces an empty line before returning the command prompt. Examining the usb with a different computer, the normal.mod file is there in its correct place, however the boot folder and a few other folders cannot be written to or modified due to permission issues which I can't figure out. My best guess is that grub simply isn't allowing itself to read the boot folder, but I'm not sure

After updating with pacman -Syu system fails to boot. ERROR: device '/dev/lvmSystemXXX/volRootXXX' not found. Skipping fsck. mount: /new_root: fsconfig() failed: /dev/lvmSystemXXX/volRootXXX: Can't lookup blockdev. ERROR: failed to mount '/dev/lvmSystemXXX/volRootXXX' on real root You are now being dropped into an emergecy shell. sh: can't access tty: job control truned off [rootfs ~]# Some background info Linux: [rootfs ~]# uname -a Linux archlinux 6.15.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 02 Aug 2025... x86_64 GNU/Linux Drives [rootfs ~]# blkid /dev/sdb2:UUID="A123456789" TYPE="crypto_LUKS" PARTUUID="A987654321" /dev/sdb1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="B123456789" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="B987654321" Is there a possibility to check if the kernel was updated and eventually downgrade from emergecy shell? mkinitcpio.conf file here # vim:set ft=sh # MODULES # The following modules are loaded before any boot hooks are # run. Advanced users may wish to specify all system modules # in this array. For instance: # MODULES=(usbhid xhci_hcd) MODULES=() # BINARIES # This setting includes any additional binaries a given user may # wish into the CPIO image. This is run last, so it may be used to # override the actual binaries included by a given hook # BINARIES are dependency parsed, so you may safely ignore libraries BINARIES=() # FILES # This setting is similar to BINARIES above, however, files are added # as-is and are not parsed in any way. This is useful for config files. FILES=() # HOOKS # This is the most important setting in this file. The HOOKS control the # modules and scripts added to the image, and what happens at boot time. # Order is important, and it is recommended that you do not change the # order in which HOOKS are added. Run 'mkinitcpio -H ' for # help on a given hook. # 'base' is _required_ unless you know precisely what you are doing. # 'udev' is _required_ in order to automatically load modules # 'filesystems' is _required_ unless you specify your fs modules in MODULES # Examples: ## This setup specifies all modules in the MODULES setting above. ## No RAID, lvm2, or encrypted root is needed. # HOOKS=(base) # ## This setup will autodetect all modules for your system and should ## work as a sane default # HOOKS=(base udev autodetect modconf block filesystems fsck) # ## This setup will generate a 'full' image which supports most systems. ## No autodetection is done. # HOOKS=(base udev modconf block filesystems fsck) # ## This setup assembles a mdadm array with an encrypted root file system. ## Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices. # HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck) # ## This setup loads an lvm2 volume group. # HOOKS=(base udev modconf block lvm2 filesystems fsck) # ## This will create a systemd based initramfs which loads an encrypted root filesystem. # HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck) # ## NOTE: If you have /usr on a separate partition, you MUST include the # usr and fsck hooks. HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck) # COMPRESSION # Use this to compress the initramfs image. By default, zstd compression # is used for Linux ≥ 5.9 and gzip compression is used for Linux Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.12.41-1-lts' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] -> Running build hook: [base] ... [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [modconf] [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [block] [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/95-dm-notify.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-initramfs.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/ossl-modules/legacy.so': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] install: error writing '/tmp/mkinitcpio.evH3PB/root/hooks/encrypt': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/pdata_tools': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-lvm.rules': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device ... [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/twofish_common.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/aegis128.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_raid6_recov.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm4-aesni-avx-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/curve25519-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast6_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast_common.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/hctr2.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/hid/hid-generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/ecrdsa_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/cdrom/cdrom.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/intel/iaa/iaa_crypto.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/wp512.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-raid.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/chelsio/chcr.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/scsi/virtio_scsi.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/fcrypt.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast5_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-mod.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/aegis128-aesni.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/crc32c-intel.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-thin-pool.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/camellia-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_pq.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xxhash_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/vmac.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/raid456.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/crypto_null.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_xor.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme-core.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cryptd.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/sm4_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cmac.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xcbc.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/blake2b_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm3-avx-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-region-hash.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/padlock-sha.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/geniv.ko.zst': No space left on device ... [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/crypto/seqiv.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/input/keyboard/applespi.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/smb/common/cifs_arc4.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/mfd/max14577.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/vfio/vfio.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/zonefs/zonefs.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: Could not create index 'modules.dep'. Output is truncated: No space left on device [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img' [2025-08-05T00:26:58+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete. [2025-08-05T00:26:58+0200] [ALPM] running 'dbus-reload.hook'... [2025-08-05T00:26:58+0200] [ALPM] running 'detect-old-perl-modules.hook'... [2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/5.40' contains data from at least 1 packages which will NOT be used by the installed perl interpreter. [2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET] -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.40' [2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig.hook'... [2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig-32.hook'... [2025-08-05T00:27:00+0200] [ALPM] running 'gdk-pixbuf-query-loaders.hook'... [2025-08-05T00:27:00+0200] [ALPM] running 'ghc-register.hook'... [2025-08-05T00:27:13+0200] [ALPM] running 'glib-compile-schemas.hook'... [2025-08-05T00:27:13+0200] [ALPM] running 'gtk-update-icon-cache.hook'... [2025-08-05T00:27:14+0200] [ALPM] running 'texinfo-install.hook'... [2025-08-05T00:27:16+0200] [ALPM] running 'update-desktop-database.hook'... [2025-08-05T00:27:16+0200] [ALPM] running 'xorg-mkfontscale.hook'... [2025-08-05T00:27:18+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:18+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:21+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:21+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:24+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:24+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:27+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:27+0200] [PACMAN] synchronizing package lists [2025-08-05T00:28:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:28:00+0200] [PACMAN] synchronizing package lists [2025-08-05T00:29:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:29:00+0200] [PACMAN] synchronizing package lists

I dual booted windows 11 and Endeavor OS on my HP notebook without any problem, but after a BIOS update the Boot options menu listed Endeavour os as EFI hard drive. Also now the OS boot manager doesn't show Endeavour os as another OS and thus cannot choose the os on bootup. Any help would be much appreciated.

I am trying to dual boot Linux on my laptop (Dell XPS 15) which is running Windows 10 Pro. I did not have any problem dual booting the two operating systems on my desktop. I cannot boot up **ANY** Linux Distro, I have tried Mint, Ubuntu and Elementary OS. Whenever I try to boot from a live USB, I get the this message on all attempts: **GNU GRUB version 2.02~beta2-9ubuntu1** **Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists are possible device or file completions.** **grub>** When I type in "boot" I get the error: **you need to load the kernel first.** Secure boot is disabled, and I have tried both in legacy and UEFI BIOS mode. I have never come across this error before, what causes it?

I’m using Parrot OS in dual boot with Windows 10. One day Windows just stopped booting from GRUB with next error:

/EndEntire
file path: /ACPI(a034d0,0)/PCI(1,1)/PCI(0,0)/UnknownMessaging(17)/HD(1,800,32000,f452754febf9674d,2,2)
/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi)/EndEntire 
error: cannot load image.
I have tried using boot-repair to fix this but it didn’t help. Here is its log: http://paste.ubuntu.com/p/6SXYdWxwxh/ 

When I try to boot Windows directly from BIOS, the screen just blinks for a second and nothing happens. Linux is working fine. have tried using boot-repair to fix this but it didn’t help. Here is its log: http://paste.ubuntu.com/p/6SXYdWxwxh/ Secure boot in BIOS is set to off.

I am attempting to install a dualboot (Ubuntu on top of Windows 10) to a PC I have just built myself. I have no problem installing Ubuntu, its just I am unable to setup my computer to boot into it afterwards. During the instalation I am told that the GRUB does not install properly and I also hit errors when trying to run a boot repair program in terminal. I am creating the installation using Rufus, and making use of the MBR parition scheme. The Disk I am creating it on is GPT, but when I try use this partition scheme in Rufus an error scheme comes up when I try boot this from a USB stick. This is shown in the next image (and note my bios mode is set to UEFI). For reference my motherboard is a "MSI B450 TOMAHAWK MAX Motherboard ATX". What is the best course of action to take? I found some videos that showed how to convert my from UEFI to legacy boot and to change my disk to a MSB partition, would this be the best solution or will this create further problems down the line?

I am trying to boot Fedora Silverblue onto my laptop VIA a USB drive and I keep getting

[FAILED] Failed to start checkisomd5@dev-sdb.service - Media check on /dev/sdb.
dracut-initqueue: Job for checkisomd5@dev-sdb.service failed because the control process exited with error code.
dracut-initqueue: See "systemct1 status checkisomd5@dev-sdb.service" and "journalct1 -xeu checkisomd5@dev-sdb.service" for details
dracut: FATAL: CD check failed!
dracut: Refusing to continue

I tried running the ISO I downloaded directly on a VM through VBox and it worked fine, any clue why I keep getting this error?

In a simple install of Redhat from rhel-8.10-x86_64-dvd.iso I have this /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/fbx64.efi /boot/efi/EFI/redhat/grubx64.efi /boot/efi/EFI/redhat/mmx64.efi /boot/efi/EFI/redhat/shimx64.efi /boot/efi/EFI/redhat/shimx64-redhat.efi Can a quick explanation be given of each? On a Dell server, in the F11 boot menu when making an Add Boot option, which of the above is the proper one to choose?

1. Installed Remix OS 3.0 With official supported tool i.e., RemixUSBTool. On Hard Drive Partition. What Actually Happened ? 2. **After Installing** **->** **Working Normally** **->** **Download Updates** **->** **Reboot** **->** **After Installing Updates** **->** **Rebooted Again** **->** **Got Following Error** **--->** find --set-root --ignore-floppies /menu.lst error 15:File Not Found Press any key to continue . . . Here's some more information (in case needed) - Triple-booted computer with Windows 10, Ubuntu 16.10 & This One. - Ubuntu stopped working after the above error. (But I fixed this with EasyBSD). Also, after that error, the **RemixOS folder is inaccessible** from Windows 10 (and from other OSes as well.) _______________________ So, does anybody have any solution for it? (I've already tried a solution suggested on googlegroupchat, but it doesn't work for me.)