Maybe something has changed in the new Ubuntu version related to how the packet forwarding happens within the server from the private IP subnet to the public IP subnet. Is it possible to bind the TFTP server and NFS server to the private IP address of the bootserver?
Are you running iptables or some other firewall process on the bootserver? If so, maybe there is logging you can enable there to see whether the firewall is unexpectedly blocking any traffic from/to the ROACH2. When you soloboot, can you run “showmount -a 192.100.16.206”? Dave > On Aug 24, 2022, at 6:02 AM, Gary, Dale E <dale.e.g...@njit.edu> wrote: > > Hi Dave, > > This is the information in the server syslog: > Aug 24 12:41:59 ovsa in.tftpd[35999]: RRQ from 192.168.24.121 filename > uImage-roach2 > Aug 24 12:42:16 ovsa rpc.mountd[1022]: authenticated mount request from > 192.168.24.121:892 <http://192.168.24.121:892/> for > /mnt/data0/srv/roach2_boot/etch (/mnt/data0/srv/roach2_boot) > Aug 24 12:42:21 ovsa rpc.mountd[1022]: authenticated mount request from > 192.168.24.121:773 <http://192.168.24.121:773/> for > /mnt/data0/srv/roach2_boot/etch (/mnt/data0/srv/roach2_boot) > Aug 24 12:42:31 ovsa rpc.mountd[1022]: authenticated mount request from > 192.168.24.121:932 <http://192.168.24.121:932/> for > /mnt/data0/srv/roach2_boot/etch (/mnt/data0/srv/roach2_boot) > Aug 24 12:42:51 ovsa rpc.mountd[1022]: authenticated mount request from > 192.168.24.121:733 <http://192.168.24.121:733/> for > /mnt/data0/srv/roach2_boot/etch (/mnt/data0/srv/roach2_boot) > Aug 24 12:43:21 ovsa rpc.mountd[1022]: authenticated mount request from > 192.168.24.121:935 <http://192.168.24.121:935/> for > /mnt/data0/srv/roach2_boot/etch (/mnt/data0/srv/roach2_boot) > Aug 24 12:43:51 ovsa rpc.mountd[1022]: authenticated mount request from > 192.168.24.121:799 <http://192.168.24.121:799/> for > /mnt/data0/srv/roach2_boot/etch (/mnt/data0/srv/roach2_boot) > so it seems that it tried 6 times and succeeded 6 times, but it doesn't seem > to know it. I guess this suggests a transport issue (version incompatibility > or something) rather than a configuration or permissions error. > > I am curious about the root=/dev/nfs part of the netboot command. I assume > the ROACH is trying to mount /srv/roach2_boot/etch as /. There is a > directory /srv/roach2_boot/etch/dev, but not a /srv/roach2_boot/etch/dev/nfs. > But of course that hasn't changed from the previous working version, so I > don't see how it can be a problem. > > Regards, > Dale > > On Wed, Aug 24, 2022 at 1:26 AM David Harold Edward MacMahon > <dav...@berkeley.edu <mailto:dav...@berkeley.edu>> wrote: > Have you looked for any messages in /var/log/syslog on the NFS server? When > things work you’ll see a line that says something like “authenticated mount > request from w.x.y.x” (though I haven’t tried this on a modern Ubuntu version > so that message might have changed), but if there’s a problem you might see a > helpful(?) error message instead. > > Dave > >> On Aug 23, 2022, at 5:57 PM, Gary, Dale E <dale.e.g...@njit.edu >> <mailto: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. >> >> Regards, >> Dale >> >> On Tue, Aug 23, 2022 at 8:31 PM David Harold Edward MacMahon >> <dav...@berkeley.edu <mailto:dav...@berkeley.edu>> wrote: >> I notice these excerpts from your u-boot log: >> >>> TFTP from server 192.100.16.206; our IP address is 192.168.24.121; sending >>> through gateway 192.168.24.1 >> >> …and... >> >>> IP-Config: Complete: >>> device=eth0, addr=192.168.24.121, mask=255.255.255.0, gw=192.168.24.1 >>> host=roach1.solar.pvt, domain=solar.pvt solar.ovro.caltech.edu >>> <http://solar.ovro.caltech.edu/>, nis-domain=(none) >>> bootserver=192.100.16.206, rootserver=192.100.16.206, >>> rootpath=/srv/roach2_boot/etch >>> nameserver0=192.100.16.2VFS: Unable to mount root fs via NFS, trying >>> floppy. >> >> It is not technically wrong to have the boot and root server be on a >> different subnet (192.100.16.x) from the ROACH2s, but I wonder if this is >> what you really intend. The IP address 192.100.16.206 appears to be the >> public facing IP address of your server. I suspect maybe you really want >> those to be using IP address 192.168.24.1 (or some other address on the >> 192.168.24.0/24 <http://192.168.24.0/24> subnet). This is something that >> would get changed in the DHCP config files. Are you using dnsmasq for >> DHCP/TFTP/DNS for the ROACH2s? >> >> Dave >> >> >>> On Aug 23, 2022, at 5:08 PM, Gary, Dale E <dale.e.g...@njit.edu >>> <mailto:dale.e.g...@njit.edu>> wrote: >>> >>> Hi Dave, >>> >>> Okay, this "worked" to set those two recommended settings (I also had to >>> set the rootpath environment variable correctly first): >>> setenv netboot 'dhcp 0x4000000; setenv bootargs ${bootargs} root=/dev/nfs >>> rootpath=${rootpath},vers=4,tcp ip=dhcp; bootm 0x4000000' >>> but unfortunately the result was the same. There may be some different >>> problem. >>> >>> Regards, >>> Dale >>> >>> On Tue, Aug 23, 2022 at 6:42 PM David Harold Edward MacMahon >>> <dav...@berkeley.edu <mailto:dav...@berkeley.edu>> wrote: >>> I don’t think you need the single quotes in the middle. I think at the >>> u-boot prompt you can just run: >>> >>> setenv ’netboot=dhcp 0x4000000; setenv bootargs ${bootargs} root=/dev/nfs >>> rootpath=${rootpath},nfsver=4 ip=dhcp; bootm 0x4000000’ >>> >>> You can run printenv afterwards to see whether it did what we hope it will >>> do. If it does, I suggest running `run netboot` to test it out. If it >>> works, you’ll have to reboot, go into netboot, enter the `setenv` command >>> again, then run `saveenv`. I’m reluctant to change a >>> known-though-non-working config to something that may or may not work, so >>> that’s why I suggest testing before running `saveenv`. When in doubt, you >>> can always reboot to “undo” any unsaved changes. >>> >>> Good luck, >>> Dave >>> >>>> On Aug 23, 2022, at 3:19 PM, Gary, Dale E <dale.e.g...@njit.edu >>>> <mailto:dale.e.g...@njit.edu>> wrote: >>>> >>>> Hi Dave, >>>> >>>> I think you are right that I found the place to do it, but I don't know >>>> what syntax to use to set the environment variable for >>>> netboot=dhcp 0x4000000; setenv bootargs ${bootargs} root='/dev/nfs' >>>> rootpath=${rootpath} ip=dhcp; bootm 0x4000000 >>>> I am not sure what needs escaping, etc. Can I just add single quotes >>>> around the whole and escape the ticks? I guess I'll play with it. >>>> >>>> Regards, >>>> Dale >>>> >>>> On Tue, Aug 23, 2022 at 5:55 PM David Harold Edward MacMahon >>>> <dav...@berkeley.edu <mailto:dav...@berkeley.edu>> wrote: >>>> Hi, Dale, >>>> >>>> It sounds like you’ve found where to set the `vers=4` option. If that >>>> doesn’t work, it’s possible that the ROACH2s don’t support NFSv4. If >>>> that's the case (I’m not sure it is), then you may have to look into >>>> exporting the root filesystem via NFSv3 instead. >>>> >>>> I always have to double check the MTU configuration on the NFS server’s >>>> network interface. I think setting it to larger than 1500 won’t work for >>>> the ROACH2s. >>>> >>>> I’m curious to know what the solution ends up being! >>>> >>>> Cheers, >>>> Dave >>>> >>>>> On Aug 23, 2022, at 12:08 PM, Gary, Dale E <dale.e.g...@njit.edu >>>>> <mailto:dale.e.g...@njit.edu>> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> I upgraded my remote boot server to a new machine running ubuntu 20.04, >>>>> and although I tried to set everything up the same for remote booting the >>>>> ROACH2s, the process fails as shown in the attached file because the root >>>>> file system could not be mounted. I found one suggestion on the web to >>>>> edit the Linux/PPC load configuration to add vers=4,tcp to the line, i.e. >>>>> it might look like this: >>>>> root=/dev/nfs nfsroot=192.100.16.206:/srv/roach2_boot/etch,vers=4,tcp >>>>> ip=dhcp >>>>> but I cannot find any file where that configuration is set. There is a >>>>> file in /srv/roach2_boot called pxelinux.cfg that looks promising, but it >>>>> is an empty file. Am I on the right track? >>>>> >>>>> Any suggestions? >>>>> Thanks, >>>>> Dale >>>>> >>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "casper@lists.berkeley.edu <mailto: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 >>>>> <mailto:casper+unsubscr...@lists.berkeley.edu>. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUiMwt1RWdSmW6qACbPptY_Dfc1TYiddZa6CdTdUDkDGSA%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUiMwt1RWdSmW6qACbPptY_Dfc1TYiddZa6CdTdUDkDGSA%40mail.gmail.com?utm_medium=email&utm_source=footer>. >>>>> <ROACH_uboot_dialog.txt> >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "casper@lists.berkeley.edu <mailto: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 >>>> <mailto:casper+unsubscr...@lists.berkeley.edu>. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/61DC9F78-39C0-4EF9-9F84-1E3704648F0D%40berkeley.edu >>>> >>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/61DC9F78-39C0-4EF9-9F84-1E3704648F0D%40berkeley.edu?utm_medium=email&utm_source=footer>. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "casper@lists.berkeley.edu <mailto: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 >>>> <mailto:casper+unsubscr...@lists.berkeley.edu>. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgTWZpPgcYfn0ZjRp-9a%2BMH8RyVTn-94H5dRahTdHcmhA%40mail.gmail.com >>>> >>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgTWZpPgcYfn0ZjRp-9a%2BMH8RyVTn-94H5dRahTdHcmhA%40mail.gmail.com?utm_medium=email&utm_source=footer>. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "casper@lists.berkeley.edu <mailto: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 >>> <mailto:casper+unsubscr...@lists.berkeley.edu>. >>> To view this discussion on the web visit >>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/C75BE57C-08FA-498D-BA6F-2F19E6CD61FB%40berkeley.edu >>> >>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/C75BE57C-08FA-498D-BA6F-2F19E6CD61FB%40berkeley.edu?utm_medium=email&utm_source=footer>. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "casper@lists.berkeley.edu <mailto: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 >>> <mailto:casper+unsubscr...@lists.berkeley.edu>. >>> To view this discussion on the web visit >>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUipK-fp1iwapH%3DZjkcf6Hf4LFRyG8GHPO6OukEuQiHW6Q%40mail.gmail.com >>> >>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUipK-fp1iwapH%3DZjkcf6Hf4LFRyG8GHPO6OukEuQiHW6Q%40mail.gmail.com?utm_medium=email&utm_source=footer>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "casper@lists.berkeley.edu <mailto: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 >> <mailto:casper+unsubscr...@lists.berkeley.edu>. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/865E1BE3-5C71-4E24-AC78-81E2414DB0E0%40berkeley.edu >> >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/865E1BE3-5C71-4E24-AC78-81E2414DB0E0%40berkeley.edu?utm_medium=email&utm_source=footer>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "casper@lists.berkeley.edu <mailto: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 >> <mailto:casper+unsubscr...@lists.berkeley.edu>. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgX%3D_e84UU5x_xkF9pby2uKZeqfhWZ%3DUbeSR%3Du_fYoQdg%40mail.gmail.com >> >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgX%3D_e84UU5x_xkF9pby2uKZeqfhWZ%3DUbeSR%3Du_fYoQdg%40mail.gmail.com?utm_medium=email&utm_source=footer>. > > > -- > You received this message because you are subscribed to the Google Groups > "casper@lists.berkeley.edu <mailto: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 > <mailto:casper+unsubscr...@lists.berkeley.edu>. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/1FA0DFC2-02CC-4E5B-B90A-A7F215B30B47%40berkeley.edu > > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/1FA0DFC2-02CC-4E5B-B90A-A7F215B30B47%40berkeley.edu?utm_medium=email&utm_source=footer>. > > -- > 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 > <mailto:casper+unsubscr...@lists.berkeley.edu>. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgVKVd4SFiCVOXFCvzCBXQ9HCbo-7v8m%2BRGejED2EmG2Q%40mail.gmail.com > > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgVKVd4SFiCVOXFCvzCBXQ9HCbo-7v8m%2BRGejED2EmG2Q%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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/33DF210B-4153-4FDE-A847-5917FD6BED50%40berkeley.edu.
