-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
NOT working on Synology 720+ with DSM 6.2.4 update 7. #64
Comments
Can you post the output of the script. |
I will run it again as I lost connection to the SSH session at 90%. I did run the script again and it told me data scrubbing is running. Once that was finished, I rebooted the 720+, and I am able to see the SSD pool, but no volume is created. |
Is it possible to create the volume once the SSD Pool has been created? |
If you run it again, now that the data scrubbing has finished, it should work (unless something changed between 6.2.4 update 6 and update 7). Because DSM 6 does not have the "online assemble" the script does create the volume for DSM 6, so after a reboot the storage pool and volume should show up in storage manager without you needing to do anything else. Personally I would upgrade to DSM 7.2 unless you have some USB device or app that needs DSM 6. If you do update to DSM 7.2 use https://github.com/007revad/Synology_HDD_db instead. You'd need to update to 7.0.1 first: DS720+ DSM 7.0.1-42218 |
Thank you for the response. I use DSM 6 as Moments has better subject / facial recognition. I am running the script again and will post the entire SSH session output. |
Did the script work? |
On the 3rd attempt the script worked! |
NOT working on Synology 720+ with DSM 6.2.4 update 7.
It will create the storage pool, but the volume is not created. I do not see any option for creating a volume from the SSD storage pool.
Config: two 500GB SSD, configured in RAID 1.
I had this working on DSM 7.1.1 with RAID 0, but I downgraded to DSM 6 and the script is not able to create the volume.
Originally posted by @Ruben-Isai in #52 (comment)
The text was updated successfully, but these errors were encountered: