Re: Preupgrade does not work 16-17

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 7, 2012 at 12:35 AM, Adam Williamson <awilliam@xxxxxxxxxx> wrote:
> On Wed, 2012-06-06 at 08:28 +0530, Ankur Sinha wrote:
>> On Wed, 2012-06-06 at 08:18 +0530, A. Mani wrote:
>> > I tried to upgrade fedora 16 x86-64 via preupgrade a few days ago.
>> > After the first stage up to download of packages and installation of
>> > grub2 for the actual install process ... it went fine.
>> > The new grub2 entry was not bootable (known bug?), but anyway I
>> > modified it manually and started anaconda.
>>
>> Yes. This is a known bug:
>>
>> http://fedoraproject.org/wiki/Common_F17_bugs#preupgrade_from_Fedora_16_does_not_update_bootloader_configuration
>
> I'm not sure that's the same thing. The most common case of the bug
> referred to there means that an entry is present and bootable, it's just
> not the _default_. As A. Mani describes it, the entry he got wasn't
> bootable at all, which would be something different.



The entry looked like
({STRING} was the actual UUID)

menuentry 'Upgrade to Fedora 17 (Beefy Miracle)' --class gnu-linux
--class gnu --class os {
	 linux /boot/upgrade/vmlinuz preupgrade
repo=hd::/var/cache/yum/preupgrade
ks=hd:UUID={STRING}:/boot/upgrade/ks.cfg
stage2=hd:UUID={STRING}:/boot/upgrade/squashfs.img
        initrd /boot/upgrade/initrd.img
}

This would not boot

The missing part is

        insmod part_msdos
	insmod ext2
	set root='(/dev/sdc,msdos1)'
	search --no-floppy --fs-uuid --set=root {STRING}

_______________

I think I have the ks file.... will check


Best

A. Mani





-- 
A. Mani
CU, ASL, CLC,  AMS, CMS
http://www.logicamani.co.cc
-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux