Hi,
I tried preupgrade without success, but at least it didn't destroy my old installation. :-)
I started package downloads with preupgrade 0.9.3-1, then killed it when 0.9.3-2 came out, upgraded and continued downloading. Total download size was about 6.2 GB, I have many huge games installed from Fedora 8 Everything. However, this version hung at the last download phase, which was fixed by 0.9.3-3. This version offered to reboot into upgrade finally, which I did. It booted into anaconda upgrade, which detected my partitions correctly. The problem that made the upgrade unsuccessful was that Anaconda doesn't pull the network settings from my old installation and I have an ADSL connection with a dump ADSL modem, not a router. The GRUB boot line for preupgrade is this:
kernel /upgrade/vmlinuz preupgrade lang=hu_HU.UTF-8 keymap=hu stage2=hd:sda1:/upgrade/stage.img \ method=http://ftp.crc.dk/fedora/linux/releases=9/Fedora/x86_64/os
Anaconda stalled at "Retrying package download" because the network connection isn't established. Replacing the method= parameter with method=file:///mnt/sysimage/var/cache/yum/anaconda-upgrade i.e. to point to the download directory gave me a Python exception in Anaconda.
Best regards, Zoltán Böszörményi
Zoltan Boszormenyi írta:
Hi,
I tried preupgrade without success, but at least it didn't destroy my old installation. :-)
I started package downloads with preupgrade 0.9.3-1, then killed it when 0.9.3-2 came out, upgraded and continued downloading. Total download size was about 6.2 GB, I have many huge games installed from Fedora 8 Everything. However, this version hung at the last download phase, which was fixed by 0.9.3-3. This version offered to reboot into upgrade finally, which I did. It booted into anaconda upgrade, which detected my partitions correctly. The problem that made the upgrade unsuccessful was that Anaconda doesn't pull the network settings from my old installation and I have an ADSL connection with a dump ADSL modem, not a router.
typo, it's a "dumb" modem.
The GRUB boot line for preupgrade is this:
kernel /upgrade/vmlinuz preupgrade lang=hu_HU.UTF-8 keymap=hu stage2=hd:sda1:/upgrade/stage.img \ method=http://ftp.crc.dk/fedora/linux/releases=9/Fedora/x86_64/os
Anaconda stalled at "Retrying package download" because the network connection isn't established. Replacing the method= parameter with method=file:///mnt/sysimage/var/cache/yum/anaconda-upgrade i.e. to point to the download directory gave me a Python exception in Anaconda.
Best regards, Zoltán Böszörményi
2008/5/14 Zoltan Boszormenyi zboszor@freemail.hu:
Hi,
I tried preupgrade without success, but at least it didn't destroy my old installation. :-)
I started package downloads with preupgrade 0.9.3-1, then killed it when 0.9.3-2 came out, upgraded and continued downloading. Total download size was about 6.2 GB, I have many huge games installed from Fedora 8 Everything. However, this version hung at the last download phase, which was fixed by 0.9.3-3.
I think it has something to do with preupgrade looking for a ".treeinfo" file, which wasn't available on my mirror. I've fixed it by pointing the preupgrade configuration to a mirrorsite that had the treeinfo file.
This version offered to reboot into upgrade finally, which I did. It booted into anaconda upgrade, which detected my partitions correctly. The problem that made the upgrade unsuccessful was that Anaconda doesn't pull the network settings from my old installation and I have an ADSL connection with a dump ADSL modem, not a router.
Does anaconda need an internet connection after preupgrade has downloaded all the relevant files for your upgrade?
Another small bug I've found which could be handled better is that the kernel from Fedora 9 swapped my sda and sdb disks (I've got a SATA and an IDE disk in my system), and anaconda isn't able to find the stage2 image (there's a prompt asking for the correct disk, but none of the options work).
Kj
Klaasjan Brand írta:
2008/5/14 Zoltan Boszormenyi <zboszor@freemail.hu mailto:zboszor@freemail.hu>:
Hi, I tried preupgrade without success, but at least it didn't destroy my old installation. :-) I started package downloads with preupgrade 0.9.3-1, then killed it when 0.9.3-2 came out, upgraded and continued downloading. Total download size was about 6.2 GB, I have many huge games installed from Fedora 8 Everything. However, this version hung at the last download phase, which was fixed by 0.9.3-3.
I think it has something to do with preupgrade looking for a ".treeinfo" file, which wasn't available on my mirror. I've fixed it by pointing the preupgrade configuration to a mirrorsite that had the treeinfo file.
This version offered to reboot into upgrade finally, which I did. It booted into anaconda upgrade, which detected my partitions correctly. The problem that made the upgrade unsuccessful was that Anaconda doesn't pull the network settings from my old installation and I have an ADSL connection with a dump ADSL modem, not a router.
Does anaconda need an internet connection after preupgrade has downloaded all the relevant files for your upgrade?
What else would the "Retrying package download" message indicate? I have many packages installed from both Fedora Everything and Livna.
Another small bug I've found which could be handled better is that the kernel from Fedora 9 swapped my sda and sdb disks (I've got a SATA and an IDE disk in my system), and anaconda isn't able to find the stage2 image (there's a prompt asking for the correct disk, but none of the options work).
Kj
Klaasjan Brand wrote:
<snip>
Another small bug I've found which could be handled better is that the kernel from Fedora 9 swapped my sda and sdb disks (I've got a SATA and an IDE disk in my system), and anaconda isn't able to find the stage2 image (there's a prompt asking for the correct disk, but none of the options work).
Kj
</snip>
Had experienced the similar problem with externally usb connected HD ( #445650 ) The line that Preupgrade added to grub.conf marked stage2 on sdb while anaconda search for it on sdc Try changing the stage2 line in grub to sdb or visa versa and see if you get further.
Either this is an anaconda problem or preupgrade. ( My money's on anaconda ) I think one way to solve this is for preupgrade to do some check to to take into account for external/extra HD and adjust the grub entry appropriately to "match" what anaconda might thinking it to be.. sda becomes sdb, sdb becomes sdc etc.
Best regards. Johann B.
kernel /upgrade/vmlinuz preupgrade lang=hu_HU.UTF-8 keymap=hu stage2=hd:sda1:/upgrade/stage.img \ method=http://ftp.crc.dk/fedora/linux/releases=9/Fedora/x86_64/os
You shouldn't even need a method= parameter here. anaconda is smart enough to know you're using preupgrade and will look in the right place. So try removing it from your boot config and see what happens.
- Chris
Chris Lumens wrote:
kernel /upgrade/vmlinuz preupgrade lang=hu_HU.UTF-8 keymap=hu stage2=hd:sda1:/upgrade/stage.img \ method=http://ftp.crc.dk/fedora/linux/releases=9/Fedora/x86_64/os
You shouldn't even need a method= parameter here. anaconda is smart enough to know you're using preupgrade and will look in the right place. So try removing it from your boot config and see what happens.
- Chris
Hum I think this line is there for a dependency check, as in package can be fetch from a mirror if it runs into trouble if not then it's a bug that the "method" entry is added if not needed..
I experienced one time while testing preupgrade that it needed and tried to fetch the package online ( there also seemed to be missing some sanity check on network connection before it tried to fetch the package in anaconda. it hanged for to long time before ui window which allowed me to set the network connection popped up).
Been awhile since I tested preupgrade so it might be fixed..
JB..
Chris Lumens írta:
kernel /upgrade/vmlinuz preupgrade lang=hu_HU.UTF-8 keymap=hu stage2=hd:sda1:/upgrade/stage.img \ method=http://ftp.crc.dk/fedora/linux/releases=9/Fedora/x86_64/os
You shouldn't even need a method= parameter here. anaconda is smart enough to know you're using preupgrade and will look in the right place. So try removing it from your boot config and see what happens.
- Chris
It didn't work. Now I got a dialog "Missing ISO 9660 image" telling "The installer tried to mount image #1 but cannot find it on the hard drive ..."
Best regards, Zoltán Böszörményi