Hello.

I'm trying to setup a jumpstart server to be able to install clients
from the LAN. To do so, I did on the install server to be:

mount -F hsfs -o ro `lofiadm -a $(dirname "$0")/sol-10-u5-ga-sparc-dvd.iso` $(dirname "$0")/iso
cd iso
cd Solaris_10/Tools
./setup_install_server /data/software/solaris/Solaris10/U5/install
cd /data/software/solaris/Solaris10/U5/install
cd Solaris_10/Tools
./add_install_client -i 10.0.1.22 -e 00:03:ba:12:d3:04 \
-p sys01.unx:/data/software/solaris/Solaris10/U5/sysidcfg/sys02 \
sys02 sun4u

Ie. I loop mounted the Solaris 10 U5 Sparc image to the "iso" directory.
After that, I created an install server and had it put all the files in
/data/software/solaris/Solaris10/U5/install. After that, I added an install
client. System name is sys02 with the shown IP and MAC adress. I created
a custom sysidcfg file for this machine:

$ cat /data/software/solaris/Solaris10/U5/sysidcfg/sys02
keyboard=Swiss-German
system_locale=de_CH.UTF-8
timezone=Europe/Zurich
terminal=sun-cmd
timeserver=10.0.1.11
name_service=DNS {domain_name=unx
name_server=10.0.1.11,10.0.2.1,10.0.15.4
search=unx}
nfs4_domain=dynamic
root_password=r...
network_interface=PRIMARY {hostname=sys02
default_route=10.0.0.254
ip_address=10.0.1.22
netmask=255.255.248.0
protocol_ipv6=no}
security_policy=NONE
service_profile=limited_net

Now I'm trying to get the installation going. So I switch to the
ok prompt on sys02 and do:

{0} ok boot net
Resetting ...
RSC Alert: Host System has Reset
NOTICE: RSC-Initiated Reset



Sun Fire 280R (2 X UltraSPARC-III+) , No Keyboard
Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.10.11, 4096 MB memory installed, Serial #51565316.
Ethernet address 0:3:ba:12:d3:4, Host ID: 8312d304.



Rebooting with command: boot net
Boot device: /pci@8,700000/network@5,1: File and args:
38e00 boot: lookup /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot failed
panic - boot: Could not mount filesystem.
Program terminated
{0} ok

Hm. Why does that happen? /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
exists:

$ ls -al /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
total 44
drwxr-xr-x 18 root root 25 May 13 13:52 .
drwxr-xr-x 5 root bin 10 May 13 13:51 ..
lrwxrwxrwx 1 root other 16 May 13 14:05 .java -> ./tmp/root/.java
lrwxrwxrwx 1 root root 13 May 13 14:05 .swapinfo -> tmp/.swapinfo
lrwxrwxrwx 1 root root 13 May 13 14:05 .swappart -> tmp/.swappart
drwxr-xr-x 3 root other 5 Mar 24 21:55 .tmp_proto
drwxr-xr-x 2 root sys 2 Mar 24 21:16 a
lrwxrwxrwx 1 root root 9 May 13 14:05 bin -> ./usr/bin
[...]

It is NFS exported - it's on a ZFS.

$ zfs get all data/software/solaris/Solaris10/U5/install
NAME PROPERTY VALUE SOURCE
data/software/solaris/Solaris10/U5/install type filesystem -
data/software/solaris/Solaris10/U5/install creation Tue May 13 13:43 2008 -
data/software/solaris/Solaris10/U5/install used 2.37G -
data/software/solaris/Solaris10/U5/install available 52.7G -
data/software/solaris/Solaris10/U5/install referenced 2.37G -
data/software/solaris/Solaris10/U5/install compressratio 1.10x -
data/software/solaris/Solaris10/U5/install mounted yes -
data/software/solaris/Solaris10/U5/install quota none default
data/software/solaris/Solaris10/U5/install reservation none default
data/software/solaris/Solaris10/U5/install recordsize 128K default
data/software/solaris/Solaris10/U5/install mountpoint /data/software/solaris/Solaris10/U5/install inherited from data/software
data/software/solaris/Solaris10/U5/install sharenfs ro,rw=10.0.3.115:sys00:sys05:sys06,root=10.0.3.115 ,anon=0 local
data/software/solaris/Solaris10/U5/install checksum on default
data/software/solaris/Solaris10/U5/install compression on inherited from data/software
data/software/solaris/Solaris10/U5/install atime off inherited from data
data/software/solaris/Solaris10/U5/install devices on local
data/software/solaris/Solaris10/U5/install exec on local
data/software/solaris/Solaris10/U5/install setuid on local
data/software/solaris/Solaris10/U5/install readonly off default
data/software/solaris/Solaris10/U5/install zoned off default
data/software/solaris/Solaris10/U5/install snapdir hidden default
data/software/solaris/Solaris10/U5/install aclmode groupmask default
data/software/solaris/Solaris10/U5/install aclinherit secure default
data/software/solaris/Solaris10/U5/install canmount on default
data/software/solaris/Solaris10/U5/install shareiscsi off default
data/software/solaris/Solaris10/U5/install xattr on default

