Unable to upgrade Fedora 16 to 17 on a multiboot system
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unable to upgrade Fedora 16 to 17 on a multiboot system
Hello Everyone!!
I have a multi-boot PC containing Windows 7, Fedora 16 and Kubuntu 12.04. The system starts up in Kubuntu grub.
Ever since the stable release of Fed17, I am trying to upgrade my Fed16 to it - I have tried preupgrade and I have tried upgrading from a DVD - nothing has worked for me.
"786 meg"? Where is that documentation? All I can find is
Quote:
Fedora 13 and above has a 500 MB default boot partition. The default /boot filesystem size of 200MB for previous releases can be a problem for users upgrading from that release.
and do a new clean install
using a custom layout
and a custom boot option
This is what I would do. After much trial and error, I've found that clean installs are really more of a mental block than anything else. It usually takes me LESS time to wipe the partition, install the new version from scratch, restore my backed up files, and set everything up how it was versus trying to do a live in-place upgrade and then fight through all of the problems that arise from it.
I recently did this when upgrading my laptop from OpenSUSE 12.1 to 12.2. I did some research, did the live upgrade, fought tooth and nail with the live upgrade until it finally went through (which took 3-4 hours in total), then spent the next WEEK fighting weird bugs here and there...random lockups, etc, before caving and installing 12.2 from scratch. Installing from scratch and getting everything set back up took two hours total. I should have just done that from the beginning.
Distribution: RH, FC 1-6, F 7-21, Debian, LinuxPPC, Knoppix, Ubuntu, Yellow Dog
Posts: 176
Rep:
If you use preupgrade, and the /boot partition is too small, preupgrade will complain saying that it does not have enough space (it will ask you to free up x amount of space). If space is low, you can safely delete all kernels, initrams, etc. except the latest one. I have a system with a 200 MB boot partition (started the system with F8; been upgrading with each new release ever since); I have managed to upgrade using preupgrade, DVD upgrade or netinstall with minimum problems (so far). Usually, upgrades using netinstall works best as you can get the latest version of the packages (sometimes, dependencies may fail; you may have to manually remove some of the old packages after reboot). At what point is your upgrade failing?
Hej, that's really the first post that says upgrading actually works. I'll give it one more try this weekend, else I'll override the system.
My preupgrade fails, as described, after the reboot. So preupgrade downloads all the stuff, installs itself into /boot and then restarts, showing a gray screen with some weird-looking window manager. It asks me to enter the key to my harddrive but then decides that it can't upgrade the existing system. As if it couldn't tell right from the start.
Maybe this also is a problem of a 32 vs. 64 bit architecture thingy?
Distribution: RH, FC 1-6, F 7-21, Debian, LinuxPPC, Knoppix, Ubuntu, Yellow Dog
Posts: 176
Rep:
Preupgrade should have downloaded the correct version (either 32-bit or 64-bit, depending on what is installed in your system); so, it may not be a problem with 32 vs- 64-bit (unless you tried the DVD upgrade option with the wrong version). Kernels for the new version are stored in the /boot partition, while the other packages are stored in the tmp directory. I am not sure I understand about the key - I have never been asked to enter a key during upgrades. However, periodically, a new GPG key is required before signed packages can be installed. The software should have asked you to accept the new key before reboot. Can you see the F16 kernels in the boot manager (in addition to the F17 preupgrade option)? You could also try netinstall (need to configure your internet connection during install). Good luck with the upgrade!
I've tried the DVDs as well (17 and 16), they don't say "version mismatch" but else the same problem.
About the key, it's not some gpg key of the repository, it's the key to the hard drive, my fedora is encrypted with luks (standard method provided by the fedora installer).
I'll give the netinstall a try.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.