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...

Installing Debian on a virtual machine interactively:

virt-install --virt-type kvm --name debian-13-x64 \
--memory 4096 \
--vcpus 4 \
--cdrom /mnt/data/iso/debian-testing-amd64-DVD-1.iso \
--os-variant debiantesting \
--disk size=64

Boots into the desktop environment as expected. However, when performing an unattended install:

virt-install --virt-type kvm --name debian-13-x64 \
--memory 4096 \
--vcpus 4 \
--os-variant debiantesting \
--disk size=64 \
--graphics none \
--location /mnt/data/iso/debian-testing-amd64-DVD-1.iso \
--initrd-inject /mnt/data/debian-13-preseed.txt \
--extra-args "auto=true priority=critical preseed/file=/debian-13-preseed.txt console=ttyS0,115200n8"

It hangs after the "Loading initial ramdisk" message upon completing the installation and rebooting. Before rebooting, I captured the last lines of output from the unattended install log:

Jul 26 22:40:58 finish-install: info: Running /usr/lib/finish-install.d/10update-initramfs
Jul 26 22:40:58 /bin/in-target: warning: /target/etc/mtab won't be updated since it is a symlink.
Jul 26 22:40:58 finish-install: info: Running /usr/lib/finish-install.d/15cdrom-detect
Jul 26 22:40:58 cdrom-detect: Unmounting and ejecting '/dev/sr0'
Jul 26 22:40:58 finish-install: info: Running /usr/lib/finish-install.d/20final-message
Jul 26 22:41:10 finish-install: /usr/lib/finish-install.d/20final-message backed up
Jul 26 22:41:10 main-menu: INFO: Menu item 'finish-install' succeeded but requested to be left unconfigured.
Jul 26 22:41:10 depthcharge-tools-installer: Not installing to non-ChromeOS board.
Jul 26 22:41:10 systemd-boot-installer: systemd-boot is only usable on 64bit EFI systems, not amd64/generic
Jul 26 22:41:10 depthcharge-tools-installer: Not installing to non-ChromeOS board.
Jul 26 22:41:10 systemd-boot-installer: systemd-boot is only usable on 64bit EFI systems, not amd64/generic
Jul 26 22:41:21 main-menu: INFO: Menu item 'di-utils-shell' selected

It appears to be attempting to write BIOS to an EFI partition. Why the difference in behavior between interactive and unattended installs? As far as I can tell the selections are the same. From this I based debian-13-preseed.txt. Here's the content:

#_preseed_V1
#### Contents of the preconfiguration file (for trixie)
### Localization
# Preseeding only locale sets language, country and locale.
d-i debian-installer/locale string en_US.UTF-8

# Keyboard selection.
d-i keyboard-configuration/xkb-keymap select us

# netcfg will choose an interface that has link if possible. This makes it
# skip displaying a list if there is more than one interface.
d-i netcfg/choose_interface select auto

# Any hostname and domain names assigned from dhcp take precedence over
# values set here. However, setting the values still prevents the questions
# from being shown, even if values come from dhcp.
d-i netcfg/get_hostname string unassigned-hostname
d-i netcfg/get_domain string unassigned-domain

# Disable that annoying WEP key dialog.
d-i netcfg/wireless_wep string

### Mirror settings
# Mirror protocol:
# If you select ftp, the mirror/country string does not need to be set.
# Default value for the mirror protocol: http.
#d-i mirror/protocol string ftp
d-i mirror/country string manual
d-i mirror/http/hostname string http.us.debian.org
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string

### Account setup
# Skip creation of a root account (normal user account will be able to
# use sudo).
d-i passwd/root-login boolean false

# To create a normal user account.
d-i passwd/user-fullname string Debian User
d-i passwd/username string debian
# Normal user's password, either in clear text
d-i passwd/user-password password insecure
d-i passwd/user-password-again password insecure

### Clock and time zone setup
# Controls whether or not the hardware clock is set to UTC.
d-i clock-setup/utc boolean true

# You may set this to any valid setting for $TZ; see the contents of
# /usr/share/zoneinfo/ for valid values.
d-i time/zone string US/Eastern

# Controls whether to use NTP to set the clock during the install
d-i clock-setup/ntp boolean true

### Partitioning
# The presently available methods are:
# - regular: use the usual partition types for your architecture
# - lvm:     use LVM to partition the disk
# - crypto:  use LVM within an encrypted partition
d-i partman-auto/method string lvm

# You can define the amount of space that will be used for the LVM volume
# group. It can either be a size with its unit (eg. 20 GB), a percentage of
# free space or the 'max' keyword.
d-i partman-auto-lvm/guided_size string max

# If one of the disks that are going to be automatically partitioned
# contains an old LVM configuration, the user will normally receive a
# warning. This can be preseeded away...
d-i partman-lvm/device_remove_lvm boolean true
# The same applies to pre-existing software RAID array:
d-i partman-md/device_remove_md boolean true
# And the same goes for the confirmation to write the lvm partitions.
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true

# You can choose one of the predefined partitioning recipes:
# - atomic: all files in one partition
# - home:   separate /home partition
# - multi:  separate /home, /var, and /tmp partitions
# - server: separate /var and /srv partitions; swap limitted to 1G
# - small_disk: scheme dedicated to small harddrives (under 10GB)
d-i partman-auto/choose_recipe select atomic

# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true

# This makes partman automatically partition without confirmation.
d-i partman-md/confirm boolean true
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true

### Base system installation
# Configure APT to not install recommended packages by default. Use of this
# option can result in an incomplete system and should only be used by very
# experienced users.
#d-i base-installer/install-recommends boolean false

# The kernel image (meta) package to be installed; "none" can be used if no
# kernel is to be installed.
#d-i base-installer/kernel/image string linux-image-686

### Apt setup
# Choose, if you want to scan additional installation media
# (default: false).
d-i apt-setup/cdrom/set-first boolean false

### Boot loader installation
# Grub is the boot loader (for x86).

# This is fairly safe to set, it makes grub install automatically to the UEFI
# partition/boot record if no other operating system is detected on the machine.
d-i grub-installer/only_debian boolean true

# This one makes grub-installer install to the UEFI partition/boot record, if
# it also finds some other OS, which is less safe as it might not be able to
# boot that other OS.
d-i grub-installer/with_other_os boolean true

# Due notably to potential USB sticks, the location of the primary drive can
# not be determined safely in general, so this needs to be specified:
#d-i grub-installer/bootdev  string /dev/sda
# To install to the primary device (assuming it is not a USB stick):
d-i grub-installer/bootdev  string default

### Finishing up the installation
# During installations from serial console, the regular virtual consoles
# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next
# line to prevent this.
d-i finish-install/keep-consoles boolean true

# Avoid that last message about the install being complete.
#d-i finish-install/reboot_in_progress note

I'm using dual boot Windows 11 and Fyde OS. On my bootloader screen there are 3 other boot options which are not any OS, they are EFI and recovery partition. I want only Windows and Fyde OS boot logo on my bootloader screen. The boot manager is rEFInd boot manager which got installed automatically with Fyde OS. I also have Linux environment installed on Fyde OS.

I want to install grub on SD card because my laptop don't boot from external sata port. I've the SSD connected to the laptop through the external port sata to make it easier for me to boot the operating system also on my desktop. I would like only to have to install grub in the SD, but maybe the only solution is to install linux on the card just to modify the grub configuration and be able to launch the existing operating system on the ssd disk. I'll never use the OS written on the SD. Is possible setup grub on SD card? Thanks

I am trying to setup proxmox on Dell r720xd, which does have UEFI boot option but can not boot from PCIe nvme drives. If I install proxmox (or any os) on a usb flash, it boots fine. For testing, I installed CentOS with advanced partitioning, and used USB flash as /boot partition, and nvme for all other partitions and that too works flawlessly. With proxmox, there is no custom partitioning option during the setup, so I was unable to set usb key as /boot partition during install. Other option listed in proxmox forums are - use clover as bootloader on a USB key, described here - install debian first with custom partition and then install proxmox over it and remove debian kernel. Obviously clover is adding a boot partition on usb and then forwarding the control to nvme. My question is, how to install proxmox on nvme and then migrate the /boot partition to the usb flash? Seems like a very straight forward process and I followed this guide to handle it, however, I could not get it to work. grub2 always complained with messages like - not matching UUID - you need to load kernel first - and so on any hints please. P.S. I also tried to edit the centos /boot installed on flash drive, by using grub2-mkconfig which found the proxmox and updated the grub.cfg but still got errors during boot like - error: cant't find command linux - error: cant't find command initrd fixed these errors (ref ) by linuxefi and initrdefi but then it could not find the drive with given UUID

