On Mon, 2013-11-04 at 10:28 -0500, Gene Czarcinski wrote: > In aticipation that we will have to live with efi and gparted disks > "real soon now", I decided to give the gparted a try first. Before > actually commiting to it on real hardware, I though I would do it on a > KVM virtual. > > So I define a simple KVM kickstart install with a biosboot, swap, and > btrfs partitions. Booted F19 DVD-ISO and sp[ecified gpt ks=http:// > > The install went just find and the system booted just fine. > > Now, before proceeding to real hardware I want to make sure that I can > re-install another system (except it will be F19 again). So I specify > the swap and btrfs partitions --noformat and a different name for the > root subvol > > This did not work! Anaconda would not accept either --onpart=UUID=... > or --onpart=vda2/3 for the partition specification (gpt was specified on > the cmdline for the kernel). Anaconda claims that 'No preexisting > partition with the name "vda2" was found'. anaconda.log and storage.log (from /tmp) would be useful, as is almost always the case when reporting problems related to anaconda. > > OK, so how do you specify a pre-existing gparted partition? Is this a > bug? Or the lack of a "feature"? Or perhaps some special (undocumented) > parameter that I need to specify? > > I know that anaconda has been supporting installation into gparted > partitions for some time because gparted is used for really, really big > disks and I assume that someone might want to reinstall into existing > partitions. > > Gene > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
