Hi Sundar, Thanks for responding... since I don't see your reply posted on the discussion, I'll respond in email.
On Nov 1, 2007, at 4:51 PM, Sundar Yamunachari wrote: > > The reason why you can't specify size in mirrors for jumpstart is > that the two disks may have different geometry so the cylinder size > and number of cylinders are different. This makes perfect sense, and didn't occur to me because my disks are identical. > You shouldn't specifiy c1t0d0s2 and c1t1d0s2 in your jumpstart > profile. They represent the while disk. Done... I removed that. >> This causes the check script to fail in the following way: >> >> js# ./check >> Validating rules... >> Validating profile Profiles/profile.mirror... >> expr: syntax error >> ./check: test: argument expected >> >> Although "existing" isn't officially allowed in the filesys mirror >> line, I modify the line to look like this: >> >> filesys mirror:d0 c1t0d0s0 c1t1d0s0 existing / >> >> And check gives me a reasonable error at least: >> >> js# ./check >> Validating rules... >> Validating profile Profiles/profile.mirror... >> >> Error in file "Profiles/profile.mirror", line 48 >> filesys mirror:d0 c1t0d0s0 c1t1d0s0 existing / >> ERROR: Size "existing" is invalid >> > Check script doesn't accept this because it doesn't know which > 'existing' slice to use (c1t0d0s0 or c1t1d0s0). The problem boils down to the check script not accepting this line without *something* in the size field, contrary to the user manual examples. > Once it failed, run the jumpstart in dryrun mode to provide more > debug information and it will tell you which jumpstart line has the > problem. > > # /usr/sbin/install.d/pfinstall -D <name of the profile> > (Usually your config files directory will be mounted under /tmp/ > <xxx> directory) Unfortunately, I don't believe I can do that because my Jumpstart server is Solaris 9, and it doesn't have the same disk geometry as the target. I *am* using the check script from the Solaris 10 8/07 media. Steve