My PC takes a long time booting. I have reason to believe it is caused by delays after grub, but before kernel logging starts (booting takes 30 seconds, but dmesg messages have time stamps between 0.00000 - 9.34223, details in [this post](https://unix.stackexchange.com/questions/499832/long-time-spent-between-grub2-menu-before-kernel-boot)) . Are there any ways to debug what's going on? In particular: * Is there a way to make grub itself more verbose, or keep logs? * Are there any other processes between grub and the kernel logging that could be taking time? How do I debug those? I believe the question is not specific to my setup. But just in case, I'm running Ubuntu 16.10 and grub(2) **EDIT**: Following a suggestion by @TooTea, I set the debug=all environment variables which produced a lot of messages a la script/script.c:50 malloc 0x7a9a2ca0 that should not be a problem. Then there is one block of messages that coincide with a 8 seconds delay delay: kern/dl.c:56 Detecting ext2... lib/relocator.c:1397 chunks = 0x7a7e0ae0 lib/relocator.c:434 trying to allocate in ...-... aligned ... size ... lib/relocator.c:1198 allocated: ...+... lib/relocator.c:1409 allocated .../... lib/relocator.c:1410 chunks = 0x7a7e0ae0

It seems that the even the most recent version of GRUB2 doesn't support LUKS2 with the PBKDF Argon2ID ([source](https://wiki.archlinux.org/index.php/GRUB#Encrypted_/boot)) . The Raspberry Pi bootloader for instance fully supports this new hashing function. Is there an actively maintained (and widely enough adopted) desktop Linux bootloader that supports LUKS2 devices with Argon2ID? Would it be possible to achieve an encrypted /boot (other than /) partition with this PBKDF?

A couple years ago I set up a computer build with an ASUS motherboard for running POP! OS. Then, shortly afterward, I purchased a second hard drive, and I installed windows on it for a dual-boot, using windows bootloader. The problem, now, is the Windows drive got broken, and when I try to boot to just the POP! OS installation the only option to boot to in the BIOS is windows boot manager, and when I boot to it I get a blue screen, and some options, but no matter what option I choose, they all just reboot the system and repeat the process. I am wondering is there a way I can revert to a normal boot using just the POP! OS grub as it was before? Someone else on this forum had a similar issue: https://unix.stackexchange.com/questions/688253/windows-breaks-bootloader-in-dual-boot-with-pop-os but their problem is currently unresolved. Any help is appreciated!

I have googled a lot for this problem. I found this, but it didn't solve my problem. Other solutions suggest me to reinstall grub (run grub-install), which didn't work either. Here is what I am doing: (my grub version is 2.02) 1. I use grub2-mkrescue to make my X.iso 2. I boot a VMWareWorkstation virtual machine, which has a 1.0GB SATA disk, from X.iso 3. I install X.iso on disk, the details are: 3.1. erase /dev/sda in case there are old partitions on it: dd if=/dev/zero of=/dev/sda bs=1M count=1 3.2. Create 3 primary partitions on /dev/sda as dev/sda1,sda2,sda3 (the size is 100M, 30M and 70M), and toggle sda1 to be bootable

Disk /dev/sda: 1024 MB, 1073741824 bytes, 2097152 sectors
130 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sda1 *  0,1,1       12,191,50           63     204862     204800  100M 83 Linux
/dev/sda2    12,191,51   16,147,2        204863     266302      61440 30.0M 83 Linux
/dev/sda3    16,147,3    25,127,37       266303     409662     143360 70.0M 83 Linux

3.3. Format the 3 partitions as ext2, and mount /dev/sda1

mkfs.ext2 /dev/sda1
mkfs.ext2 /dev/sda2
mkfs.ext2 /dev/sda3
ROOTFS_PATH=/var/.rootfs
mkdir $ROOTFS_PATH
mount /dev/sda1 $ROOTFS_PATH

3.4 copy files...

for i in bzImage initrd.img vmlinuz-*; do
    cp -rf /boot/$i $ROOTFS_PATH/boot
done
cp -f /boot/grub/device.map $ROOTFS_PATH/boot/grub/device.map
for i in init linuxrc; do
    cp -rf /$i $ROOTFS_PATH
done
for i in bin etc lib sbin share usr; do
    cp -a /$i $ROOTFS_PATH
done
for i in dev var proc sys tmp data log; do
    mkdir -p $ROOTFS_PATH/$i
done

3.5 Install grub and make grub config file

chroot $ROOTFS_PATH

And the most strange thing is that ls command shows nothing in grub-rescue cli ---- as someone says, it should show disk list.

My Lenovo laptop is running Arch Linux with a UEFI GPT partition table. One day I powered up my laptop, but couldn't get passed the Lenovo boot screen. I used a USB stick to boot up and reinstall Arch. However after this I still couldn't get passed the Lenovo boot screen. I tried to reinstall it again using the same USB stick and ended up with two entries in my UEFI boot menu. I formatted the GUID partition to FAT32 using GPARTED live USB which deleted them. However I can no longer use my Arch UEFI USB stick to boot up. I get to the bootloader menu on the USB stick but after the timeout I get a blank screen.

I have a Windows 10 install on an NVMe drive. I've installed Ubuntu 20.04 and all installed smoothly, until the first boot. I was greeted with a grub prompt. grub> After searching the forums and finding a wealth of information, I've been able to issue the following command and reach GRUB bootloader (and both Windows and Ubuntu load correctly from there): grub> configfile (hd1,gpt5)/boot/grub/grub.cfg However, when I reboot, I'm back to the grub command line. I've also found the following commands from the forums: grub> set root=(hd1,gptN) grub> set prefix=(hd1,gptN)/boot/grub/ grub> insmod normal grub> normal These commands also bring me to my grub menu and I can safely boot into either OS (Windows or Ubuntu). The problem is that I have to do this each time. Thus, I'm trying to make a permanent change to my grub settings. Once in Ubuntu, I can update grub from the command line, and I can also reinstall grub. Both with the following. $: sudo update-grub $: sudo grub-install /dev/nvme0n1pX However, I'm at a loss of how to ensure the correct partition number for X in the grub-install command. Is it as simple as N from the root/prefix commands within the above grub terminal? Or is there more definitive way to check which partition number to choose? Any help is much appreciated.

I was using a dual boot of openSUSE and Windows and I decided to delete OpenSUSE by deleting the partition. On rebooting, I found out that the secure boot for openSUSE was still there, leading to an error. to make things worse, the Windows boot loader was no longer there and I have to access it through the UEFI settings. How do I change this to automatically boot windows again?

After upgrade to Debian Bookworm, I'm encountering slow boot, significantly slower than the previous Bullseye version. How to find the real reason and fix it? **boot log:**

[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
[  OK  ] Reached target Network.
         Starting CUPS Scheduler...
         Starting OpenVPN service...
         Starting Permit User Sessions...
[  OK  ] Finished Permit User Sessions.
         Starting Light Display Manager...
         Starting Hold until boot process finishes up...
[  OK  ] Finished OpenVPN service.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Finished Rotate log files.
------------ Mon Jun 23 15:27:17 EEST 2025 ------------
root: clean, 257828/1638400 files, 4733489/6553600 blocks
     Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System...
[  OK  ] Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System.
[  OK  ] Finished systemd-binfmt.service - Set Up Additional Binary Formats.
         Starting binfmt-support.service - Enable support for additional executable binary formats...
[  OK  ] Finished ufw.service - Uncomplicated firewall.
[  OK  ] Finished binfmt-support.service - Enable support for additional executable binary formats.
[  OK  ] Finished systemd-tmpfiles-setup.service - Create System Files and Directories.
[  OK  ] Started resolvconf.service - Nameserver information manager.
[  OK  ] Reached target network-pre.target - Preparation for Network.
         Starting systemd-timesyncd.service - Network Time Synchronization...
         Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
[  OK  ] Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
[  OK  ] Started systemd-timesyncd.service - Network Time Synchronization.
[  OK  ] Reached target time-set.target - System Time Set.
         Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
[  OK  ] Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
         Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
         Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
         Starting modprobe@loop.service - Load Kernel Module loop...
[  OK  ] Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
[  OK  ] Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
[  OK  ] Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
[  OK  ] Finished modprobe@loop.service - Load Kernel Module loop.
[  OK  ] Finished apparmor.service - Load AppArmor profiles.
[  OK  ] Reached target sysinit.target - System Initialization.
[  OK  ] Started acpid.path - ACPI Events Check.
[  OK  ] Started cups.path - CUPS Scheduler.
[  OK  ] Started anacron.timer - Trigger anacron every hour.
[  OK  ] Started apt-daily.timer - Daily apt download activities.
[  OK  ] Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
[  OK  ] Started dpkg-db-backup.timer - Daily dpkg database backup timer.
[  OK  ] Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Started exim4-base.timer - Daily exim4-base housekeeping.
[  OK  ] Started fstrim.timer - Discard unused blocks once a week.
[  OK  ] Started fwupd-refresh.timer - Refresh fwupd metadata regularly.
[  OK  ] Started logrotate.timer - Daily rotation of log files.
[  OK  ] Started man-db.timer - Daily man-db regeneration.
[  OK  ] Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[  OK  ] Reached target paths.target - Path Units.
[  OK  ] Reached target timers.target - Timer Units.
[  OK  ] Listening on acpid.socket - ACPID Listen Socket.
[  OK  ] Listening on avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on cups.socket - CUPS Scheduler.
[  OK  ] Listening on dbus.socket - D-Bus System Message Bus Socket.
[  OK  ] Listening on pcscd.socket - PC/SC Smart Card Daemon Activation Socket.
[  OK  ] Listening on uuidd.socket - UUID daemon activation socket.
[  OK  ] Reached target sockets.target - Socket Units.
         Starting networking.service - Raise network interfaces...
[  OK  ] Reached target basic.target - Basic System.
         Starting alsa-restore.service - Save/Restore Sound Card State...
[  OK  ] Started anacron.service - Run anacron jobs.
         Starting avahi-daemon.service - Avahi mDNS/DNS-SD Stack...
         Starting bluetooth.service - Bluetooth service...
[  OK  ] Started cron.service - Regular background program processing daemon.
         Starting dbus.service - D-Bus System Message Bus...
         Starting e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots...
         Starting lm-sensors.service - Initialize hardware monitoring sensors...
         Starting polkit.service - Authorization Manager...
         Starting rsyslog.service - System Logging Service...
         Starting smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon...
         Starting systemd-logind.service - User Login Management...
         Starting udisks2.service - Disk Manager...
[  OK  ] Finished alsa-restore.service - Save/Restore Sound Card State.
[  OK  ] Reached target sound.target - Sound Card.
[  OK  ] Started rsyslog.service - System Logging Service.
[  OK  ] Finished lm-sensors.service - Initialize hardware monitoring sensors.
[  OK  ] Started smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.
[FAILED] Failed to start networking.service - Raise network interfaces.
See 'systemctl status networking.service' for details.
[  OK  ] Started dbus.service - D-Bus System Message Bus.
         Starting NetworkManager.service - Network Manager...
         Starting wpa_supplicant.service - WPA supplicant...
[  OK  ] Started bluetooth.service - Bluetooth service.
[  OK  ] Started avahi-daemon.service - Avahi mDNS/DNS-SD Stack.
[  OK  ] Started systemd-logind.service - User Login Management.
[  OK  ] Reached target bluetooth.target - Bluetooth Support.
[  OK  ] Finished e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots.
[  OK  ] Started polkit.service - Authorization Manager.
         Starting ModemManager.service - Modem Manager...
         Starting systemd-hostnamed.service - Hostname Service...
[  OK  ] Started wpa_supplicant.service - WPA supplicant.
[  OK  ] Started systemd-hostnamed.service - Hostname Service.
[  OK  ] Started udisks2.service - Disk Manager.
[  OK  ] Started NetworkManager.service - Network Manager.
[  OK  ] Reached target network.target - Network.
         Starting NetworkManager-wait-online.service - Network Manager Wait Online...
         Starting cups.service - CUPS Scheduler...
         Starting openvpn.service - OpenVPN service...
         Starting systemd-user-sessions.service - Permit User Sessions...
[  OK  ] Finished openvpn.service - OpenVPN service.
[  OK  ] Finished systemd-user-sessions.service - Permit User Sessions.
         Starting lightdm.service - Light Display Manager...
         Starting plymouth-quit-wait.service - Hold until boot process finishes up...
------------ Mon Jun 23 23:30:33 EEST 2025 ------------
root: clean, 235447/1638400 files, 3704404/6553600 blocks
     Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System...
[  OK  ] Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System.
[  OK  ] Finished systemd-binfmt.service - Set Up Additional Binary Formats.
         Starting binfmt-support.service - Enable support for additional executable binary formats...
[  OK  ] Finished ufw.service - Uncomplicated firewall.
[  OK  ] Finished binfmt-support.service - Enable support for additional executable binary formats.
[  OK  ] Finished systemd-tmpfiles-setup.service - Create System Files and Directories.
[  OK  ] Started resolvconf.service - Nameserver information manager.
[  OK  ] Reached target network-pre.target - Preparation for Network.
         Starting systemd-timesyncd.service - Network Time Synchronization...
         Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
[  OK  ] Started systemd-timesyncd.service - Network Time Synchronization.
[  OK  ] Reached target time-set.target - System Time Set.
[  OK  ] Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
[  OK  ] Finished apparmor.service - Load AppArmor profiles.
[  OK  ] Reached target sysinit.target - System Initialization.
[  OK  ] Started acpid.path - ACPI Events Check.
[  OK  ] Started cups.path - CUPS Scheduler.
[  OK  ] Started anacron.timer - Trigger anacron every hour.
[  OK  ] Started apt-daily.timer - Daily apt download activities.
[  OK  ] Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
[  OK  ] Started dpkg-db-backup.timer - Daily dpkg database backup timer.
[  OK  ] Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Started exim4-base.timer - Daily exim4-base housekeeping.
[  OK  ] Started fstrim.timer - Discard unused blocks once a week.
[  OK  ] Started fwupd-refresh.timer - Refresh fwupd metadata regularly.
[  OK  ] Started logrotate.timer - Daily rotation of log files.
[  OK  ] Started man-db.timer - Daily man-db regeneration.
[  OK  ] Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[  OK  ] Reached target paths.target - Path Units.
[  OK  ] Reached target timers.target - Timer Units.
[  OK  ] Listening on acpid.socket - ACPID Listen Socket.
[  OK  ] Listening on avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on cups.socket - CUPS Scheduler.
[  OK  ] Listening on dbus.socket - D-Bus System Message Bus Socket.
[  OK  ] Listening on pcscd.socket - PC/SC Smart Card Daemon Activation Socket.
[  OK  ] Listening on uuidd.socket - UUID daemon activation socket.
[  OK  ] Reached target sockets.target - Socket Units.
[  OK  ] Reached target basic.target - Basic System.
         Starting alsa-restore.service - Save/Restore Sound Card State...
[  OK  ] Started anacron.service - Run anacron jobs.
         Starting avahi-daemon.service - Avahi mDNS/DNS-SD Stack...
[  OK  ] Started cron.service - Regular background program processing daemon.
         Starting dbus.service - D-Bus System Message Bus...
         Starting e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots...
         Starting lm-sensors.service - Initialize hardware monitoring sensors...
         Starting polkit.service - Authorization Manager...
         Starting rsyslog.service - System Logging Service...
         Starting smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon...
         Starting systemd-logind.service - User Login Management...
         Starting udisks2.service - Disk Manager...
[  OK  ] Finished alsa-restore.service - Save/Restore Sound Card State.
[  OK  ] Reached target sound.target - Sound Card.
[  OK  ] Started rsyslog.service - System Logging Service.
         Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
[  OK  ] Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
[  OK  ] Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
         Starting bluetooth.service - Bluetooth service...
         Starting networking.service - Raise network interfaces...
[  OK  ] Finished lm-sensors.service - Initialize hardware monitoring sensors.
[  OK  ] Started smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.
[  OK  ] Started dbus.service - D-Bus System Message Bus.
         Starting NetworkManager.service - Network Manager...
         Starting wpa_supplicant.service - WPA supplicant...
[  OK  ] Started systemd-logind.service - User Login Management.
[  OK  ] Started avahi-daemon.service - Avahi mDNS/DNS-SD Stack.
[  OK  ] Started bluetooth.service - Bluetooth service.
[  OK  ] Reached target bluetooth.target - Bluetooth Support.
[FAILED] Failed to start networking.service - Raise network interfaces.
See 'systemctl status networking.service' for details.
[  OK  ] Started polkit.service - Authorization Manager.
         Starting ModemManager.service - Modem Manager...
         Starting systemd-hostnamed.service - Hostname Service...
[  OK  ] Started systemd-hostnamed.service - Hostname Service.
[  OK  ] Started wpa_supplicant.service - WPA supplicant.
[  OK  ] Started udisks2.service - Disk Manager.
[  OK  ] Started NetworkManager.service - Network Manager.
[  OK  ] Reached target network.target - Network.
         Starting NetworkManager-wait-online.service - Network Manager Wait Online...
         Starting cups.service - CUPS Scheduler...
         Starting openvpn.service - OpenVPN service...
         Starting systemd-user-sessions.service - Permit User Sessions...
[  OK  ] Finished openvpn.service - OpenVPN service.
[  OK  ] Finished systemd-user-sessions.service - Permit User Sessions.
         Starting lightdm.service - Light Display Manager...
         Starting plymouth-quit-wait.service - Hold until boot process finishes up...

$ sudo systemctl status networking.service
 
× networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2025-06-23 23:30:40 EEST; 2h 22min ago
       Docs: man:interfaces(5)
    Process: 657 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
    Process: 731 ExecStopPost=/usr/bin/touch /run/network/restart-hotplug (code=exited, status=0/SUCCESS)
   Main PID: 657 (code=exited, status=1/FAILURE)
        CPU: 116ms

Jun 23 23:30:39 debian11 dhclient: than a configuration issue please read the section on submitting
Jun 23 23:30:39 debian11 dhclient: bugs on either our web page at www.isc.org or in the README file
Jun 23 23:30:39 debian11 dhclient: before submitting a bug.  These pages explain the proper
Jun 23 23:30:39 debian11 dhclient: process and the information we find helpful for debugging.
Jun 23 23:30:39 debian11 dhclient: 
Jun 23 23:30:39 debian11 dhclient: exiting.
Jun 23 23:30:40 debian11 ifup: ifup: failed to bring up eth0
Jun 23 23:30:40 debian11 systemd: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 23 23:30:40 debian11 systemd: networking.service: Failed with result 'exit-code'.
Jun 23 23:30:40 debian11 systemd: Failed to start networking.service - Raise network interfaces.

$ systemd-analyze blame
    10.964s ifupdown-pre.service
    10.561s e2scrub_reap.service
     8.615s dev-sda3.device
     7.678s systemd-journal-flush.service
     7.670s NetworkManager-wait-online.service
     7.138s udisks2.service
     5.499s polkit.service
     5.082s avahi-daemon.service
     5.056s systemd-logind.service
     5.036s dbus.service
     4.465s networking.service
     4.253s bluetooth.service
     3.208s ModemManager.service
     3.157s cups.service
     3.039s smartmontools.service
     2.742s NetworkManager.service
     1.956s dpkg-db-backup.service
     1.897s systemd-udevd.service
     1.820s exim4.service
     1.372s apparmor.service
     1.267s plymouth-start.service
     1.182s systemd-modules-load.service
     1.049s logrotate.service
    lines 1-23...skipping...
    10.964s ifupdown-pre.service
    10.561s e2scrub_reap.service
     8.615s dev-sda3.device
     7.678s systemd-journal-flush.service
     7.670s NetworkManager-wait-online.service
     7.138s udisks2.service
     5.499s polkit.service
     5.082s avahi-daemon.service
     5.056s systemd-logind.service
     5.036s dbus.service
     4.465s networking.service
     4.253s bluetooth.service
     3.208s ModemManager.service
     3.157s cups.service
     3.039s smartmontools.service
     2.742s NetworkManager.service
     1.956s dpkg-db-backup.service
     1.897s systemd-udevd.service
     1.820s exim4.service
     1.372s apparmor.service
     1.267s plymouth-start.service
     1.182s systemd-modules-load.service
     1.049s logrotate.service
      837ms lm-sensors.service
      796ms wpa_supplicant.service
      788ms systemd-udev-trigger.service
      786ms systemd-fsck@dev-disk-by\x2duuid-93c98828\x2d5fb8\x2d4c0e\x2db6bf\x2dde8d13a9d22e.service
      785ms systemd-tmpfiles-setup-dev.service
      729ms lightdm.service
      695ms plymouth-quit-wait.service
      642ms systemd-fsck@dev-disk-by\x2duuid-2F1D\x2d01E6.service
      619ms tftpd-hpa.service
      612ms systemd-random-seed.service
      608ms colord.service
      541ms rsyslog.service
      524ms systemd-backlight@backlight:intel_backlight.service
      508ms systemd-tmpfiles-setup.service
      442ms systemd-sysusers.service
      364ms inetd.service
      306ms user@1000.service
      305ms systemd-tmpfiles-clean.service
      272ms upower.service
      255ms systemd-journald.service
      252ms binfmt-support.service
      252ms systemd-sysctl.service
      250ms keyboard-setup.service
      229ms boot-efi.mount
      215ms systemd-remount-fs.service
      209ms exim4-base.service
...
    lines 52-80/80 (END)

$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @31.489s
└─multi-user.target @31.489s
  └─exim4.service @29.667s +1.820s
    └─network-online.target @29.631s
      └─NetworkManager-wait-online.service @21.959s +7.670s
        └─NetworkManager.service @19.187s +2.742s
          └─dbus.service @14.112s +5.036s
            └─basic.target @14.041s
              └─sockets.target @14.041s
                └─uuidd.socket @14.041s
                  └─sysinit.target @13.976s
                    └─apparmor.service @12.603s +1.372s
                      └─local-fs.target @12.581s
                        └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @12.737s
                          └─local-fs-pre.target @4.418s
                            └─systemd-tmpfiles-setup-dev.service @3.631s +785ms
                              └─systemd-sysusers.service @3.169s +442ms
                                └─systemd-remount-fs.service @2.929s +215ms
                                  └─systemd-journald.socket @2.872s
                                    └─-.mount @2.815s
lines 1-23...skipping...
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @31.489s
└─multi-user.target @31.489s
  └─exim4.service @29.667s +1.820s
    └─network-online.target @29.631s
      └─NetworkManager-wait-online.service @21.959s +7.670s
        └─NetworkManager.service @19.187s +2.742s
          └─dbus.service @14.112s +5.036s
            └─basic.target @14.041s
              └─sockets.target @14.041s
                └─uuidd.socket @14.041s
                  └─sysinit.target @13.976s
                    └─apparmor.service @12.603s +1.372s
                      └─local-fs.target @12.581s
                        └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @12.737s
                          └─local-fs-pre.target @4.418s
                            └─systemd-tmpfiles-setup-dev.service @3.631s +785ms
                              └─systemd-sysusers.service @3.169s +442ms
                                └─systemd-remount-fs.service @2.929s +215ms
                                  └─systemd-journald.socket @2.872s
                                    └─-.mount @2.815s
                                      └─-.slice @2.815s

$ sudo journalctl -b0 -u networking.service Jun 24 14:58:48 debian11 systemd: Starting networking.service - Raise network interfaces... Jun 24 14:58:52 debian11 dhclient: Internet Systems Consortium DHCP Client 4.4.3-P1 Jun 24 14:58:52 debian11 ifup: Internet Systems Consortium DHCP Client 4.4.3-P1 Jun 24 14:58:52 debian11 ifup: Copyright 2004-2022 Internet Systems Consortium. Jun 24 14:58:52 debian11 ifup: All rights reserved. Jun 24 14:58:52 debian11 ifup: For info, please visit https://www.isc.org/software/dhcp/ Jun 24 14:58:52 debian11 dhclient: Copyright 2004-2022 Internet Systems Consortium. Jun 24 14:58:52 debian11 dhclient: All rights reserved. Jun 24 14:58:52 debian11 dhclient: For info, please visit https://www.isc.org/software/dhcp/ Jun 24 14:58:52 debian11 dhclient: Jun 24 14:58:52 debian11 ifup: Cannot find device "eth0" Jun 24 14:58:52 debian11 dhclient: Failed to get interface index: No such device Jun 24 14:58:52 debian11 ifup: Failed to get interface index: No such device Jun 24 14:58:52 debian11 ifup: If you think you have received this message due to a bug rather Jun 24 14:58:52 debian11 ifup: than a configuration issue please read the section on submitting Jun 24 14:58:52 debian11 ifup: bugs on either our web page at www.isc.org or in the README file Jun 24 14:58:52 debian11 ifup: before submitting a bug. These pages explain the proper Jun 24 14:58:52 debian11 ifup: process and the information we find helpful for debugging. Jun 24 14:58:52 debian11 ifup: exiting. Jun 24 14:58:52 debian11 dhclient: Jun 24 14:58:52 debian11 dhclient: If you think you have received this message due to a bug rather Jun 24 14:58:52 debian11 dhclient: than a configuration issue please read the section on submitting Jun 24 14:58:52 debian11 dhclient: bugs on either our web page at www.isc.org or in the README file Jun 24 14:58:52 debian11 dhclient: before submitting a bug. These pages explain the proper Jun 24 14:58:52 debian11 dhclient: process and the information we find helpful for debugging. Jun 24 14:58:52 debian11 dhclient: Jun 24 14:58:52 debian11 dhclient: exiting. Jun 24 14:58:52 debian11 ifup: ifup: failed to bring up eth0 Jun 24 14:58:52 debian11 systemd: networking.service: Main process exited, code=exited, status=1/FAILURE Jun 24 14:58:52 debian11 systemd: networking.service: Failed with result 'exit-code'. Jun 24 14:58:52 debian11 systemd: Failed to start networking.service - Raise network interfaces. lines 3-31/31 (END) EDIT: /etc/network/interfaces.d folder contains 'setup' file with content auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Partial output of command systemctl show "run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount": Id=run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount Names="run-credentials-systemd\\x2dtmpfiles\\x2dsetup.service.mount" Graphic image of systemd .

How do we edit grub in a UEFI HDD to have multi boot option having more than just one linux one Windows OS, readily being selected and run at PC startup

I just installed fedora 30 on my laptop which has EFI. Before that, Windows was installed, and after the installation of fedora, the boot just disappeared. I am sure that fedora is installed correctly, since I see the bootloader of it (in the partitions section) when I try to reinstall it. Now there is just one message on the black screen saying: >Reboot and Select proper Boot device > Or Insert Boot Media in selected Boot device and press a key I tried to change the BIOS settings. But there is no boot option for fedora. How should I fix this? Update: I reinstalled fedora, and the problem was fixed. However, the question still remains. Was there a way to fix this without reinstallation?

I have a 2TB external SSD connected to a server. Using the server, I booted into the RHEL8 installer and successfully installed onto the external drive, however during the post-install reboot (and all reboot attempts after) the boot hangs at the switch-root step. Obviously the drive is recognized by the system and is able to provide the bootloader / initramfs, but dracut/systemd seems to just hit a hard stop when switching to /sysroot using the slash partition on the drive (non-llvm ext4 formatted). The interesting thing is several machines (laptops, desktops) will successfully boot from the drive into the OS, indicating the server chipset/usb bus is the cause. Unfortunately, I am stuck with the server (a Gigabyte... didn't realize they made more than boards) and the external drive (a Kanguru UltraLock SSD). Kanguru claims there are no drivers required for their drive, which makes sense. Also, I have not attempted to update/flash the UEFI on the server. I've avoided it for fear of making things worse. I did try adding a short delay in a pre-mount-hooked dracut script within the initramfs, thinking it might be a race condition of some sort, but it had no effect. That script also does an ls /dev/disk/by-uuid which shows the drives and partitions as they should be (i.e. the root=UUID:.. in the kernelopts matches the partition in the list). Anything obvious I'm missing? Update: I realized that I actually used a PXE kickstart to install the OS because I was unable to boot into the RHEL8 installer using my thumbdrive USB stick. Initially I thought the issue was my stick (old USB2 SanDisk), so I switched to my PXE server on my laptop. I just tested a theory now and was able to boot into System Rescue (CD) on that same USB stick that did not work with the RHEL8 installer. System Rescue CD uses the typical embedded busybox boot approach, which seems to point to a dracut issue in RHEL with regard to the server's hardware or USB connections? Thanks in advance!

I have a Linux image from which I've extracted a rootfs.img file. The file seems to contain files and information. I would like to "boot into it". File contents:

bin
dev
etc
home
lib
media
mnt
proc
run
sbin
service
sys
tmp
usr
var
lib64

How can I install a bootloader to boot it? I've tried getting a live Ubuntu image, adding a partition, and placing the contents of rootfs.img inside the partition and running "Boot Repair", which did find the other system as another bootable Linux, but I can't boot into it, it seems like I'm missing something

On the old YUMI tool for Legacy systems, there was a distribution option of "unlisted ISO" for using the iso rescue disk image from TrueCrypt. On YUMI 0.0.1.6 (UEFI), there is nothing like that in the drop down list of options. It's all just specific distros of linux, or specific tools like DBAN, Clonezilla, etc etc etc. There's no plain unlisted ISO option. What do I select in YUMI 0.0.1.6 to burn the ISO of a Veracrypt rescue disk?

I have **Windows 10 pro and Ubuntu 24.04** installed on **HDD and SSD** respectively in **same** HP laptop. When booting I am getting 2 GRUB menu. First a blue + white screen, and later the normal ubuntu grub once I choose ubuntu. The boot order is set correctly. When I checked boot entries. I saw boot entry, > Boot0000* ubuntu HD(1,GPT,770c5016-f173-4ce9-84d6-0e067d606859,0x800,0x219800)/File(\EFI\ubuntu\shimx64.efi) File(.䍒) notice the File(.䍒) here! I deleted the boot entry and re-installed grub. Now I got the ubuntu grub first itself next time. However, after few days the old issue re-appeared. Now, when I checked - the same "File(.䍒)" was again found at end of boot entry. How to fix this? Another thing I noticed is that, during bootup there is a flash message 'Press F9 to change boot order' shown automatically although I don't do anything.

I don't necessarily need it to be GRUB, I just want *a* bootloader. I've done a lot of troubleshooting already, but here's what I found. The last thing before the installer dies on me, it says:

mint grub-installer: error: Running 'grub-install --force --target x86_64-efi "/dev/sda"' failed.
mint rtkit-daemon: Supervising 11 threads of 8 processes of 1 users.
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:20: Warning: Source ID 6749 was not found when attempting to remove it.
    GLib.source_remove(self.timeout_id)
Unable to install GRUB in /dev/sda/
Executing 'grub-install /dev/sda' failed. This is a fatal error.

Now keep in mind, all three partitions of Linux are on sdb6, sdb5, and sdb7 (extended sdb3) respectively. At no point did I ever specify the system to touch sda whatsoever, so I don't know why it's trying to install GRUB or anything there. So I tried a couple of things. Mounting my EFI partition and attempting to chroot it yields this error:

chroot: failed to run command ‘/bin/bash’: No such file or directory

Initially, GRUB rescue gave me this back:

grub rescue> set prefix=(hd0,msdos8)/boot/grub
grub rescue> insmod normal
error: file '/boot/grub/i386-pc/normal.mod' not found.
grub rescue> normal
Unknown command 'normal'.

After performing cp -r on the directory from lib, it gives me a different, equally unhelpful error:

grub rescue> set boot=(hd0,msdos7)
grub rescue> set prefix=(hd0,msdos7)/boot/grub)
grub rescue> insmod normal
error: unknown filesystem.

A buddy of mine suggested to just unplug what is currently sda, and see what it tries to do then (since, again, I never asked it to install anything to that drive). No clue if it'll work or not, but I'm trying everything, and I appreciate any further ideas.