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

Re: F10 -> F11 using preupgrade [SOLVED}



PS = Pete Stieber
PS>> I have a Dell Power Edge 1435SC that is running F10.
PS>> I followed the preupgrade procedure on
PS>>
PS>> http://fedoraproject.org/wiki/How_to_use_PreUpgrade
PS>>
PS>> When the machine rebooted it asked me to select the
PS>> Ethernet connection to update over using the
PS>> NetworkManager.  I couldn't get this to work.
PS>>
PS>> On a positive note, when I rebooted the machine, F10
PS>> still worked.  I was not using the NetworkManager
PS>> with F10...
PS>>
PS>> $ chkconfig | grep etw
PS>> NetworkManager  0:off   1:off   2:off   3:off   4:off   5:off   6:off
PS>> network         0:off   1:off   2:on    3:on    4:on    5:on    6:off
PS>>
PS>> Is there a way around this?

B = Beartooth
B> I have recently done three machines, using first yum
B> update, then simply "preupgrade" as root. It looked
B> to operate normally on all three, and did on two --
B> both are now happily running F11. It -- or something
B> I did without noticing -- loused the other up royally
B> and  then some. I'm having to do fresh installs (the
B> first two failed, and the third is still under weigh).
B> Maybe that machine has a hardware problem ...

In the hopes of helping someone else out with similar problems...

This machine was configured with static a IP address. A while ago the NetworkManager had problems with a static IP configuration so I switched the machine to the old network service. The static IP address problem has been fixed in the NetworkManager, so I enabled the NetworkManager in F10. After manually adding the proper lines to /etc/sysconfig/network-scripts/ifcfg-* to get DNS working, the NetworkManager worked under F10.

When performing an upgrade reboot, the NetworkManager still had problems. It turns out this was anaconda's fault. It setup the system to use a Kickstart file that didn't have a static IP configuration line. When this is the case, anaconda defaults to using DHCP. This broke the install. I added the proper "network" line to /boot/upgrade/ks.cfg and the install is now working.

Here is a bugzilla reference that will explain this better...

https://bugzilla.redhat.com/show_bug.cgi?id=475027

I have upgraded this system several times. I must have loaded a pre F8 version because my boot partition was only 100 MB. This made it impossible to download the install image (111 MB) from mirrors during the preupgrade process. This made network access absolutely essential for the upgrade reboot to work.

I really hope this helps someone else out,
Pete


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