I'm new to cobbler....
I've succeeded in creating a PXE + kickstart environment, but something odd is happening
I've run an installation (CentOS 5.6) many times now on a machine and each time it alternates creating labeling the disks as
LABEL=/ LABEL=/boot etc...
and then next time
LABEL=/1 LABEL=/boot1 etc..
alternating with whatever it was before. If I change it manually after the system comes up, the next kickstart will label it the other way. If I change one of the file system labels and leave the others, it will still label with the name other to what it was.
Here is my kickstart snippet for the disks
#System bootloader configuration bootloader --location=mbr ##Clear the Master Boot Record #zerombr yes #Disk partitioning information clearpart --linux --drives=sda part /boot --fstype ext3 --ondisk=sda --size 300 part / --fstype ext3 --ondisk=sda --size 25000 part swap --size 2048 --ondisk=sda part /var --fstype ext3 --ondisk=sda --size 2000 part /tmp --fstype ext3 --ondisk=sda --size 2000 part /scratch --fstype ext3 --ondisk=sda --size 1 --grow
It's a Dell PowerEdge and I wish to preserve the Diagnostics partition, hence the clearpart --linux am I missing something?
I have not run into this before with kickstart, outside of cobbler.
Thanks, Tony Schreiner
Hi,
On Fri, May 13, 2011 at 04:20:18PM -0400, Tony Schreiner wrote:
I'm new to cobbler....
Welcome!
I've run an installation (CentOS 5.6) many times now on a machine and each time it alternates creating labeling the disks as LABEL=/ LABEL=/boot etc... and then next time LABEL=/1 LABEL=/boot1 etc..
My guess is that anaconda detects these bevore they get removed and uses different labels then for the new partitions.
One could think of - creating a %pre script that removes the partitions, but also just a small possibility it helps you - easiest way is maybe in %post section to change the labels to what you expect.
part /boot --fstype ext3 --ondisk=sda --size 300 part / --fstype ext3 --ondisk=sda --size 25000 part swap --size 2048 --ondisk=sda part /var --fstype ext3 --ondisk=sda --size 2000 part /tmp --fstype ext3 --ondisk=sda --size 2000 part /scratch --fstype ext3 --ondisk=sda --size 1 --grow
Quite oldschool, logvol for volumes has --name .
I have not run into this before with kickstart, outside of cobbler.
Its more of a kickstart issue.
Christian
On May 13, 2011, at 4:39 PM, Christian Horn wrote:
Hi,
On Fri, May 13, 2011 at 04:20:18PM -0400, Tony Schreiner wrote:
I'm new to cobbler....
Welcome!
I've run an installation (CentOS 5.6) many times now on a machine and each time it alternates creating labeling the disks as LABEL=/ LABEL=/boot etc... and then next time LABEL=/1 LABEL=/boot1 etc..
My guess is that anaconda detects these bevore they get removed and uses different labels then for the new partitions.
One could think of
- creating a %pre script that removes the partitions, but also
just a small possibility it helps you
- easiest way is maybe in %post section to change the labels
to what you expect.
part /boot --fstype ext3 --ondisk=sda --size 300 part / --fstype ext3 --ondisk=sda --size 25000 part swap --size 2048 --ondisk=sda part /var --fstype ext3 --ondisk=sda --size 2000 part /tmp --fstype ext3 --ondisk=sda --size 2000 part /scratch --fstype ext3 --ondisk=sda --size 1 --grow
Quite oldschool, logvol for volumes has --name .
I have not run into this before with kickstart, outside of cobbler.
Its more of a kickstart issue.
Christian _______________________________________________
Thanks, I'll probably follow your recommendation and use %post.
I would have thought it was a kickstart issue too, but I was using this particular kickstart file before, and never saw that happening. Might also be new with latest CentOS. I probably won't get around to testing.
Tony
On Fri, 13 May 2011 16:20:18 -0400, Tony Schreiner tony.schreiner@bc.edu wrote:
##Clear the Master Boot Record #zerombr yes #Disk partitioning information clearpart --linux --drives=sda
Might want to say --all. I suspect it might be doing it because of that.
cobbler@lists.fedorahosted.org