search

linuxmint / mint20-beta

BETA Bug Squah Rush
20 stars 8 forks source link

ubiquity: Installer can't continue, can't abort when unable to install grub in previously selected place #33

Open rschr opened 4 years ago

rschr commented 4 years ago

I installed Mint 20 MATE on an Acer D270 netbook alongside 19.3 Xfce, which sits in its own btrfs subvolumes so that it doesn't interfere with new Mint installs.

To make sure not to overwrite the grub that was already on /dev/sda, I chose /dev/sda1 instead as the place to install grub when asked by the installer (the only drive, the only partition).

When the installation came near end, it complained it couldn't write grub to /dev/sda1, and showed me the choice again (/dev/sda, /dev/sda1) with the options to continue with a new choice or to abort the installation.

No matter what I selected, the continue button stayed disabled, and aborting didn't do anything, either. Nor could the window be closed by its close button.

(After forcing a reboot, I found grub.cfg was missing, but after creating it manually from outside and reconfiguring my existing grub the new Mint 20 installation booted alright and seems to be well.)

Martin-Laclaustra commented 4 years ago

I confirm that the same happens in the cinnamon version. In a 2 hard-drive system I chose /sda for grub and installed in a partition on the second drive /sdb2. At the end I received the same complaint. Tried to change the option to /sdb and nothing happened, choosing continue or cancel behave the same. The ok button did not produce any action. I forced shut-down and fixed grub with boot-repair leading to a successful installation.

simonwiles commented 4 years ago

I had the same problem using guided partitioning (and with lvm enabled, but I don't think that's relevant) -- "FATAL ERROR" installing grub, and then an unresponsive dialog that couldn't even be force-closed. After digging a bit, I realised that I was booting from the install USB media in legacy/MBR mode. Once I booted the machine in UEFI mode the installer worked as expected. Possibly one for the release notes?

pasch256 commented 4 years ago

reinstall with efi, solved the problem... even with virtualbox.