Re: Net-installing SS20 & NFS woes (?)

[Romain Dolbeau <romain%dolbeau.org@localhost>]

Le dim. 9 août 2020 à 12:14, Romain Dolbeau <romain%dolbeau.org@localhost> a écrit :
> I'm trying to netinstall a new SS20 I just got. But I can't get the
> bootloader to download the kernel.

Thanks for all the replies everyone :-)

Turns out it was an issue with Debian NFS not supporting v2 despite my
attempts. NetBSD bootloader requests NFSv2, so it didn't get the file
(I had previously eliminated the network as a culprit by adding an
intermediate 10BaseT/10Base2 hub to remove the carrier error as
suggested... though probably not many of us have one of those left :-)
).

Debian-side (probably all Linuxes) it can be seen with:

```
(dolbeau)x7sbl:~> sudo cat /proc/fs/nfsd/versions
+2 +3 +4 +4.1 +4.2
```

I had '-2' instead of '+2'. My attempt to fix that was on the wrong
variable in /etc/default/nfs-kernel-server (I hadn't discovered the
/proc entry then), I needed to fix the one passed to rpc.nfsd, not
rpc.mountd:

```
# Number of servers to start up
RPCNFSDCOUNT="8 --nfs-version 2"
```

In tcpdump when v2 is not available in Debian the reply to the file
request says (`sudo tcpdump -vvv -X host x7sbl and ss20p`)

```
11:04:39.578962 IP (tos 0x0, ttl 64, id 62279, offset 0, flags [DF],
proto UDP (17), length 60)
    x7sbl.dolbeau.name.nfs > ss20p.1021: NFS reply xid 6 reply ok 32
lookup PROG_MISMATCH
        0x0000:  4500 003c f347 4000 4011 c512 c0a8 00c8  E..<.G@.@.......
        0x0010:  c0a8 003e 0801 03fd 0028 7139 0000 0006  ...>.....(q9....
        0x0020:  0000 0001 0000 0000 0000 0000 0000 0000  ................
        0x0030:  0000 0002 0000 0003 0000 0004            ............
```

At the last line here, the 2 is 'PROG_MISMATCH' (it's the rpc_call
error displayed by the boot loader), the following 3 and 4 are the
range of NFS versions supported (the mismatch_info structure in the
reply; the earlier 6 is the XID as displayed by tcpdump, the following
1 is the msg_type REPLY, etc.)

I'm guessing newer distributions are disabling v2 by default for
security reasons - everything was working fine out-of-the-box when I
netbooted my SS330 in the NetBSD 6 (or 7?) era from the same host
(haven't tried it recently, too noisy).

It's installing now. Once that is done, I might try to replace the
lone SM61 by a pair of SM100 and see if NetBSD works SMP on those
(they are rev7 501-1388 so according to
http://mbus.sunhelp.org/modules/ Solaris won't do SMP on those, though
SunOS 4 will...)

Cordially,

-- 
Romain Dolbeau