Sat 2 Jun 2007
Now that Fedora 7 has been release it is time to upgrade from that crusty old Fedora Core 6. Note that they have removed the "Core" from the name so a few things have changed with the paths used in yum. Last year I did a post on how to upgrade from FC5 to FC6 and this upgrade happened on the first box I used for that.
- Before you start see the note after these steps about checking for disk labels
- yum update
- yum clean all
- I repeated update and clean all a second time to make sure everything got updated
- I then ran the command:
rpm -Uhv http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/Fedora/fedora-release-7-3.noarch.rpm http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/Fedora/fedora-release-notes-7.0.0-1.noarch.rpm
- I then found that I had to move fedora-development.repo and fedora-updates.repo out of /etc/yum.repos.d/ and replace them with fedora-development.repo.rpmnew and fedora-updates.repo.rpmnew. I also needed to remove a custom repo I had but no longer used so I didn't take time to figure out why it needed to be removed.
- I then did a yum -y update and waited
- After a good wait another X server was started so you may think about not doing the update while running under X. Luckily it was able to start on another console so all was ok. Now it was time for a reboot.
- After the reboot I had to fix up some NVidia issues but overall it looks like it upgraded without a problem
Notes on disk labels:
There are a few things listed in the release notes under Upgrade Related Issues.
The first was to make sure all your drives have labels. You can do this by running the command "/sbin/blkid" and then checking that each line that is not part of the LVM system has a LABEL entry. If you need to add a label to a drive use the "/sbin/e2label" command and then edit your /etc/fstab to use the label on boot instead of the device.
You don't need to label LVM drives since the LVM keeps track of the drives it uses on its own. The only drive I had on a stock install that wasn't under the LVM was /boot and it had a label already.
After you upgrade they sugest running the following command and then upgrading anything that has a date before the upgrade date:
June 2nd, 2007 at 9:59 pm
[...] Despite the previous warning someone has successfully migrated from Fedora Core 6 to Fedora 7 via Yum [...]
June 3rd, 2007 at 9:07 am
Hi Carson
I'm fairly new to the Fedora OS and all it's commands. If you could email me the whole process and commands so I can do the yum upgrade from Fedora Core 6 to Fedora 7 I would greatly appreciate it.
Thanks
Alan
June 7th, 2007 at 12:51 pm
@alan
he just did, read the article and you'll find everything you need in order to upgrade from one to the other.
I didn't need them, cause I'd already done it, but it was nice to see someone else who did it and had 0 problems, well, depending on whether you see a 2 hour download as a problem or not
chris
June 7th, 2007 at 2:31 pm
This is a great post for users new to Fedora & Yum. I used the instructions on this site to upgrade from FC5 to FC6. Thanks for taking the time.
June 7th, 2007 at 11:19 pm
Carson,
Thank you so much for this useful information. I successfully upgraded two servers from FC6 to FC7 via yum. I followed all the steps but have to manually upgrade python, yum, rpm and ncurses packages before I executed 'yum -y update'. After that everything was just perfect. I still have to test the rest though but I think no problems will occur.
Thanks again man…
June 8th, 2007 at 1:57 pm
Thanks for the time you spend to write this help page.
cheers
June 10th, 2007 at 4:38 am
Do you know if it's possible to upgrade directly from FC5 to 7 with yum? Or two upgrades 5->6->7 are required?
June 10th, 2007 at 4:57 am
Also, what to do with swap partition, if it's not in LVM? Mount it by UUID?
June 10th, 2007 at 6:06 am
Ok, solved swap problem:
swapoff -a
mkswap -L SWAP /dev/
swapon -a
Then swap partition can also be mounted in /etc/fstab by
LABEL=SWAP
June 10th, 2007 at 1:25 pm
how about /dev/mdX? how to label them?
June 10th, 2007 at 4:24 pm
for ext2/ext3: e2label /dev/mdX LABEL
for reiserfs (partition must be unmounted): reiserfstune -L LABEL /dev/mdX
for swap: mkswap -L SWAP /dev/mdX
June 11th, 2007 at 2:53 pm
Your post is fabulous!
I have one question though: where do we find the file data for "fedora-development.repo.rpmnew" and "fedora-updates.repo.rpmnew" ?
Thanks.
June 11th, 2007 at 8:47 pm
I upgraded successfully from FC6 to FC7. I do have the following issues.
1) Nvidia driver loads up but Beryl doesn't. It says "Root window size (2560/1024) is bigger then maximum texture size (2048×2048)". It was working before the upgrade.
2) There still are some *.fc6 packages (some 200 of them) and when I tried to batch remove them, many fc7 are also getting removed due to dependency issues. I didnt go thru with it but I would like a machine with just fc7 packages instead of a hybrid :[
thanks for the post !
Saro
June 11th, 2007 at 9:32 pm
Saro,
I have been getting that same Beryl error for months now. I assume you have dual screens? I upgraded Beryl some time ago and it started producing that error. I found a thread at some point saying they had opened a bug to fix it because it was something they had hard coded since they figured nobody would have a screen that large. I haven't gone back to Beryl since then but it seems like something they would get fixed soon.
June 12th, 2007 at 3:45 pm
I have successfully upgrade but I can't boot from Fedora7. However, I can boot from fedora core 6 which is selected from boot menu list.
I paste the related information:
==========================================
# /sbin/blkid
/dev/mapper/VolGroup00-LogVol01: TYPE="swap"
/dev/mapper/VolGroup00-LogVol00: UUID="828418eb-aa98-4848-887d-b7bbcea8ebde" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdb1: TYPE="ntfs"
/dev/hdb5: TYPE="ntfs"
/dev/hdb6: LABEL="D DISK" UUID="2C5C-1D93" TYPE="vfat"
/dev/hdd1: LABEL="/boot" UUID="c500cfbc-4a8d-4520-be26-1f4c180e4188" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdd2: TYPE="swap"
/dev/VolGroup00/LogVol01: TYPE="swap"
/dev/VolGroup00/LogVol00: UUID="828418eb-aa98-4848-887d-b7bbcea8ebde" SEC_TYPE="ext2" TYPE="ext3"
############################################
# cat /etc/fstab
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
===============================================
# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hdb
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.21-1.3194.fc7)
root (hd1,0)
kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.21-1.3194.fc7.img
title Fedora Core (2.6.20-1.2952.fc6)
root (hd1,0)
kernel /vmlinuz-2.6.20-1.2952.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.20-1.2952.fc6.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1
===========================================
I can boot from fc6 but not fedora 7. of course I can boot windows XP.
Looking forward to hearing from you
Thanks in advance!
June 12th, 2007 at 7:07 pm
Yep, you guessed right. I do have dual monitor
June 14th, 2007 at 8:01 am
great job indeed!
i'm attempting to upgrade a "dedibox" dedicated distant server from FC5 to FC 6 (using your previous howto: worked perfectly!)
and now from FC6 to F7.
The server is minimalistic: no apps, no X server, no desktop, remote ssh access by putty, just scratch from the box… -> I shouldn't have any exotic driver problem.
I have successfully labeled my drives using lim's tip, installed the new repo.rpm (why x86_64!!?) and launched yum update.
boiled for a while and got :
——————————————--
--> Processing Dependency: mkinitrd >= 6.0.9-7.1 for package: kernel
--> Finished Dependency Resolution
Error: Missing Dependency: mkinitrd >= 6.0.9-7.1 is needed by package kernel
——————————————--
op aborted…
trying and trying I found that mkinitrd-6.0.9-7.1.i386.rpm needs nash-6.0.9-7.1.i386.rpm
(old nash rough uninstall removes FC5 & FC6 kernel…)
I tried rpm -U but
——————————————--
# rpm -U mkinitrd-6.0.9-7.1.i386.rpm
erreur: Dépendances requises:
nash = 6.0.9-7.1 est nécessaire pour mkinitrd-6.0.9-7.1.i386
# rpm -U nash-6.0.9-7.1.i386.rpm
erreur: Dépendances requises:
nash = 6.0.9-5 est nécessaire pour (déja installé) mkinitrd-6.0.9-5.i386
——————————————--
any idea ?
June 14th, 2007 at 8:20 am
EDIT
checking the F7 release mirrors (http://mirror.anl.gov/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/)
it appears that F7 comes with mkinitrd & nash 6.0.9.5…
alors?
why the *** am i requested to provide >= 6.0.9-7.1 ?
I'm going to try out changing …x86_64/os/Fedora/fedora-release-7-3.noarch.rpm and so on for …i386/os/Fedora/fedora-release-7-3.noarch.rpm and so on
coming next
ps: apologies for my broken english…
June 14th, 2007 at 11:00 am
Thanks for posting these instructions. Everything was going smoothly until the "yum -y update" step.
--> Processing Dependency: mkinitrd >= 6.0.9-7.1 for package: kernel
--> Finished Dependency Resolution
Error: Missing Dependency: mkinitrd >= 6.0.9-7.1 is needed by package kernel
The latest mkinitrd in the yum repository is
6.0.9-5, which I have. It looks like the 6.0.9-7.1 is still being tested and was submitted two days ago: http://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=39098&forum=12
How can I get around this problem easily ?
June 14th, 2007 at 11:15 am
I found out from this thread that this is a new bug introduced in yum FC7: http://marc.info/?l=fedora-list&m=118183340219277&w=2
Until it is fixed you can update mkinitrd by:
"yum install mkinitrd --enablerepo=updates-testing"
and then do follow with the
"yum -y update"
June 15th, 2007 at 3:44 am
thanks a lot for your reactivity mike and for the job you do
i'll give it a try and feed back soon
marc
June 15th, 2007 at 8:36 pm
Hi Carson
Below is the terminal output when I run ym update on my FC6 machine:
--> Populating transaction set with selected packages. Please wait.
—> Package libpurple.i386 0:2.0.1-1.fc6 set to be updated
—> Package busybox.i386 1:1.2.0-4 set to be updated
--> Running transaction check
--> Processing Dependency: faad2 Processing Dependency: libmeanwhile.so.1 for package: libpurple
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
—> Package meanwhile.i386 0:1.0.2-3.fc6 set to be updated
--> Running transaction check
--> Processing Dependency: faad2 Finished Dependency Resolution
--> Populating transaction set with selected packages. Please wait.
—> Package kernel.i686 0:2.6.18-1.2798.fc6 set to be erased
—> Package kernel-devel.i686 0:2.6.18-1.2798.fc6 set to be erased
--> Running transaction check
--> Processing Dependency: faad2 Finished Dependency Resolution
Error: Missing Dependency: faad2
June 15th, 2007 at 8:38 pm
I guess my previous post was too long to fit everything in.
My question is how to get around this missing dependency problem in this particular case and also in general because I am sure after resolving this one there will be more !!!
June 16th, 2007 at 11:24 am
Did a upgrade from FC6 to F7, worked more or less without problems (x86_64).
Some notes:
- to get rid of the .fc6 packages, i did a package-cleanup --orphans | grep -v 'Setting up' | (more grep -v for packages still needed) | rpm -e. Worked fine so far, and according to the release note some FC6 packages haven't been name-changed because nothing else was updated.
- Got ugly java errors again, referring to ld-linux-x86-64.so.2+0×91bd (offset may vary). If that happens, running /etc/cron.daily/prelink helps.
Thanks for this post!
June 18th, 2007 at 4:06 am
retried everything using
"yum install mkinitrd --enablerepo=updates-testing"
before
yum update
… worked perfectly !
uname -a says
Linux xxxxxxx 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 i686 i386 GNU/Linux
great job Mike and thanks for your help
see you for next upgrade !
June 20th, 2007 at 3:37 pm
Hi carson,
I fixed the nvidia "Root window size (2560/1024) is bigger then maximum texture size (2048×2048)" problem.
I had to remove the nvidia drivers and install nvidia-96xx drivers which support AIGLX
Now Beryl is working fine and I am a happy man
Saro
June 21st, 2007 at 2:50 pm
Sure wish I would have seen this about 5 minutes ago!
I am in the middle of a DVD upgrade (aka precurser to fresh a install) from FC6 to F7.
Pray for me.
June 24th, 2007 at 12:09 pm
Error: Unable to satisfy dependencies
Error: Package mkinitrd needs nash = 5.1.19.0.3-1, this is not available.
Error: Package mkinitrd needs libparted-1.8.so.2, this is not available.
Any clues?
June 24th, 2007 at 9:51 pm
Hi Carson --
After wading through a whole river of crap trying to install F7 from DVD, net, etc., I went back to FC6 until I found your instructions and subsequent addendums from everyone else tonight. I'm now in the middle of an upgrade…
And Terry, I pray that you got through your DVD upgrade - if not, we can weep together…
Mick
June 25th, 2007 at 1:57 pm
Thanks for the guide - worked fine, apart from one problem:
I get the following error while trying to boot the F7 kernel (the old FC6 kernel works fine):
/bin/nash: error while loading shared libraries: libm.so.6: cannot open object file: No such file or directory
(pic: http://img236.imageshack.us/img236/2651/panicre5.jpg )
libm.so.6 exists, as shown here:
Any ideas?
June 30th, 2007 at 3:55 am
Have you checked that libm is still in your path statement? that one is usually caused by a missing path in you env.
July 3rd, 2007 at 10:25 am
Keep an eye out for Clamav bugs. You currently can't use the version on Crash-hat with fc7, because fc7 removes libcurl.so.3. Default clamav-0.90-2 from fedora does work.
July 4th, 2007 at 7:25 am
i've problems with a python dependences…
July 4th, 2007 at 7:26 am
retried everything using
"yum install mkinitrd --enablerepo=updates-testing"
before
yum update
July 5th, 2007 at 9:35 pm
well I just upgraded with pretty much no problem at all, on a vanilla Dell desktop (i386). Everything seems to be running fine so far.
Had to yum remove 4suite kdemultimedia rhnlib and clamav to get 'yum -y update' to do its stuff. I never use them anyway and had no idea they were installed.
Also I got a bit confused with instruction (6) as there were no rpmnew files in my yum.repos.d after updating fedora-release, and in fact the fedora-release update didn't change my repo files at all. I first moved them out of yum.repos.d and then realized they were okay and moved them back in. ymmv.
July 6th, 2007 at 2:39 am
for help~thanks
hello, I also have a problem like Dennis'(http://www.ioncannon.net/linux/68/upgrading-from-fc6-to-fedora7-with-yum/#comment-20752)
after I update from FC5—>FC6—>FC7, I can boot from FC5 the menu list.but can't from FC7
To be worse, I miss to delete the files about FC5, so now, I can boot to the system.
What can I do next?
thanks a lot to note this help!
July 12th, 2007 at 2:18 am
I Just want thank you for guide it work great update to fc6 to 7 no issues at all
July 12th, 2007 at 8:49 am
Hello,
I have tried to upgrade my FC6 to version 7.
… but I can not upgrade because of missing dependency.
…
--> Finished Dependency Resolution
Error: Missing Dependency: libgcj = 4.1.2-12 is needed by package libgcj-src
From other side:
# rpm -q libgcj
libgcj-4.1.2-13.fc6
This means that FC6 has a newer package then Fedora 7.
What should I do in order to make the upgrade as smooth as possible?
Thank you in advance
Regards,
Z
July 13th, 2007 at 4:06 am
(continue)
… I have solved the problem above with downloading and installing libgcj-src-4.1.2-13.fc6. That allowed me to contimue tha upgrade.
There were still some problems with conflicting files, but removing older files solved that issue as well.
Also on yet another box there was also problem with libgcj… but this tme with shareble object version. I got a missing dependency for libgcj.so.8rh that does not even exist yet in i386 architecture (just in x86_64) - well, I erased some 5-6 -java packages that was dependent on that and the upgrade continued.
It is strange that it worked for you all smooth…
To be honest I have used redhat and later fedora distibutions since 1995 and I could not make a smooth upgrade - not even once.
Regards,
Z
July 14th, 2007 at 5:01 pm
… and one last note.
From two boxes that I have upgraded one booted up OK (except that the F7 kernel changed hda device to sda for some reason)… but another box fails with F7 kernel with kernel panic (can not find /dev/root ???)
With old FC6 kernel it boots OK.
Any ideas?
Regards,
Z
July 16th, 2007 at 8:54 am
I have found that with the change in the naming of Hard disks in F7 there are a few other issues, such as you can't boot a system that only has SATA Hard disks without a kernel panic… Otherwise, I would have upgraded my little box 3 weeks ago!
Great guide though!
July 20th, 2007 at 10:33 pm
Are you sure the initial rpm -Uvh links are correct? As far as I understand EC2 does not support 64-bit images. Someone will get thrown off by that.
July 20th, 2007 at 10:34 pm
Never mind. I guess this is about a simple, non-EC2 specific upgrade. My bad!
July 23rd, 2007 at 3:49 am
What if we have a system under Reiserfs and wish to upgrade from FC6 to F7 through yum. There are no appropriate tool to label reiserfs partition when it's mounter. The problem is only with the ATA disks. Extract from FC site "Use of /dev/hdX is deprecated on i386 and and x86_64 for IDE drives, and has changed to /dev/sdX except on PPC".See note about the importance of labeling devices for upgrades from FC6. Nothing was provided to tackle with partition Reiserfs
July 23rd, 2007 at 4:06 pm
Already anyone with a successful FC5 -> F7 upgrade without going via FC6? Or should I go via FC6
July 23rd, 2007 at 4:32 pm
Nearly flawless! I had two problems which I'll note here in case anybody else encounters them:
1. When I ran "yum -y update" it was upset about dependencies relating to libgcj and libFLAC. Couldn't quickly figure out why but resolved this by manually downloading the proper FC7 packages and installing them with "rpm -U --nodeps --force". After this I was able to run the yum command successfully.
2. After the reboot, I had NVidia issues as well, quite possibly the same as carson's. My steps to resolve this were first running "sh NVIDIA-Linux-x86-1.0-9755-pkg1.run". Once that completed, I had to do the following:
cp -rp /usr/X11R6/lib/modules/* /usr/lib/xorg/modules
X came right up after that.
Oh, #3 discovered just now. Thunderbird wouldn't start, had to:
chmod 755 /usr/lib/thunderbird-2.0.0.5
Hope this helps, thanks for the instructions!
Allen
July 30th, 2007 at 3:45 am
Hello,
I would like to add a finale note to all my FC6->F7 upgrade.
As you could read, it was not smooth at all but at the end I was able to boot into my box with F7 kernels.
The key was:
1. label all partitions that are not labeled.
2. in fstab use just LABELs.
3. edit grub.conf to use boot from LABEL=/
This is not straightforward from the documentation and everybody who upgraded older FC distributions will face such problems.
Specially my old box that went through RH 7.3->8->9->FC3->FC4->FC5->FC6->F7 upgrades with same partitions!
… but as I told you, not even one went smooth. Wonder, have RH and Fedora folk tried yum updates at all.
OK, I know that it is not reccomended nor supported, but as we can see here, there is a huge demand for such updates - therfore Fedora should change the approach if they want to keep the leading position. You know, Debian and recently Ubuntu have never made such troubles during (dselect) updates.
Regards,
Z
August 3rd, 2007 at 5:19 pm
I'm running into some problems. I upgraded python, python-libs, python-devel, rpm, rpm-python, python-urlgrabber and yum manually. Then I try to run yum -y upgrade,
It says
sqlite3.DatabaseError: Older version of yum sqlite
Then I manually updated sqlite and it still give me that.
August 4th, 2007 at 12:00 pm
Ahh, forgot to update yum-metadata-parser. Hopefully, it'll go smoothly now.
August 11th, 2007 at 10:50 am
Dave (at entry 28), assuming you haven't fixed this yet ….
I had the same problem - seems to be a multilib issue if you're running x86-64. Try this:
Remove any and all of the i386 RPM versions of parted, mkinitrd and nash (you may not have all). Then re-run your yum upgrade.
August 14th, 2007 at 4:09 am
I tried this upgrade but came up with this error:
error: Failed dependencies:
fedora-release = 6 is needed by (installed) yum-fedorafaq-6-2007.02.03.noarch
Any Ideas???
Please…
August 15th, 2007 at 6:37 pm
Hey, i had dependancy issues will libgcj so i removed the stuff that required it (cairo-java libgconf-java glib-java libgtk-java frysk libgnome-java libglade-java ). Upgrade went smoothly but now i think i have broken some stuff. I tried reinstalling it but yum tells me that i need libgcj.so.8rh. Which doesnt seem to exist anywhere. I would like to reinstall those packages i removed.
August 16th, 2007 at 4:03 pm
Thanks for the info - coupled with some info from http://fedoraproject.org/wiki/YumUpgradeFaq, it worked a charm!
Now just to re-compile the latest kernel
For info, I've just upgraded from FC4, but to be on the safe side I went FC4->FC5->FC6->F7.
I think I could have gone direct from 4->7 but I wanted to be sure!
September 5th, 2007 at 8:10 am
First thanxs for your information about the upgrade. I had to do it this way cause my hardware is really old and i have no DVD Drive and no fast USB for an external disk.
I ran into a litte problem with missin dependancies to python(abi). I solved this problem just by: "rpm --rebuilddb" and now everything works fine.
September 10th, 2007 at 11:39 am
did anyone ever figure out the workaround for mkinitrd? I still get the error saying I need nash, even though the exact version it wasn't is installed.
September 11th, 2007 at 10:26 am
I had to uninstall Open Office and some other packages to get the update running.
After update and reboot, I had problems reinstalling Open Office. Found I had to manually download and install (rpm -U --nodeps) certain packages.
Thanks for the guide!
September 11th, 2007 at 1:43 pm
I did get that fixed by uninstalling things related to nash, and uninstalling the x86 versions of mkinitrd. However I get an error saying thatfleminggent repo is not signed. and nothing installs.
September 14th, 2007 at 3:52 pm
Thanks for the rather simple instructions. I hit the libgcj issue as well. Upgrading i386 rpms not x86_64 rpms. The FC6 version is indeed newer. Zeroed in and resolved it no issues. Thanks to those who preceeded me.
Have problems in FC7 running webmin in secure mode (https://…). Webmin works fine w/o secure mode. Looks like perl SSLeay is out of date. Failed to find an up to date FC7 perl module. The SSLeay module complains about an undefined subroutine: ::CTX_new being called by webmin.
Also, logwatch perl choked on a rouge Errno.pm sitting in /usr/lib/perl5/site_perl/5.8.8. I removed it and logwatch works.
Nice way to get from FC6 --> FC7.
September 20th, 2007 at 9:19 am
RE: Instruction 6 - "move fedora-development.repo and fedora-updates.repo out of /etc/yum.repos.d/ and replace them with fedora-development.repo.rpmnew and fedora-updates.repo.rpmnew."
I found that just adding the *.rpmnew files worked instead of moving the old out.
Anybody Else?
September 20th, 2007 at 10:30 am
Thank you very very much for this. I used to it upgrade FC-7 to 8. (There are various differences--for instance the release rpm is in a different location) but the basic concept made it simple.
Thank you.
September 21st, 2007 at 9:55 am
I recently tried the upgrade from fedora 6 to fedora 7 via yum. Everything looked ok until I rebooted the box. When using the 2.6.22.5-76 kernel, the box kernel panics with no init found. The legacy fedora 6 kernel will boot without issue. I read that fedora 7 has problems with unlabeled partitions, however the only labeled partition I have is /boot (which is labeled properly). Everything else is LVM. I'm at a complete loss at the moment.
September 23rd, 2007 at 8:09 pm
Hi all,
Ive been trying to follow all the above info, post and comments, and have run into a couple of problems already mentioned here, but never really got a clean answer about any of them. When I do yum -y update I get the below
Error: Package cairo-java needs libgcj.so.8rh, this is not available.
Error: Package glib-java needs libgcj.so.8rh()(64bit), this is not available.
Error: Package libglade-java needs libgcj.so.8rh()(64bit), this is not available.
Error: Package mkinitrd needs nash = 5.1.19.0.3-1, this is not available.
Error: Package libgnome-java needs libgcj.so.8rh()(64bit), this is not available.
Error: Package cairo-java needs libgcj.so.8rh()(64bit), this is not available.
Error: Package pidgin needs libedataserver-1.2.so.7, this is not available.
Error: Package libgtk-java needs libgcj.so.8rh, this is not available.
Error: Package glib-java needs libgcj.so.8rh, this is not available.
Error: Package libvte-java needs libgcj.so.8rh()(64bit), this is not available.
Error: Package libgnome-java needs libgcj.so.8rh, this is not available.
Error: Package libgconf-java needs libgcj.so.8rh()(64bit), this is not available.
Error: Package libvte-java needs libgcj.so.8rh, this is not available.
Error: Package libglade-java needs libgcj.so.8rh, this is not available.
Error: Package frysk needs libgcj.so.8rh()(64bit), this is not available.
Error: Package mkinitrd needs libparted-1.8.so.2, this is not available.
Error: Package libgtk-java needs libgcj.so.8rh()(64bit), this is not available.
I already have nash 5.1.19.0.3-1 installed and have tried the --enable-testing to fix the libgcj problem, but then get another set of dep problems,
Error: Package mkinitrd needs nash = 5.1.19.0.3-1, this is not available.
Error: Package frysk needs libgcj.so.7rh, this is not available.
Error: Package pidgin needs libedataserver-1.2.so.7, this is not available.
Error: Package mkinitrd needs libparted-1.8.so.2, this is not available.
Yet again a problem with nash, I can remove the pidgin and frysk, I dont mind about them, but mkinitrd still doesnt want to work. Any ideas?
September 24th, 2007 at 3:09 pm
Hi,
I'm exactly at the same situation than Nick, (and with no terminal access 'cause I rent a dedicated server).
the old kernel is Fedora 5, the new one fedora 7.
At this moment, it's booted on the old kernel but can't reboot it till I fix the grub problem.
Thank for help
Regards
Tony
September 26th, 2007 at 9:44 pm
When I run 'yum -y upgrade', I also get several python dependency errors. How do I get around this?
I tried doing a 'yum localinstall python…rpm, but I get the same errors. Seems like I am running into a circular dependency.
September 27th, 2007 at 3:40 pm
Do you have to label the swap partition? My blkid output says:
/dev/hda3: LABEL="/" UUID="a2e18d02-c5e4-44a3-ab89-daa94cc7891c" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda2: TYPE="swap"
/dev/hda1: LABEL="/boot" UUID="576180e9-03cc-4ff1-9a39-fb3c8eaa4e56" SEC_TYPE="ext2" TYPE="ext3"
As you can see, /dev/hda2 is the swap, but there is no label. Attempting to label it, I get the error:
/sbin/e2label: Bad magic number in super-block while trying to open /dev/hda2
Couldn't find valid filesystem superblock.
I'd hate to install and reboot only to find that I no longer have a swap drive…
September 27th, 2007 at 3:52 pm
Never mind, somehow I missed the swap comment in the comments the first time.
September 29th, 2007 at 3:45 am
How do you get around the python(abi) = 2.4 dependency issue. I tried to blow away what needs it but it was too much stuff like yum etc so I backed out. Also another poster said to rpm --rebuilddb but that didn't work.
Also, I get hpijs needs libnetsnmp and I don't even have hpijs installed.
September 30th, 2007 at 4:20 pm
Nick & Charlie:
Probably you have to recreate initrd of your Fedora 7 kernel by issuing this command under root account (or use sudo):
mkinitrd /boot/initrd-2.6.22.5-76 2.6.22.5-76
then check the contents of /boot/grub/grub.conf
September 30th, 2007 at 4:24 pm
2 upgrader comment #45:
I've successfully upgraded two fedora 5 servers to fedora 7.
October 4th, 2007 at 3:17 pm
[...] http://www.ioncannon.net/system-administration/99/upgrade-fc5-to-fc6-with-yum/ http://www.ioncannon.net/linux/68/upgrading-from-fc6-to-fedora7-with-yum/ [...]
October 13th, 2007 at 9:49 am
If you're new and hesitant to upgrade your system this way, don't forget that you can always burn the install DVDs and update that way. It's also the preferred method of upgrading that the Fedora mantainers recommend.
October 14th, 2007 at 4:37 pm
I've tried everything here and moved ahead, to yum upgrade to FC7 but had more troubles.
1) I had to erase many i386 libraries by hand (Mine is a 64bit PC with a FC7 x86_64). It looks like I had old libraries from previous installs that were not needed anymore. Sometimes I had to point to the whole name of the library which was causing the trouble to avoid having half my Fedora erased due to dependencies.
2) Then I also had memory problems and sorted that out with starting my computer without Gnome or KDE (how is it called in English? In Spanish ys just a console "A prueba de fallos" or something like that. Then when I run yum -y update it worked out fine (after two days of struggle, of course).
All this probably seem quiet obvius for most users but was missing in most sites so other newbies can probably appreciate the tip.
thanks a lot
October 16th, 2007 at 3:15 pm
One last thing: does anyone else have trouble after the upgrade with open office? I can't use it because it freezes my fedora both in gnome and KDE.
???
October 29th, 2007 at 11:03 am
I have done several of these updates on several boxes, but only one has been set up with LVM's and it is giving me fits. I'm hoping I can get some insight! Here is my /etc/fstab:
/dev/RootUsr/root / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
/dev/Home/home /home ext3 defaults 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/TmpVar/temp /tmp ext3 defaults 1 2
/dev/RootUsr/usr /usr ext3 defaults 1 2
/dev/RootUsr/usrlocal /usr/local ext3 defaults 1 2
/dev/TmpVar/Var /var ext3 defaults 1 2
LABEL=SWAP-sda5 swap swap defaults 0 0
Here is my /etc/grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/RootUsr/root
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
# FC7 is kernel panicing with being unable to find /dev/root, will set to boot in FC6 for now
title Fedora (2.6.22.9-91.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.22.9-91.fc7 ro root=/dev/RootUsr/root rhgb quiet
initrd /initrd-2.6.22.9-91.fc7.img
title Fedora Core (2.6.20-1.2925.fc6)
root (hd0,0)
kernel /vmlinuz-2.6.20-1.2925.fc6 ro root=/dev/RootUsr/root rhgb quiet
initrd /initrd-2.6.20-1.2925.fc6.img
and my /sbin/blkid:
/dev/mapper/RootUsr-usr: UUID="30efb3c6-afbe-4317-b305-abfd963a937c" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/Home-home: UUID="94fbd273-d772-48e1-85bc-4b538da687f3" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/TmpVar-temp: UUID="0ceb8a2d-560e-413c-977c-21553ed0862f" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/TmpVar-Var: UUID="0698dc8b-a4bc-479a-9a78-a255adb64d19" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/RootUsr-root: UUID="8ece899e-6da2-4c5b-9bbb-10a9e3c508c9" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/RootUsr-usrlocal: UUID="0d01b49f-cba1-4891-94b5-126f1176dee4" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda1: LABEL="/boot" UUID="e7513adf-203b-4f57-a30f-52b4eec84b0a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda5: TYPE="swap" LABEL="SWAP-sda5"
/dev/RootUsr/root: UUID="8ece899e-6da2-4c5b-9bbb-10a9e3c508c9" SEC_TYPE="ext2" TYPE="ext3"
I get a kernel panic with it saying it cannot mount /dev/root
It boots fine if I roll back to FC6
November 1st, 2007 at 4:02 pm
Found the solution here, apparently there is a bug with FC7 and LVM's:
https://bugzilla.redhat.com/show_bug.cgi?id=241949#c26
Executed this while booted in FC6:
/sbin/mkinitrd -f --force-lvm-probe /boot/initrd-2.6.22.9-91.fc7.img
2.6.22.9-91.fc7
Booted back in FC7 just fine.
November 27th, 2007 at 5:49 pm
For those having python issues
yum remove rhnlib up2date
That should take care of your problem
December 4th, 2007 at 2:51 am
It worked perfectly for me. I'm using raid.
If, like me, you have the server in a remote location it's a good idea to use grub's "savedefault" and "fallback" features. That way you can tell grub to fall back to another kernel if the default panics.
December 8th, 2007 at 9:47 am
After following this entire thread, I still have:
Error: Missing Dependency: libnetsnmp.so.10 is needed by package hpijs
Error: Missing Dependency: python(abi) = 2.4 is needed by package authconfig
Error: Missing Dependency: python-abi = 2.4 is needed by package system-config-printer-libs
Error: Missing Dependency: libedataserver-1.2.so.7 is needed by package pidgin
Error: Missing Dependency: python(abi) = 2.4 is needed by package hplip
Error: Missing Dependency: libnetsnmp.so.10 is needed by package hplip
Error: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python
Error: Missing Dependency: libnetsnmp.so.10 is needed by package libsane-hpaio
Error: Missing Dependency: python(abi) = 2.4 is needed by package system-config-printer-libs
Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python
Error: Missing Dependency: libpq.so.4 is needed by package dovecot
What is the command to force the install? Or is that suggested?
January 12th, 2008 at 10:18 am
Hi I had the same problem (python(abi) = 24. etc).
I found a solution (the upgrade is running now), via
http://fcp.surfsite.org/modules/newbb/viewtopic.php?viewmode=flat&order=ASC&topic_id=49437&forum=10&move=next&topic_time=1197946322
.
i.e: remove authconfig and other depending packages.
Good luck.
Ton
January 12th, 2008 at 11:40 am
keeps on stupping at this on doung a yum update.
any suggestions?
regards and tks
--> Processing Dependency: libFLAC.so.7 for package: gstreamer08-plugins
--> Processing Dependency: xine-lib = 1.1.9.1 for package: xine-lib-extras-nonfree
--> Finished Dependency Resolution
Error: Missing Dependency: libFLAC.so.7 is needed by package gstreamer08-plugins
Error: Missing Dependency: xine-lib = 1.1.9.1 is needed by package xine-lib-extras-nonfree
January 13th, 2008 at 5:32 am
I tried to upgrade fedora 6 to 7 and followed the instructions carefully. But after almost I was come-up an error such as -> Finished Dependency Resolution
Error: Missing Dependency: python(abi) = 2.4 is needed by package authconfig
Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python
Error: Missing Dependency: python-abi = 2.4 is needed by package system-config-printer-libs
Error: Missing Dependency: python(abi) = 2.4 is needed by package hplip
Error: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python
Error: Missing Dependency: python(abi) = 2.4 is needed by package system-config-printer-libs
Error: Missing Dependency: libedataserver-1.2.so.7 is needed by package pidgin
I was tried to check the version of python installed and I am currently using Python 2.4.4 (#1, Oct 23 2006, 13:58:00)
[GCC 4.1.1 20061011 (Red Hat 4.1.1-30)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Please help me to understand what's the meaning of the error were occured during yum update.
I am looking forward for possible reply for the best minded people who are willing to share their ability and great knowledge to everyone.
Thank you.
Philip
January 20th, 2008 at 12:17 am
i updated fc6 to fc8 directly ad it worked like charm after following the steps.
January 22nd, 2008 at 9:03 am
Zoltan,
I had the same problem upgrading to F7. F7 would not see the boot drive and kept getting kernel panic. FC6 kernel would boot fine. Even when I booted with F8 install CD, the install did not see the hard drive.
Two critical steps:
1) manually change /boot/grub/device.map to it has /dev/sda and not /dev/hda.
2) My old WD Cavier boot drive had the jumper on master. I changed the jumper to cable select (CS).
Now F7 and F8 see the drive and everything works perfectly. I didn't think Fedora was picky about the master/slave/cable select thing, but starting in F7, it is.
Hope this helps.
Greg James
January 22nd, 2008 at 9:05 am
Philip Diaz,
I had a similar problem. I just rpm -e the packages having the problem then I could do the upgrade. Then I just yum installed them back in after the upgrade.
Hope this helps.
Greg James
February 16th, 2008 at 8:52 am
i know people have been asking left right and center if it's possible to skip a version, and i'm no different appart from that i want to go from fc6 to f8. is this possible without the whole f7 step, could i just put the f8 repo's in rather than f7?
February 17th, 2008 at 10:22 am
This seems to be a very good guide EXCEPT that its for x86_64 systems. I did not realize that and stupidly fired the rpm -Uhv command on my non 64 bit system. I am still trying to recover. With more and more folks now running the new hardware which is 64bit, it might not be an issue but it might help if you put it up in the title that the steps are for x64 architecture. My upgrade is running currently and I will post the changes (no renaming to rpmnew is required etc) once the upgrade finishes. I intend to do a 2 step upgrade going from FC6 to Fedora 8.
February 18th, 2008 at 8:29 am
The two step upgrade went fine after I got the i386 versions of the rpms in the first command. All the dependency erros (there were hundereds of them) went away and an hour and half later I was at Fedora 7. I had the labels correctly and I followed the fedora Upgrading using yum instructions too and changed my boot drive to /dev/sda in the grub config (from /dev/hda/) before booting. Machine booted up just fine.
Thanks for the instructions. They too came in pretty handy.
February 20th, 2008 at 5:44 am
I had a problem after the update on a system where LVM was on a soft RAID. The system has 2 ATA and 2 SATA drives on soft (md) RAID-1 configuration. Yes, I know, I could make raid on LVM by itself, but at the time it was built I was more familiar with md. Know, upon boot with the kernel of fedora 7, the order of drives changes, and sata drives do not come as sda/sdb but as sdbc/sdd, and the ata disks take the sda & sdb labels. As i have the / partition on ata disks, the system boots, but loses completely the filesystem on LVM (it does not get recognized). Any hints will be welcomed!
May 15th, 2008 at 3:35 am
Good work Artem S. Tashkinov !!!
Your tip to re-create the initrd image fixed my problem.
Now I just need to figure out why udev is only building device nodes for 2 out of 4 drives in my RAID array…