Re: problems with unpartitioned harddrives and automatic partitioning

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Here is what it's on the console when drives are unpartitioned:

Traceback (most recent call last):
File "/usr/bin/anaconda", line 938, in ?
instClass.setInstallData(anaconda)
File "/usr/lib/anaconda/kickstart.py", line 831, in setInstallData
self.ksparser.readKickstart(self.file)
File "/usr/lib/python2.4/site-packages/pykickstart/parser.py", line 1151, in readKickstart
self.handleCommand(lineno, args)
File "/usr/lib/anaconda/kickstart.py", line 719, in handleCommand
self.handler.handlers[cmd](cmdArgs)
File "/usr/lib/anaconda/kickstart.py", line 440, in doPartition
if not hds.has_key(pd.disk) and hds.has_key('mapper/'+pd.disk):
TypeError: cannot concatenate 'str' and 'NoneType' objects
install exited abnormally [1/1]

sending termination signals...done
sending kill signals...done
...
...

Does anyone from the anaconda development team actually read this list?

Eugeny Zadevalov wrote:
Hello All,

I've been trying to setup automatic partitioning with Kickstart.
Everything is okay until I try to run my Kickstart setup on machine with unpartitioned drives (like if partition table is broken or filled with zeros).

I'm experiencing same issue with both Centos4.6 and Centos5.1.

My goal is to get raid1 setup automatically through kickstart. Below is cut from ks.cfg:
===
zerombr
clearpart --initlabel --all
part raid.01 --size=2048 --onbiosdisk=80 --asprimary
part raid.02 --size=8192 --onbiosdisk=80 --asprimary --grow
part raid.03 --size=2048 --onbiosdisk=81 --asprimary
part raid.04 --size=8192 --onbiosdisk=81 --asprimary --grow
raid /    --level=RAID1 --device=md0 --fstype=ext3 raid.02 raid.04
raid swap --level=RAID1 --device=md1 --fstype=swap raid.01 raid.03
===

If I remove this part and run kickstarting machine over Kickstart with manual partitioning I get warning about drives needs to be initialized. That's normal I guess. But with my automatic partitioning I've "clearpart --initlabel --all" and that supposed to be initializing any/all unpartitioned drives but that's not happening. Kickstart just hangs giving bunch of errors.

If I just go ahead and do something like:
fdisk /dev/hda
w
ENTER
fdisk /dev/hdc
w
ENTER
And then try again that automatic partitioning scheme it works like expected.

I've searched over the mailling list archive but wasn't able to find anything.

For me it looks like a bug with "--initlabel" option.

Any suggestions?

Thanks!

_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list


_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list

[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux