Fedora Installation :: Preupgrade From 10 To 11 Worked / But Updates Don't Work
Jun 12, 2009
I have a small atom-based workstation.I used preupgrade to move from F10 to F11.The process seemed to go smoothly.I boot up and everything is working as I expect, except for yum update.
I was running preupgrade and while it was downloading packages the system was suspended and then shut off. When I brought it back up and tried to run preupgrade again it would not finish the download it just said 'Download complete. Reboot.' So I did bit nothing happened. I tried running it again but still nothing.
I then ran 'yum clean all' and then tried preupgrade again and then it tried to download again but once it goes to the download part it just says its done and says to reboot.
I did preupgrade and no i have no desktop icons and my right mouse button does not give menu on desktop and if i try to launch nautilus i get this error ->
corey@coreyhome:~$ nautilus (nautilus:20177): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. corey@coreyhome:~$
i noticed that my %gconf.xml in .gconf/gnome/desktop was zero bytes and since i replaced it now i get a picture on my desktop. before i did not get a picture.
my .xsession-errors has 1000+ of this handle_message(member:'NameOwnerChanged') handle_message(member:'NameOwnerChanged') handle_message(member:'NameOwnerChanged') handle_message(member:'NameOwnerChanged')
if i grep -v out these errors i get
(gnome-panel:4995): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.HalVolumeMonitor: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Yesterday upgrading from F13 to F14, preupgrade failed on VirtualBox repository (it was about 80%). I had to reset the machine, booting the old kernel, removing the repository and launching preupgrade again. It was successful, but I have A LOT (almost every package) of duplicates.
After different yum remove / package-cleanup --orphans / package-cleanup --cleandupes, it seems that everything is working fine. code...
After preupgrade downloads install media and reboots to start install, I get a dirty file systems error on /dev/sda2, my / partition.I fsck'd sda1,2,3,4,5,6 (all clean) and rebooted, ran preupgrade again and got same error. No other disks are mounted other than internal SSD.wtf is going on here? ;-)More importantly how does one get around this error? Only half-solution I have found on the net for this problem is to set allowDirty=1 in upgrade.py and recreate install.img. Have no preupgraded before so don't want to take any more risks than necessary.Thanks for any workarounds....---------- Post added at 03:12 PM ---------- Previous post was at 08:31 AM ----------Anyone have ideas here? I'd like to avoid yum upgrading as that looks to entail more pain.Why on earth does Anaconda see my /dev/sda2 on "/" as dirty when fsck reports it as clean
I have with the Videocard of one of my laptops. This laptop has a Mobility Radeon X600 card (RV380 based). I always had 3D hardware acceleration with mesa (at least in Fedora 12 and 13), but now it doesn't work. Boot seems normal, but reviewing the logs, I see this in the Xorg.0.log (after loading the radeon modues):
[Code]....
I don't have hardware acceleration, so no compositing and no gnome-shell I tried with both 7.9.1 and 7.9.2 versions of mesa-dri-driver (and its libs). The xorg-x11-drv-ati version is 6.13.1-0.3.20100705git37b348059.fc14
I'm not an early adopter; i prefer to wait and see, and let others suffer the new distro's teething troubles. Finally, I decided to try preupgrade. I was a little astonished to find that it doesn't install itself to any menu, but that's OK. I ran it as root, and went on with what I was doing while it got ready. Eventually it prompted me to reboot and I did.
I'd like to say that everything went fine, and in about an hour, I had a working system with no glitches. Alas, that would be a lie. Not only did it change all my customized system sounds (with no apparent way of getting back what I want; the new sounds aren't selectable.) it replaced my carefully-tweaked fstab with one of its own. This mean that several partitions that I don't want mounted were. Not only that, in some cases right-click and unmount got a message that the partition wasn't mounted, even though I could browse it. I had to open a terminal and manually unmount them, followed by copying back my fstab to keep this from happening again.
While doing this, I learned that the arrow keys on my keyboard don't work right, with the up arrow mapped to screen shot, and the Enter key by the number pad disabled. I'm still working around that one.
Worst was that Firefox wouldn't open. Trying it from a terminal, I learned that it couldn't start XCOM. Weird.
I tried a system update, but the livna issue popped up. By good luck, I knew enough to locate the appropriate file and disable it. Yumex has been spending over four hours, downloading and installing more updates than preupgrade did, by almost 100%.
failure: repodata/3a2a6da78e69f9b2608b1c399561b99073baa86b5454618459 ceecb79d58da09-filelists.sqlite.bz2 from preupgrade-updates: [Errno 256] No more mirrors to try.
I receive this error when I run try to run preupgrade to go from F12 to F13.
It's definitely not an issue with my internet connection, I'm running this from a college campus with a 150mbps connection.
I've tried running it 3 times now, and get this every time. It also gives me the error about not enough space on the boot partition, so I press continue there to move on.
it's possible to use preupgrade to go directly from FC8 to FC11.
Also, I'm wondering if this will allow me to avoid formatting my hard drive or not. I'll have backups ready just in case, but was hoping maybe I could get away with not having to do the old two-step shuffle with all my data.
I went to upgrade my daughters machine that was running F9 using preupgrade-cli after having issues with mirrors timing out it finally completed the first part with the notification install will start once you reboot. so I rebooted the machine and when it rebooted the grub menu came up with the F9 install selected but with an option for the F11 Upgrade I choose the upgrade and it starts and I see the installation screen with the stop watch and all of a sudden the comp restarts now at the grub menu again and there is no option for F11 upgrade so I boot into F9 try to run it again and it throws a bunch of errors about the rpm database... Encountering this before i run
rm -f /var/lib/rpm/__db* rpm -vv --rebuilddb yum clean all
but yum just blows errors now and if I run rpm -qa it returns nothing. Is there any recovering from this? or should I back up the home dirs and do a fresh install? this is the output of the rebuild
Code:
D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.2367 D: creating directory /var/lib/rpmrebuilddb.2367 D: opening old database with dbapi 3
I tried a pre-upgrade last night and after downloading 7GB of stuff over night, (don't ask me why it was that much) I rebooted.
Everything looked okay until I got an error message that said that /mnt/sysimage/... (I can't remember exactly what the error message was, sorry) what did not have enough space and needed 19MB more to install the upgrades.
Now, this system quad boots between Fedora, XP, Vista and 7 with grub being the intial boot loader giving me the option of Fedora or the Windows bootloader.
What I don't understand is why the installer (anaconda?) is having a fit about space when I have 8GB RAM and the system partitions are >10GB in size.
I upgraded to fedora 12 from fedora 11 with the preupgrade tool and all went very well at first try. But now I can't seem to get any sound from anything! I'm using KDE (for the past few years ) and my system in running on an ASUS Z91F.
I did have F11 on my laptop all running smoothly and everything which is good. But now I've updated from F11 using the preupgrade tool which for what I could see everything downloaded and installed ok, that was until the reboot after the install had completed after seemingly loading F12 it left me with a black screen with a blinking cursor so after a few more reboots with the same out come I decided to see what the loading was stopping at and this is what it came up with
Code:
Welcome to Fedora Press 'I' to enter interactive startup. Starting udev: [ OK ] Setting Hostname Fireline.Yuki: [ OK ] mdadm: No arrays found in config or automatically
[code]....
And it stops loading after "Starting atd: [ OK ]" I am going to try a CD install either tomorrow or the day after then I'll go back to F11 depending if it works or not.
I upgraded to Fedora 10 using preupgrade. It installed fine and everything loaded fine. Unfortunately the mouse would not work so I restarted my laptop. Now Fedora won't load at all the PC just turns on then keeps rebooting itself. I really want to avoid using the recovery disk. How to rectify?
I tried upgrade with dvd media and preupgrade from F12 but in both cases there is anaconda exception. I have dual boot windows xp (/dev/sda1) and F12 (/dev/sda2).
sudo fdisk -l /dev/sda: Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xa070b627
I know this has been covered a lot but it seems as though there should be a definitive answer and I have yet to find one.How much free space in /boot is required to make preupgrade work? I have 173M, which according to the figures I've seen should be enough, but the preupdate client still complains. Any workarounds? I have already tunefs'ed and deleted old kernels.
I have downloaded all packages and prepared to update my laptop (Lenovo 3000 N200, F10 x86_64) from F10 to F13 via preupgrade. Everything works fine, until I reboot and go into the upgrade process.
The problem is at the screen which configs NetworkManager. It shows only two interfaces, eth0 and wlan0, but I use a 3G dongle to connect to the internet. I tried feeding random values for the fields, but it does not allow to go beyond without configuring NetworkManager first.
can I work around the upgrade process without configuring NetworkManager? ie. can I do that manually after installing the upgrade?
today i've tried to PreUpgrade from f12 to f14. In the past i preferred always begin with a fresh install, removing abruptly the preivious one with a CLEAN FRESH installation. (I think it's the best procedure). However i wanted exeperiment with this soution giving it one, two, three N+1 chances. So this is my first up-grade (or "double" upgrade).
My system is CPU: INTEL P4 RAM 1024 MB Video: NVidia O.S. F12 Desktop: GNOME only (removed unused KDE app)
I'm trying to upgrade from Fedora 12 to Fedora 15 using preupgrade, but it seems to crash, I also tried going to Fedora 13 instead, but got similar errors. Here's the output to the command line. Let me know if there are logs anywhere that it would be helpful to provide. I replaced all the urls with "URL" to appease the forum's spam filters.
Code: [yashabk@localhost ~]$ sudo preupgrade Loaded plugins: blacklist, dellsysidplugin2, kernel-module, whiteout No plugin match for: rpm-warm-cache No plugin match for: remove-with-leaves No plugin match for: presto preupgrade-main (mirrorlist)
I was about to "preupgrade" (as I have, previously, used successfully) to F11 . While in terminal, I go to run preupgrade & I see the following:
/usr/lib/python2.5/site-packages/yum/__init__.py:181: UserWarning: Use .preconf instead of passing args to _getConfig warnings.warn('Use .preconf instead of passing args to _getConfig') Loaded plugins: blacklist, refresh-packagekit, whiteout
I have used Fedora since Fedora 5 or6, can't remember. Learning as I went, but I still don't know much. My electronic abacus has: Intel 865GBF motherboard, 2.0G of memory, P4 / 2.4Ghz processor, the on board Intel graphics, 73 GB available on HDD. Currently using Fedora 10.
I got the /boot is to small error when I tried the preupgrade from FC 11 to 12. I would like to clean out all the installation files and try again with the recommended fixes. Preupgrade just reboots the box no and restarts FC11 up so I need to start over fresh.
Where are all the files that I need to clean up for the preupgrade?
after preupgrade f12 >> f13 many *.fc12 packages remain installed. If I remove them and try to install again only the fc12 package is to be installed. Here some output:
[~]# uname -a Linux phobos 2.6.33.5-124.fc13.x86_64 #1 SMP Fri Jun 11 09:38:12 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux [~]# yum repolist Loaded plugins: aliases, auto-update-debuginfo, changelog, download-order, downloadonly, fastestmirror, filter-data, fs-snapshot, keys, langpacks, list-data, local, merge-
I'm trying to upgrade from F12 to F13 via preupgrade tool.The tool appears to be divided into 5 actions.
(1) Download release info (2) Download installer images (3) Determine wich packages to download (4) Download packages (5) Prepare and test upgrade
The tool has a tip too : "Tip: If you quit right now, your download will continue the next time you run this assistant." Well, after a long night, the tool runs until the almost finish of step 4. Then, the connection goes out, and i decided to continue in the following day. I just closed the tool and shutdown.
In the next day, i restarted preupgrade. But the application restarts from the very beginning of step 1.But, i think, the step 2 is very heavy. The file "install.img" is very very big. Re-download it is not desired.
I want to upgrade my F11 system to F13 using preupgrade-cli. Can I do that directly, or should I first upgrade to F12 and then to F13?
I have read elsewhere that Anaconda can skip one but not two versions, is that correct? If so, I assume that moving directly from F11 to F13 is OK, right?
I've run the preupgrade twice and both times I'm told that everything is perfect, all I have to do is reboot. When I reboot, nothing happens. Theory: I'm using Fedora with Ubuntu and GRUB2. I never allowed Fedora to install GRUB. I'm guessing that the preupgrade would normally alter GRUB so that I could continue the upgrade process. However, GRUB isn't there.
-> retrieve install image, ok -> examine storage (or similar), ok -> transfer install image to disk, ok -> dependency check in install packages, ok -> start installation process, ok -> preparing to install
=> there was an error running yout transaction for the following reason(s): insufficient diskspace
you need more space on the following filesystems: 1089 M on unfortunately not more information displayed. only exit possible. Any experiences with this kind of behaviour? Many thanks for any feedback.