Red Hat Bugzilla – Bug 501428
Installing livecd from usb stick, partitioning does not complete
Last modified: 2009-09-26 17:27:55 EDT
Created attachment 344560 [details]
anaconda error log
If I create a usb stick from a live cd iso(rawhide/f11 - 20080515).
Boot from the usb stick, try to install using "liveinst".
Partitioning never completes after clicking on Next.
Eventually if I do click next i.e. 20 minutes later a error dialog appears.
Asks me to format "/"
Then I get an Exception Occured Dialog.
Error attached to ticket.
The same image booted from iso installs correctly.
This method worked previously with Fedora 10.
If I manually format the partition from the console and only assign a mount
point in anaconda, it installs correctly.
Created attachment 344563 [details]
Missed my entry, I tested using anaconda-220.127.116.11-1, anaconda fails now before I can partition. See log.
This will be fixed in the next build of anaconda for F11. Thanks for the bug report.
So I updated to anaconda-18.104.22.168-1 & pykickstart-1.54-1 from koji. Not sure if the initial bug would be fixed in this. Also seeing this which I am sure is related to the drive not getting formatted.
If I select "replace existing Linux system" or "Use entire drive".
The following errors occurred with your partitioning:
Your / partition does not match the the live image you are installing from. It must be formatted as ext3.
This can happen if there is not enough space on your hard drive(s) for the installation.
Press 'OK' to choose a different partitioning option.
"Use entire drive" should just nuke everything right?
When you have selected the partitioning of the harddisk, clicked next and waiting for the install to start. The NEXT button is still clickable, if you click on this by mistake or think the install is not running, it will fail.
Perhaps this is only present on slower machines.
Would it be possible to disable Next after paritioning starts, so this cannot fail?
Created attachment 345329 [details]
Install Error Log
*** Bug 505363 has been marked as a duplicate of this bug. ***
These are completely separate bugs from the initial report. Please use one bug per problem. Thanks.