-
-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DS423+ Supported with 1 nvme driver only #243
Comments
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 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... Maybe it will survive an DSM update anyway ? |
The DS423+ is one of the 8 Synology models that officially support NVMe volumes, so you didn't the script. |
yes and no, in order to create storage volumes officially on DS423+ , you need 2 x nvme drives 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 |
I also think creating volumes you need an official synology brand for nvme drives , (if 2 x nvme are installed) |
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. |
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 |
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. |
Ok that makes sense :-) |
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)
The text was updated successfully, but these errors were encountered: