Same problem, 20.04 on 2019 Mac Pro. And in this case, I *can't*
install GRUB on the internal drive at all, because the built-in NVME
disk is non-writable in Linux. So I had to go through a lengthy process
of mounting things and running grub manually with about a hundred-
character-long command.
I ran into this problem under Ubuntu 20.04 Beta on my 2008 MacPro while
attempting to have the boot loader installed on the same drive as the
linux installation rather than the drive with my macOS installation.
Using the Custom Partitioning option to install / on /dev/sde2 (ext4)
and the device for
Two years later, still a problem in 18.04 installer. I was trying to
install Ubuntu to a USB drive.
The graphical installer has a dropdown for "bootloader location", but it
does not work and instead installs to /dev/sda1.
--
You received this bug notification because you are a member of Ubuntu
B
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/704763
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I'm using UEFI. I've found that Rod Smith (of rodsbooks.com fame) has
written some typically detailed reports about this problem in bug
#1571354 and bug #1567534.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
It gets worse After trying all the suggested ways of restoring the
boot sector and failing, I used the live cd to re-install xenial, with
the other two internal drives I have, disconnected. Ubiquity on the lat
April testing version) - showed grub being installed, and update-grub
being run. BU
The release version of xenial trashed the boot sector on the target
disk. I've re-installed from the late April testing version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704763
Title:
boot loa
I installed Xubuntu 16.04 from a DVD to a new SDD. I ended up with a
system that had no bootloader. I have other disks with earlier Ubuntu
releases and thought "Erase and use entire disk" was the safest. I had
to re-install using manual partitioning.
--
You received this bug notification because
I installed Xubuntu 16.04 from a DVD to a new SDD. I ended up with a
system that had no bootloader. I have other disks with earlier Ubuntu
releases and thought "Erase and use entire disk" was the safest. I had
to re-install using manual partitioning.
--
You received this bug notification because
I think there are two different symptoms.
One is for legacy BIOS and the other is for UEFI BIOS.
Regarding UEFI BIOS, it may be caused by Bug #1512589.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704
Problem is still there in 16.04 LTS (pre-release).
In my case I have a laptop with one internal disk and I'm installing on
an external USB-attached disk (/dev/sda and /dev/sdc respectively).
The result makes no sense to me. If I boot the laptop without the
external disk, I end up at a Grub comman
** Attachment added: "Penultimate screen before installation. "3 partitions
will be deleted" it says, referring to /dev/sdc. No mention of /dev/sda."
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/704763/+attachment/4615733/+files/install.jpg
--
You received this bug notification be
** Attachment added: "Final warning screen, showing which partitions will be
changed. Again, no mention of /dev/sda."
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/704763/+attachment/4615734/+files/write.jpg
** Tags added: xenial
--
You received this bug notification because you a
You make a good point about the erase option, but we still want the side
by side option to stick with sda because you don't want people have to
figure out that they need to tell their bios to boot from the second
drive. Then again, I don't think the side by side option even lets you
pick the other
The problem with the installer at the moment is that it blindly tries to
install GRUB to the first disk in GRUB's device map, regardless of if it
can or not (apart from the special removable device code). This causes
problems when /dev/sda is a secondary disk that isn't configured at the
time of in
The problem is that the installer has no way of knowing that you intend
to remove the other disk from the system and manually boot them
separately. It assumes you just have two disks and want to be able to
choose which OS to load at boot time. At best it would need some kind
of prompt to ask whic
The attachment "ubiquity-grub.patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
~brian-mu
The attached patch fixes the issue, as it allows grub-installer to use
the boot device passed to grub_default() when no GRUB installation
device is explicitly set like in 'Erase disk and install'. As such, if
the target is /dev/sdb, GRUB will no longer try to be installed to
/dev/sda (assuming both
(Status change on behalf of dmakfan - 12.04)
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704763
Title:
boot loader not inst
Bug is still there in 12.04 LTS.
When doing an install from a USB stick, the installer defaults to
putting the boot stuf on the USB stick instead of the harddrive I am
installing the OS to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
11.10 will not have a point release with cd-images. Please verify this
bug with 12.10 daily and/or 12.04.1 images. There have been changes to
boot loader target device selection in 12.10. Then set the bug back to
confirmed if you can reproduce it there.
** Changed in: ubiquity (Ubuntu)
Stat
I can confirm this to be still present with 11.10 (didn't test it with 12.04
but will test with 12.10stable).
The bootloader of the primary disk is overwritten to start grub, which is
installed on the linux-HDD. This results in problems when the linux-disk gets
removed or formatted.
** Change
** Package changed: casper (Ubuntu) => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704763
Title:
boot loader not installed to target disk
To manage notifications about this bug
** Changed in: casper (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704763
Title:
boot loader not installed to target disk
To manage notifications about th
** Changed in: casper (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704763
Title:
boot loader not installed to target disk
To manage notifications about th
** Changed in: casper (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704763
Title:
boot loader not installed to target disk
To manage notifications about th
26 matches
Mail list logo
