Hi Marc and Dave, Here are responses to your suggestions while in soloboot: > showmount -a 192.100.16.206 There is no showmount command in the soloboot. > running a firewall? Yes, I am running ufw on the server. Its status gives:
dgary@ovsa:~$ sudo ufw status verbose Status: active Logging: on (low) Default: deny (incoming), allow (outgoing), disabled (routed) New profiles: skip To Action From -- ------ ---- 22/tcp ALLOW IN Anywhere 80/tcp ALLOW IN Anywhere 443/tcp ALLOW IN Anywhere Anywhere ALLOW IN 192.168.24.0/24 22/tcp (v6) ALLOW IN Anywhere (v6) 80/tcp (v6) ALLOW IN Anywhere (v6) 443/tcp (v6) ALLOW IN Anywhere (v6) Maybe this disabling of routed connections is related to the problem? I then edited the ufw sysctl.conf and restarted the firewall, and the status is dgary@ovsa:~$ sudo ufw status verbose Status: active Logging: on (low) Default: deny (incoming), allow (outgoing), deny (routed) However, the default is still deny. The example I found for setting an allow rule is ufw route allow in on eth1 out on eth2 but there is only one interface so I can't make such a rule. I am not sure how Rick Hobbs at Caltech has this set up. I'll send him a request about it. > cat /proc/filesystems I see nfs and nfs4 in the list, so I assume that means it is there and known. > mount -t nfs 192.100.16.206:/srv/roach2_boot/etch /usr/local/ovsasrv Here I get something potentially useful: svc: failed to register lockdv1 RPC service (errno 111). mount: mounting 192.100.16.206:/srv/roach2_boot/etch on /usr/local/ovsasrv failed: Connection refused On the servers syslog I get Aug 24 19:54:30 ovsa rpc.mountd[1022]: authenticated mount request from 192.168.24.121:714 for /mnt/data0/srv/roach2_boot/etch (/mnt/data0/srv/roach2_boot) in response, so it did send the mount request. I then tried setting options for tcp, vers=3, and got the same error. Finally, I tried vers=4 and got mount: NFSv4 not supported mount: mounting 192.100.16.206:/srv/roach2_boot/etch on /usr/local/ovsasrv failed All of this does indeed seem to point to the firewall as the culprit. But what bothers me is that *I *can* mount the share on an ubuntu machine on the private network*, and that has to negotiate this same thicket so I still have doubts. Anyway, I hope we are starting to narrow the problem. Regards, Dale On Wed, Aug 24, 2022 at 1:10 PM Marc <m...@sarao.ac.za> wrote: > Hello > > So first check if the kernel you are booting knows about nfs by doing > a "cat /proc/filesystems". > > If so then try specifying the filesystem type explicity, using a "-t > nfs". If I recall correctly the mount executable is busybox, so might > not be as featureful as the mount we normally encounter. > > regards > > marc > > On Wed, Aug 24, 2022 at 3:54 PM Gary, Dale E <dale.e.g...@njit.edu> wrote: > > > > Marc, I tried soloboot and it did let me log in, but I couldn't seem to > create a mount point. The filesystem shows > > > > Filesystem 1K-blocks Used Available Use% Mounted on > > /dev/root 6641 6641 0 100% / > > /dev/mtdblock2 49152 1352 47800 3% /usr > > tmpfs 387004 8 386996 0% /var > > > > and I was able to make a directory /usr/local/ovsasrv, but when I tried > to mount into that I got > > > > ~ # mount 192.100.16.206/srv/roach2_boot/etch /usr/local/ovsasrv > > mount: mounting 192.100.16.206/srv/roach2_boot/etch on > /usr/local/ovsasrv failed: No such file or directory > > > > > > I also tried to mount into /tmp, /usr/tmp, and other places but got the > same result. I created an empty file in /usr/local/ovsasrv thinking I > would get a different error like "directory not empty" but it still gave > the above error. Can you suggest something else to test local mounting in > soloboot? > > > > Regards, > > Dale > > > > On Wed, Aug 24, 2022 at 3:05 AM Marc <m...@sarao.ac.za> wrote: > >> > >> On Wed, Aug 24, 2022 at 12:57 AM Gary, Dale E <dale.e.g...@njit.edu> > wrote: > >> > > >> > Hi Dave, > >> > > >> > There is only one interface on the server. I am not actually sure > how it works with the private network, but it is not a dedicated NIC. I > was using dnsmasq on the old server but when I changed to the new one I was > trying not to use it. Since I can mount the share on another client on the > private network I don't understand why the ROACH can't do it. I tried the > nolock option also, and specifying vers=3. Nothing makes any difference. > >> > >> Perhaps try soloboot the roach and try to mount the nfs share in some > >> random subdirectory - maybe the error messages are more informative > >> there ? I'd try to go with nolock and an earlier NFS version across > >> UDP, at least initially. That might give you an idea what > >> versions/options the roaches understand. > >> > >> regards > >> > >> marc > >> > >> -- > >> https://katfs.kat.ac.za/~marc/ > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups "casper@lists.berkeley.edu" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an email to casper+unsubscr...@lists.berkeley.edu. > >> To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGrhWaTVAsJD-Tn1z3w_dLwtEdZant%2Bz2Sn5C%2BG1fQw0Rjk9Bw%40mail.gmail.com > . > > > > -- > > You received this message because you are subscribed to the Google > Groups "casper@lists.berkeley.edu" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to casper+unsubscr...@lists.berkeley.edu. > > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUjvfnXQCLj%3DnHnJ%2B62v1KywYPzEobdwHqae2Vr5i18Juw%40mail.gmail.com > . > > > > -- > https://katfs.kat.ac.za/~marc/ > > -- > You received this message because you are subscribed to the Google Groups " > casper@lists.berkeley.edu" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to casper+unsubscr...@lists.berkeley.edu. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGrhWaT0k%3DExNRVD6gqKUKH%2Bv3R3AmQPGYkYM6BpXjAhOGXnVg%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "casper@lists.berkeley.edu" group. To unsubscribe from this group and stop receiving emails from it, send an email to casper+unsubscr...@lists.berkeley.edu. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUhN8JMb%2Bq2R69DvwBW2psSxSF7ZtYV-%2Bhq5BBEX_xz8Hg%40mail.gmail.com.
