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