mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 13:05:54 +03:00
[GH-ISSUE #177] DSM 7.2.1-69057 Update 5 not working #247
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#247
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 @Deftone-Squad on GitHub (May 1, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/177
Hi there, it looks like the "Synology enable M2 volume" script is not working with the DSM 7.2.1-69057 Update 5 on the DS1821+.
I tried it several times with the tasked schedule in combination of the hdd vendor script but it's not working.
Is there an update in the work?
Regards
@007revad commented on GitHub (May 1, 2024):
You don't need "Synology enable M2 volume" on a DS1821+. You only need "Synology_HDD_db".
syno_enable_m2_volume.sh -r@Deftone-Squad commented on GitHub (May 2, 2024):
Ok just to make clear I have 2 DS1821+.
On Nr. 1 I added the scheduled task to Update 4 and then updated to 5 --> worked.
On Nr. 2 I added the scheduled task after updated to 5 --> not working.
I now have added --restore to the scheduled path which looks like this:
/volume2/Synology Scripts/Synology_HDD_db/Synology_HDD_db-3.5.89/syno_hdd_db.sh --restore
On both DS1821+ this leads to no change at all.
Is there a limit in the path length?
I'm sorry but I have no experience in scripts so I'm very happy that you made that pictured guidance.
@007revad commented on GitHub (May 3, 2024):
I meant run "Synology enable M2 volume" with it's restore option.
"/volume2/Synology Scripts/Synology_enable_M2_volume/Synology_enable_M2_volume-1.1.21/syno_enable_M2_volume.sh" --restore"/volume2/Synology Scripts/Synology_HDD_db/Synology_HDD_db-3.5.89/syno_hdd_db.sh" -n@Deftone-Squad commented on GitHub (May 3, 2024):
Ok the following drives are installed:
After trying several times the procedures above nothing - helped!
I make a completely clean install on one of the 2 DS1821+ and the newest DSM 7.2.1-69057 Update 5 was installed.
After that I tried the "Synology HDD db" and yes the Samsung SSD is listed as registered.
The Samsung M2 is still not registered and do NOT let me use it as a Pool or Volume.
I then added the "Synology enable M2 volume" and still do NOT let me use it as a Pool or Volume.
So to me after Update 5 both scripts do NOT helped for the M2.
@007revad commented on GitHub (May 4, 2024):
Does Storage Manager show the NVMe drive?
@Deftone-Squad commented on GitHub (May 4, 2024):
Yes
@007revad commented on GitHub (May 4, 2024):
I just removed my HDDs from my DS1821+, installed a spare HDD and did a clean install. During the install it updated to DSM 7.2.1 Update 5. Then I manually ran
syno_hdd_db.sh -nfrom Task Schedule, then closed and reopened Storage Manager and I was able to create a volume on the NVMe drive.Can you go to "Control panel > Task Scheduler" then:
@Deftone-Squad commented on GitHub (May 4, 2024):
New Install only on the Samsung 940 Pro and then done the steps above:
@007revad commented on GitHub (May 4, 2024):
Enable HDDfolder toEnable_HDDso there's no space.Then try the steps again.
@007revad commented on GitHub (May 4, 2024):
Enable HDDfolder toEnable_HDDso there's no space.Then try the steps again.
@Deftone-Squad commented on GitHub (May 4, 2024):
Worked!
The space was the mistake...just that simple. Maybe you add a notice in your guidance, for beginner like me.
Thank you very much for your support!
@Deftone-Squad commented on GitHub (May 4, 2024):
Now I can finally post the result:
Synology_HDD_db v3.5.89
DS1821+ DSM 7.2.1-69057-5
StorageManager 1.0.0-0017
ds1821+_host_v7 version 8054
Using options: -n
Running from: /volume1/Scripts/Enable_HDD/Synology_HDD_db-3.5.89/syno_hdd_db.sh
HDD/SSD models found: 1
SSD 840 PRO Series,DXM06B0Q
M.2 drive models found: 1
Samsung SSD 970 PRO 512GB,1B2QEXP7
No M.2 PCIe cards found
No Expansion Units found
[0;33mSSD 840 PRO Series[0m already exists in [0;36mds1821+_host_v7.db[0m
[0;33mSamsung SSD 970 PRO 512GB[0m already exists in [0;36mds1821+_host_v7.db[0m
Support disk compatibility already enabled.
Support memory compatibility already enabled.
NVMe support already enabled.
M.2 volume support already enabled.
Drive db auto updates already disabled.
DSM successfully checked disk compatibility.
You may need to [0;36mreboot the Synology[0m to see the changes.
@007revad commented on GitHub (May 4, 2024):
I'll update the instructions.