You are not logged in.
I have laptop with two disks. Windows OS was installed on the first disk, and i tried to install an Arch on the second( the second disk was bought and added after installing Windows on the first). But BIOS does not recognize the second disk as bootable.
I use GRUB for booting.
Looking for a solution, I came across this info https://wiki.archlinux.org/title/GRUB#G … not_loaded
This is the response I received.
> efibootmgr -v
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0001
Boot0000* Windows Boot Manager HD(2,GPT,ab......1-......-......-.....-b5f.......c,0xa.....,0x....)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)3400640034003700390035007d00000033000100000010000000040000007fff0400.......
dp: 04 01 2a ...
data: 57 49....
Boot0001 Windows Boot Manager HD(1,GPT,0......3-9....-.....-......-72.......1,0x8....,0x.....0)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)0000424f
dp: 04 01 2a 0.....
data: 00 00 ...
Boot0002* UEFI: ADATA USB Flash Drive 1100 PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/CDROM(1,0x194800,0x1e000)0000424f # Arch installer stick
dp: 02 01 0c 00 d.....
data: 00 00 42 4fBIOS displays two bootable Widows OS from the first disk as options too.
https://pasteboard.co/HCdL60AgUQuZ.jpg
> fdisk -l
Disk /dev/nvme1n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 980 500GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: gpt
Disk identifier: 93.....-....-....-....-10.......AB
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 2099199 2097152 1G EFI System
/dev/nvme1n1p2 2099200 976773119 974673920 464.8G Linux filesystem
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Micron_2450_MTFDKBA1T0TFK
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: 22......-C...-4...-8...-46........EB
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 718847 716800 350M Microsoft basic data
/dev/nvme0n1p2 718848 923647 204800 100M EFI System
/dev/nvme0n1p3 923648 956415 32768 16M Microsoft reserved
/dev/nvme0n1p4 956416 1978348951 1977392536 942.9G Microsoft basic data
/dev/nvme0n1p5 1978349568 1979435007 1085440 530M Windows recovery environment
/dev/nvme0n1p6 1979437056 2000408575 20971520 10G Microsoft basic data
Disk /dev/sda: 7.61 GiB, 8166703104 bytes, 15950592 sectors
Disk model: USB Flash Drive
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: dos
Disk identifier:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 1656831 1656768 809M 0 Empty
/dev/sda2 1656832 1687551 30720 15M ef EFI (FAT-12/16/32)So... What to do? o_0
Last edited by tupadown228 (2023-02-12 19:41:25)
Offline
The output suggests the Bios doesn't see the 2nd disk at all.
What does lsblk -f show from the arch install stick ?
Some (older) bioses can only boot from one harddisk (which one is booted from can usually be changed from within bios setup), what is brand & model of the laptop ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
First off, you're not booting BIOS, so stop saying that. UEFI relies on those NVRAM entries that efibootmgr shows, when you run grub-install, does it show up there? What command are you using, exactly?
Offline
What does lsblk -f show from the arch install stick ?
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/archiso/airootfs
sda iso9660 Joliet Extension ARCH_202302 2023-02-01-09-09-31-00
├─sda1 iso9660 Joliet Extension ARCH_202302 2023-02-01-09-09-31-00
└─sda2 vfat FAT16 ARCHISO_EFI ...8-....
nvme1n1
├─nvme1n1p1 vfat FAT32 4...-0... 898.9M 12% /mnt/boot
└─nvme1n1p2 crypto_LUKS 2 b.......d-....-....-b...-8.........5
└─cryptlvm LVM2_member LVM2 001 ey...-....-....-....-.....-....-....
└─encrypted-root ext4 1.0 6......b-4....-4....-.....-......... 431.1G 0% /mnt
nvme0n1
├─nvme0n1p1 vfat FAT32 EFI ....-....
├─nvme0n1p2 vfat FAT32 ....-....
├─nvme0n1p3
├─nvme0n1p4 ntfs 7..............8
├─nvme0n1p5 ntfs 5..............4
└─nvme0n1p6 ntfs DriverCD A..............6 Some (older) bioses can only boot from one harddisk (which one is booted from can usually be changed from within bios setup), what is brand & model of the laptop ?
MSI GF76 Katana 12UG... It'd be fun if it wasn't so sad T_T
Last edited by tupadown228 (2023-02-11 14:50:32)
Offline
First off, you're not booting BIOS, so stop saying that.
Okay, I'm sorry... T_T
UEFI relies on those NVRAM entries that efibootmgr shows, when you run grub-install, does it show up there?
> grub-install --target=x86_64-efi --bootloader-id=GRUB --efi-directory=/boot/efi --recheck
Installing for x86_64-efi platform.
Installation finished. No error reported.What command are you using, exactly?
Ooohhh... Okay, i will try to remember.
> pacman -S grub efibootmgr intel-ucode
then I added UUID_encrypted_thing to /etc/default/grub
then I edited /etc/mkinitcpio.conf (hooks, modules)
> mkinitcpio -P
> grub-install --target=x86_64-efi --bootloader-id=GRUB --efi-directory=/boot/efi --recheck
> grub-mkconfig -o /boot/grub/grub.cfg # I realize now what a mistake I have just made. > grub-mkconfig -o /boot/efi/EFI/GRUB/grub.cfg # I forgot to change dirpath... I'm so silly...
> efibootmgr -v # fresh output
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0003,0002,0000,0001
Boot0000* Windows Boot Manager HD(2,GPT, /File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)
Boot0001 Windows Boot Manager HD(1,GPT,0 /File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)
Boot0002* UEFI: ADATA USB Flash Drive 1100 PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/CDROM(1,0x194800,0x1e000)
Boot0003* GRUB HD(1,GPT, /File(\EFI\GRUB\grubx64.efi)I'm going to reboot right now. Wish me luck, plz.
Offline
Nope. Nothing changed...
https://pasteboard.co/PxHzajOQF1yv.jpg
https://pasteboard.co/LZoWukKQmjAV.jpg
Offline
So grub-install is adding the NVRAM entry correctly, but the motherboard isn't saving it. Bad firmware. Try using grub-install's --removable option, it will install to the default loader location and the firmware may let you choose that drive to boot. This may not work with two ESPs on the same disk, though, and you censoring of UUIDs means I don't know what's where.
Offline
Just FYI:
> grub-mkconfig -o /boot/grub/grub.cfg # I realize now what a mistake I have just made. [...] > grub-mkconfig -o /boot/efi/EFI/GRUB/grub.cfg # I forgot to change dirpath... I'm so silly...
The second command is incorrect. GRUB's configuration is expected to be under /boot/grub/.
Jin, Jîyan, Azadî
Offline
So... I solved the problem.
*after all necessary actions of official inst guide*
> grub-install --target=x86_64-efi --bootloader-id=GRUB --efi-directory=/boot --recheck # I changed /boot/efi to /boot . So... That was a problem.
> grub-mkconfig -o /boot/grub/grub.cfg P.S.
Unfortunately I did not understand how boot process works...
I'm sorry to have wasted your time. Thank you all.
Last edited by tupadown228 (2023-02-12 16:00:24)
Offline