[Bug 1769404] Re: grub is installed to /dev/sda by default and fails
AtesComp
atescomp at gmail.com
Fri Mar 22 19:00:08 UTC 2019
Bin Li is incorrect. The boot order may not determine the allocation of
/dev/sdX for any number of hard drives. In general, IDE drives will
always be assigned first and SATA drives will be assigned second. If
you are booting from a SATA drive and have 2 IDE drives, you will always
get /dev/sda to the first IDE, /dev/sdb to the second IDE, and /dev/sdc
to the SATA drive NO MATTER HOW YOU SET THE BIOS BOOT ORDER.
Therefore, grub should have a hint, option, or other setting to point to
the "default" and not assume /dev/sda. A better way would be to use
UUID like in the fstab file since /dev/sdX assignment may not be
guaranteed.
** Changed in: ubiquity (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1769404
Title:
grub is installed to /dev/sda by default and fails
Status in ubiquity package in Ubuntu:
New
Bug description:
I choose to install Ubuntu 18.04 on /dev/sdb. I don't want to do
partitioning manually so I don't open advanced partitioning tool.
I expect grub to be installed on same disk. Because my /dev/sdb is SSD
and it is first in boot list in BIOS, and my /dev/sda is empty HDD and
I'm not going to install anything on it and going to use it as
storage.
But it seems grub-installer tries to install grub on /dev/sda by default. There are 2 cases:
1) If /dev/sda has no partition grub-installer fails. After the failure it suggests to choose another disk for grub. I choose /dev/sdb and it still fails.
2) If /dev/sda has any partition Ubuntu installation finishes
successfully. But it doesn't boot after installation. I see only black
screen with cursor blinking.
The workaround I found is to open advanced partitioning tool, change
grub installation disk to /dev/sdb, go back, and again choose Ubuntu
installation on /dev/sdb.
All logs attached here are from VirtualBox where I have reproduced the
issue with grub-installer failure. I've reproduced second case as well
but I'm not sure how to collect logs in this case.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sun May 6 00:21:57 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
LANGUAGE=en_US.UTF-8
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1769404/+subscriptions
More information about the foundations-bugs
mailing list