[Bug 1874066] Re: Cannot install on non-RST drive if RST is enabled and there is a second RST-enabled drive
Bruce Ide
1874066 at bugs.launchpad.net
Tue Jun 23 12:42:51 UTC 2020
Can I jump on this bug? My laptop's a MSI Titan. From the factory, they
RAID together two 500GB SSD drives with a windows 10 install. There's
also a 1TB 7200 RPM SATA disk which I'd installed Ubuntu 18.04 in the
past with no problems. I know that 20.04 will run on this machine and if
the installer would simply provide a way to continue the install despite
the fact that RST is detected on the machine, I could just install it.
Just make it a warning, possibly even a very strong warning, but provide
a way to continue anyway.
--
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/1874066
Title:
Cannot install on non-RST drive if RST is enabled and there is a
second RST-enabled drive
Status in OEM Priority Project:
New
Status in ubiquity package in Ubuntu:
New
Status in ubiquity source package in Focal:
New
Bug description:
Test Case:
1. On a machine with 2 disk 1 spinning disk and 1 nvme disk, enable RST
2. Start ubiquity and proceed zith the installation to the partitioning step
Expected result
Despite RST being enabled, user should be able to install on the non-RST disk
Actual result
Installation is blocked on the RST page and user cannot proceed without disabling RST
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.14
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 21 12:35:53 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1874066/+subscriptions
More information about the foundations-bugs
mailing list