SMB bug in 4.3.6.1040 (2019/08/20)

[bigorno]

On a TS-453S Pro with firmware 4.3.6.1040 (2019/08/20), in /etc/init.d/smb.sh at line 1038, we have:

Code: Select all

homes_smb_encrypt=`/sbin/getcfg homes "smb encrypt" -d "disable" -f /etc/config/smb.conf`

Which creates entries in /etc/config/smb.conf:

Code: Select all

smb encrypt = disable

These entries are invalid, it should be "disabled" with a "d", not "disable".
As a consequence, SMB fails to start properly, and it is not possible to connect to the NAS.

Replacing "disable" by "disabled" in the script fixes the problem.

How should I report this issue in a proper way, if not here?

[Toxic17]

raise a ticket with QNAP. either using the online forms

https://service.qnap.com/en-uk/user/create-ticket

or using the "Helpdesk" app on your NAS

[emufan]

Thanks bigorno. SMB Connection are not working here as well. Will give this a try, too!

[emufan]

Argh. Is there any way to solve this myself, so that SMB Connections are working temporarily?

If I edit smb.sh, this is overwritten after reboot. Though, that I can edit this.

[aesculus]

Replacing "disable" by "disabled" in the script fixes the problem.

How should I report this issue in a proper way, if not here?

Thanks for this. I also reported it with a link to this thread.

Cannot understand why this has gotten this far.

[emufan]

Cannot understand why this has gotten this far.

Same here. The quality from their updates is horrible at the moment. HBS is not working anymore -> no Cloud backups possible with this tool. Now SMB -> no SMB-backups from the PCs possbiel without work arounds.

If this is the future Quality of QNAP NAS. Wow.

[and600]

bigorno, many thanks ! you saved me a lot of troubles

[intothevoid]

I have the same problem on my 453U.

noob question : What do I need to do once I've edited the smb.conf? Stop/starting MS networking from the GUI just overwrites the file and puts me back to square one.

thx

[effetredici]

Firmware 4.3.6.1040 has been deleted from the qnap servers.

[fstueckradt]

Almost same issue here (TS453Pro).
I can access the shares reading without any problems.
But I can't bulk-write - like copying a folder to a network share or doing a backup or folder sync.
Is there any solution with manual intervention to this yet?
I intended to do some serious software updates on the windows machines this weekend and wanted to backup data before.
(OK, backup is for wimps...)
Cheers!
Frank

[effetredici]

Almost same issue here (TS453Pro).
I can access the shares reading without any problems.
But I can't bulk-write - like copying a folder to a network share or doing a backup or folder sync.
Is there any solution with manual intervention to this yet?
I intended to do some serious software updates on the windows machines this weekend and wanted to backup data before.
(OK, backup is for wimps...)
Cheers!
Frank

Simply go back to firmware 4.3.6.0993 build 20190704.

[fstueckradt]

Simply go back to firmware 4.3.6.0993 build 20190704.

Thanks for the prompt feedback!

Never done it before...
Is the procedure the following (Assume that I'm an IT professional with some 30 years of experience, but not OS-based, more application.side of the world.)?
- Get the legacy firmware file somewhere from the QNAP website. Carefully searching if it's suitable for the machine.
- Invoke the Update routine in QNAP.
- Specify the update file manually.
- Have a strong liquor while waiting for the update running with a couple of beeps.
- Enjoy the successful backflip.

Are there any side effects in the downgrade?
Like for example the freshly updated version of the virtualisation station no longer running on the old firmware release?

Thanks!

Frank

[dgypnas]

I was overjoyed when I found this thread because I thought my problem would be solved! I am running Windows clients and a TS-251. The clients could all see the contents of folders/shares but I couldn't open any files - if I tried to open even a small text file I'd get the error "The system cannot find the file specified" (curiously, I could CREATE a file just fine).

Anyway, I found this thread, went through the steps to downgrade the firmware. The qnap download site had "TS-X51_20190816-4.4.1.1031.img" as the first choice, without thinking I went ahead and downgraded but when it all rebooted... SAME PROBLEM!

(for those looking to downgrade - google it.. you'll need to install Qfinderpro and find the .img to download, that app has a tool that'll let you load firmware from an image)

It wasn't until afterward that I noticed the firmware version available for download is "4.4.1" yet the thread here is 4.3.6.. WTH? I really didn't pay attention to the fact it was the same version# and a "beta" version. So after failure - I went back to the download page and the most recent non-Beta vesion is from July: TS-X51_20190704-4.3.6.0993.

Using THAT version and the same tool after 1.5 hours of panic I now have my files back!

So... Make sure you use the NON-BETA version and yes, use the downgrade method to restore!

ouch - this one hurt!

[P3R]

Is the procedure the following (Assume that I'm an IT professional with some 30 years of experience, but not OS-based, more application.side of the world.)?
- Get the legacy firmware file somewhere from the QNAP website. Carefully searching if it's suitable for the machine.

No it's much simpler. Go to the Qnap Download Center, specify what NAS you have and download 4.3.6.0993 build 20190704 (avoid the beta versions at the top of the list).

Also I wouldn't call 4.3.6.0993 (released less than 50 days ago) legacy firmware. In fact it's currently the latest stable build available.

- Invoke the Update routine in QNAP.
- Specify the update file manually.
- Have a strong liquor while waiting for the update running with a couple of beeps.
- Enjoy the successful backflip.

Yes

Are there any side effects in the downgrade?
Like for example the freshly updated version of the virtualisation station no longer running on the old firmware release?

Hopefully not but you'll know for sure when you've installed it. If something doesn't work, open a case with Qnap support. They will only fix problems they're made aware of.

Edit: okay, I was too slow and someone already made the mistake of installing a beta. Also avoid the firmwares with the title vQTS as those are intended for use in VMs only.

[fstueckradt]

No it's much simpler. Go to the Qnap Download Center, specify what NAS you have and download 4.3.6.0993 build 20190704 (avoid the beta versions at the top of the list).
Also I wouldn't call 4.3.6.0993 (released less than 50 days ago) legacy firmware. In fact it's currently the latest stable build available.

Thanks a lot P3R!
This rocked. It was a piece of cake, not even enough to get out the strong liquor.
Looks like the machine comes back on 4.3.6.0993 in good health.
I'm spechless about the firmware upgrade...
Because, if there would be the one essential function that a NAS should always and ever be able to provide, well, network shares would be a good choice.
How can deployment with this kind of error get though internal testing?

However, that's QNAP to find out and decide how to treat their customers.

Thanks a lot for your specific and qualified help!

Frank