mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #118] Storage pool on E10M20-T1 on DS1618+ cannot be created #552
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#552
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 @Edwardvanderveen on GitHub (Jul 18, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/118
Awsome script. Two remarks:
on my DS1618+ i have a E10M20-T1 card with two samsung 980 pro 2tb nvme. I deleted the cache and ran the script, but synology 7.2-64570 update 1 does not allow me to create a storage pool on the pcie card. Anything I am doing wrong or forgetting?
Since the nvme's are getting bigger, is it possible to partition the nvme's and use one partition on both nvme's as cache and the other partitions on both nvme's as storage pool with raid?
Thanks for the work! Edward
@007revad commented on GitHub (Jul 19, 2023):
The DSM ui won't let you create a storage pool on NVMe drives in PCIe card. But my https://github.com/007revad/Synology_M2_volume script will partition the drive and create the storage pool so you can then do an online assemble and create the volume in storage manager.
I haven't looked at how DSM creates or manages an NVMe cache, but since a couple of people have asked about splitting NVMe drives into cache and storage pool I will eventually have a look at it.
@Edwardvanderveen commented on GitHub (Jan 29, 2024):
Hi, did you ever had the opportunity to look whether the enhancement I proposed for large SSD drives was possible?
Thanks for the great work Edward
@007revad commented on GitHub (Jan 29, 2024):
Cache drives have 1 single partition that uses the whole drive. Drives with storage pools have some free space, a system partition, a swap partition and a data partition. DSM expects the cache to be partition 1. But on a data drive partition 1 is the ssytem partition. So I don't think it's possible.
FYI, this script, since v3.3.70, now enables creating storage pools in Storage Manager for M.2 drives in PCIe adaptor cards (for DSM 7.2.1 and above only). So there's no need for the syno_m2_volume script.