NFS service fails to start after reboot on TS-453D with QM2-2P10G1TB card

English Networking
1

After rebooting my TS-453D, the NFS service fails to respond to mount requests even though it shows as “enabled” in the web UI.

SYMPTOMS:

  • NFS checkbox is enabled in Control Panel > Network & File Services > Win/Mac/NFS
  • showmount command from NFS clients times out with “rpc mount export: RPC: Timed out”
  • QNAP responds to ping normally
  • Web interface accessible
  • All other services working

WORKAROUND THAT FIXES IT:

  1. Go to Control Panel > Network & File Services > NFS Service
  2. Uncheck “Enable Network File System (NFS) service”
  3. Click Apply
  4. Re-check “Enable Network File System (NFS) service”
  5. Click Apply
  6. NFS immediately starts working

This occurs after EVERY reboot and requires manual intervention each time.

SYSTEM CONFIGURATION:

NAS Details:

  • Model: TS-453D
  • Firmware: QTS 5.2.8.3350 Build 20251216
  • CPU: Intel Celeron J4125 (4 cores, 4 threads)
  • Memory: 32GB (2x 16GB Crucial Technology)
  • PCIe Card: QM2-2P10G1TB (2x 1TB NVMe SSD + 10GbE port)

Network Setup:

  • Dual network interfaces (built-in 1GbE + QM2 10GbE)
  • NFS traffic primarily uses 10GbE interface (192.168.20.188)
  • Shares exported to 192.168.20.0/24 and 192.168.1.0/24
  • NFS versions enabled: NFSv2, NFSv3, NFSv4, NFSv4.1

Drive Configuration:

  • RAID5 array
  • 4x 8TB HGST HUH728080ALE604 drives (3.5" SATA)
  • 2x 1TB NVMe SSDs in QM2 card slots

Client Systems:

  • Proxmox VE 8.x (Debian-based)
  • Used for PBS backups and Immich & Nextcloud data mounts
  • Clients connect via NFSv3

ADDITIONAL CONTEXT:
The NFS daemon processes do not start automatically on boot even though the configuration shows the service as enabled. This appears to be a timing issue where NFS tries to start before the PCIe network interface or M.2 storage is fully initialized.

NOTE: I attempted to submit a support ticket through both the QNAP support portal website and the QNAP Help Desk app, but both failed (website shows “something went wrong”, app reports connection issues despite network being fine).

QUESTION:
Is this a known issue with the QM2 card or service initialization order? What’s the permanent fix to ensure NFS starts properly on boot without manual intervention?

Has anyone else experienced this? Any suggestions appreciated!

2

I will have our internal team attempt to reproduce the issue again. Thank you!

3

May be worth to re-install the current firmware (it is possible).

Since when does this occur?

If re-install does not solve the issue, downgrade to a previous firmware which did not show the issue and update again.

Regards