HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: kickstart boot cd
Operating System - Linux
1830207
Members
1562
Online
109999
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2004 07:16 AM
10-18-2004 07:16 AM
kickstart boot cd
Hi all:
I am in the processes of trying to build a kickstart boot cd that will do a ks=nfs:x.x.x.x/export
I need to assign a static ip address since we do use dhcp.
If I boot to a standard boot cd and enter the following at the linux: prompt everything is ok
linux: ks=nfs:x.x.x.x:/export/ks.cfg ksdevice=eth0 ip=x.x.x.x gateway=x.x.x.x netmask=x.x.x.x
however, if I try to modify the isolinux.cfg with the same parameters prior to burning the iso, and boot to the install, it does NOT properly locate the ks.cfg file. from another system, I can ping hte ip, but I just cannot get it to locate the nfs export
Any hints or suggestions would be greatly appreciated
I am in the processes of trying to build a kickstart boot cd that will do a ks=nfs:x.x.x.x/export
I need to assign a static ip address since we do use dhcp.
If I boot to a standard boot cd and enter the following at the linux: prompt everything is ok
linux: ks=nfs:x.x.x.x:/export/ks.cfg ksdevice=eth0 ip=x.x.x.x gateway=x.x.x.x netmask=x.x.x.x
however, if I try to modify the isolinux.cfg with the same parameters prior to burning the iso, and boot to the install, it does NOT properly locate the ks.cfg file. from another system, I can ping hte ip, but I just cannot get it to locate the nfs export
Any hints or suggestions would be greatly appreciated
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2004 07:44 AM
10-18-2004 07:44 AM
Re: kickstart boot cd
Check the nfs permissions on the targe server:
/etc/exports
Its possible now to limit what IP addresses are allowed to make nfs connections. You may need to make sure the dhcp address you are getting is permitted on the nfs server.
exportfs -av
See if there are any errors.
If you can do an nfs mount from another machine just to verify nfs connectivity.
If there is a reject or failure, the /var/log/messages file on the target server should show it with some possibly useful information.
If you can do an ipconfig off this kickstart image, is the network mask compatible with the target server?
Is there a firewall between you and the server blocking the nfs ports?
SEP
/etc/exports
Its possible now to limit what IP addresses are allowed to make nfs connections. You may need to make sure the dhcp address you are getting is permitted on the nfs server.
exportfs -av
See if there are any errors.
If you can do an nfs mount from another machine just to verify nfs connectivity.
If there is a reject or failure, the /var/log/messages file on the target server should show it with some possibly useful information.
If you can do an ipconfig off this kickstart image, is the network mask compatible with the target server?
Is there a firewall between you and the server blocking the nfs ports?
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2004 10:49 AM
10-18-2004 10:49 AM
Re: kickstart boot cd
I've done exactally what you're trying to do (give or take explicitly defining the IP adderss details) for a KS CD:
default linux ks=nfs::/var/ftp/pub/ks.cfg
display boot.msg
F1 boot.msg
label linux
kernel vmlinuz
append initrd=initrd.img
That's the content of my 'isolinux.cfg' file in the isolinux/ structure of the CD.
If something as simple as that is failing when booting from the CD, check the 2nd/3rd/4th VTY screens for error messages (ctrl-alt-F2, F3, F4 respectivly).
If it's failing, it will tell you why there.
default linux ks=nfs:
display boot.msg
F1 boot.msg
label linux
kernel vmlinuz
append initrd=initrd.img
That's the content of my 'isolinux.cfg' file in the isolinux/ structure of the CD.
If something as simple as that is failing when booting from the CD, check the 2nd/3rd/4th VTY screens for error messages (ctrl-alt-F2, F3, F4 respectivly).
If it's failing, it will tell you why there.
One long-haired git at your service...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP