Skip to main content

​
NFS Mount Not Found (Child Nodes)

​
Symptom

Child node logs show: 
[ERROR] Failed to detect temp file after 10 retries
[ERROR] ENOENT: no such file or directory

​
Cause

Worker node cannot access shared storage via NFS mount. Common reasons:
  • NFS server is down
  • Export path not configured correctly
  • Network connectivity issue
  • Mount point not created

​
Fix

1

Verify NFS Server Running

On the main node (Unraid):
# Check NFS service status
systemctl status nfs-server

# If stopped, start it
systemctl start nfs-server
2

Check NFS Exports

Verify shared directories are exported:
# View active exports
exportfs -v
Should show something like:
/mnt/user/bitbonsai  192.168.1.0/24(rw,sync,no_subtree_check)
If missing, add to /etc/exports:
/mnt/user/bitbonsai 192.168.1.0/24(rw,sync,no_subtree_check,no_root_squash)
exportfs -ra
3

Test Mount Manually

On the child node (worker):
# Create mount point if missing
mkdir -p /mnt/bitbonsai

# Test mount
mount -t nfs 192.168.1.100:/mnt/user/bitbonsai /mnt/bitbonsai

# Verify access
ls -la /mnt/bitbonsai
touch /mnt/bitbonsai/test.txt
rm /mnt/bitbonsai/test.txt
If mount fails, check network connectivity:
ping 192.168.1.100
showmount -e 192.168.1.100
4

Check Firewall Rules

NFS requires these ports open on the main node:
  • TCP/UDP 2049 (NFS)
  • TCP/UDP 111 (portmapper)
On Unraid, check firewall settings or disable temporarily to test.
5

Restart Worker Service

After fixing mount issues, restart the backend container:
docker compose restart backend
docker compose logs -f backend
BitBonsai retries temp file detection 10 times with 2-second delays. If NFS mount is slow to come up after boot, increase retry count in encoding-processor.service.ts.