[GH-ISSUE #158] How can I fix my m2 array storage pool. #233

Closed
opened 2026-03-12 18:21:30 +03:00 by kerem · 2 comments
Owner

Originally created by @lingyinsam on GitHub (May 26, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/158

Originally assigned to: @007revad on GitHub.

My Synology model is DS920+. Used your Synology_HDD_db script to create the hard drive whitelist.
I used two 1TB m2 SSDs to create a raid 1 array. I would like to know if I need to replace m2 in the array or if an m2 fails and needs to be replaced, how to rebuild the raid1 array after replacement.
The method in [https://github.com/007revad/Synology_M2_volume/wiki/Repair-M.2-RAID-1-in-internal-M.2-slots] cannot be operated because DS920+ does not support using m2 to create storage Pool, when rebuilding the array and selecting the hard disk, the new m2 cannot be selected. Prompt that the hard disk is installed in the slot used for caching (this is probably what it means).
Thank you so much!

Originally created by @lingyinsam on GitHub (May 26, 2024). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/158 Originally assigned to: @007revad on GitHub. My Synology model is DS920+. Used your Synology_HDD_db script to create the hard drive whitelist. I used two 1TB m2 SSDs to create a raid 1 array. I would like to know if I need to replace m2 in the array or if an m2 fails and needs to be replaced, how to rebuild the raid1 array after replacement. The method in [https://github.com/007revad/Synology_M2_volume/wiki/Repair-M.2-RAID-1-in-internal-M.2-slots] cannot be operated because DS920+ does not support using m2 to create storage Pool, when rebuilding the array and selecting the hard disk, the new m2 cannot be selected. Prompt that the hard disk is installed in the slot used for caching (this is probably what it means). Thank you so much!
kerem closed this issue 2026-03-12 18:21:35 +03:00
Author
Owner

@007revad commented on GitHub (May 26, 2024):

For a DS920+ the only script you need is Synology_HDD_db then you create an manage NVMe storage pools and volumes from storage manager.

A DS920+ does NOT need Synology_M2_volume or Synology_enable_M2_volume

The steps in Repair-M.2-RAID-1-in-internal-M.2-slots works for a DS920+ if you have the Synology_HDD_db script scheduled to run at boot.

I just tested it with my DS720+

  1. Opened Storage Manager and created RAID 1 storage pool and volume with 2 NVMe drives.
  2. Shut down the 720+ and removed 1 NVMe drive.
  3. Booted the 720+ so it detected the missing the NVMe drive and marked the storage pool as degraded.
  4. Shut down the 720+ and reinstalled the NVMe drive.
  5. Booted the 720+.
  6. Opened Storage Manager and clicked on the degraded NVMe storage pool.
  7. Clicked on the "repair now" link.
  8. Selected the unused NVMe drive.
  9. Clicked on Next then Apply.
<!-- gh-comment-id:2132050965 --> @007revad commented on GitHub (May 26, 2024): For a DS920+ the only script you need is Synology_HDD_db then you create an manage NVMe storage pools and volumes from storage manager. A DS920+ does NOT need Synology_M2_volume or Synology_enable_M2_volume The steps in [Repair-M.2-RAID-1-in-internal-M.2-slots](https://github.com/007revad/Synology_M2_volume/wiki/Repair-M.2-RAID-1-in-internal-M.2-slots) works for a DS920+ if you have the Synology_HDD_db script scheduled to run at boot. I just tested it with my DS720+ 1. Opened Storage Manager and created RAID 1 storage pool and volume with 2 NVMe drives. 2. Shut down the 720+ and removed 1 NVMe drive. 3. Booted the 720+ so it detected the missing the NVMe drive and marked the storage pool as degraded. 4. Shut down the 720+ and reinstalled the NVMe drive. 5. Booted the 720+. 6. Opened Storage Manager and clicked on the degraded NVMe storage pool. 7. Clicked on the "repair now" link. 8. Selected the unused NVMe drive. 9. Clicked on Next then Apply.
Author
Owner

@lingyinsam commented on GitHub (May 26, 2024):

I'll give it a try, thank you very much for your answer!

<!-- gh-comment-id:2132052701 --> @lingyinsam commented on GitHub (May 26, 2024): I'll give it a try, thank you very much for your answer!
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_M2_volume#233
No description provided.