The directory holding the sysidcfg file is also NFS exported:

$ zfs get sharenfs data/software/solaris/Solaris10/U5/sysidcfg
NAME PROPERTY VALUE SOURCE
data/software/solaris/Solaris10/U5/sysidcfg sharenfs ro,rw=10.0.3.115:sys00:sys05:sys06,root=10.0.3.115 inherited from data

$ cat /etc/bootparams
sys02.unx root=sys01.unx:/data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot install=sys01.unx:/data/software/solaris/Solaris10/U5/install boottype=:in sysid_config=sys01.unx:/data/software/solaris/Solaris10/U5/sysidcfg/sys02 rootopts=:rsize=8192

sys02 (the client which I want to install) and sys01 (the install
server) are on the same subnet.

What's going wrong here?

Thanks a lot,

Michael

Michael Schmarck <usenet-michael@schmarck.cn> wrote:

> What's going wrong here?

I now tried a "verbose" boot:

Rebooting with command: boot net -v - install
Boot device: /pci@8,700000/network@5,1: File and args: -v - install
38e00 Using RARP/BOOTPARAMS...
Internet address is: 10.0.1.22
hostname: sys02.unx
domainname: unx
Found 10.0.1.21 @ 0:3:ba:47:2a:3
root server: sys01.unx (10.0.1.21)
root directory: /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
boot: lookup /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot failed
panic - boot: Could not mount filesystem.
Program terminated

Here we see, that it finds the correct server (10.0.1.21 or sys01).
But for some reason or the other "lookup" fails. What does that
indicate?

When the system is normally booted (there's S10 on it right now), I
can NFS mount the root directory just fine.

I also tried making the root directory be in a "shorter" path (ie.
/data/s10-install). And I also tried changing the sharenfs property
to ro,anon=0. Both things didn't change a thing

What is actually failing here? And why?

Thanks a lot,

Michael

Michael Schmarck schrieb:
> Michael Schmarck <usenet-michael@schmarck.cn> wrote:
>
>> What's going wrong here?
>
> I now tried a "verbose" boot:
>
> Rebooting with command: boot net -v - install
> Boot device: /pci@8,700000/network@5,1: File and args: -v - install
> 38e00 Using RARP/BOOTPARAMS...
> Internet address is: 10.0.1.22
> hostname: sys02.unx
> domainname: unx
> Found 10.0.1.21 @ 0:3:ba:47:2a:3
> root server: sys01.unx (10.0.1.21)
> root directory: /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
> boot: lookup /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot failed
> panic - boot: Could not mount filesystem.
> Program terminated
>
> Here we see, that it finds the correct server (10.0.1.21 or sys01).
> But for some reason or the other "lookup" fails. What does that
> indicate?
>
> When the system is normally booted (there's S10 on it right now), I
> can NFS mount the root directory just fine.
>
> I also tried making the root directory be in a "shorter" path (ie.
> /data/s10-install). And I also tried changing the sharenfs property
> to ro,anon=0. Both things didn't change a thing
>
> What is actually failing here? And why?
>
> Thanks a lot,
>
> Michael

one problem could be a nonexistent defaultrouter, is yours (10.0.0.254)
reachable for the netbooted server? the bootp works fine, but i had the
same error and i think it is described in some older docs from sun. I am
not shure if this is a fixed bug.

Have you snooped nfs on the install-server, does it get nfs-packets?

Wolfgang

Wolfgang <wtrappe@AT.web.de> wrote:

> Michael Schmarck schrieb:
>> Michael Schmarck <usenet-michael@schmarck.cn> wrote:
>>
>>> What's going wrong here?
>>
>> I now tried a "verbose" boot:
>>
>> Rebooting with command: boot net -v - install
>> Boot device: /pci@8,700000/network@5,1: File and args: -v - install
>> 38e00 Using RARP/BOOTPARAMS...
>> Internet address is: 10.0.1.22
>> hostname: sys02.unx
>> domainname: unx
>> Found 10.0.1.21 @ 0:3:ba:47:2a:3
>> root server: sys01.unx (10.0.1.21)
>> root directory:
>> /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot boot:
>> lookup /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
>> failed panic - boot: Could not mount filesystem. Program terminated
>>
>> Here we see, that it finds the correct server (10.0.1.21 or sys01).
>> But for some reason or the other "lookup" fails. What does that
>> indicate?
>>
>> When the system is normally booted (there's S10 on it right now), I
>> can NFS mount the root directory just fine.

I don't know what I did at that time. I think that I verified that.
I don't know anymore.

>> I also tried making the root directory be in a "shorter" path (ie.
>> /data/s10-install). And I also tried changing the sharenfs property
>> to ro,anon=0. Both things didn't change a thing
>>
>> What is actually failing here? And why?
>>
>> Thanks a lot,
>>
>> Michael
>
> one problem could be a nonexistent defaultrouter, is yours (10.0.0.254)
> reachable for the netbooted server?

It should be. In the sysidcfg file, I've set:

network_interface=PRIMARY {hostname=sys02
Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â*default_route=10.0.0.254
Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â*ip_address=10.0.1.22
Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â*netmask=255.255.248.0
Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â*protocol_ipv6=no}

Hm.

Is the defaultrouter reachable? I don't know - what subnet mask
is used at that part of the booting process? But either way,
it seems that it was able to contact the server somehow, because
it got the /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
from "somewhere" - and I defined that path only on sys01 (the
install server).

I tried this:

./add_install_client -i 10.0.1.22 -e 00:03:ba:12:d3:04 \
-p sys01.unx:/data/software/solaris/Solaris10/U5/sysidcfg/winds02 \
-n 'none(255.255.248.0)' winds02 sun4u

Ie. I added "-n 'none(255.255.248.0)'" to the command line, which
resulted in "ns=none(255.255.248.0)" being set in /etc/bootparams.

Didn't change anything.

> the bootp works fine, but i had the
> same error and i think it is described in some older docs from sun. I am
> not shure if this is a fixed bug.
>
> Have you snooped nfs on the install-server, does it get nfs-packets?

I'll do that.

8:11:16.47863 sys02.unx -> sys01.unx MOUNT3 C Mount /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
8:11:16.48164 sys01.unx -> sys02.unx MOUNT3 R Mount Permission denied
8:11:16.48226 sys02.unx -> sys01.unx PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=UDP
8:11:16.48272 sys01.unx -> sys02.unx PORTMAP R GETPORT port=32783
8:11:16.48325 sys02.unx -> sys01.unx MOUNT1 C Mount /data/software/solaris/Solaris10/U5/install/Solaris_10/Tools/Boot
8:11:16.48608 sys01.unx -> sys02.unx MOUNT1 R Mount Permission denied

Direct answer to your question: Yes, the install-server gets the
nfs-packages from the netbooted system (sys01 is the install-server,
sys02 is the booted system).

Hm. "Mount Permission denied"? Why's that?

.....

Argl.

For some reason or the other, the install path wasn't shared
A "zfs share data/software/...." fixed that. Bummer (

Thanks a lot for the "snoop" hint!

Michael

Michael Schmarck <usenet-michael@schmarck.cn> wrote:
> When the system is normally booted (there's S10 on it right now), I
> can NFS mount the root directory just fine.

Then I'd break out 'snoop' on the server and compare the mount the
jumpstart client does and the mount that the Solaris 10 server does.
See where the difference is, then post that.

--
Darren