mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #93] DS923+ already succeed with Synology_M2_volume, should I run this Synology_enable_M2_volume? #442
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_M2_volume#442
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 @uliod on GitHub (Jul 10, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/93
Hi 007revad, BIG thanks for sharing these great scripts, as I have already run Synology_M2_volume script last weekend on my DS923+, and successfully created volume with my 2T West Digital NVMe drive.
Now I am planning to add one more NVMe drive to DS923+, as it has two NVMe slots. My plan is to bind these two drives and create a 4T pool as a whole, instead of two separate 2T volumes. But I am not sure what to do with that... It seems I have to run this new Synology_enable_M2_volume script and then choose the JBOD mode in Disk Manager, is that correct? And do I need to erase the previous Synology_M2_volume script before I run the new one?
Many thanks!
Chris
@007revad commented on GitHub (Jul 26, 2023):
Sorry, somehow I didn't see this issue until now.
You've probably answered your own question by now. You are correct. I'd use the Synology_enable_M2_volume script and then choose the JBOD mode in Disk Manager.