Looks like nothing has finished yet and I got additional boot failure.The bios_grub flag is meant for a BIOS boot partition, which is unformatted space grub-install can write to the same as an MBR. Frankly, I wouldn't have expected you to be able to install UEFI Grub to a partition with that flag, but apparently the script has something to handle the scenario. As for the questions you asked. No, I've never switched the flags. I set them correctly in the first place.Have tried to switch over flags from 'bios-grub' to both 'boot' 'esp' . This turns off initial flag completely. Won't it disturb my booting table/order?As an aside, with full install USB drives I generally create both a BBP and an ESP, with appropriate flags for each. As for boot order, in UEFI that's a setting in NVRAM. The flags don't enter into it.
As an aside, with full install USB drives I generally create both a BBP and an ESP, with appropriate flags for each. As for boot order, in UEFI that's a setting in NVRAM. The flags don't enter into it.Today I booted up my PC only to find that GRUB has been disrupted some way and can't load installed Debian.
I've reverted back to the same routine to restore GRUB but got stuck at step # 3 during mounting /dev/sda1 as /boot/efi . Got this instead:
Code:
root@debian:/home/user# mount /dev/sda7 /mnt root@debian:/home/user# mount /dev/sda1 /mnt/boot/efi/ mount: /mnt/boot/efi/: mount point does not exist. dmesg(1) may have more information after failed mount system call.Anyway here is output:
Code:
root@debian:/home/user# dmesg | grep efi[ 0.000000] efi: EFI v2.3.1 by American Megatrends[ 0.000000] efi: ESRT=0xcbf7b918 ACPI=0xcb38c000 ACPI 2.0=0xcb38c000 SMBIOS=0xcbf7b518 MOKvar=0xcbd98000 INITRD=0xc4e99898 [ 0.000000] efi: Remove mem113: MMIO range=[0xf8000000-0xfbffffff] (64MB) from e820 map[ 0.000000] efi: Not removing mem114: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map[ 0.000000] efi: Not removing mem115: MMIO range=[0xfed00000-0xfed03fff] (16KB) from e820 map[ 0.000000] efi: Not removing mem116: MMIO range=[0xfed1c000-0xfed1ffff] (16KB) from e820 map[ 0.000000] efi: Not removing mem117: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map[ 0.000000] efi: Remove mem118: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map[ 0.012492] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns[ 0.172722] efivars: Registered efivars operations[ 0.721480] efifb: probing for efifb[ 0.721487] efifb: framebuffer at 0xe0000000, using 2400k, total 2400k[ 0.721488] efifb: mode is 800x600x32, linelength=4096, pages=1[ 0.721489] efifb: scrolling: redraw[ 0.721489] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0[ 1.208185] tsc: Refined TSC clocksource calibration: 3599.996 MHz[ 9.182787] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...[ 9.183908] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).[ 9.294980] pstore: Registered efi_pstore as persistent store backend[ 9.315783] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.[ 9.315978] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.To make it clear I fired up LiveDebian once again and run GParted to find out that /dev/sda has some 'exclamation mark' on it:
Code:
"Unable to read the contents of this file system!Because of this some operations may be unavailable.The cause might be a missing software package.The following list of software packages is required for fat32 file system support: dosfstools, mtools."Meanwhile my /dev/sda7 partition got stuck with /mnt. Fist I have to mount it back to / isn't it? I'm not sure how to perform that in wright manner from here.
How to boot up what I got installed so far?
Statistics: Posted by nikobit — 2025-02-18 05:50