TS-131P QTS 4.3.6.0993 build 20190704 Official

Release Notes for QTS

[Important Notes]

  • To learn more about NAS models that support the TR-004/TR-002, see the Compatibility List at https://www.qnap.com/en/compatibility-expansion
  • To use a TR-004 external RAID enclosure to expand NAS storage space, the enclosure must have exactly one external RAID group. Individual disks cannot be used to expand NAS space.
  • To ensure system functionality, after updating QTS to 4.3.6, please also update Container Station to 1.9 in App Center before enabling QVR Pro.
  • The RADVD service previously did not have an outgoing interface. Please reconfigure the RADVD service after upgrading.
  • Due to security concerns, support for "Wi-Fi ad-hoc mode" has been removed.
  • This QTS update changes the file system of the system partition to ext4 for ARM-based models with Annapurna Labs processors. For data security reasons, you are not able to downgrade QTS to a previous version after this update.

Affected models: TS-131P, TS-231P, TS-431P, TS-531P, TS-231+, TS-431+, TS-231P2, TS-431P2, TS-431X, TS-431X2, TS-531X, TS-831X, TS-1231XU-RP, TS-1231XU, TS-831XU-RP, TS-831XU, TS-431XU-RP, TS-431XU, TS-431XeU, and TS-1635.

Kernel 3.10.20: TS-128, TS-228
Kernel 3.2.26: TS-x31, TS-x31U
Kernel 3.4.6: TS-x69, TS-x69U, TS-x69L
Kernel 4.2.8: all other models supported by QTS 4.3.6

  • Due to the limitations of future kernel updates, QTS 4.3.6 is the final available QTS update for the following NAS models: TS-EC1679U-SAS-RP, TS-EC1679U-RP, TS-1679U-RP, TS-EC1279U-SAS-RP, TS-EC1279U-RP, TS-1279U-RP, TS-1079 Pro, TS-EC879U-RP, TS-879U-RP, TS-1270U-RP, TS-870U-RP, TS-470U-RP, TS-470U-SP, TS-879 Pro, TVS-870, TS-870 Pro, TS-870, TVS-670, TS-670 Pro, TS-670, TVS-470, TS-470 Pro, and TS-470.
  • Due to the limitations of non-expandable memory capacity and 32-bit processor architecture, starting from QTS 4.3.6, the TS-128 and TS-228 no longer support Container Station and all the dependent applications, including Notes Station 3, Qcontactz, QcalAgent, AWS Greengrass, and QIoT Suite Lite.


[Fixed Issues]

  • Fixed a checksum validation vulnerability in Samba Active Directory domain controllers.
  • Guest users could not access SMB shared folders even when administrators disabled access restrictions in Control Panel > Win/Mac/NFS > Microsoft Networking > Advanced Options.
  • The Smart Installation Guide on the ARM models did not inform users that disks would be formatted during QTS installation.
  • TwonkyMedia server could not finish file scanning when the TwonkyMedia database contained a large number of files.
  • Control Panel could not display available domain groups when users edited shared folder permissions after joining the NAS to a domain.
  • Users sometimes could not access file-based iSCSI LUNs in Windows File Explorer when storage space on the volume was full.
  • The Thunderbolt connection between the NAS and the Mac would drop unexpectedly when users manually set the Mac in sleep mode.
  • The QNA-UC5G1T USB 3.0 to 5GbE adapter could not be detected again after users restarted the NAS when QNA-UC5G1T and other USB devices were connected to the NAS.
  • Control Panel could not display available domain groups when users edited shared folder permissions after setting the NAS as a domain controller.
  • Users would be signed out of myQNAPcloud after restarting vQTS in Virtualization Station.
  • OpenSSH command line interface would not start a new line when users entered a long NAS folder path.


[Known Issues]

  • When a TR-002 external RAID enclosure is connected to a USB 3.1 Gen2 port on the NAS, the bus type incorrectly appears as USB 3.0 in the QTS UI. This is a UI problem only, data will actually be transferred at USB 3.1 Gen2 speeds.
  • When data is being transferred to or from a QNAP external RAID enclosure, changes to the status of a degraded RAID group might not be visible immediately in Storage & Snapshots.
  • When an external RAID group is in degraded mode its read/write performance will be greatly reduced.
  • A failed external RAID group may have the status "Unknown" instead of "Failed".