Alles anzeigenQuTS hero h5.0.1.2376 build 20230421
2023-04-24
Applicable Models
- TS-h2490FU/TS-h1090FU
- TS-h1290FX
- TDS-h2489FU
Show more
Security Updates
- Applied multiple security updates to further enhance system security.
Fixed Issues
- Fixed an issue where searching NAS files in Windows 10 File Explorer would fail to return any results after updating QuTS hero to h5.0.1.2713.
- Fixed an issue in Network & Virtual Switch where the URL field did not accept more than 6 characters when configuring a customized DDNS server.
- Resolved an issue where attempting to remove a user from a shared folder's ACL permissions list would not remove the user, but instead removed a group with the same name as the user.
- Resolved an issue where attempting to add a user to a shared folder's ACL permissions list would cause an existing group to disappear if the group had the same name as the user.
- Fixed an issue where network connection issues would occur when users added both 10 GbE ports of the QXG-10G2SF-CX4 network expansion card to a virtual switch.
- Fixed an issue where users were sometimes unable to switch between different FEC (Forward Error Correction) modes for the QXG-25G2SF-CX6 network expansion card.
- Addressed an issue where users could not restore files from a snapshot to a remote location.
- Fixed an issue where after enabling Daylight Saving Time and then configuring a shutdown schedule, 10 minutes before the scheduled shutdown, the same confirmation message would repeatedly reappear.
- Resolved an issue where the system threw a password verification error even if the user entered the correct encryption password when creating a SnapSync job with an encrypted shared folder or LUN as the source.
- Fixed an issue where users would unexpectedly encounter a "No available storage pool" error message when connecting to the destination NAS in the SnapSync job creation wizard if the destination NAS account password contained space characters.
- Resolved an issue where attempting to add a user and a group with identical names at the same time to a shared folder's ACL permissions list would result in only the user being added.
- Fixed an issue where after configuring the firmware update schedule to weekly on Sunday, "0" would appear in the weekly field.
- Addressed an issue where the QXG-100G2SF-CX6 network expansion card could not be detected after updating QuTS hero to h5.0.1.2277.
- Fixed an issue where after upgrading QuTS hero from h4.5.3 to h4.5.4 or later, a LUN could not be expanded and different sizes would be displayed for the same LUN between Storage & Snapshots and iSCSI & Fibre Channel.
- Resolved a memory allocation issue that caused VAAI-enabled iSCSI LUNs to become disconnected and unresponsive when the system ran out of memory.
- Fixed an issue where running a backup job in Hybrid Backup Sync from a NAS running QTS 4.2.6 to a NAS running QuTS hero h5.0.1 would fail with an error.
- Fixed an issue in File Station where users would encounter an input error message when trying to create a share link, if the DDNS server happened to be unreachable at that moment.
- Fixed an issue in Notification Center where under certain conditions, delivered email notifications would not display the email subject line properly.
- Addressed an issue in QuLog Center where after creating a style rule with an "Excludes" condition in the Display Style Settings screen, the condition would change to "Includes" upon reopening the settings screen.
- Fixed an issue where after successfully dragging and dropping a file between two File Station windows, the source window would not refresh.
- Resolved an issue where specifying an iSCSI target alias that contained space characters could cause the target to become unreachable.
- Fixed an issue in HybridMount where guest access to a remote mount would unexpectedly be reset to "Deny Access" every time after the mount was reconnected.
- Fixed an issue where installing over 24 disks on a NAS would cause Qfinder Pro for Windows to incorrectly indicate that the NAS was in an abnormal state.
- Fixed an issue where QuTS hero was sometimes unable to display the installed firmware version of a connected JBOD enclosure.
- Fixed an issue where after creating a Snapshot Replica job and using an external storage device to transfer data to the destination for the first run, running the job the second time would cause an already transferred snapshot at the destination to be destroyed, and the job would fail.
- Resolved an issue where users could not set up and enable an additional domain controller or a read-only domain controller if the specified password contained a special character.
- Fixed an issue where transferring large files (over 3 GB) via SMB would become slow after a firmware update.
- Improved the speed of transferring large files via SMB.
- Fixed an issue where the NAS would stop responding when deleting a chain of related snapshots and snapshot clones.
- Fixed a rendering issue in File Station where shared folder information would not display correctly.
- Fixed an issue where users could not create share links in File Station, Qsync Central, and Qsync Client.
- Fixed a rare issue where after replacing a faulty disk in a RAID group with a healthy disk and rebuilding the RAID group, the RAID group would still remain degraded.
- Fixed an issue where static route settings would revert to default values after restarting the NAS.
- Resolved an issue where under certain circumstances the kernel log would become flooded with unnecessary messages.
- Resolved an issue where users could not configure LDAP authentication if the LDAP server password contained certain special characters.
- Fixed an issue where after updating to QuTS hero h5.0.1.2277, if the NAS had over 16 LUNs, Storage & Snapshots would stop responding when users tried to create a Snapshot Replica job.
- Fixed an issue where real-time SnapSync jobs would become inactive after modifying the source or destination NAS hostname.
- Resolved a rare issue where after updating Container Station to 3.0.0.122, there was a chance the NAS would restart or shut down unexpectedly after some time.
- Fixed some Korean translation issues in Control Panel.
- Fixed some French translation issues in Storage & Snapshots.
- Fixed an issue where some users frequently received notifications that myQNAPcloud Link service was ready.
- Fixed an issue in QuLog Center where the timestamps for event logs were incorrectly displayed in Safari.
- Fixed an issue where users could not import certain custom root certificates to certify the SSL certificate of a server that the NAS needed to access.
Known Issues
- After users edit LUN settings and run a Snapshot Replica job, the destination NAS cannot correctly display LUN information in Snapshot Vault.
- Storage & Snapshots and iSCSI & Fibre Channel sometimes display different sizes of the same LUN after users revert a LUN by importing a snapshot.
QuTS hero h5.0.1.2376 build 20230421 released
-
- X86
- QuTS
- Xydoc
- Unerledigt
-
-
Hi, also bei mir lief die Installation durch. Will nicht was falsches behaupten, aber habe vermutlich seit dem Update Probleme mit einem lxd Container. Muss das noch genauer beobachten. Vielleicht hat ja jemand Erfahrungen mit der oben genannten Version und Containerstation?
Ein schönes langes Wochenende wünschend
-
Unter Berechtigungen ist die UID des Benutzers "admin" = 0
Merkwürdig oder Normalfall? Ich dachte die UID werden logisch aufsteigend ab 500 oder 1000 vergeben?
Weiter noch:
Im CS sind einige Docker-Installationen grau dargestellt. Stimmt hier vielleicht was nicht mit den Berechtigungen?
-
Der User mit UID 0 und GID 0 ist der einzige wahre root-User unter Linux der alles darf. Wie der heißt (normal root, bei QNAP admin) wird beim kompilieren des Kernels festgelegt.
-
Danke
-
Also ich musste unter Docker einige Container neu erstellen. War aber nicht so wild. Was ich aber nicht verstehe, dass ich mit einem LXD Container echt Probleme habe. Habe dort keinen Root Zugriff mehr. Hatte zunächst aus einem Backup neu erstellt. Hat gepasst, nun habe ich das Problem wieder, aber will nicht nochmal wieder alles einspielen. Das Problem kommt vermutlich nach einem Neustart. Vermutlich mache ich heute Abend ein Ticket auf und sitze für Not das Problem aus, bis zur Hero 5.1.0 und entsprechend neuer Container Station. Hat noch wer das Problem?