Comment 73 for bug 1396379
Revision history for this message
| Vlad Tudorache (tudorache-vlad) wrote | #73 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
70fb091
demo site
(Get the code!)
I've encountered this bug today (2022-05-20) on Debian 11 and Ubuntu 22.04. Configuration:
Samsung SSD 500 GB as /dev/sda
- EFI System Partition
- MSR
- NTFS (C:)
- Recovery
Toshiba HDD 2 TB as /dev/sdb
- 1,9 TB NTFS (D:)
- 512 MB (/dev/sdb2 -> /boot/efi)
- 2 GB swap (/dev/sdb3)
- 64 GB ext4 (/dev/sdb4 -> /)
It seems that even after selecting /dev/sdb2 as /boot/efi mount point to avoid tampering with the Windows boot loader's location, the installer mounts /dev/sda1 as the EFI partition. So the bug is still there and, for me, it happens also on Debian. This isn't a big problem for me, I've built the PC myself, I know how to use efibootmgr. What about a non-technical user?
Is it really a GRUB bug? Or it's an error of an early step of the installer which happens to be used also by the Ubuntu's installer (should they have some common parts)?