F10 automatic F10 upgrades to F11?

[Daniel B. Thurman]

Paul W. Frields wrote:
> On Wed, Jul 22, 2009 at 09:17:39AM -0700, Daniel B. Thurman wrote:
>   
>> For the last several weeks, I have been getting "automatic"
>> F11 upgrade notices on my F10 system.  I do not know if
>> this is a feature or standard operating procedure for this sort
>> of thing since I have never initiated such an upgrade request
>> to begin with.
>>
>> But then again, I thought to myself... why not?  I was getting
>> tired of waiting for the missing gnome `sessions save' package
>> which for the most part may never be released for F10.
>>
>> So, when I was prompted (automatically from yum?) for F10 to
>> F11 upgrade, I proceeded to start the update process.  After
>> entering root permission, the upgrade dialog window pops
>> and and starting "firing away" with the upgrade process:
>>
>>     "Upgrade your system"
>> "Preparing system for upgrade"
>>
>> + Download release info
>> + Download installer images
>> + Determine which packages to install
>> + Download packages
>> + Prepare and test upgrade
>> + Ready to begin upgrade
>>         [Reboot Now]
>> + Pressed the [Reboot Now] button
>>   On rebooting, it shutdown the services, rebooted,
>>   and grub starts kernel & runs Anaconda.
>> + X11 "Finding storage devices... dialogbox pops up
>> + X11 Passphrase dialog pops up.  Entered the encrypted disk
>>    password & checked the "This is a global passphrase" checkbox
>> + X11 "Retrieving installation information for installation repo..."
>>    dialogbox pops up
>> + "Checking dependencies in packages selected for installation..."
>>    & progressbar shows, takes awhile to complete...
>>
>> The progressbar got 1/3 of the way, and then suddenly X11 quits
>> and proceeds into text mode:
>> =============================
>> [TIME] Starting graphical installation...
>> install exited abnormally [1/1]
>> disabling swap...
>> [...]
>> unmounting filesystems...
>> [...]
>> you may safely reboot your system
>> [cursor]
>> =============================
>>
>> So, I had to power-cycle the PC to reboot.
>>
>> Grub shows:
>> ==========================
>>  Upgrade to Fedora 11 (Leonidas) *
>>  initng boot  *
>>  Fedora (2.6.27.25-170.2.72.fc10.i686)
>>  Windows 2000
>> ==========================
>> * = new additions due to the upgrade process.
>>
>> ====================================
>> I have gone through this about 5 times over the
>> course of several weeks, each time, resulting a
>> failed upgrade.  I can still boot into my F10 system,
>> nothing was lost or corrupted (as far as I can tell) and
>> the Upgrade repos still remain in the yum directories.
>>
>> Can someone tell me, what is going on, why is it
>> that Yum repeatedly does this from time to time
>> due to a normal F10 boot, yum F10 updates, and
>> occasionally popping up the upgrade process?
>>
>> Every time I think "it's gonna work this time..",
>> upgrades (from F10 to F11) *always* fails.
>>     
>
> FWIW, the following page (and links) may help
> https://fedoraproject.org/wiki/How_to_use_PreUpgrade
>
> If you can provide a more detailed bug filed against preupgrade, I
> know there are some folks who would love to improve the experience of
> preupgrade.  I was just talking to them last week, matter of
> fact... :-)
>
> I know problems currently exist with exotic configurations like /boot
> volume on RAID, and one of the things I've suggested is to look for
> these cases and then have preupgrade apologize and bail out before
> doing anything else.
>   
I have been at the suggested link before, tried it, and it
does not seem to change anything other than I have
cleaned up a lot of things in the F10 filesystem as
suggested.  It did not seem to change the outcomes
of the failed upgrade process as far as I can tell.

What else can I provide by way of "more details"?
Is there something I have left out?

As for filesystem layout:
=========================================
/dev/sda2: ntfs:            29.31GB            /w2kPro
/dev/sda4: extd:            160.61GB
/dev/sda5: ntfs:            29.29GB            /w-App1
/dev/sda6: ntfs:            29.29GB            /w-App2
/dev/sda7: ext3:            196.08GB         /boot
/dev/sda8: crypt-luks:    101.82GB        /root (lvm)

Keep in mind that the above sdaX is not sequentially
labeled due to the use of gparted and manipulation
of the partitions from a previous configuration prior
to installation for F10 at the time. Dunno if this
is a big deal or not...

As for grub:
=========================================
# 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 (hd0,6)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=saved
timeout=5
splashimage=(hd0,6)/grub/splash.xpm.gz
#hiddenmenu
title Fedora (2.6.27.25-170.2.72.fc10.i686)
    root (hd0,6)
    kernel /vmlinuz-2.6.27.25-170.2.72.fc10.i686 ro 
root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.25-170.2.72.fc10.i686.img
    savedefault
title Windows 2000
    rootnoverify (hd0,1)
    chainloader +1
    savedefault

Kind regards,
Dan