Hello,
Do you have any updates?
This feature needs to be introduced in the coming release, your quick response
is appreciated. Thanks in advance.
Regards
R.Nageswara Sastry
On 11/28/2013 4:58 PM, Nageswara R Sastry wrote:
On 11/27/2013 10:33 PM, David Lehman wrote:
Hello David,
> What version of anaconda are you using for development? I think there
> may be a bug in anaconda that's causing your problem with boot disk.
> Also, could you send me a set of logs including both storage.log and
> anaconda.log?
I am using Fedora19's Anaconda and Blivet.
anaconda-19.30.13
blivet-0.17
boot-disk is not setting because of the condition disk.protected == true,
from the following code - ksdata.bootloader.execute(storage, ksdata, instClass)
is not executed
anaconda-19.30.13/pyanaconda/kickstart.py
def doKickstartStorage(storage, ksdata, instClass):
""" Setup storage state from the kickstart data """
ksdata.clearpart.execute(storage, ksdata, instClass)
if not any(d for d in storage.disks
if not d.format.hidden and not d.protected):
return
ksdata.bootloader.execute(storage, ksdata, instClass)
...
I tricked it to execute it, but later when the installation completed, the disk is
corrupted because parted object is not properly initialized by
blivet-0.17/formats/disklabel.py: def partedDisk
After the partedDisk initialization happens correctly, installation fails at
device creation, blivet-0.17/devices.py: def create(self):
and raising error - raise DeviceCreateError(str(e), self.name)
Reason for the above error is - request for committing the partition is sent to
parted tool and parted tool thrown error "Too many primary partitions".
Because
already the disk is having one partition and can not create one more. This happens
because of the disk's nature can not create/delete a partition.
Thanks!!
Regards
R.Nageswara Sastry