[Bug 1883040] Re: groovy daily won't boot anymore on BIOS boxes
Ubuntu QA Website
1883040 at bugs.launchpad.net
Thu Jun 11 04:06:32 UTC 2020
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/1883040
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to syslinux in Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on BIOS boxes
Status in syslinux package in Ubuntu:
New
Bug description:
** Synopsis
I haven't been able to get ISOs to boot on older BIOS based boxes
since late Sunday (7-June). Examples are Ubuntu, Ubuntu-Studio,
Kubuntu, Xubuntu and since then Lubuntu too.
NOTE:
This `ubuntu-bug` report was filed on the only box that booted, and
didn't have an issue, so details of box are NOT the problem.
On boxes that have the issue boot stops at
"unable to find medium container a live file system
Attempt interactive netboot from a URL?"
** Background (timing)
On Sunday Morning 7-June I zsync'd the lubuntu daily & wrote to media
to continue testing of our updated LXQt (0.15.0) without issue (AEST
or my local Melbourne time)
That night I grabbed ubuntu-studio, ubuntu, xubuntu, kubuntu (& tried
to grab ubuntu-mate but it's not available yet) and was unable to get
these to boot I may not have tried all or in many combinations - just
gave them all up as problematic. I also deleted all entries I'd
started on iso.qa.ubuntu.com (assuming bad media)
Last night (Wednesday 10 June) I grabbed all again, wrote to media
again, and tried booting & failed. ISO was tried on four different
thumb-drives, using two boxes to write the media. It failed to boot on
multiple tried boxes (HP, DELL.. all BIOS). Also the Lubuntu was
updated (zsync) & written and it won't boot either anymore.
Most hardware I test on is old/BIOS boxes. Just now I re-tried a
thumb-drive on this newer UEFI and it boots here - ie. issue appears
to impact only BIOS boxes (c2d, c2q etc)
Note: I also have loads of issues with thumb-drive (worn out maybe?)
which is why I deleted my iso.qa.ubu entries, and didn't raise this
till today. 3 thumb-drives were purchased this year, 2 have never
given me issues.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: syslinux 3:6.04~git20190206.bf6db5b4+dfsg1-2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu38
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.449
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 11 03:31:57 2020
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1883040/+subscriptions
More information about the foundations-bugs
mailing list