mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #243] DS423+ Supported with 1 nvme driver only #91
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#91
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 @pergolafabio on GitHub (Feb 12, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/243
First of all, thnx a lot for this script!!! Works great
Usefull for other people:
DS423+ here, added only 1 x Samsung 970 evo plus TB
Running this script only is enough to make a storage pool from 1 nvme driver only
DSM 7.2.1-69057 Update 4 ( at this moment)
@pergolafabio commented on GitHub (Feb 13, 2024):
hey @007revad , can you explain below?
I got a new DS423+ , i had an old SATA disk, only 1 disk present in the 4 bays, this was pure for testing the DS423
Also inserted one nvme syno drive , also for testing and your script worked, i was able to create a storage pool on the nvme
Now i purchased 4 new SATA drives, removed the old DISK, inserted 4 new DISKs ... i rerpesented me the wizard to setup a new DS423+ ... all OK
What i noticed, the DS423+ already recognized the storage pool on the nvme drive? without running your script...
How is that possible? Is it because the drive is already created as a storage pool before?
Maybe it will survive an DSM update anyway ?
@007revad commented on GitHub (Feb 13, 2024):
The DS423+ is one of the 8 Synology models that officially support NVMe volumes, so you didn't the script.
@pergolafabio commented on GitHub (Feb 13, 2024):
yes and no, in order to create storage volumes officially on DS423+ , you need 2 x nvme drives
if only 1 is used, its only cacche
When i first installed DSM on the test drive, and i inserted the nvme drive later, i was not able to create a volume on the nvme, only after i runned your script
@pergolafabio commented on GitHub (Feb 13, 2024):
I also think creating volumes you need an official synology brand for nvme drives , (if 2 x nvme are installed)
@007revad commented on GitHub (Feb 13, 2024):
DSM should let you create an NVMe volume with just 1 Synology NVMe drive.
With my script I don't need Synology branded NVMe drives and can create a Basic or SHR storage pool and volume on just 1 NVMe drive. All my script does (for NVMe drives) is make DSM think my NVMe drive is a Synology NVMe drive.
@pergolafabio commented on GitHub (Feb 13, 2024):
Yeah, but i have an "Samsung EVO 970 plus drive" :-) , it should not be possible
It was not possible when i first installed the DS423+ ... after running the sript, i was able to create the volume , not before
After replacing the DISKS in drive bay and reinstalling the DS423+ , the volume on the nvme was default visible
@007revad commented on GitHub (Feb 14, 2024):
Okay. In your 2nd comment you mentioned "inserted one nvme syno drive" so I thought you had a Synology NVMe drive.
DSM copies the system partition to all drives that have a storage pool on them (including NVMe drives even though DSM never runs from an NVMe drive).
So when you removed the single HDD the settings changes made by the script remained on the NVMe drive, which DSM would have copied to the new HDDs.
@pergolafabio commented on GitHub (Feb 14, 2024):
Ok that makes sense :-)