** Tags removed: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901137
Title:
UEFI on Legacy - grub-install fails due to no space left on ESP
To manage notifications about this bug go
** Tags removed: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901137
Title:
UEFI on Legacy - grub-install fails due to no space left on ESP
To manage notifications about this bug go to:
Thank you for your email. I went back to reinstall 20.04.LTS without any
problem.
On Fri 11 Dec, 2020, 3:20 PM Plurtu, <1901...@bugs.launchpad.net> wrote:
> Even the most straight-forward option "Erase disk and install Ubuntu"
> failed for me on non-UEFI system when installing from USB. I
Even the most straight-forward option "Erase disk and install Ubuntu"
failed for me on non-UEFI system when installing from USB. I noticed
that 20.04 created a single bootable partition while 20.10 creates
additional BIOS Boot and EFI System partitions.
The Bug #1893964 Comment #8 workaround
I managed to run 20.10 after connecting to that installation from my
other running Ubuntu with chroot, installing net-tools (seemed to be
missing for some reason so I had no ifconfig) and then update + upgrade.
There was a kernel update and grub found what it needed to be able to
boot also 20.10.
My bug report #1902269 has been marked as duplicated of this one even if
the description it's not exactly the same.
In any case it looks the problem is related to the EFI (ESP) partition,
that should never be used on old BIOS or UEFI in Legacy Mode, but for
some reasons the installer want it...
I know there is not much happening here, but anyone managed to install?
Should I select the /dev/sda6 partition for installing the grub (or
whatever it installs) - it is the partition I keep another Ubuntu
version (besides Windows) or it will mess up booting the laptop? Until
now, on both Ubuntu
I just tried the workaround tested by @Matt, to add the toram option on
booting the USB drive, but in my case, it did not work. Maybe "toram"
did not work, don't know how to test thst, but in my installation of
20.10 Ubuntu, I got the same grub intall failure. If it matters, I did
not remove the
As additional confirmation that the installer was trying to write the
MBR to the install media, I was successful in installing 20.10 from the
same install media on the same hardware by booting the install media to
ram, as described here:
For me, it seems that the installer is ignoring my setting on where to
install MBR (on the Something else... partition screen of the
installer). I confirmed that the selected device both has an EFI
partition, and that the EFI Partition has space (more than 200 MB). I am
booting off external SD
** Tags removed: rls-hh-incoming
** Tags added: fr-873
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901137
Title:
UEFI on Legacy - grub-install fails due to no space left on ESP
To manage
** Changed in: ubiquity (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901137
Title:
UEFI on Legacy - grub-install fails due to no space left on ESP
To
I have 3 OS's (Windows and last 2 Ubuntu's) on my first laptop hard drive
(SDD). Every 6 months (for the last few years) I had these actions: keep
Windows 10 that came with the laptop, keep the previous Ubuntu and install the
latest formatting the partition with the ones 2 launches away. This
I have only the existing partitions ; since I wanted a fresh install and
therefore both the / and /home partitions were formatted.
I am not able to follow the "No space in ESP" since I never needed to know
about it.
I decided to test with another distro and I could succeed with no issues
(Fedora
Ubiquity tries to re-use ESP if possible.
Given that we booted in Bios mode, I wonder, if ubiquity missdetects the
ESP on the usb/cdrom that installer was booted from, as the one that can
be reused when it really can't.
Whilst looking through the logs, it is not obvious to me, if a sane ESP
15 matches
Mail list logo
