Re: Upgrade to F30 gone wrong

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/7/19 8:15 PM, Chris Murphy wrote:
On Tue, May 7, 2019 at 12:40 AM Nicolas Mailhot
<nicolas.mailhot@xxxxxxxxxxx> wrote:



Le May 6, 2019 4:29:22 PM UTC, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> a écrit :
On Mon, May 6, 2019 at 1:52 AM Nicolas Mailhot
<nicolas.mailhot@xxxxxxxxxxx> wrote:

Le dimanche 05 mai 2019 à 16:14 -0600, Chris Murphy a écrit :

Right and that's the same with beta testing, which is how bugs like
this can sometimes not even get found until after release. A lot of
tests are done on pristine systems that are throw away. It's
entirely
understandable few people want to test Fedora pre-release on their
rock solid 5+ year old Fedora system, but we actually stumbled on
this
in some sense by luck of alternate arch acting like a canary.

That's not true, many boot problems are found quite early in the
process by rawhide users, but rawhide users feedback is not taken
into
account by installer folks because they don't look at boot problems
before quite late in the cycle, when rawhide users have already moved
on manually, and the default solution is always to reinstall from
scratch.

So problems are found, just not fixed

This is out of scope because the context of the conversation is
upgrades. You're talking about the installer which means clean
installs.

I'm talking rescuing systems that do not boot anymore and that means the install media. You can't rescue a system with broken boot from within this system

I have no idea what you're talking about. The context of this thread
is a bug that happens during upgrades, and you do not need
rescue/install media to fix it. The Common Bugs lists the step you
need to successfully boot and fix the problem within this system.


Nicolas' point is that the rescue boot entry only works in a limited number of scenarios.

And in some cases the rescue media IS needed to fix this particular issue as well. For example my box never got to the grub prompt at all, it was busy reboot-looping, probably due to negletting to reinstall grub in almost a decade. Others have pointed out other "completely broken" symptoms.

Really, if you don't even get a menu from grub, how many people are going to be able to work it from there? Even if there was another computer comfortably nearby for googling, I wouldn't bother even trying. Much easier to grab that rescue image, which thank goodness is there still.

	- Panu -
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux