[clug] f14->f16 upgrade blues [conclusion]

Eyal Lebedinsky eyal at eyal.emu.id.au
Wed Mar 21 15:59:32 MDT 2012

[3rd time after an iinet spam filter stopped this]

I gave up and did a f14->f15 upgrade, which was a real test of my
will but was completed.

On my other machine, which was already on f15, I did a f15->f16 preupgrade
last weekend.

Apart from a few unusual errors(1), and the machine non-bootable at the
end (2) it was much less trouble that the 14->15.


(1) when encountering an error the install aborts, leaving you with a
useless mishmash. A reboot into preupgrade did continue from the failure
point to completion (but see [2]).

This is what came up during the cleanup stage:

ERR anaconda: AnacondaYum._run: PackageSackError: Rpmdb checksum is invalid: dCDPT(pkg checksums): x264-libs.x86_64 0:0.0.0-0.31.20110811.fc16 - u

(2) The grub conf had *only* the preupgrade entry and the necessary files
for this were actually removed. I net booted from my clonezilla image,
edited the config (added the missing f16 entry, the files were present)
and it booted OK.

On 02/08/12 18:34, Eyal Lebedinsky wrote:
> I have a f14 machine which I am upgrading to f16 the preugrade route.
> Or at least I was trying last Saturday...
> I got it to go through the motions up to the post-download reboot. At
> this point it did *not* boot into f16 (brought up the old f14).
> There was not even an upgrade grub entry to be found.
> After some searching/reading I decided to install grub2 (seems not to
> be strictly needed). I still needed to create the grub2/grub.cfg entry
> by hand, no matter how many times I re-run preupgrade.
> I now can boot the f16 upgrade kernel, however it does not manage to find
> its file system. I also see an error after reading initrd where it complains
> that it could not load the file (but it carries on with the boot process).
> The boot fails because it uses my f14 root rather than the one in the squashfs
> image included in the initrd.img file.
> I had no trouble extracting the two cpio files (stored in initrd.img) and it
> seems that grub2 is not successful extracting the two concatenated archives
> here.
> I found people listing an entry like this:
> linux /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=f9f345f0-39d7-4b2b-8ed0-57b25da62edf:/upgrade/ks.cfg
> initrd /upgrade/initrd.img
> but the kernel asks for a 'root=' entry. I expected it to use a ramdisk with the
> image provided in initrd.img (the second part). The UUID is for the /boot
> partition.
> Does anyone have a working grub2/grub.cfg file?
> Any help or comment welcome.
> cheers and TIA

Eyal Lebedinsky	(eyal at eyal.emu.id.au)

More information about the linux mailing list