mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #168] Sharing test results for all models in DSM 7.2.1-69057 Update 4 #246
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_M2_volume#246
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PeterSuh-Q3 on GitHub (Feb 24, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/168
I have tested all models supported by Redpill in DSM 7.2.1-69057 Update 4 (based on TCRP).
TCRP supports a total of 9 platforms that support Epyc7002.
Among them, DS3615xs (Bromallow) was discontinued in 7.1.1.
As of now, DSM 7.2.1 brings the total to 8 platforms.
I supplemented it further by referring to your results sheet.
I added the results of the new working SA6400 and the non-working DS3615xs and DVA3221, and tested all of DSM 7.2.1-69057 Update 4.
All Broadwillnks do not work as expected except for the special DS1621xs+ which I discussed with you last time.
https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/nvmevolume-onthefly#readme
I simplified the hexa patching of libhwcontrol.so.1 further as shown below.
This is similar to the method I used with my nvme-cache addon.
https://github.com/PeterSuh-Q3/tcrp-addons/blob/main/nvmevolume-onthefly/src/install.sh
Due to the nature of Redpill, it needs to be activated immediately after DSM installation is completed and the logon account is created, so the OS ON LOAD point where tmpRoot is used was used.
My script also operates in the same way as your result sheet regarding whether each model operates or not.
@PeterSuh-Q3 commented on GitHub (Feb 24, 2024):
In the case of DSM 1019+, NVMe cache must be activated with the Hexa patch in the libsynonvme.so.1 file, and only one can be used.
@19jm81 commented on GitHub (Apr 27, 2024):
Any news on DSM 7.2.1-69057 Update 5?
@007revad commented on GitHub (Apr 27, 2024):
@19jm81
DSM 7.2.1-69057 Update 5 should not be a problem because the only change Synology made was to fix a bug that prevented 7.2.1-69057 Update 4 updating to 7.2.2 (which hasn't been released yet).