mirror of
https://github.com/007revad/Synology_M2_volume.git
synced 2026-04-25 07:46:05 +03:00
[GH-ISSUE #40] Split SSD for cache and volume use #6
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_M2_volume#6
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 @Protoncek on GitHub (Apr 27, 2023).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/40
Hello!
I have ds920+ and i won't be able to create volume officially. So, i wonder, is it possible to use my two SSD's partially for creating volume and rest of space for synology cache? I have 2x500GB SSD's and my syno cache advisor says that i need cache of 250GB. I'd like to have an SSD volume of not more than 100GB for Home Assistant use, rest of space i'd use for cache.
Possible?
@007revad commented on GitHub (Apr 28, 2023):
I don't think it's possible. DSM won't let you split an NVMe drive into cache and volume. It won't even let you set the storage pool or volume size on a single NVMe drive (it will on a pair of NVMe drives as RAID 0 or 1). If a script created a storage pool with a volume and a cache partition I don't think DSM would mount it or use it.
@Protoncek commented on GitHub (Apr 28, 2023):
Yeah, that’s what i feared… thanks for info. And thanks for this script, too. Since ds920 isn’t supported officially it will come handy at a later stage perhaps.
Yesterday i disabled ssd cache only - just for testing, and home assistant pretty much goes to a crawl without it, so it seems that it runs from ssd anyway. I guess i wouldn’t gain much if i create ssd volume to replace current ssd cache anyway.