Micks Distractions

I’ve been play­ing around with Solaris jump­start recently. I haven’t used it since the early days. It seems that a lot of the old prob­lems still exist. So, I’ve listed most of the com­mon prob­lems and their solu­tion here. This also cov­ers Sun’s JET, (Jump­start Enter­prise Toolkit).
This is a Work In Progress — so I’ll be updat­ing this from time time as I come across issues.

The ‘ERROR: (_app_set_slice) Disk is not selected’ error message.

So, you’re try­ing to setup some DiskSuite metade­vices dur­ing the jump­start instal­la­tion. You are get­ting this error because you don’t have the slices prop­erly defined in your JET tem­plate. You will need to have some­thing sim­i­lar to the fol­low­ing defined in your JET tem­plate file, (under /opt/SUNWjet/Templates):

base_config_profile_root=512
base_config_profile_swap=16384
base_config_profile_s3_mtpt="/usr"
base_config_profile_s3_size="8192"
base_config_profile_s4_mtpt="/opt"
base_config_profile_s4_size="2048"
base_config_profile_s5_mtpt="/var"
base_config_profile_s5_size="2048"
base_config_profile_s6_mtpt=""
base_config_profile_s6_size=""

base_config_profile_disk_c0t1d0s0_mtpt="free"
base_config_profile_disk_c0t1d0s0_size="512"
base_config_profile_disk_c0t1d0s1_mtpt="free"
base_config_profile_disk_c0t1d0s2_size="8192"
base_config_profile_disk_c0t1d0s3_mtpt="free"
base_config_profile_disk_c0t1d0s3_size="8192"
base_config_profile_disk_c0t1d0s4_mtpt="free"
base_config_profile_disk_c0t1d0s4_size="2048"
base_config_profile_disk_c0t1d0s5_mtpt="free"
base_config_profile_disk_c0t1d0s5_size="2048"
base_config_profile_disk_c0t1d0s6_mtpt=""
base_config_profile_disk_c0t1d0s6_size=""
sds_root_mirror="c0t1d0"
sds_database_locations="c0t0d0s7:3 c0t1d0s7:3"
sds_database_partition="c0t0d0s7:64 c0t1d0s7:64"
sds_device_numbers="/:d100:d0:d10 swap:d101:d1:d11 /usr:d103:d3:d13 /opt:d104:d4:d14 /var:d105:d5:d15"

I had this error when I hadn’t spec­i­fied the *_mtpt and set it to’free’, I had just left it blank.

Jump­start direc­tory not found

I had the fol­low­ing issue and it took me a while to fig­ure it out.

Searching for JumpStart directory...
not found
Warning: Could not find matching rule in rules.ok
Press the return key for an interactive Solaris install program...

In the end I started to debug the ‘install-solaris’, and ‘profind’ scripts line by line. It turns out that I had defined my hosts with FQDN in my /etc/hosts file. When the server starts to look for the jump­start direc­tory it’ll use the /usr/sbin/install.d/profind s
cript to deter­mine this. Con­tained within that is the line:

 set -- `/sbin/bpgetfile -retries 1 install_config`

Because I was using the stan­dard RARP method of boot­ing, bpget­file was called to deter­mine where to nfs mount the jump­start direc­tory. boot­params didn’t return any infor­ma­tion from the boot server, because it was ask­ing for ‘host­name’, rather than ‘hostname.domain.name’. So, if you get this issue. run the command

/sbin/bpgetfile -retries 1 install_config

from your install shell.

If you get noth­ing, then this is your issue. You will need to ensure you define your hosts not with a FQDN.

Actu­ally, in my trav­els on this issue. Most of the res­o­lu­tions to ‘no match­ing rule found in rules.ok’ issues had to do with access­ing the jump­start server from the client. So, check all your net­work set­tings, (net­masks, routes, etc). If not, then the above res­o­lu­tion will be it. On my clients, this was all OK, so it was baf­fling for a while.

Also, make sure that you have the match­ing swap and root par­ti­tions set correctly:

base_config_profile_root=512
base_config_profile_disk_c0t1d0s0_mtpt="free"
base_config_profile_disk_c0t1d0s0_size="512"
base_config_profile_swap=8192
base_config_profile_disk_c0t1d0s1_mtpt="free"
base_config_profile_disk_c0t1d0s1_size="8192"

Be Socia­ble, Share!

• 

No related posts.