mirror of
https://github.com/007revad/Synology_SHR_switch.git
synced 2026-04-25 16:25:53 +03:00
[GH-ISSUE #51] SHR (not an issue) #3
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_SHR_switch#3
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 @jjvelar on GitHub (Jun 1, 2024).
Original GitHub issue: https://github.com/007revad/Synology_SHR_switch/issues/51
Originally assigned to: @007revad on GitHub.
Hi @007revad,
Thanks for providing these scripts. Much appreciated.
I am currently using a RAID1 configuration but plan to add additional drives so your script allows me to consider migrating to RAID5 or SHR.
How dows this work? I mean, I am not an expert user but Synology does not allow to move from RAID to SHR, so was wondering which kind of sorcery :-) are you using, and which will be the process.
Thanks in advance for your help and support.
@007revad commented on GitHub (Jun 1, 2024):
The script doesn't allow changing an existing RAID 5 storage pool to SHR, or vice versa. It only enables the option to create an SHR storage pool on enterprise models that don't have SHR.
@jjvelar commented on GitHub (Jun 1, 2024):
Oh, I see.
Thanks for clarifying.
On Sat, Jun 1, 2024 at 11:02 PM Dave Russell @.***>
wrote: