client: searching for jumpstart directory: not found. No entry in ?rules file.
in [Solaris]
|
Prev: client: searching for jumpstart directory: not found. No entry in rules file.
Next: client: searching for jumpstart directory: not found. No entryin rules file.
From: hume.spamfilter on 21 Dec 2009 07:45 In comp.unix.solaris BertieBigBollox(a)gmail.com <bertiebigbollox(a)gmail.com> wrote: > /etc/bootparams seems to be doing its job because client boots up ok > and seems to find the correct sysidcfg. > > However, for some reason its saying rules is wrong. The error (which you put in the subject line, making it very hard to read) seems to indicate rather that it can't find the jumpstart dir. I would interpret that to mean it can't find the rules file at all. > What to check first? Is this a SPARC or x86 system? Are you using RARP or DHCP? And what do you have specified for the install_config parameter? -- Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: BertieBigBollox on 21 Dec 2009 09:01 On Dec 21, 12:45 pm, hume.spamfil...(a)bofh.ca wrote: > In comp.unix.solaris BertieBigBol...(a)gmail.com <bertiebigbol...(a)gmail.com> wrote: > > > /etc/bootparams seems to be doing its job because client boots up ok > > and seems to find the correct sysidcfg. > > > However, for some reason its saying rules is wrong. > > The error (which you put in the subject line, making it very hard to read) > seems to indicate rather that it can't find the jumpstart dir. I would > interpret that to mean it can't find the rules file at all. > > > What to check first? > > Is this a SPARC or x86 system? Are you using RARP or DHCP? And what do > you have specified for the install_config parameter? > > -- > Brandon Hume - hume -> BOFH.Ca,http://WWW.BOFH.Ca/ X86 using RARP. install_config (in bootparams) :- install_config=10.1.99.10:/jumpstart which is correct. 10.1.99.10 is the IP address of the server, jumpstart is the directory containing the rules file etc, and its shared on the server.
From: Cydrome Leader on 27 Dec 2009 13:18
In comp.unix.solaris phil.googlenews(a)bolthole.com <phil.googlenews(a)bolthole.com> wrote: > On Dec 23, 1:52?pm, Cydrome Leader <prese...(a)MUNGEpanix.com> wrote: > >> By using a non-sun DHCP server, we finally got a kernel to boot. rules >> never worked, ever. Nobody at sun could get it to work either, which >> doesn't surprise me as they keep changing all the secret paramaters and >> settings every 9 seconds with their junior attempts as PXE booting. >> >> To this day, there's still no accurate or even close to upto date doc on >> jumpstarting sun stuff with PXE where the commands as they show actually >> work. There's some "blueprint" from 2006 or so. it's completely useless. > > FYI: I had some problems in that area myself. > I discovered by a lot of trial and error, that > > #1. it doesnt like subdirectories for profiles. has to be in same dir > as rules file. > (Same problem with using WANBOOT on sparc now!!!) nice. I wonder how you found this, or how sun forgot the cd command. > #2. I gave up on regular rules/profile sharing for PXE/sol x86,and > went to a little known method of using a tarfile. I checked my notes and case history and found this is what wasn't working. No matter what the rules were, no host would ever match a profile and the install would be interactive. Any rules we made or recycled for sparc worked fine though, so there wasn't a clueless factor. This wasn't a case of no nfsv domain- a client being jumped would never match anything except the generic profile for an i86 client. This was solaris 10 08/06. > My grub entries look like the following: > > title 6 Solaris 10 net install experimental tarcfg, serial console > kernel /boot/200810/multiboot kernel/unix - install nfs://x.x.x.x > /jumpstart/jumpstart.tar -B console=ttya,install_media=nfs://x.x.x.x/ > jumpstart/s10x86200810 > module /boot/200810/x86.miniroot > > Even WANBOOT, ugly as it it, would be an improvement over this mess. > Dammit sun, pick a technology and STANDARDIZE!! they can't even pick names for established products. I noticed in meetings everybody knows what "apache" is, but depending on how long the person has been around the sun webserver is "SJWS", "iPlanet" or just a generic and safe "sun webserver". > Tips: > > "/boot" entries, are references to a subdir in /tftpboot > > jumpstart.tar is created by a Makefile in the jumpstart dir that looks > like the following: > > > FILES = README rules rules.ok sysidcfg *.prof begin_* finish_* > > jumpstart.tar: $(FILES) > tar cvf jumpstart.tar $(FILES) weird, I'll need to try this. I wonder why they even made it, or used something easy like tar. I'd expect it to need cpio-ed file like a flar or something you can't open and examine again. |