[Yum] preupgrade stuck

[Gerry Reno]

Gerry Reno wrote:
> Gerry Reno wrote:
>> Seth Vidal wrote:
>>>
>>>
>>> On Thu, 23 Apr 2009, Gerry Reno wrote:
>>>
>>>> Seth Vidal wrote:
>>>>>
>>>>>
>>>>> On Thu, 23 Apr 2009, Gerry Reno wrote:
>>>>>
>>>>>> Yes, anaconda puts the system into about the same as "rescue 
>>>>>> mode" and then performs the operations there. But that is why I 
>>>>>> thought that the upgrade could be completed from rescue mode 
>>>>>> because it is very similar if not exactly similar to how anaconda 
>>>>>> handles the upgrade.
>>>>>
>>>>> Anaconda does a lot of things other than that, too. Especially in 
>>>>> post.
>>>>>
>>>>> -sv
>>>> I can't leave this machine stuck like this. I have to try something 
>>>> from rescue mode to get the upgrade completed. I know anaconda has 
>>>> to do some post tasks but probably the biggest one is just 
>>>> straightening out the bootloader and then removing the install 
>>>> kernel and install.img from /upgrade. I can't see where it needs to 
>>>> do any more than that.
>>>>
>>>
>>> How about figuring out why it won't boot into anaconda for the 
>>> preupgrade to begin with?
>>>
>>> -sv
>>>
>> Yes, I already know why. I was able to check the program.log from the 
>> /tmp ramdisk in the ctrl-alt console and it is failing to assemble 
>> the raid arrays because of a bad argument ot mdadm. It is trying to 
>> assemble "/dev/md/0" instead of "/dev/md0" and the assembly fails, 
>> therefore the volume groups fail, therefore the filesystems cannot 
>> mount and then it reports that it cannot find the root of the 
>> existing installation. I put all this in the bug: 
>> https://bugzilla.redhat.com/show_bug.cgi?id=496258
>>
>> Regards,
>> Gerry
>>
> Did you have a chance to see what is happening in the logs I sent? Can 
> this typo or whatever be fixed quickly? If not, can you tell me how to 
> complete this stuck preupgrade manually in the rescue mode?
>
> Regards,
> Gerry
>
I've made several attempts at completing this stuck preupgrade using 
rescue mode. I can see the 'preupgrade' repo and I made sure that it has 
everything: comps.xml, sqllite, the packages, the preupgrade.repo in 
/etc/yum.repos.d. So I tried using 'yum upgrade'. That resulted in a 
list of depsolving and missing dependency problems. So I tried 'yum 
--skip-broken upgrade' and that resulted in craziness. I started it 
running and several hours later, it was still running! When it finally 
did finish it just quit and gave back the command prompt showing missing 
dependencies. So what good is '--skip-broken' if it isn't going to skip 
anything?

Regards,
Gerry