mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 05:35:59 +03:00
[GH-ISSUE #5] Reboot not necessary on db change #506
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#506
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 @mh-muc on GitHub (Mar 7, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/5
The reboot on changing the drive db is not necessary, just execute this and the drive db will be reloaded:
/usr/syno/sbin/synostgdisk --check-all-disks-compatibility
@007revad commented on GitHub (Mar 8, 2023):
Very nice. Thank you.
@007revad commented on GitHub (Mar 8, 2023):
I notice that that would work in DSM 6 but I'm not sure about DSM 7
In DSM 6 "synostgdisk --help" returns:
--check-all-disks-compatibility check all disk compatibility info.In DSM 7 "synostgdisk --help" returns:
@mh-muc commented on GitHub (Mar 8, 2023):
For me ist is working well with DSM 7.1.1-42962 Update 4 on RS2421+
@007revad commented on GitHub (Mar 8, 2023):
Thank you for confirming that.
I'll use
/usr/syno/sbin/synostgdisk --check-all-disks-compatibilityfor both DSM 7 and DSM 6 but leave the "You may need to reboot..." message for DSM 6.