Date: Sat, 21 Jan 2017 14:10:43 -0700 From: stan
<stanl-fedorauser@xxxxxxxxxxx> Subject: Re: Spectacular
F24 to F25 dnf Upgrade Failure To:
users@xxxxxxxxxxxxxxxxxxxxxxx Message-ID:
<20170121141043.3a363873@xxxxxxxxxxx> Content-Type:
text/plain; charset=UTF-8
What was the command you used to do the upgrade? Is there
anything unusual about your installation?
I used ‘dnf system-upgrade download --releasever=25’ follow by
‘dnf system-upgrade reboot’. Nothing terribly unusual. Typical
dual boot Win10 & Fedora on a 3 year old HP Envy 15t laptop
with two SSDs.
Does windows still boot properly?
Yes, Win10 still running fine.
You should open a bugzilla against dnf to document your
experiences and allow the potential to get this fixed for the
future. https://bugzilla.redhat.com/
Agreed. Unfortunately, I didn't save enough detail before
moving on. I will try to recreate and capture what I need.
Whew, that's a bad experience.
I'm not knowledgeable enough to help you, but there are some
experts on the list, so maybe they'll be able to help you
recover.
It is because of potential experiences like yours that I
always do my upgrades to new versions while leaving my old
version intact. You could just create the new partitions, and
rsync your old version to the new partitions before doing the
upgrade. Then, if disaster strikes, you have a fallback
position of a working system.
I usually use this laptop as my test machine. If it works here,
then I'll run it on my other Fedora machines. For my main
workstation, that's always done with a very cautious approach.
Maybe it's just me but I tend to have more issues with the odd
numbered releases. Call my superstitious.
Anyway, last night I did a full re-install over this mess with
a F25 net install USB image and that failed as well. With this
latest attempt I deleted and recreated all partitions except for
the shared efi partition. I used a basic ext4 partitioning
scheme (/boot; /boot/efi; /; swap). It seemed like the install
was going well but on reboot it failed. From the logs, it
appears the new grub config written by the installer is looking
for a device UUID that doesn't exist.
Maybe I should clear out the /boot/efi/EFI/fedora directory
before re-install?
This morning I ran one additional test. I did a fresh install
from a F25 XFCE Live USB. This was successful, but it leaves me
with a ton of reconfiguration and restoration work. Once I get
everything up and running again I will do some additional tests
with the F25 net installer to see if I can accurately document
what happened.
-Brian
![]()
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
I once remember a situation something like that happening to me way
back when the latest version was F19. I had to take a more drastic
approach, I completely backed up the entire system onto my external
2TB HDD, and blew away the drive completely with DBAN (D-arik's
B-oot A-nd N-uke) then tried a fresh install of F19 and it
WORKED!...I wouldn't suggest that now of course,...but I was tired
and I was angry so I went Ninja on it....LoL!