Shared Folders not shown in Control Panel after FW Update

[WvandeHoef]

To all viewers: wishing you a healthy, happy and successful 2025!

System:
TS-431P2
FW QTS 5.2.2.2950

Issue
During the weekend I have updated to the above firmware and as tonight I wanted to maintain my Shared Folders and give access to one for a new Media Player, I found that after creating a new Folder the GUI remains stuck at a message that reads (translated from dutch) “Data is being retrieved, please wait…”. After 15 minutes I went back to the main screen to check in File Station if the folder was created or not and there it is shown.
In Control Panel under Users and User Groups I can maintain the access rights as before, also for the new folder, but when switching to the Shared Folder tab in Control Panel, it remains blank and also my already existing folders are not shown. When triggering a refresh, the same “Data is being retrieved” message is shown, but not going away.

Things checked
I have tried resetting the Network services to default, rebooted several times, reinstalled the latest FW, rebooted, but no solution.

I tried “Restore Default Shared Folders”, but that one is showing a message that there are already shared fodlers, or the volume is not formatted or disconnected, which scared the sh#t out of me as I do not want to loose my data.

Via command prompt I do not see anything strange, folders are there and rights are as I would expect.

Checked the log files for errors and warnings, these are the only ones I get:
load_crypt_module.log:ERROR: /lib/modules/misc/gasket.ko missing
load_crypt_module.log:ERROR: /lib/modules/misc/apex.ko missing
load_crypt_module.log:ERROR: /lib/modules/misc/hailo_pci.ko missing
nc.log:2025-01-01 22:44:27,270 [Warning] app.cpp:341, void NC::App::update(const char*, bool) [App] A214 read icon file error: File not found : /mnt/ext/opt/NotificationCenter/share/apps/A214/.qpkg_icon_80.gif

Request
So I am looking for a fix, either from the web GUI, or via SSH, to get my Shared Folders back in the view.

I hope one can help me out?

The issue as displayed in the Control Panel:

[Toxic]

@WvandeHoef

To all viewers: wishing you a healthy, happy and successful 2025!

and to you.

you issue has been documented a few times on the old forums but found a similar blog on the net. i would guess somehow the smb.conf has become corrupted or reset.

You could also raise a ticket with QNAP support they would be able to do the same for you.

also a smb backup may help.

https://forum.qnap.com/viewtopic.php?t=110805

here is one post I found though your situation/paths etc may be different in your situation.

Recreate a default shared folder in QNAP

[WvandeHoef]

Thanks Simon, much appreciated.

Following your first link, I confirm I do have 10 backups available.

To restore the smb.conf from before the update I would like to restore the one from Dec 25, but unfortunately the .bak file is double packed and the instructions to untar therefore do not work

tar xvfz $(dirname $(getcfg -f /etc/config/smb.conf public path))/.@backup_config/3_20241225_0304.tar.gz etc/config/smb.conf --overwrite

I have tried to manualy untar the file to get to the 0_20241225_0304.tar.gz within the .bak archive, but that one is password protected and I do not know what password to use. admin pw does not work.

Do you happen to know what pw is used or where I can retrieve that?

[Toxic]

Sorry I don’t know myself.

I guessing this is some added security that Qnap have added since that post. I would suggest you raise a ticket with Qnap support and ask them to remote help you in this situation. Explain in detail what you require I am sure they should be able to help unless someone here in the community can suggest otherwise.

You could try a number of passwords I guess?

admin
Mac address of 1st port
Your own admin username password
Cloudkey password

[WvandeHoef]

Thanks Simon!

Ticket opened, logs attached.

BR
Wouter

[Toxic]

You can run this command to find the password. it worked for me anyhow.

Run

/sbin/gen_encstr

on the NAS and the whole string that appears is the decompression password.

there will be another tar.gz inside of the file (no pwd) then extract the \etc\config\smb.conf

and use that. (check the file for all your shares are listed) I think you should be able to reload the smb.conf using:

/etc/init.d/smb.sh restart

[WvandeHoef]

Many, many thanks Simon!

I used that to open the backup file in 7Zip and found my old smb.conf and you were right: the current one is corrupted and particularly in the [home] section, where it has the user names without “” and as “%D%w%U”.

I am now doing the restore and will let you know.

Best regards,
Wouter

[WvandeHoef]

Unfortunately the restore of smb.conf did not resolve the issue.
Restarting smb showed an error for the cache folder, which did not exist.

This one I have created and with that the error is gone, but I’m still looking for a solution to bring back the Shared Folders in the Control Panel.

I hope QNAP support will be able to help me out and when they do, I will update.

Regards,
Wouter

[Toxic]

I dont use QTS mine is on QuTS Hero. though i would have thought the samba folder should just be that and not samba_target

mine all resides under:

/share/ZFS1_DATA/.samba

if you dont have backups of your data it would be a good time to make sure you do. using winscp you’ll be able to at least grab your data and back it up to another media format.

lets see what QNAP say, unless someone else can help here.

[WvandeHoef]

Hi Simon,

I get the impression QNAP FW overwrites the backed up and restored smb.conf, as the folder I created yesterday now again is in that config file, where it was not after I did restore it.

I will see that I backup those files and the configuration, but as it is ~700GB it will take some time to backup over USB

[Toxic]

hopefully QNAP will get you sorted soon. let us know how you get on

[WvandeHoef]

Hi Simon,

No response from QNAP yet and as I wanted it sorted I took matters into own hands and after screenshotting a lot, I did the 10-sec reset button trick to keep the data, but set everything else back to standard. This solved the issue.

I expect the root cause is in the changed admin password policy, as the QNAP ID password did not meet my set security policy for my users. I had the feeling some parts of the FW are using that ID instead of the correct pw. After the reset indeed the admin pw was set to the QNAP ID and the account disabled after creating a new admin.

Kind regards,
Wouter