[EN] PC boots into BIOS

[hendrikL]

Did you decrypt via cli or from another method. I've been trying luksopen the running chroot-helper but get prompted drive is already in use. Might need to chroot manually

Well, I do not have an encrypted harddrive, so I can't test it
But I think you are right, you have to chroot manually, sorry folks.

[titan]

I see there have been two updates to grub since yesterday has anyone tried the latest version rc1-9

[sotnik]

I booted using super grub2
my booting disk specification is

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      2048   1023999   1021952   499M Windows recovery environment
/dev/nvme0n1p2   1024000   1228799    204800   100M EFI System
/dev/nvme0n1p3   1228800   1261567     32768    16M Microsoft reserved
/dev/nvme0n1p4   1261568 368642047 367380480 175,2G Microsoft basic data
/dev/nvme0n1p5 368642048 369256447    614400   300M EFI System
/dev/nvme0n1p6 369256448 493160447 123904000  59,1G Linux filesystem
/dev/nvme0n1p7 493160448 909664255 416503808 198,6G Linux filesystem
/dev/nvme0n1p8 909664256 976773119  67108864    32G Linux swap

Wich partition I have to use in grub-install ?

[towo]

If you are in your siduction system and since your system is using efi, a simple

Code: [Select]

grub-install
is needed.

[sotnik]

Whatever I have try does not work
For example

Code: [Select]

grub-install
Installing for i386-pc platform.
grub-install: error: install device isn't specified.

# grub-install /dev/nvme0n1
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.

[Teriarch]

@titan
The files will be overwritten by the new release and you have to repeat the quick and dirty fix.
Most of the time the problem can be resolved by a grub-install, but it depends
on the ability of the scripts to find the grubx64.efi loader. esp. on dual boot
systems different from a vanilla siduction install. Once successfully booted run a
"efibootmgr -v" command, i.g.:

BootCurrent: 0005
Timeout: 1 seconds
BootOrder: 0005,0001,0000,0009,000A,000B,000C,0002,0003,0004,0006
Boot0000* debian        HD(10,GPT,14336d57-7fb1-49b6-92ff-b4a20578619c,0xcfe058b0,0x32000)/File(\EFI\debian\grubx64.efi)
Boot0001* CD/DVD Drive  BBS(CDROM,,0x0)...
Boot0002* Hard Drive    BBS(HD,,0x0)...
Boot0003* UEFI:CD/DVD Drive     BBS(129,,0x0)
Boot0004* UEFI:Removable Device BBS(130,,0x0)
Boot0005* UEFI OS       HD(10,GPT,14336d57-7fb1-49b6-92ff-b4a20578619c,0xcfe058b0,0x32000)/File(\EFI\BOOT\BOOTX64.EFI)

I boot siduction with secure boot enabled (although I dropped the sec policies afterwards):

$ mokutil --sb-state
SecureBoot enabled

The replacement of  modified BOOTX64.EFI by the standard unsigned grubx64.efi would therefore have resulted
into a complete disaster.

Hence in your case find the recent grubx64.efi  bootloader with the above command and replace it manually
by the new one, if update-grub fails for some reason.

[towo]

@sotnik

what does

Code: [Select]

mount
say?

[Teriarch]

@sotnig:

> # grub-install /dev/nvme0n1
> Installing for i386-pc platform.

In your case grub-install is detecting your platform as legacy
and could not find space on the disk for the bootloader. Are you
sure you have uefi enabled in the BIOS?

[sotnik]

@towo

Code: [Select]

# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=32860892k,nr_inodes=8215223,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6577208k,mode=755,inode64)
/dev/nvme0n1p6 on / type ext4 (rw,noatime,discard,errors=remount-ro,commit=180)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14391)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
systemd-1 on /efi type autofs (rw,relatime,fd=57,pgrp=1,timeout=120,minproto=5,maxproto=5,direct,pipe_ino=27971)
/dev/sda1 on /mnt/ResearchData type ext4 (rw,noatime,errors=remount-ro,commit=180,x-gvfs-show)
/dev/nvme0n1p4 on /mnt/Data type ext4 (rw,noatime,errors=remount-ro,commit=180,x-gvfs-show)
/dev/sdb2 on /mnt/LData type ext4 (rw,noatime,errors=remount-ro,commit=180,x-gvfs-show)
/dev/sdb3 on /media/sotnik type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
none on /run/shm type tmpfs (rw,noatime,inode64)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576,inode64)
none on /var/log type tmpfs (rw,noatime,inode64)
/dev/nvme0n1p7 on /home type ext4 (rw,noatime,discard,errors=remount-ro,commit=180)
none on /var/tmp type tmpfs (rw,noatime,inode64)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=6577204k,nr_inodes=1644301,mode=700,uid=1000,gid=1004,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1004)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1004)

@Teriarch
I think it is legacy. I will  check and correct and I will let to you know what happens.

[Teriarch]

@sotnik
In the meantime you can also do a

$ sudo fdisk -l /dev/nvme0n1

and post the output to see whether you have
a GPT or DOS formated disk and ESP or BIOS partition.

[sotnik]

@Teriarch

It is gtp (I knew it )

# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 465,76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO 500GB               
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: 4F1DC3A8-0333-4A48-AC33-5C5E6DA5C3DF

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      2048   1023999   1021952   499M Windows recovery environment
/dev/nvme0n1p2   1024000   1228799    204800   100M EFI System
/dev/nvme0n1p3   1228800   1261567     32768    16M Microsoft reserved
/dev/nvme0n1p4   1261568 368642047 367380480 175,2G Microsoft basic data
/dev/nvme0n1p5 368642048 369256447    614400   300M EFI System
/dev/nvme0n1p6 369256448 493160447 123904000  59,1G Linux filesystem
/dev/nvme0n1p7 493160448 909664255 416503808 198,6G Linux filesystem
/dev/nvme0n1p8 909664256 976773119  67108864    32G Linux swap

I don't know why but it can not find efi dir

Code: [Select]

# grub-install
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.

same when i specify the partition

grub-install nvme0n1p5
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.

[towo]

You haven't mounted your efi partition as /boot/efi, that's why grub-install will fail!

[adix]

Saved my day, I had the same issue today   

grub-install from live-cd did the job

Thanks!!!

[sotnik]

@towo

I thought it is not needed. Any way I did it but the problem remains

[towo]

On an efi system, propper mounting of efi partition is indeed needed!
And since you have 2 efi partitions, you have to use the right efi partition!

And btw, if you want really help, you should exact explain, what you are doing.