[GH-ISSUE #526] Strange errors in the File Services Control Panel #181

New issue

Open

opened 2026-03-07 19:16:48 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 19:16:48 +03:00

Owner

Originally created by @mswildma77 on GitHub (Nov 11, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/526

I started having strange errors in the file services control panel that do not allow me to make any changes to any of the tabs. I get a red message at the bottom that says "Failed to Load the Required Resources". As of late the only thing I have done to the system aside from the DSM update to 7.3.1-86003 was start using this script before the 7.3 update. I also had to restore a VM to an ESXi host via NFS. I reached out to Synology Support and after they SSH'ed into the unit they said the /etc/nfs/syno_nfs_conf file was modified to force NFS 4.1 and that they found this as a similar issue in their KB. They added that nfs_minor_ver_enable=1 was added to the conf file. I know I made no such conscious change and was curious if that may have come from the HDD updater file since they offered to fix it but if it came from the script it would just happen again. There is a chance, and likely that is, that the change happened when I did the NFS restore to the ESXi host.

I just wanted to check so I don't shoot myself in the foot with support.

Thanks

Originally created by @mswildma77 on GitHub (Nov 11, 2025). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/526 I started having strange errors in the file services control panel that do not allow me to make any changes to any of the tabs. I get a red message at the bottom that says "Failed to Load the Required Resources". As of late the only thing I have done to the system aside from the DSM update to 7.3.1-86003 was start using this script before the 7.3 update. I also had to restore a VM to an ESXi host via NFS. I reached out to Synology Support and after they SSH'ed into the unit they said the /etc/nfs/syno_nfs_conf file was modified to force NFS 4.1 and that they found this as a similar issue in their KB. They added that nfs_minor_ver_enable=1 was added to the conf file. I know I made no such conscious change and was curious if that may have come from the HDD updater file since they offered to fix it but if it came from the script it would just happen again. There is a chance, and likely that is, that the change happened when I did the NFS restore to the ESXi host. I just wanted to check so I don't shoot myself in the foot with support. Thanks

kerem commented

2026-03-07 19:16:49 +03:00

Author

Owner

@007revad commented on GitHub (Nov 12, 2025):

I've seen people online mention forcing NFS 4.1 so it sounded familiar. I just searched all of my current and old scripts, including syno_hdd_db, and none of them edit /etc/nfs/syno_nfs_conf or /etc.defaults/nfs/syno_nfs_conf.

I suspect the NFS restore to the ESXi host may have changed it.

@007revad commented on GitHub (Nov 12, 2025): I've seen people online mention forcing NFS 4.1 so it sounded familiar. I just searched all of my current and old scripts, including syno_hdd_db, and none of them edit /etc/nfs/syno_nfs_conf or /etc.defaults/nfs/syno_nfs_conf. I suspect the NFS restore to the ESXi host may have changed it.

kerem commented

2026-03-07 19:16:49 +03:00

Author

Owner

@mswildma77 commented on GitHub (Nov 12, 2025):

Thanks, I just wanted to check before I said anything more to Synology and caused trouble..:)

@mswildma77 commented on GitHub (Nov 12, 2025): Thanks, I just wanted to check before I said anything more to Synology and caused trouble..:)