Re: jumpstart Solaris 10 on Solaris 9 server
- From: lax <d_dave@xxxxxxxxxxx>
- Date: Tue, 19 Feb 2008 10:41:13 -0800 (PST)
On Jan 16, 9:26 am, d_d...@xxxxxxxxxxx wrote:
On Jan 15, 5:24 pm, Cydrome Leader <prese...@xxxxxxxxxxxxxx> wrote:
d_d...@xxxxxxxxxxx wrote:
On Jan 14, 6:30 pm, Gary Mills <mi...@xxxxxxxxxxxxxxx> wrote:
In <04deb606-2c06-498b-b4a7-c4ec3ff7d...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> d_d...@xxxxxxxxxxx writes:
I just built ajumpstartserveron aSolaris9 sun box and have had no
problems jumpstarting other sol9 boxes using the custom rules. I've
also copied aSolaris10image onto that samesolaris9serverand
have had problems loadingSolaris10. These boxes will go directly to
the manual network configuration and never check/find a rules.ok
file.
Do I need aSolaris10jumpstartserverto be serving outSolaris10?
Nope. I use aSolaris9JumpstartserverforSolaris8, 9,10, and 11,
both SPARC and x86. The setup_install_server and add_install_client
know about the differences. Check your bootparams or DHCP configuration
if the rules file is being ignored.
--
-Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
Here is the /etc/bootparams file:
agate root=jade:/opt/jumpstart/01/Solaris_10/Tools/Boot install=jade:/
opt/jumpstart/01 boottype=:in sysid_config=jade:/opt/jumpstart/01/
hosts/agate install_config=jade:/opt/jumpstart/01
rootopts=:rsize=8192
The 'boot net -v - install' helped in seeing that the sysidcfg file is
being seen:
Using sysid configuration file 192.27.176.49:/opt/jumpstart/01/hosts/
agate/sysidcfg
But the rules.ok file is still being ignored. What other files should
I be checking?
how are you running add_install_client, and are you possibly trying to
install the 08/07 or u4solaris10?
I'm installing a copy of 08/07. I do not know what u4solaris10 is.
i'm also receiving this error at times:
...Jumpstart Error:Unabletomount/cdrom/Solaris_*/Tools/Boot/usr...
the solution may be on sunsolve but i dont have access:http://sunsolve.sun.com/search/document.do?assetkey=1-25-49142-1&sear...
Here is the content for the above SunSolve link:
Resolution
2X2X3ZK Internal ID use only.
Reason:
The above error occurs due to ambiguity in resolving the directory
name " Solaris_* " located in the install image directory.
This happens if more than one file or directory exists with "
Solaris_ "
in the install image directory.
During the jumpstart, the install directory is mounted on
mountpoint: /cdrom
The problem is that the install image directory may have a link
"Solaris_2.8" to "Solaris_8"
To verify if this is the case, run the following command:
# ls -l /export/install <--assuming /export/install is the install
image directory
-r--r--r-- 1 root root 6104 Feb 12 2001 Copyright
lrwxrwxrwx 1 root other 9 Aug 24 2001 Solaris_2.8 -> Solaris_8
drwxr-xr-x 8 root root 512 Jul 1 15:28 Solaris_8
The path name the jumpstart install script looks for:
/cdrom/Solaris_*/Tools/Boot/usr
whiches causes the ambiguity in the install script not able to
resolve the image mount point.
.
- Prev by Date: Re: service listener for both IPv4 and IPv6
- Next by Date: Re: service listener for both IPv4 and IPv6
- Previous by thread: service listener for both IPv4 and IPv6
- Next by thread: SunFire V20z, SunOS 5.10, disc problem
- Index(es):
Relevant Pages
|
