mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #196] Error after using DTS file #470
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#470
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 @bdrwu on GitHub (Sep 17, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/196
I'm using SA6400 model 7.2.2
NVME creates a storage pool when DTS is not used. Shut down and then on again. The storage pool is normal.
However, if you create a storage pool after compiling DTS and then shut down and then restart the storage pool, an error will occur.
The following is some information about DTS
nvme_slot@1 {
pcie_root = "0000:00:01.0,00.0,03.0,00.0";
port_type = "ssdcache";
};
nvme_slot@2 {
pcie_root = "0000:00:01.0,00.0,07.0,00.0";
port_type = "ssdcache";
};
@007revad commented on GitHub (Sep 17, 2024):
Run https://github.com/007revad/Synology_HDD_db
@bdrwu commented on GitHub (Sep 22, 2024):
All are used
This problem only occurs on original factory models that do not support NVME storage pools.
And there is a phenomenon that when compiling DTS files, the file is lost and is not supported by DSM at present.
If you don’t use DTS files, there will be no problem
However, SATA hot plug will be invalid because the SATA PORT does not correspond.
For example, the 923+ original factory supports the use of DTS files for NVME storage pools without any problem.
But SA6400 920+ or other DT models that do not support NVME storage pools
The above error will occur after compiling DTS files.