Hello All,
I ran into problems when I tried to use Fedup to upgrade from Fedora 20 to 21, and although the cause of those problems was never clear, I suspected that having locally built and installed packages may have been part of the problem.
I have looked for advice on any preparation one should take on this (e.g remove/uninstall any locally built packages) prior to using Fedup, but never seen anything on the subject.
Does anyone have any knowledge/experience on this?

Cheers,
Terry

rual #1 with fedora
HOPE for the best
PLAN FOR THE WORST

you did make a back up ?

reformat and install 22 and copy over the data from the back up

with rpmfusion the main "extra" repo
that "? should ?" not be much of a issue ??? maybe ???


if the code you built from source is some of the system files - that WILL!!!!! caues problems

did you also use rpmbuild on them - THAT might have a big impact on fedora
--- i have NEVER had a fedora upgrade work out well
i have ALWAYS ended up reformatting and installing the NEW version

No system files, only applications, and built with rpmbuild.
I doubt that local builds that don't involve the package manager are ever going to be an issue as they are unknown to the package database.

Cheers,
Terry

Fedora upgrades have always been a bit hit-and-miss - they are getting better despite the constant protestations of @John VV.

I use a separate /home which allows me to simply do a clean re-install if the fedup goes pear shape. Of course I always have a backup first as well.
I think all my recent fedups have (eventually) worked - including a system where I have built kernels as a rpm package locally. Only problem is usually missing keys - google chrome, rpmfusion, fedora repository. Yep, even the target fedora itself. Go figger.

I did a lot of careful preparation, un-installed all my locally built and installed rpms, prepared 2 backups, each on different disks, of all my /home stuff, then followed the story of how to use fedup to get from 21 to 22, using network.
It all went exactly as they said it should, and the reboot provided a new boot option "system upgrade", which showed me progress as it did it's business, and finally it rebooted and this time gave me a boot option "twenty two"...and then it went well and truly pear shaped!
I end up with a message " Failed to start load kernel modules".
How on earth could it do everything without error, and leave me with a buggered system?
I can log in as root into a text only system, but blowed if I know what to do now.
Any advice would be appreciated.
P.S I have managed to boot into Fedora 20, on another disk...and this is S-L-O-W...an iron disk. My system disk is now an SSD, if I could only boot into it!

Cheers,
Terry

Fedora 22 boots into 'emergency mode', which leaves me a bit out of my depth as to what to do.
I have run 'journalctl -xb' and perused the output and I find (highlighted in red) "failed to find module 'vboxguest' ", also modules " vboxsf" and vboxvideo", so I'm guessing this may the problem.
Clearly my fault for overlooking the fact that I had VirtualBox installed, but I don't recall fedup calling foul on this before actually running the upgrade.
So, the big question, is there a way to extricate myself from this, after booting into emergency mode?

Cheers,
Terry

Anything in /etc/modules-load.d/ ?

Nothing in /etc/modules-load.d/

Cheers,
Terry

Emergency mode probably means initramfs. Sooo - if it was me I'd just check I was on the F22 kernel (uname -r), then rebuild the initramfs (dracut -f) then reboot. If it didn't fix it, I wouldn't waste any more time on it, and just do a full (clean) install of F22.

The dracut manpage has plenty of good info for your situation - including a sosreport file that will be created in your case.

OK, uname -r reports '4.0.6-300.fc22.x86_64', so that looks OK.
'dracut -f' silently went about its business, and no sign of an sosreport file.
A reboot puts me back in exactly the same situation...so not good.
I'll now set about a clean install, which is a real bugger.
The ability to upgrade, instead of having to do a clean install, really should be foolproof, but perhaps that's asking too much :-)

Thanks for your help.

Cheers,
Terry

I ran Fedup from 21 to version 22. I had external repositories for codecs, adobe, etc. And I ran it without reading he manual.

It ran for almost 8 hours (I put it on before retiring for the night), and in the AM, when I rebooted, I had a perfect Fedora22 system. That Fedora22 system included all updates and some for the non Fedora (external) repositories.

If you experienced problems with Fedora, I would attribute it to Nvidia graphics card drivers. These are very very kernel version specific.

I have actually, since Fedora22 was released, switched over to Chapeau Linux (www.chapeaulinux.org) or Distrowatch.

Chapeau Linux came with all of the items that I wanted to have included in a Fedora release. Chapeau Linux just worked after the reboot.

There were two warning messages which I was advised to ignore. One was for Dropbox updates and the other for Pharlap updates. I disabled the two repositories by changing the line enable=1 to enable=0. I have 4 versions of Chapeau Linux wrapping itself around Fedora22. Chapeau Linux is a superset of Fedora22. And yes, Fedup worked to bring Chapeau Linux 21 to Chapeau Linux 22.

One version -- a 1 gig memory netbook (atom processors)
One version a 4 gig memory Samsung laptop (I3 processor)
Two versions on 8 gig desktop -- one that boots from a 1 terabyte drive, the other from a 120 gig SSD.

Because Chapeau Linux is clean, clean, clean, the only updates I am receiving are for LibreOffice, Adobe, Firefox and the Gnome stuff.

I doubt that...I wasn't using a proprietary graphics driver, just the Fedora supplied driver.

Cheers,
Terry

No vulnerability fixes (think ssl, ssh), no kernel updates, no nuthin' ... ?.
Doesn't sound like a Fedora spin I would want to play in.