Hi Dave,
Bingo!
I found that the rpc-statd.service was inactive (dead), so I started it.
Then I tried mounting from soloboot without the nolock and the connection
was still refused. Then I tried nolock and it mounted! Now to see if I
can get it to netboot. I guess I'll still have to update the
Hi, Dale,
> On Aug 24, 2022, at 1:18 PM, Gary, Dale E wrote:
>
> > 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).
Is the rpc-statd service running on the NFS server? On a
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 (
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
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 o
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% /
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 for /mnt/data0/srv/roach2_boot/etch
(/mnt/data0/srv/roach2_boot)
A
On Wed, Aug 24, 2022 at 12:57 AM Gary, Dale E 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
8 matches
Mail list logo
