The tcpdump is telling me the server responds to the mount request with: Accept State: remote can't support version # (2) Program version (Minimum): 3 Program version (Maximum): 4
-- Russell Senior [email protected] On Wed, Dec 18, 2024 at 6:03 AM Russell Senior <[email protected]> wrote: > > My kernel config in /boot/config-5.10.0-33-amd64 has > "CONFIG_NFSD_V2=y" ... which makes me think there is a configuration > that has disabled v2 support despite it being available. > > -- > Russell Senior > [email protected] > > On Wed, Dec 18, 2024 at 5:48 AM Russell Senior > <[email protected]> wrote: > > > > ... but my debian 11 server seems (according to my packet capture) to > > only support NFSv3 and NFSv4. Does anyone happen to know how to enable > > NFSv2 on nfs-kernel-server for this device? Or have any other > > suggested solutions to this problem? > > > > The device is an ancient Soekris net4826 from the mid-aughts. It has > > soldered on flash storage, so the only way to recover from crashing > > firmware is to netboot. My setup *used to* work. It's getting DHCP > > information for PXE booting, TFTP's a kernel, but when the kernel > > attempts to mount an nfs rootfs, the mount fails and it kernel panics. > > We have one of them still in service in the field (and I have another > > one sitting in my test bed, crashing). > > > > The right solution is probably just to retire the one in the field and > > put the whole lot of them into a "museum box", but hey, it's the > > holidays. What better period to waste a bunch of time keeping creaking > > hardware alive. And anyway, the museum curators will be more thrilled > > to create an exhibit if they have working firmware. > > > > Thanks for any clues, meanwhile I'll keep searching the interwebs. > > > > -- > > Russell Senior > > [email protected]
