mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #61] SSD Volume Support in older NAS models #27
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#27
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 @jakemauer on GitHub (Apr 19, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/61
Hi Dave,
First thanks for writing and maintaining this script. I have a DS1019+ with two 512gb M.2 SSDs that I had been using as a RAID1 volume. I set up the volume via the commandline using instructions that I found on Reddit and it has been performing just fine.
I found this script today and decided to give it a shot to see if I could create an SSD storage Volume via the DSM. I deleted my existing volume and ran the script, then rebooted, however the DSM is still saying that I can't create a storage pool because I don't have any drives that meet the requirements.
Is creating SSD storage volumes in "unsupported" older NAS models actually a thing this script should allow or have I misunderstood?
Here's what I see in the drive requirements modal window:
Thanks for your time!
@007revad commented on GitHub (Apr 20, 2023):
The M.2 volume part of the Synology_HDD_db script only seems to work on newer models. I do have another script that works on all models with DSM 7.1.1 or newer.
https://github.com/007revad/Synology_M2_volume
@jakemauer commented on GitHub (Apr 20, 2023):
oh wow I didn't realize you had that separate script. Thank you!