9:09 p.m.
What kind of server do you have, what is the name of your primary disk.
----- Original Message -----
From: cobbler-bounces(a)lists.fedorahosted.org
<cobbler-bounces(a)lists.fedorahosted.org>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Sent: Sat Jun 18 18:16:20 2011
Subject: partitioning scsi disk
Hello list!!
hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
I haven't as yet resolved the networking issue I was experiencing the other day. But
if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
Thanks!!
tim
## boot error
VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
## sample.ks
#platform=x86, AMD64, or Intel EM64T
# System authorization information
auth --useshadow --enablemd5
# System bootloader configuration
bootloader --location=mbr
# Partition clearing information
clearpart --all --initlabel
# Use text mode install
text
# Firewall configuration
firewall --enabled
# Run the Setup Agent on first boot
firstboot --disable
# System keyboard
keyboard us
# System language
lang en_US
# Use network installation
url --url=$tree
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
# Network information
$SNIPPET('network_config')
# Reboot after installation
reboot
#Root password
rootpw --iscrypted $default_password_crypted
# SELinux configuration
selinux --disabled
# Do not configure the X Window System
skipx
# System timezone
timezone America/New_York
# Install OS instead of upgrade
install
# Clear the Master Boot Record
zerombr
# Allow anaconda to partition the system as needed
autopart
%pre
$SNIPPET('log_ks_pre')
$kickstart_start
$SNIPPET('pre_install_network_config')
# Enable installation monitoring
$SNIPPET('pre_anamon')
%packages
$SNIPPET('func_install_if_enabled')
$SNIPPET('puppet_install_if_enabled')
%post
$SNIPPET('log_ks_post')
# Start yum configuration
$yum_config_stanza
# End yum configuration
$SNIPPET('post_install_kernel_options')
$SNIPPET('post_install_network_config')
$SNIPPET('func_register_if_enabled')
$SNIPPET('puppet_register_if_enabled')
$SNIPPET('download_config_files')
$SNIPPET('koan_environment')
$SNIPPET('redhat_register')
$SNIPPET('cobbler_register')
# Enable post-install boot notification
$SNIPPET('post_anamon')
# Start final steps
$kickstart_done
# End final steps
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
9:42 p.m.
New subject: partitioning scsi disk
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM, <marek.dohojda(a)thomsonreuters.com> wrote:
What kind of server do you have, what is the name of your primary
disk.
----- Original Message -----
From: cobbler-bounces(a)lists.fedorahosted.org
<cobbler-bounces(a)lists.fedorahosted.org>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Sent: Sat Jun 18 18:16:20 2011
Subject: partitioning scsi disk
Hello list!!
hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
I haven't as yet resolved the networking issue I was experiencing the other day. But
if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
Thanks!!
tim
## boot error
VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
## sample.ks
#platform=x86, AMD64, or Intel EM64T
# System authorization information
auth --useshadow --enablemd5
# System bootloader configuration
bootloader --location=mbr
# Partition clearing information
clearpart --all --initlabel
# Use text mode install
text
# Firewall configuration
firewall --enabled
# Run the Setup Agent on first boot
firstboot --disable
# System keyboard
keyboard us
# System language
lang en_US
# Use network installation
url --url=$tree
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
# Network information
$SNIPPET('network_config')
# Reboot after installation
reboot
#Root password
rootpw --iscrypted $default_password_crypted
# SELinux configuration
selinux --disabled
# Do not configure the X Window System
skipx
# System timezone
timezone America/New_York
# Install OS instead of upgrade
install
# Clear the Master Boot Record
zerombr
# Allow anaconda to partition the system as needed
autopart
%pre
$SNIPPET('log_ks_pre')
$kickstart_start
$SNIPPET('pre_install_network_config')
# Enable installation monitoring
$SNIPPET('pre_anamon')
%packages
$SNIPPET('func_install_if_enabled')
$SNIPPET('puppet_install_if_enabled')
%post
$SNIPPET('log_ks_post')
# Start yum configuration
$yum_config_stanza
# End yum configuration
$SNIPPET('post_install_kernel_options')
$SNIPPET('post_install_network_config')
$SNIPPET('func_register_if_enabled')
$SNIPPET('puppet_register_if_enabled')
$SNIPPET('download_config_files')
$SNIPPET('koan_environment')
$SNIPPET('redhat_register')
$SNIPPET('cobbler_register')
# Enable post-install boot notification
$SNIPPET('post_anamon')
# Start final steps
$kickstart_done
# End final steps
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
10:35 p.m.
New subject: partitioning scsi disk
Do you know the SCSI ID? What brand of hard drive? Is the optical drive
SCSI too?
The reason I'm asking is because you might have to use a specific
Kickstart syntax for partitioning SCSI disks, and the syntax may need to
know the SCSI id of the hard drive device. If you have other SCSI hard
disk machines which were partitioned successfully with Red Hat operating
systems, there is an anaconda-ks.cfg file that is saved to ~/root. You
can copy this and study the Kickstart syntax for partitioning SCSI disks.
Bob Cochran
On 6/18/11 10:42 PM, Tim Dunphy wrote:
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM,<marek.dohojda(a)thomsonreuters.com> wrote:
> What kind of server do you have, what is the name of your primary disk.
>
> ----- Original Message -----
> From:
cobbler-bounces@lists.fedorahosted.org<cobbler-bounces(a)lists.fedorahosted.org>
> To: cobbler mailing list<cobbler(a)lists.fedorahosted.org>
> Sent: Sat Jun 18 18:16:20 2011
> Subject: partitioning scsi disk
>
> Hello list!!
>
> hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
>
> I haven't as yet resolved the networking issue I was experiencing the other day.
But if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
>
> Thanks!!
>
> tim
>
>
> ## boot error
>
> VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
>
> ## sample.ks
>
> #platform=x86, AMD64, or Intel EM64T
> # System authorization information
> auth --useshadow --enablemd5
> # System bootloader configuration
> bootloader --location=mbr
> # Partition clearing information
> clearpart --all --initlabel
>
> # Use text mode install
> text
> # Firewall configuration
> firewall --enabled
> # Run the Setup Agent on first boot
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # Use network installation
> url --url=$tree
> # If any cobbler repo definitions were referenced in the kickstart profile, include
them here.
> $yum_repo_stanza
> # Network information
> $SNIPPET('network_config')
> # Reboot after installation
> reboot
>
> #Root password
> rootpw --iscrypted $default_password_crypted
> # SELinux configuration
> selinux --disabled
> # Do not configure the X Window System
> skipx
> # System timezone
> timezone America/New_York
> # Install OS instead of upgrade
> install
> # Clear the Master Boot Record
> zerombr
> # Allow anaconda to partition the system as needed
> autopart
>
>
> %pre
> $SNIPPET('log_ks_pre')
> $kickstart_start
> $SNIPPET('pre_install_network_config')
> # Enable installation monitoring
> $SNIPPET('pre_anamon')
>
> %packages
> $SNIPPET('func_install_if_enabled')
> $SNIPPET('puppet_install_if_enabled')
>
> %post
> $SNIPPET('log_ks_post')
> # Start yum configuration
> $yum_config_stanza
> # End yum configuration
> $SNIPPET('post_install_kernel_options')
> $SNIPPET('post_install_network_config')
> $SNIPPET('func_register_if_enabled')
> $SNIPPET('puppet_register_if_enabled')
> $SNIPPET('download_config_files')
> $SNIPPET('koan_environment')
> $SNIPPET('redhat_register')
> $SNIPPET('cobbler_register')
> # Enable post-install boot notification
> $SNIPPET('post_anamon')
> # Start final steps
> $kickstart_done
> # End final steps
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
11:49 a.m.
New subject: partitioning scsi disk
Hi Bob,
Sorry don't know the SCSI id and it took me a while to get physical access to the
machine to provide you with the info I do have. But it is a Seagate Cheetah Ultra320 and
the cd rom is also scsi. I since I am able to get to the machine today I will also try to
boot from dvd and run the install that way. I hope to learn the scsi syntax this way. I
will keep you posted on the results.
Thanks!
tim
----- Original Message -----
From: "Bob Cochran" <bcochran13(a)verizon.net>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Saturday, June 18, 2011 11:35:03 PM
Subject: Re: partitioning scsi disk
Do you know the SCSI ID? What brand of hard drive? Is the optical drive
SCSI too?
The reason I'm asking is because you might have to use a specific
Kickstart syntax for partitioning SCSI disks, and the syntax may need to
know the SCSI id of the hard drive device. If you have other SCSI hard
disk machines which were partitioned successfully with Red Hat operating
systems, there is an anaconda-ks.cfg file that is saved to ~/root. You
can copy this and study the Kickstart syntax for partitioning SCSI disks.
Bob Cochran
On 6/18/11 10:42 PM, Tim Dunphy wrote:
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM,<marek.dohojda(a)thomsonreuters.com> wrote:
> What kind of server do you have, what is the name of your primary disk.
>
> ----- Original Message -----
> From:
cobbler-bounces@lists.fedorahosted.org<cobbler-bounces(a)lists.fedorahosted.org>
> To: cobbler mailing list<cobbler(a)lists.fedorahosted.org>
> Sent: Sat Jun 18 18:16:20 2011
> Subject: partitioning scsi disk
>
> Hello list!!
>
> hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
>
> I haven't as yet resolved the networking issue I was experiencing the other day.
But if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
>
> Thanks!!
>
> tim
>
>
> ## boot error
>
> VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
>
> ## sample.ks
>
> #platform=x86, AMD64, or Intel EM64T
> # System authorization information
> auth --useshadow --enablemd5
> # System bootloader configuration
> bootloader --location=mbr
> # Partition clearing information
> clearpart --all --initlabel
>
> # Use text mode install
> text
> # Firewall configuration
> firewall --enabled
> # Run the Setup Agent on first boot
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # Use network installation
> url --url=$tree
> # If any cobbler repo definitions were referenced in the kickstart profile, include
them here.
> $yum_repo_stanza
> # Network information
> $SNIPPET('network_config')
> # Reboot after installation
> reboot
>
> #Root password
> rootpw --iscrypted $default_password_crypted
> # SELinux configuration
> selinux --disabled
> # Do not configure the X Window System
> skipx
> # System timezone
> timezone America/New_York
> # Install OS instead of upgrade
> install
> # Clear the Master Boot Record
> zerombr
> # Allow anaconda to partition the system as needed
> autopart
>
>
> %pre
> $SNIPPET('log_ks_pre')
> $kickstart_start
> $SNIPPET('pre_install_network_config')
> # Enable installation monitoring
> $SNIPPET('pre_anamon')
>
> %packages
> $SNIPPET('func_install_if_enabled')
> $SNIPPET('puppet_install_if_enabled')
>
> %post
> $SNIPPET('log_ks_post')
> # Start yum configuration
> $yum_config_stanza
> # End yum configuration
> $SNIPPET('post_install_kernel_options')
> $SNIPPET('post_install_network_config')
> $SNIPPET('func_register_if_enabled')
> $SNIPPET('puppet_register_if_enabled')
> $SNIPPET('download_config_files')
> $SNIPPET('koan_environment')
> $SNIPPET('redhat_register')
> $SNIPPET('cobbler_register')
> # Enable post-install boot notification
> $SNIPPET('post_anamon')
> # Start final steps
> $kickstart_done
> # End final steps
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
7:45 p.m.
New subject: partitioning scsi disk
Hello list!!
Great news! While this may be cheating a bit I did install CentOS 5.6 on the 6013-P8
supermicro I was trying to provision and grabbed the anaconda-ks.cfg file and made that
the default ks file for my rhel56 pofile. Then I went to the next server I had to
provision and it WORKS!! I can now provision both xen and hardware machines via cobbler.
This makes me very glad!
One very minute detail to work however, is that I still get prompted for the
'clearpart' answer. I was wondering if someone could please help me understand why
this part alone does not work.
Thanks the cobbler community is a tremendous asset and I genuinely appreciate your
guidance!!
# Kickstart file automatically generated by anaconda.
install
url --url=$tree
lang en_US.UTF-8
keyboard us
# Run the Setup Agent on first boot
firstboot --disable
xconfig --startxonboot
network --device eth0 --bootproto static --ip 192.168.1.48 --netmask 255.255.255.0
--gateway 192.168.1.1 --nameserver 192.168.1.44,4.2.2.2 --hostname
LCENT05.summitnjhome.com
network --device eth1 --onboot no --bootproto dhcp --hostname LCENT05.summitnjhome.com
rootpw --iscrypted $1$cFb3GUzq$HdSY6i6/lh79hbvCAD2a51
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone America/New_York
# Partition clearing information
clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --all --drives=sda
#part /boot --fstype ext3 --size=100 --ondisk=sda
#part pv.6 --size=0 --grow --ondisk=sda
#volgroup VolGroup00 --pesize=32768 pv.6
#logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow
--maxsize=5920
#logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
%packages
@admin-tools
@base
@core
@dns-server
@dialup
@editors
@ftp-server
@gnome-desktop
@games
@graphical-internet
@graphics
@kde-desktop
@legacy-network-server
@mail-server
@network-server
@news-server
@office
@printing
@server-cfg
@sound-and-video
@text-internet
@xen
@web-server
@smb-server
@base-x
puppet
koan
keyutils
kexec-tools
iscsi-initiator-utils
trousers
bridge-utils
fipscheck
device-mapper-multipath
kdegraphics
libsane-hpaio
vnc-server
kdepim
kdemultimedia
xorg-x11-server-Xnest
Tim
----- Original Message -----
From: "Tim Dunphy" <bluethundr(a)jokefire.com>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Sunday, June 19, 2011 12:49:02 PM
Subject: Re: partitioning scsi disk
Hi Bob,
Sorry don't know the SCSI id and it took me a while to get physical access to the
machine to provide you with the info I do have. But it is a Seagate Cheetah Ultra320 and
the cd rom is also scsi. I since I am able to get to the machine today I will also try to
boot from dvd and run the install that way. I hope to learn the scsi syntax this way. I
will keep you posted on the results.
Thanks!
tim
----- Original Message -----
From: "Bob Cochran" <bcochran13(a)verizon.net>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Saturday, June 18, 2011 11:35:03 PM
Subject: Re: partitioning scsi disk
Do you know the SCSI ID? What brand of hard drive? Is the optical drive
SCSI too?
The reason I'm asking is because you might have to use a specific
Kickstart syntax for partitioning SCSI disks, and the syntax may need to
know the SCSI id of the hard drive device. If you have other SCSI hard
disk machines which were partitioned successfully with Red Hat operating
systems, there is an anaconda-ks.cfg file that is saved to ~/root. You
can copy this and study the Kickstart syntax for partitioning SCSI disks.
Bob Cochran
On 6/18/11 10:42 PM, Tim Dunphy wrote:
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM,<marek.dohojda(a)thomsonreuters.com> wrote:
> What kind of server do you have, what is the name of your primary disk.
>
> ----- Original Message -----
> From:
cobbler-bounces@lists.fedorahosted.org<cobbler-bounces(a)lists.fedorahosted.org>
> To: cobbler mailing list<cobbler(a)lists.fedorahosted.org>
> Sent: Sat Jun 18 18:16:20 2011
> Subject: partitioning scsi disk
>
> Hello list!!
>
> hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
>
> I haven't as yet resolved the networking issue I was experiencing the other day.
But if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
>
> Thanks!!
>
> tim
>
>
> ## boot error
>
> VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
>
> ## sample.ks
>
> #platform=x86, AMD64, or Intel EM64T
> # System authorization information
> auth --useshadow --enablemd5
> # System bootloader configuration
> bootloader --location=mbr
> # Partition clearing information
> clearpart --all --initlabel
>
> # Use text mode install
> text
> # Firewall configuration
> firewall --enabled
> # Run the Setup Agent on first boot
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # Use network installation
> url --url=$tree
> # If any cobbler repo definitions were referenced in the kickstart profile, include
them here.
> $yum_repo_stanza
> # Network information
> $SNIPPET('network_config')
> # Reboot after installation
> reboot
>
> #Root password
> rootpw --iscrypted $default_password_crypted
> # SELinux configuration
> selinux --disabled
> # Do not configure the X Window System
> skipx
> # System timezone
> timezone America/New_York
> # Install OS instead of upgrade
> install
> # Clear the Master Boot Record
> zerombr
> # Allow anaconda to partition the system as needed
> autopart
>
>
> %pre
> $SNIPPET('log_ks_pre')
> $kickstart_start
> $SNIPPET('pre_install_network_config')
> # Enable installation monitoring
> $SNIPPET('pre_anamon')
>
> %packages
> $SNIPPET('func_install_if_enabled')
> $SNIPPET('puppet_install_if_enabled')
>
> %post
> $SNIPPET('log_ks_post')
> # Start yum configuration
> $yum_config_stanza
> # End yum configuration
> $SNIPPET('post_install_kernel_options')
> $SNIPPET('post_install_network_config')
> $SNIPPET('func_register_if_enabled')
> $SNIPPET('puppet_register_if_enabled')
> $SNIPPET('download_config_files')
> $SNIPPET('koan_environment')
> $SNIPPET('redhat_register')
> $SNIPPET('cobbler_register')
> # Enable post-install boot notification
> $SNIPPET('post_anamon')
> # Start final steps
> $kickstart_done
> # End final steps
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
11:39 a.m.
New subject: partitioning scsi disk
Are you saying that you have this in your kickstart but it isn't working?
clearpart --all --initlabel
zerombr yes
As to your disk, I am guessing that you have sda (i.e. first SCSI disk is yours). If that
is the case you can do this:
clearpart --all --init-label --driveorder=sda
Then you do this:
part /boot (or whatever) <than your size type etc..> and --ondisk=sda
That should work for you.
Marek Dohojda
720-308-8622
77 68 6f 20 69 73 20 4a 6f 68 6e 20 47 61 6c 74 3f 0d 0a
-----Original Message-----
From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Tim Dunphy
Sent: Sunday, June 19, 2011 6:45 PM
To: cobbler mailing list
Subject: Re: partitioning scsi disk
Hello list!!
Great news! While this may be cheating a bit I did install CentOS 5.6 on the 6013-P8
supermicro I was trying to provision and grabbed the anaconda-ks.cfg file and made that
the default ks file for my rhel56 pofile. Then I went to the next server I had to
provision and it WORKS!! I can now provision both xen and hardware machines via cobbler.
This makes me very glad!
One very minute detail to work however, is that I still get prompted for the
'clearpart' answer. I was wondering if someone could please help me understand why
this part alone does not work.
Thanks the cobbler community is a tremendous asset and I genuinely appreciate your
guidance!!
# Kickstart file automatically generated by anaconda.
install
url --url=$tree
lang en_US.UTF-8
keyboard us
# Run the Setup Agent on first boot
firstboot --disable
xconfig --startxonboot
network --device eth0 --bootproto static --ip 192.168.1.48 --netmask 255.255.255.0
--gateway 192.168.1.1 --nameserver 192.168.1.44,4.2.2.2 --hostname
LCENT05.summitnjhome.com
network --device eth1 --onboot no --bootproto dhcp --hostname LCENT05.summitnjhome.com
rootpw --iscrypted $1$cFb3GUzq$HdSY6i6/lh79hbvCAD2a51
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone America/New_York
# Partition clearing information
clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --all --drives=sda
#part /boot --fstype ext3 --size=100 --ondisk=sda
#part pv.6 --size=0 --grow --ondisk=sda
#volgroup VolGroup00 --pesize=32768 pv.6
#logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow
--maxsize=5920
#logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
%packages
@admin-tools
@base
@core
@dns-server
@dialup
@editors
@ftp-server
@gnome-desktop
@games
@graphical-internet
@graphics
@kde-desktop
@legacy-network-server
@mail-server
@network-server
@news-server
@office
@printing
@server-cfg
@sound-and-video
@text-internet
@xen
@web-server
@smb-server
@base-x
puppet
koan
keyutils
kexec-tools
iscsi-initiator-utils
trousers
bridge-utils
fipscheck
device-mapper-multipath
kdegraphics
libsane-hpaio
vnc-server
kdepim
kdemultimedia
xorg-x11-server-Xnest
Tim
----- Original Message -----
From: "Tim Dunphy" <bluethundr(a)jokefire.com>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Sunday, June 19, 2011 12:49:02 PM
Subject: Re: partitioning scsi disk
Hi Bob,
Sorry don't know the SCSI id and it took me a while to get physical access to the
machine to provide you with the info I do have. But it is a Seagate Cheetah Ultra320 and
the cd rom is also scsi. I since I am able to get to the machine today I will also try to
boot from dvd and run the install that way. I hope to learn the scsi syntax this way. I
will keep you posted on the results.
Thanks!
tim
----- Original Message -----
From: "Bob Cochran" <bcochran13(a)verizon.net>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Saturday, June 18, 2011 11:35:03 PM
Subject: Re: partitioning scsi disk
Do you know the SCSI ID? What brand of hard drive? Is the optical drive
SCSI too?
The reason I'm asking is because you might have to use a specific
Kickstart syntax for partitioning SCSI disks, and the syntax may need to
know the SCSI id of the hard drive device. If you have other SCSI hard
disk machines which were partitioned successfully with Red Hat operating
systems, there is an anaconda-ks.cfg file that is saved to ~/root. You
can copy this and study the Kickstart syntax for partitioning SCSI disks.
Bob Cochran
On 6/18/11 10:42 PM, Tim Dunphy wrote:
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM,<marek.dohojda(a)thomsonreuters.com> wrote:
> What kind of server do you have, what is the name of your primary disk.
>
> ----- Original Message -----
> From:
cobbler-bounces@lists.fedorahosted.org<cobbler-bounces(a)lists.fedorahosted.org>
> To: cobbler mailing list<cobbler(a)lists.fedorahosted.org>
> Sent: Sat Jun 18 18:16:20 2011
> Subject: partitioning scsi disk
>
> Hello list!!
>
> hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
>
> I haven't as yet resolved the networking issue I was experiencing the other day.
But if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
>
> Thanks!!
>
> tim
>
>
> ## boot error
>
> VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
>
> ## sample.ks
>
> #platform=x86, AMD64, or Intel EM64T
> # System authorization information
> auth --useshadow --enablemd5
> # System bootloader configuration
> bootloader --location=mbr
> # Partition clearing information
> clearpart --all --initlabel
>
> # Use text mode install
> text
> # Firewall configuration
> firewall --enabled
> # Run the Setup Agent on first boot
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # Use network installation
> url --url=$tree
> # If any cobbler repo definitions were referenced in the kickstart profile, include
them here.
> $yum_repo_stanza
> # Network information
> $SNIPPET('network_config')
> # Reboot after installation
> reboot
>
> #Root password
> rootpw --iscrypted $default_password_crypted
> # SELinux configuration
> selinux --disabled
> # Do not configure the X Window System
> skipx
> # System timezone
> timezone America/New_York
> # Install OS instead of upgrade
> install
> # Clear the Master Boot Record
> zerombr
> # Allow anaconda to partition the system as needed
> autopart
>
>
> %pre
> $SNIPPET('log_ks_pre')
> $kickstart_start
> $SNIPPET('pre_install_network_config')
> # Enable installation monitoring
> $SNIPPET('pre_anamon')
>
> %packages
> $SNIPPET('func_install_if_enabled')
> $SNIPPET('puppet_install_if_enabled')
>
> %post
> $SNIPPET('log_ks_post')
> # Start yum configuration
> $yum_config_stanza
> # End yum configuration
> $SNIPPET('post_install_kernel_options')
> $SNIPPET('post_install_network_config')
> $SNIPPET('func_register_if_enabled')
> $SNIPPET('puppet_register_if_enabled')
> $SNIPPET('download_config_files')
> $SNIPPET('koan_environment')
> $SNIPPET('redhat_register')
> $SNIPPET('cobbler_register')
> # Enable post-install boot notification
> $SNIPPET('post_anamon')
> # Start final steps
> $kickstart_done
> # End final steps
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
1:41 p.m.
New subject: partitioning scsi disk
Awseome, marek! thank you so much for your help!
----- Original Message -----
From: "marek dohojda" <marek.dohojda(a)thomsonreuters.com>
To: cobbler(a)lists.fedorahosted.org
Sent: Monday, June 20, 2011 12:39:31 PM
Subject: RE: partitioning scsi disk
Are you saying that you have this in your kickstart but it isn't working?
clearpart --all --initlabel
zerombr yes
As to your disk, I am guessing that you have sda (i.e. first SCSI disk is yours). If that
is the case you can do this:
clearpart --all --init-label --driveorder=sda
Then you do this:
part /boot (or whatever) <than your size type etc..> and --ondisk=sda
That should work for you.
Marek Dohojda
720-308-8622
77 68 6f 20 69 73 20 4a 6f 68 6e 20 47 61 6c 74 3f 0d 0a
-----Original Message-----
From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Tim Dunphy
Sent: Sunday, June 19, 2011 6:45 PM
To: cobbler mailing list
Subject: Re: partitioning scsi disk
Hello list!!
Great news! While this may be cheating a bit I did install CentOS 5.6 on the 6013-P8
supermicro I was trying to provision and grabbed the anaconda-ks.cfg file and made that
the default ks file for my rhel56 pofile. Then I went to the next server I had to
provision and it WORKS!! I can now provision both xen and hardware machines via cobbler.
This makes me very glad!
One very minute detail to work however, is that I still get prompted for the
'clearpart' answer. I was wondering if someone could please help me understand why
this part alone does not work.
Thanks the cobbler community is a tremendous asset and I genuinely appreciate your
guidance!!
# Kickstart file automatically generated by anaconda.
install
url --url=$tree
lang en_US.UTF-8
keyboard us
# Run the Setup Agent on first boot
firstboot --disable
xconfig --startxonboot
network --device eth0 --bootproto static --ip 192.168.1.48 --netmask 255.255.255.0
--gateway 192.168.1.1 --nameserver 192.168.1.44,4.2.2.2 --hostname
LCENT05.summitnjhome.com
network --device eth1 --onboot no --bootproto dhcp --hostname LCENT05.summitnjhome.com
rootpw --iscrypted $1$cFb3GUzq$HdSY6i6/lh79hbvCAD2a51
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone America/New_York
# Partition clearing information
clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --all --drives=sda
#part /boot --fstype ext3 --size=100 --ondisk=sda
#part pv.6 --size=0 --grow --ondisk=sda
#volgroup VolGroup00 --pesize=32768 pv.6
#logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow
--maxsize=5920
#logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
%packages
@admin-tools
@base
@core
@dns-server
@dialup
@editors
@ftp-server
@gnome-desktop
@games
@graphical-internet
@graphics
@kde-desktop
@legacy-network-server
@mail-server
@network-server
@news-server
@office
@printing
@server-cfg
@sound-and-video
@text-internet
@xen
@web-server
@smb-server
@base-x
puppet
koan
keyutils
kexec-tools
iscsi-initiator-utils
trousers
bridge-utils
fipscheck
device-mapper-multipath
kdegraphics
libsane-hpaio
vnc-server
kdepim
kdemultimedia
xorg-x11-server-Xnest
Tim
----- Original Message -----
From: "Tim Dunphy" <bluethundr(a)jokefire.com>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Sunday, June 19, 2011 12:49:02 PM
Subject: Re: partitioning scsi disk
Hi Bob,
Sorry don't know the SCSI id and it took me a while to get physical access to the
machine to provide you with the info I do have. But it is a Seagate Cheetah Ultra320 and
the cd rom is also scsi. I since I am able to get to the machine today I will also try to
boot from dvd and run the install that way. I hope to learn the scsi syntax this way. I
will keep you posted on the results.
Thanks!
tim
----- Original Message -----
From: "Bob Cochran" <bcochran13(a)verizon.net>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Saturday, June 18, 2011 11:35:03 PM
Subject: Re: partitioning scsi disk
Do you know the SCSI ID? What brand of hard drive? Is the optical drive
SCSI too?
The reason I'm asking is because you might have to use a specific
Kickstart syntax for partitioning SCSI disks, and the syntax may need to
know the SCSI id of the hard drive device. If you have other SCSI hard
disk machines which were partitioned successfully with Red Hat operating
systems, there is an anaconda-ks.cfg file that is saved to ~/root. You
can copy this and study the Kickstart syntax for partitioning SCSI disks.
Bob Cochran
On 6/18/11 10:42 PM, Tim Dunphy wrote:
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM,<marek.dohojda(a)thomsonreuters.com> wrote:
> What kind of server do you have, what is the name of your primary disk.
>
> ----- Original Message -----
> From:
cobbler-bounces@lists.fedorahosted.org<cobbler-bounces(a)lists.fedorahosted.org>
> To: cobbler mailing list<cobbler(a)lists.fedorahosted.org>
> Sent: Sat Jun 18 18:16:20 2011
> Subject: partitioning scsi disk
>
> Hello list!!
>
> hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
>
> I haven't as yet resolved the networking issue I was experiencing the other day.
But if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
>
> Thanks!!
>
> tim
>
>
> ## boot error
>
> VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
>
> ## sample.ks
>
> #platform=x86, AMD64, or Intel EM64T
> # System authorization information
> auth --useshadow --enablemd5
> # System bootloader configuration
> bootloader --location=mbr
> # Partition clearing information
> clearpart --all --initlabel
>
> # Use text mode install
> text
> # Firewall configuration
> firewall --enabled
> # Run the Setup Agent on first boot
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # Use network installation
> url --url=$tree
> # If any cobbler repo definitions were referenced in the kickstart profile, include
them here.
> $yum_repo_stanza
> # Network information
> $SNIPPET('network_config')
> # Reboot after installation
> reboot
>
> #Root password
> rootpw --iscrypted $default_password_crypted
> # SELinux configuration
> selinux --disabled
> # Do not configure the X Window System
> skipx
> # System timezone
> timezone America/New_York
> # Install OS instead of upgrade
> install
> # Clear the Master Boot Record
> zerombr
> # Allow anaconda to partition the system as needed
> autopart
>
>
> %pre
> $SNIPPET('log_ks_pre')
> $kickstart_start
> $SNIPPET('pre_install_network_config')
> # Enable installation monitoring
> $SNIPPET('pre_anamon')
>
> %packages
> $SNIPPET('func_install_if_enabled')
> $SNIPPET('puppet_install_if_enabled')
>
> %post
> $SNIPPET('log_ks_post')
> # Start yum configuration
> $yum_config_stanza
> # End yum configuration
> $SNIPPET('post_install_kernel_options')
> $SNIPPET('post_install_network_config')
> $SNIPPET('func_register_if_enabled')
> $SNIPPET('puppet_register_if_enabled')
> $SNIPPET('download_config_files')
> $SNIPPET('koan_environment')
> $SNIPPET('redhat_register')
> $SNIPPET('cobbler_register')
> # Enable post-install boot notification
> $SNIPPET('post_anamon')
> # Start final steps
> $kickstart_done
> # End final steps
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
3:21 p.m.
New subject: partitioning scsi disk
Tim,
You should be getting prompted for all your partitioning information...try the following
(I uncommented the partition setup):
# Kickstart file automatically generated by anaconda.
install
url --url=$tree
lang en_US.UTF-8
keyboard us
# Run the Setup Agent on first boot
firstboot --disable
xconfig --startxonboot
network
--device eth0 --bootproto static --ip 192.168.1.48 --netmask
255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.44,4.2.2.2
--hostname LCENT05.summitnjhome.com
network --device eth1 --onboot no --bootproto dhcp --hostname LCENT05.summitnjhome.com
rootpw --iscrypted $1$cFb3GUzq$HdSY6i6/lh79hbvCAD2a51
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone America/New_York
# Partition clearing information
#clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --all --drives=sda
part /boot --fstype ext3 --size=100 --ondisk=sda
part pv.6 --size=0 --grow --ondisk=sda
volgroup VolGroup00 --pesize=32768 pv.6
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow
--maxsize=5920
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
%packages
@admin-tools
@base
@core
@dns-server
@dialup
@editors
@ftp-server
@gnome-desktop
@games
@graphical-internet
@graphics
@kde-desktop
@legacy-network-server
@mail-server
@network-server
@news-server
@office
@printing
@server-cfg
@sound-and-video
@text-internet
@xen
@web-server
@smb-server
@base-x
puppet
koan
keyutils
kexec-tools
iscsi-initiator-utils
trousers
bridge-utils
fipscheck
device-mapper-multipath
kdegraphics
libsane-hpaio
vnc-server
kdepim
kdemultimedia
xorg-x11-server-Xnest
--- On Sun, 6/19/11, Tim Dunphy <bluethundr(a)jokefire.com> wrote:
From: Tim Dunphy <bluethundr(a)jokefire.com>
Subject: Re: partitioning scsi disk
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Date: Sunday, June 19, 2011, 8:45 PM
Hello list!!
Great news! While this may be cheating a bit I did install CentOS 5.6 on the 6013-P8
supermicro I was trying to provision and grabbed the anaconda-ks.cfg file and made that
the default ks file for my rhel56 pofile. Then I went to the next server I had to
provision and it WORKS!! I can now provision both xen and hardware machines via cobbler.
This makes me very glad!
One very minute detail to work however, is that I still get prompted for the
'clearpart' answer. I was wondering if someone could please help me understand why
this part alone does not work.
Thanks the cobbler community is a tremendous asset and I genuinely appreciate your
guidance!!
# Kickstart file automatically generated by anaconda.
install
url --url=$tree
lang en_US.UTF-8
keyboard us
# Run the Setup Agent on first boot
firstboot --disable
xconfig --startxonboot
network --device eth0 --bootproto static --ip 192.168.1.48 --netmask 255.255.255.0
--gateway 192.168.1.1 --nameserver 192.168.1.44,4.2.2.2 --hostname
LCENT05.summitnjhome.com
network --device eth1 --onboot no --bootproto dhcp --hostname LCENT05.summitnjhome.com
rootpw --iscrypted $1$cFb3GUzq$HdSY6i6/lh79hbvCAD2a51
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone America/New_York
# Partition clearing information
clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --all --drives=sda
#part /boot --fstype ext3 --size=100 --ondisk=sda
#part pv.6 --size=0 --grow --ondisk=sda
#volgroup VolGroup00 --pesize=32768 pv.6
#logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow
--maxsize=5920
#logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
%packages
@admin-tools
@base
@core
@dns-server
@dialup
@editors
@ftp-server
@gnome-desktop
@games
@graphical-internet
@graphics
@kde-desktop
@legacy-network-server
@mail-server
@network-server
@news-server
@office
@printing
@server-cfg
@sound-and-video
@text-internet
@xen
@web-server
@smb-server
@base-x
puppet
koan
keyutils
kexec-tools
iscsi-initiator-utils
trousers
bridge-utils
fipscheck
device-mapper-multipath
kdegraphics
libsane-hpaio
vnc-server
kdepim
kdemultimedia
xorg-x11-server-Xnest
Tim
----- Original Message -----
From: "Tim Dunphy" <bluethundr(a)jokefire.com>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Sunday, June 19, 2011 12:49:02 PM
Subject: Re: partitioning scsi disk
Hi Bob,
Sorry don't know the SCSI id and it took me a while to get physical access to the
machine to provide you with the info I do have. But it is a Seagate Cheetah Ultra320 and
the cd rom is also scsi. I since I am able to get to the machine today I will also try to
boot from dvd and run the install that way. I hope to learn the scsi syntax this way. I
will keep you posted on the results.
Thanks!
tim
----- Original Message -----
From: "Bob Cochran" <bcochran13(a)verizon.net>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Saturday, June 18, 2011 11:35:03 PM
Subject: Re: partitioning scsi disk
Do you know the SCSI ID? What brand of hard drive? Is the optical drive
SCSI too?
The reason I'm asking is because you might have to use a specific
Kickstart syntax for partitioning SCSI disks, and the syntax may need to
know the SCSI id of the hard drive device. If you have other SCSI hard
disk machines which were partitioned successfully with Red Hat operating
systems, there is an anaconda-ks.cfg file that is saved to ~/root. You
can copy this and study the Kickstart syntax for partitioning SCSI disks.
Bob Cochran
On 6/18/11 10:42 PM, Tim Dunphy wrote:
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM,<marek.dohojda(a)thomsonreuters.com> wrote:
> What kind of server do you have, what is the name of your primary disk.
>
> ----- Original Message -----
> From:
cobbler-bounces@lists.fedorahosted.org<cobbler-bounces(a)lists.fedorahosted.org>
> To: cobbler mailing list<cobbler(a)lists.fedorahosted.org>
> Sent: Sat Jun 18 18:16:20 2011
> Subject: partitioning scsi disk
>
> Hello list!!
>
> hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
>
> I haven't as yet resolved the networking issue I was experiencing the other day.
But if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
>
> Thanks!!
>
> tim
>
>
> ## boot error
>
> VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
>
> ## sample.ks
>
> #platform=x86, AMD64, or Intel EM64T
> # System authorization information
> auth --useshadow --enablemd5
> # System bootloader configuration
> bootloader --location=mbr
> # Partition clearing information
> clearpart --all --initlabel
>
> # Use text mode install
> text
> # Firewall configuration
> firewall --enabled
> # Run the Setup Agent on first boot
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # Use network installation
> url --url=$tree
> # If any cobbler repo definitions were referenced in the kickstart profile, include
them here.
> $yum_repo_stanza
> # Network information
> $SNIPPET('network_config')
> # Reboot after installation
> reboot
>
> #Root password
> rootpw --iscrypted $default_password_crypted
> # SELinux configuration
> selinux --disabled
> # Do not configure the X Window System
> skipx
> # System timezone
> timezone America/New_York
> # Install OS instead of upgrade
> install
> # Clear the Master Boot Record
> zerombr
> # Allow anaconda to partition the system as needed
> autopart
>
>
> %pre
> $SNIPPET('log_ks_pre')
> $kickstart_start
> $SNIPPET('pre_install_network_config')
> # Enable installation monitoring
> $SNIPPET('pre_anamon')
>
> %packages
> $SNIPPET('func_install_if_enabled')
> $SNIPPET('puppet_install_if_enabled')
>
> %post
> $SNIPPET('log_ks_post')
> # Start yum configuration
> $yum_config_stanza
> # End yum configuration
> $SNIPPET('post_install_kernel_options')
> $SNIPPET('post_install_network_config')
> $SNIPPET('func_register_if_enabled')
> $SNIPPET('puppet_register_if_enabled')
> $SNIPPET('download_config_files')
> $SNIPPET('koan_environment')
> $SNIPPET('redhat_register')
> $SNIPPET('cobbler_register')
> # Enable post-install boot notification
> $SNIPPET('post_anamon')
> # Start final steps
> $kickstart_done
> # End final steps
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
4:14 p.m.
New subject: partitioning scsi disk
This is great tim! I will try this sometime tonight.. best wishes!
tim
----- Original Message -----
From: "Tim Tass" <tptass(a)yahoo.com>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Monday, June 20, 2011 4:21:37 PM
Subject: Re: partitioning scsi disk
Tim,
You should be getting prompted for all your partitioning information...try the following
(I uncommented the partition setup):
# Kickstart file automatically generated by anaconda .
install
url --url=$tree
lang en_US.UTF-8
keyboard us
# Run the Setup Agent on first boot
firstboot --disable
xconfig --startxonboot
network --device eth0 --bootproto static --ip 192.168.1.48 --netmask 255.255.255.0
--gateway 192.168.1.1 --nameserver 192.168.1.44,4.2.2.2 --hostname
LCENT05.summitnjhome.com
network --device eth1 --onboot no --bootproto dhcp --hostname LCENT05.summitnjhome.com
rootpw --iscrypted $1$cFb3GUzq$HdSY6i6/lh79hbvCAD2a51
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone America/New_York
# Partition clearing information
#clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --all --drives=sda
part /boot --fstype ext3 --size=100 --ondisk=sda
part pv.6 --size=0 --grow --ondisk=sda
volgroup VolGroup00 --pesize=32768 pv.6
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow
--maxsize=5920
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
%packages
@admin-tools
@base
@core
@dns-server
@dialup
@editors
@ftp-server
@gnome-desktop
@games
@graphical-internet
@graphics
@kde-desktop
@legacy-network-server
@mail-server
@network-server
@news-server
@office
@printing
@server-cfg
@sound-and-video
@text-internet
@xen
@web-server
@smb-server
@base-x
puppet
koan
keyutils
kexec-tools
iscsi-initiator-utils
trousers
bridge-utils
fipscheck
device-mapper-multipath
kdegraphics
libsane-hpaio
vnc-server
kdepim
kdemultimedia
xorg-x11-server-Xnest
--- On Sun, 6/19/11, Tim Dunphy <bluethundr(a)jokefire.com> wrote:
From: Tim Dunphy <bluethundr(a)jokefire.com>
Subject: Re: partitioning scsi disk
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Date: Sunday, June 19, 2011, 8:45 PM
Hello list!!
Great news! While this may be cheating a bit I did install CentOS 5.6 on the 6013-P8
supermicro I was trying to provision and grabbed the anaconda-ks.cfg file and made that
the default ks file for my rhel56 pofile. Then I went to the next server I had to
provision and it WORKS!! I can now provision both xen and hardware machines via cobbler.
This makes me very glad!
One very minute detail to work however, is that I still get prompted for the
'clearpart' answer. I was wondering if someone could please help me understand why
this part alone does not work.
Thanks the cobbler community is a tremendous asset and I genuinely appreciate your
guidance!!
# Kickstart file automatically generated by anaconda.
install
url --url=$tree
lang en_US.UTF-8
keyboard us
# Run the Setup Agent on first boot
firstboot --disable
xconfig --startxonboot
network --device eth0 --bootproto static --ip 192.168.1.48 --netmask 255.255.255.0
--gateway 192.168.1.1 --nameserver 192.168.1.44,4.2.2.2 --hostname
LCENT05.summitnjhome.com
network --device eth1 --onboot no --bootproto dhcp --hostname LCENT05.summitnjhome.com
rootpw --iscrypted $1$cFb3GUzq$HdSY6i6/lh79hbvCAD2a51
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone America/New_York
# Partition clearing information
clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --all --drives=sda
#part /boot --fstype ext3 --size=100 --ondisk=sda
#part pv.6 --size=0 --grow --ondisk=sda
#volgroup VolGroup00 --pesize=32768 pv.6
#logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow
--maxsize=5920
#logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
# If any cobbler repo definitions were referenced in the kickstart profile, include them
here.
$yum_repo_stanza
%packages
@admin-tools
@base
@core
@dns-server
@dialup
@editors
@ftp-server
@gnome-desktop
@games
@graphical-internet
@graphics
@kde-desktop
@legacy-network-server
@mail-server
@network-server
@news-server
@office
@printing
@server-cfg
@sound-and-video
@text-internet
@xen
@web-server
@smb-server
@base-x
puppet
koan
keyutils
kexec-tools
iscsi-initiator-utils
trousers
bridge-utils
fipscheck
device-mapper-multipath
kdegraphics
libsane-hpaio
vnc-server
kdepim
kdemultimedia
xorg-x11-server-Xnest
Tim
----- Original Message -----
From: "Tim Dunphy" < bluethundr(a)jokefire.com >
To: "cobbler mailing list" < cobbler(a)lists.fedorahosted.org >
Sent: Sunday, June 19, 2011 12:49:02 PM
Subject: Re: partitioning scsi disk
Hi Bob,
Sorry don't know the SCSI id and it took me a while to get physical access to the
machine to provide you with the info I do have. But it is a Seagate Cheetah Ultra320 and
the cd rom is also scsi. I since I am able to get to the machine today I will also try to
boot from dvd and run the install that way. I hope to learn the scsi syntax this way. I
will keep you posted on the results.
Thanks!
tim
----- Original Message -----
From: "Bob Cochran" < bcochran13(a)verizon.net >
To: "cobbler mailing list" < cobbler(a)lists.fedorahosted.org >
Sent: Saturday, June 18, 2011 11:35:03 PM
Subject: Re: partitioning scsi disk
Do you know the SCSI ID? What brand of hard drive? Is the optical drive
SCSI too?
The reason I'm asking is because you might have to use a specific
Kickstart syntax for partitioning SCSI disks, and the syntax may need to
know the SCSI id of the hard drive device. If you have other SCSI hard
disk machines which were partitioned successfully with Red Hat operating
systems, there is an anaconda-ks.cfg file that is saved to ~/root. You
can copy this and study the Kickstart syntax for partitioning SCSI disks.
Bob Cochran
On 6/18/11 10:42 PM, Tim Dunphy wrote:
Hi marek,
It's a supermicro 6013-p8 with a scsi 320 hd. I'm not aware of the disk having a
name.
Tx!
Tim
Sent from my iPhone
On Jun 18, 2011, at 10:09 PM,< marek.dohojda(a)thomsonreuters.com > wrote:
> What kind of server do you have, what is the name of your primary disk.
>
> ----- Original Message -----
> From: cobbler-bounces(a)lists.fedorahosted.org <
cobbler-bounces(a)lists.fedorahosted.org >
> To: cobbler mailing list< cobbler(a)lists.fedorahosted.org >
> Sent: Sat Jun 18 18:16:20 2011
> Subject: partitioning scsi disk
>
> Hello list!!
>
> hey guys.. I am attempting to provision a physical server, and just to get the ball
rolling I tried to use the sample.ks file. but unfortunately when I boot the device it is
unable to find it's root device and kernel panics. I was wondering if I could get a
tip on how to partition a scsi drive.
>
> I haven't as yet resolved the networking issue I was experiencing the other day.
But if I use the url --url=$tree option the installation seems to go smoothly. Not sure
however why that would work and NFS and an external url wouldn't. Might be a routing
issue with the dns server. But as the --url=$tree option is working now I'd like to
try and focus on the partitioning aspect I am now experiencing.
>
> Thanks!!
>
> tim
>
>
> ## boot error
>
> VFS Cannot open root device VolgGroup00/LogVol00" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)
>
> ## sample.ks
>
> #platform=x86, AMD64, or Intel EM64T
> # System authorization information
> auth --useshadow --enablemd5
> # System bootloader configuration
> bootloader --location=mbr
> # Partition clearing information
> clearpart --all --initlabel
>
> # Use text mode install
> text
> # Firewall configuration
> firewall --enabled
> # Run the Setup Agent on first boot
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # Use network installation
> url --url=$tree
> # If any cobbler repo definitions were referenced in the kickstart profile, include
them here.
> $yum_repo_stanza
> # Network information
> $SNIPPET('network_config')
> # Reboot after installation
> reboot
>
> #Root password
> rootpw --iscrypted $default_password_crypted
> # SELinux configuration
> selinux --disabled
> # Do not configure the X Window System
> skipx
> # System timezone
> timezone America/New_York
> # Install OS instead of upgrade
> install
> # Clear the Master Boot Record
> zerombr
> # Allow anaconda to partition the system as needed
> autopart
>
>
> %pre
> $SNIPPET('log_ks_pre')
> $kickstart_start
> $SNIPPET('pre_install_network_config')
> # Enable installation monitoring
> $SNIPPET('pre_anamon')
>
> %packages
> $SNIPPET('func_install_if_enabled')
> $SNIPPET('puppet_install_if_enabled')
>
> %post
> $SNIPPET('log_ks_post')
> # Start yum configuration
> $yum_config_stanza
> # End yum configuration
> $SNIPPET('post_install_kernel_options')
> $SNIPPET('post_install_network_config')
> $SNIPPET('func_register_if_enabled')
> $SNIPPET('puppet_register_if_enabled')
> $SNIPPET('download_config_files')
> $SNIPPET('koan_environment')
> $SNIPPET('redhat_register')
> $SNIPPET('cobbler_register')
> # Enable post-install boot notification
> $SNIPPET('post_anamon')
> # Start final steps
> $kickstart_done
> # End final steps
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
4718
days inactive
4719
days old
cobbler@lists.fedorahosted.org
8 comments
5 participants
participants (5)
-
Bob Cochran -
marek.dohojda＠thomsonreuters.com -
Tim Dunphy -
Tim Dunphy -
Tim Tass