I have working systems and non working systems for a nfs mount on boot from an embedded device to a linux host. In both systems working and non-working I see these logs with full logging enabled.

May  7 00:37:34 dali rpc.mountd[2659]: authenticated mount request from 10.0.0.200:688 for /home/torsi/rootfs/duplo/04.00.025 (/home/torsi/rootfs)
May  7 00:37:34 dali kernel: [21419.263653] nfsd: exp_rootfh(/home/torsi/rootfs/duplo/04.00.025 [00000000b8200ae5] *:nvme0n1p2/58327288)
May  7 00:37:34 dali kernel: [21419.263743] nfsd: fh_compose(exp 103:02/58346942 duplo/04.00.025, ino=58327288)

The working system which does mount produces these additional logs:

May  7 00:27:33 r2d2 kernel: [9993048.803093] svc: socket 000000002ba94991(inet 000000004d856f7e), busy=0
May  7 00:27:33 r2d2 kernel: [9993048.803141] svc: server 0000000006b2b28f, pool 0, transport 000000002ba94991, inuse=2
May  7 00:27:33 r2d2 kernel: [9993048.803158] svc: svc_authenticate (0)
May  7 00:27:33 r2d2 kernel: [9993048.803162] svc: calling dispatcher
May  7 00:27:33 r2d2 kernel: [9993048.803164] nfsd_dispatch: vers 3 proc 0

Can anyone provide some insight, please note that the system that fails seems to provide no additional information in the logs. Is there any more pedantic logging I can enable besides using these:

sudo rpcdebug -s -m rpc
sudo rpcdebug -s -m nfs
sudo rpcdebug -s -m nfsd
sudo rpcdebug -s -m nlm

Note that the there are many more additional logs in the working system I only provided the next few lines that are logged where as the failed system has no additional logging.

Thanks,
Tom