Public bug reported:
I installed muthbuntu on a brand new WD Blue 3TB HD, but it could not
boot, saying something about faile to read/write hd0. I tried boot
repair, but no luck. So I tried re-installing with erasing the hd, but
received this error. A couple of wierd things, the HD was labeled as
sde, even though it was in the first port. and there was always a 1MB
free space partition that could not be used at the begining of the disk.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CasperVersion: 1.376
Date: Sun Aug 14 23:40:12 2016
InstallCmdLine: file=/cdrom/preseed/mythbuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mythbuntu ubiquity-2.21.63.2 xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613129
Title:
1st install would not boot. Crashed when trying to reinstall
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1613129/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
