[BUG]: grub config fails to be generated

[axtloss]

Describe the bug

for some people the grub config fails to be generated when installing through jade-gui

To reproduce the bug

just install crystal it seems

Expected behavior

the grub config gets generated and the user doesn't get sent to the shell

Screenshots

No response

Additional context

i suspect this may be an issue with the grub theme not being found, but im not sure why grub-mkconfig completely fails when doing this.

[ihatethefrench]

I've been doing some investigation, this might be an issue on BIOS systems specifically.

[axtloss]

All reports I've seen were on uefi systems

[chiq2045]

The same thing happened to me. When I tried to manually install and configure grub I got the error message
/usr/bin/grub/probe: error: cannot find a device for / (is /dev mounted?)

/dev is mounted, but I suspect that there is some problem with grub looking for /boot, when it should be looking for @/boot?

[axtloss]

how are you regenerating the grub config? and how did you mount the installation?

[fries1234]

hi, if you see an @ when you mount your drive, thats a btrfs subvolume. to mount the jade created btrfs subvolumes, you should run this command

sudo mount /dev/yourdriveletterhere -o subvol=@ /mnt
sudo mount /dev/yourdriveletterhere -o subvol=@home /mnt/home

[SomethingGeneric]

^ and then sudo mount /dev/yourdriveletterhere<p1> /mnt/boot/efi

[chiq2045]

@fries1234 I haven't tried your suggestion yet. It should have worked in my case, but I found that my issue stemmed from a broken grub config. So I went and completely deleted grub in order for the install to work. On a side note, I didn't know much about the btrfs filesystem - Thanks!

[wreedb]

So, I attempted install 3 times, once with options: no zramd and no autosnapshots. second time: zramd and no autosnapshots, and the third was with the default (both on) and that was the only one that generated a grub config it seems. the first two booted into efi shell

[ihatethefrench]

I'm going to try and troubleshoot this further today