Solaris 10custom JumpStart problems
Hi Folks,
I'm using a custom JumpStart script to try to carry out a disaster recovery strategy.
The custom script labels & formats c0t0d0s0 which will become my root filesystem disk, mounts c0t0d0s0 on mountpoint /a
The custom script then runs our third party backup / restore software to recover from a full system backup.
This works well on our Sol8 & Sol9 systems and gets us up & running with a fully patched & operating Solaris system much more quickly than a re-install from scratch.
However on our Solaris 10 system the third party restore software doesn't seem to be able to write to /a -- It just reports enormous numbers of "Can't write -- Permission Denied" messages.
Does JumpStart not run with root permissions on Sol 10?
Any other suggestions?
Many thanks in advance
Kevin
[866 byte] By [
Kevin_N] at [2007-11-26 8:29:59]
# 1
Jumpstart runs as root.
If I had to make a guess I would say that probably
/a is not mount and therefore resides on the read-only NFS server.
You should verify that in Solairs 10 the disk that once showed up as c0t0d0 in previous OS still retains that controller number. You should "boot net -s" to get to single user the type "format" to verify the controller number of the device you are trying to use.
cg
# 2
I think I've found part of the problem
I have an entry in /etc/dfs/dfstab on the Jumpstart Server along the lines of ...
share -F nfs -o ro,anon=0 /usr
I then mount /usr (of the Jumpstart Server) on /usr (Of the temporary Jumpstart Filesystem) to allow me to run my third party software.
Unfortunately if I have a look at /usr during the Jumpstart process the ownership of all the files seems to be set to
nobody nobody
This seems to be why my software can't recover anything from the backup.
From my (extremely limited) understanding of the entries in dfstab the "anon=0" bit should give anonymous users root priviledges to the shared directory.
Any ideas what's going wrong here ?
Many thanks in advance
Kevin
# 5
Just an update...
I've used the fully qualified domain name in /etc/ethers and /etc/hosts on the Jumpstart Server.
I've used the same thing in the rules file (and re-run the check script to re-create rules.ok)
I've tried setting nfs4_domain in my sysidcfg file
When I Jumpstart my client my custom Jumpstart Script gives me an xterm window.
At this point I can call "domainname" and it reports the correct domain name.
But if I change directory to / & do "ls -l" the system still reports /usr as belonging to nobody.
Any ideas as to what's going wrong?
Regards
Kevin
# 6
I'm not sure how you'd tweak the bits in the jumpstart client without mucking around in the image. On the server, it's set in /etc/default/nfs with NFSMAPID_DOMAIN.
As a workaround, you might try dropping back to NFSv3.
If you're not using NFSv4 for anything else, on the NFS server edit /etc/default/nfs and change the line:
# Sets the maximum version of the NFS protocol that will be registered
# and offered by the server. The default is 4.
#NFS_SERVER_VERSMAX=4
Uncomment it and set it to 3. Then restart the NFS server.
Maybe someone else would have more information about jumpstart client setups with NFS4.
--
Darren
