mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 13:05:54 +03:00
[GH-ISSUE #10] problem after upgrading to 7.2 #200
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#200
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 @DervilRus on GitHub (Apr 1, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/10
Hello. I have a problem after upgrading to 7.2. Help me please. I have DS 920+. Today I updated to 7.2 After the reboot, I got a non-working SSD. Synology in NVME properties writes an unsupported device. Online assembly/restoration of the volume fails. Is there any chance that your script will help in my data recovery problem?
@DervilRus commented on GitHub (Apr 1, 2023):
Please take a look.
What can be done in this situation
DS920+, DSM_DS920+_64216. Before the update to this beta, everything worked fine.
@007revad commented on GitHub (Apr 1, 2023):
Running the script wont make it worse. If it doesn't help you can run the script again with the -- restore option to undo the change the script made.
Otherwise I'd suggest connecting the M.2 drive to a Linux computer (or boot a PC from a Linux boot disk) then mount the data partition and backup your data.
@DervilRus commented on GitHub (Apr 1, 2023):
Thank you very much for the answer. I solved the problem. Or rather, you solved my problem, but with another script, https://github.com/007revad/Synology_HDD_db, it helped!!!!!!!!
@aferende commented on GitHub (Apr 1, 2023):
Is the data in the storage pool/volume intact? All recovered?
@DervilRus commented on GitHub (Apr 1, 2023):
Everything is fine, the syno_hdd_db.sh script returned my status as the before to update to 7.2
@DervilRus commented on GitHub (Apr 1, 2023):
I have an idea. Maybe it makes sense to add to this script(Synology_enable_M2_volume) the addition of nvme to the database of compatible devices? I think right now, many will begin to face my problem.
@aferende commented on GitHub (Apr 1, 2023):
I think it makes sense too. Most people who buy M2 for NAS are not using the official Synology ones.
At least a message in the M2 script warning to recommend a vision of the HDD update script could be very useful, or a clear alert in the readme.md on the github homepage
@007revad commented on GitHub (Apr 1, 2023):
Good idea.
The syno_hdd_db.sh script would have enabled support_m2_volume, as well as adding your drives to the compatibility database.
@007revad commented on GitHub (Apr 1, 2023):
I've had a think about the suggestions and I can't add the NVMe drives to the drive compatibility db files in the syno_m2_volume.sh script because the db files get replaced when doing a DSM update.
I'll add a warning on the readme and show the warning in the syno_create_m2_volume.sh script that shows when it runs.
@007revad commented on GitHub (Apr 1, 2023):
I've added a warning on the Synology_M2_volume readme and updated Synology_M2_volume v1.2.12