Dumb Q - can I create a Pool and also use M2 for cache?

[palouis64]

I have used a pair of Kingston 2Tb M.2 drives in my DS1821+ and my cache advisor only wants 200Gb used. I've tried using the script but it complains about DSM being on disk

Is there a way I can se aside say 300Gb for cache and then use the remaining space for a RAID1 pool? Also when I was testing things I noted that if I create a pool I there is no TRIMm option available to me in settings?

Regards

Paul

[007revad]

DSM won't let you use M.2 drives for both a cache and a volume. They have to be either a volume or a cache.

With a DS1821+ using DSM 7.2 or later you only need https://github.com/007revad/Synology_HDD_db to be able to create and manage M.2 volumes. You'd have to delete the cache first.

SSD drives need to support DRAT and DZAT for TRIM to be available in DSM. I can check if SATA or SAS SSDs support TRIM but for NVMe drives I haven't found how to determine if they support TRIM or not. But apparently all conforming NVME drives should at least support DRAT (Deterministic Read After Trim).

grep TRIM /var/lib/diskaction/diskaction.xml returns:

<disk model="MZ7LH(240|480|960|1T9|3T8|7T6)H(AHQ|AJR|MLT|MLA)" eunit="RX1217sas">TRIM_OFF</disk>
<disk model="MZ7LH(240|480|960|1T9|3T8|7T6)H(AHQ|AJR|MLT|MLA)" eunit="RX2417sas">TRIM_OFF</disk>
<disk model="CT.*MX300SSD.*">TRIM_OFF</disk>
<disk model="ST.*FM.*3">TRIM_OFF</disk>
<disk model="HUSMR16..ASS2(0|3)(0|1|4|5)">TRIM_OFF</disk>
<disk model="SNV[0-9]*[a-zA-Z]*">TRIM_OFF</disk>

Does your Kingston NVMe model number start with SNV and then numbers or letters?

What do the following commands return?

sudo synonvme --model-get /dev/nvme0
sudo synonvme --model-get /dev/nvme1

[palouis64]

Thanks Dave for such a quick response! Bummer I can’t have cache and volume - seems arbitrary but anyway …. The SSDs are Kingston SNV2S2000G M.2 drives. I guess I’d be better off as volume to run HyperV systems, as others the system is file storage. Of course assuming TRIM is available. Regards Paul

[007revad]

I edited your reply because you had included the email notification, which showed your mobile number, home address, facebook and linkedin usernames.

[007revad]

Unless you're running a web server or database with lots of users you are better off with a NVMe volume than a cache.

The SSDs are Kingston SNV2S2000G M.2 drives.

The "SNV[0-9]*[a-zA-Z]*" regex in /var/lib/diskaction/diskaction.xml matches the SNV2S in SNV2S2000G so DSM would prevent the TRIM option from appearing in storage manager for your Kingston NVMe drives.

This command will remove the TRIM_OFF line for Kingston SSD drives.

sed -i '/.*<disk model=\"SNV.*TRIM_OFF<\/disk>/d' /var/lib/diskaction/diskaction.xml

But Synology would have had a good reason to disable TRIM on Kingston SSDs from their compatibility testing.

[007revad]

Bummer I can’t have cache and volume - seems arbitrary but anyway ….

It's definitely an arbitrary Synology thing. Other NAS brands allow a cache and volume on the same SSD drive.

[palouis64]

Thanks Dave, I’ll go with Volume and mirrored, Id imagine not much risk of 2 drives going fritz at once. Id imagine the TRIM disable is probably another attempt to force use of their 10x expensive SSD. I’ll let you know if any issues arise. Thanks again mate Cheers,
 Paul

…

On 2 Jun 2024, at 12:31 PM, Dave Russell ***@***.***> wrote: I edited your reply because you had included the email notification, which showed your mobile number, home address, facebook and linkedin usernames. — Reply to this email directly, view it on GitHub <#159 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI3BE6VDKNH7L2MC3ODRYM3ZFJ7XFAVCNFSM6AAAAABIT5KFZ2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMMZUGIZDC>. You are receiving this because you authored the thread.

[palouis64]

Hi Dave Ive setup as a Pool and Volume but despite running your suggested script I can’t enable TRIM on the Pool with the M.2 drives. Suggestions? Thanks mate Paul

…

On 2 Jun 2024, at 1:27 PM, Dave Russell ***@***.***> wrote: Bummer I can’t have cache and volume - seems arbitrary but anyway …. It's definitely an arbitrary Synology thing. Other NAS brands allow a cache and volume on the same SSD drive. — Reply to this email directly, view it on GitHub <#159 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI3BE6VIOOQRFLT56X3XZGDZFKGKZAVCNFSM6AAAAABIT5KFZ2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMMZUGQ4TG>. You are receiving this because you authored the thread.

[palouis64]

Belay that mate It suddenly came on. TRIM is ok. Thanks P

…

On 2 Jun 2024, at 1:27 PM, Dave Russell ***@***.***> wrote: Bummer I can’t have cache and volume - seems arbitrary but anyway …. It's definitely an arbitrary Synology thing. Other NAS brands allow a cache and volume on the same SSD drive. — Reply to this email directly, view it on GitHub <#159 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI3BE6VIOOQRFLT56X3XZGDZFKGKZAVCNFSM6AAAAABIT5KFZ2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMMZUGQ4TG>. You are receiving this because you authored the thread.

[007revad]

Thanks for confirming that sed -i '/.*<disk model=\"SNV.*TRIM_OFF<\/disk>/d' /var/lib/diskaction/diskaction.xml worked.

[palouis64]

Yep and again THANK YOU for superb support mate. Cheers,
 Paul

…

On 3 Jun 2024, at 10:21 AM, Dave Russell ***@***.***> wrote: Thanks for confirming that sed -i '/.*<disk model=\"SNV.*TRIM_OFF<\/disk>/d' /var/lib/diskaction/diskaction.xml worked. — Reply to this email directly, view it on GitHub <#159 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI3BE6UXCCMFQLUAMR25NNTZFOZHRAVCNFSM6AAAAABIT5KFZ2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMNBRGUYTO>. You are receiving this because you authored the thread.