Un Cachito de la vida

Un Cachito

Un Cachito de la vida - A little piece of Cameron's life






I've upgraded Fedora Core 6 (FC6) to Fedora 7 (FC7) with yum three times now I think and my last attempt was riddled with problems, so I thought I'd try to document my problems a little.My first attempt went well, except that afterwards I scanned my rpm database for FC6 packages so I could remove them (rpm -qa | grep fc6). I had done the same with FC5 packages when I upgraded to FC6. Well, it turned out that FC7 actually included packages labeled with the fc6 tag that they decided weren't worth renaming. So, I basically screwed up my box my removing all those and ended up just reinstalling from a CD.My second attempt was on a mail server and it actually went pretty well except that it changed a db version for my users IIRC and it took some help from a friend to get it going.This time, the upgrade took about 2 days and a lot of fighting as I tried to make it work. I started by following this page, and upgrading the fedora version RPMs. I then did the yum -y update and it failed over and over on dependencies, saying mostly that it didn't have python(abi) = 2.4. That should be included in the python 2.4 package, but it appears it is missing in my python pkg. Short solution (after a day) was to upgrade python itself with yum -y update python. It failed too on the python version, but I just uninstalled a few packages that depended on it (like livna-config-display) and kept note of those. Once python was updated, everything else updated fine. I also got a bunch of strange HDD errors during the upgrade, which killed it several times, but I moved my yum cache (/var/cache/yum) to a different directory and sector on the HDD (by tarring it up and untarring it elsewhere) and that seemed to fix the problem.So I was good to go, except that the system now wouldn't boot. It would give me errors like these:Unable to access resume device (/dev/hda3)
Creating root device
Mounting root filesystem
mount: could not find filesystem '/dev/root/'
Setting up other filesystems
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
I had to remove the "quiet" keyword from the grub boot line to see the real problem - and that's where I saw that it had converted my drives from IDE to SCSI notation (hda ->sda). Once I saw that, I could go in and edit my grub config file and the /etc/fstab file and was good to go. Now I need to find out why starting Google Earth restarts my X server!Hopefully, someone wlse will find this useful too.

Posted by charr at 4:31 PM



Reader Comments

Post a comment













Remember Info?