QuTS hero h6 SMB problems

Beta Program Archive QuTS hero h6.0 Beta
1

I’ve just re-initialized our QNAP TS-h1683XU-RP so I could swap from QTS to QuTS and am facing a very weird issue with a specific software and file format.

When running Autodesk 3dsmax, some plugins are in .dlt format, and even though they’re visible to the NAS (Win10 SMB connection), once it tries to read them it gives an error saying failed to initialize (Error code 126 - The specified module could not be found). I’ve tried doing new Pools and just having those files there to see if there was anything wrong, but same result. If I copy the same files to my desktop, they load perfectly, but once I try to read them from the NAS, they won’t work.

I’ve tried almost everything, but here’s some of the things I remember:

  • Restart SMB service
  • Update NAS, Windows, Visual C++, 3dsmax to the latest versions
  • Restart Workstation Service
  • Remount shares using UNC and IP and on different Drive letters
  • Access from a different NIC on the NAS
  • Restart NAS
  • Restart PC
  • Restart Network (Unifi)
  • Enable/Disable Jumbo Frames
  • Give full permitions to every user
  • Windows “Unblock” option on the files
  • Turn off any firewalls/antivirus

I’m out of ideas, specially because it’s just this kind of file, and it’s happening to other 10 workstations the similar problem. Sometimes one of the workstations can read the file, but if it tries again later, it can’t anymore, it’s very random.

2

I know Solidworks and Autodesk have specific issues with folder path lengths.

Are these problematic files within long depth paths ? (Try to reduce the path length as a test)

3

Everything is the same as it was before with QTS. Same named, same place. Ive also tried do put it on the root and has the same behaviour.

Backup was done one with robocopy and one with HSB3. Restore the files from bota copies, to see if it had been how it was backed up, but have the same error

4

I just shutdown the NAS and uplugged the power cords for 1 min and turned it back on and one of the NIC cards disappeared and isn’t found

5

I think I have a lead on the problem.

Since I was using Ext4 it wasn’t a problem but it seems it is with ZFS. Some of the softwares, like 3dsmax, normalize the path of some requests and lowercase the path required, making it different from the existing one. Is there a way to mitigate this without renaming 50TB of information?

6

Hi, thank you for providing the information. I will forward it to our internal team for further investigation and confirmation. Thanks!

7

Thanks for the information! We’ve tried to replicate the issue on our end, but haven’t been successful so far. If it’s convenient for you, could you share a sample .dlt file—specifically one that works on Windows but doesn’t work on the NAS? I’d like to pass it to our technical team to see if they can identify the cause. Thanks for your help!

8

Also, I’d like to confirm: are you currently using the max2026 plugin? Thank you!

9

We’ve re-initialized the NAS and went back to version 5 as version 6 SMB connection was very unstable, the graphics looked like an earthquake was happening. Also the file path naming issue was a deal brake and with 5 the connection is very stable and the path naming is correct or at least it isn’t changing it anymore when looking through Procmon.

10

Samba is case-insensitive when talking to windows clients.
It should not be possible to hit the linux filesystem with mixed case. Samba is going to use file handles to interface with the FS, not file names.

Very weird problem.