Red Hat Bugzilla – Bug 851342
autopartitioning doesn't work in anaconda 18.6.1 (text mode/ppc64)
Last modified: 2014-06-23 20:19:04 EDT
Description of problem:
It appears autopartitioning does not work in text mode on ppc64. When attempting to complete step 2 ("Installation Destination"), after selecting the appropriate options it returns an error stating "Error checking storage configuration". This occurs with both the "Use All Space" and "Replace Existing Linux system(s)" options.
anaconda.log contains the following:
20:06:24,210 ERR anaconda: You have not defined a root partition (/), which is required for installation of Fedora to continue.
20:06:24,211 ERR anaconda: you have not created a bootloader stage1 target device
20:06:24,212 ERR anaconda: You have not created a bootable partition.
(full logs will be attached)
Version-Release number of selected component (if applicable):
The ISO was built with:
Created attachment 606708 [details]
Created attachment 606709 [details]
Can you attach the other log files too? program.log etc.. Might not be necessary but it would be good to have a whole picture of what's going on.
What is the storage available on this system? How did you boot the installer?
Created attachment 606710 [details]
Created attachment 606711 [details]
(In reply to comment #3)
> What is the storage available on this system? How did you boot the
It has a single 50G disk on /dev/sda. DVD iso is in /dev/sr0 which we booted off of with just 'linux'. There is no graphics hardware, so it defaulted to text mode.
So the first screen of the installation destination spoke presented you a choice of drives, you picked the option to choose /dev/sda ?
Correct; after selecting it sda had a check next to it, then I hit 'c' to continue onto partitioning.
Ok, I think this is something specific to PPC, or something specific to having LVM data on the disk before hand.
Can you blank the disks, like really blank the disks so that there is no LVM bits left and try again?
This is caused by 848173. When that works, so will this.
*** This bug has been marked as a duplicate of bug 848173 ***
I have verified that this works when the patch in 848173 has been applied...