mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #75] Small scheduled task question - big thank you #18
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#18
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 @Fonta on GitHub (Jun 20, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/75
Not an issue, just a small question and a big thank you for this script.
After updating my 1019+ to DSM 7.2-64570 Update 1 the storage pool on the m.2 disks was no longer available.
Ran this script and restarted after which the storage pool was available again.
Thanks!!
I've configured a scheduled task to run on shutdown.
My question is if it's needed to add the --noupdate after syno_hdd_db.sh or if can leave that out.
I did use --noupdate the first time running the script.
Also, would it be better to run these scripts at shutdown or at startup? I'd think on shutdown?
Current commands:
@007revad commented on GitHub (Jun 20, 2023):
I would continue using the --noupdate option because without it DSM can update the drive databases whenever it wants.
@007revad commented on GitHub (Jun 21, 2023):
I missed this question in my previous reply.
Originally I used to think running the scripts at shutdown was the better choice. But now I think at startup might be better.
@Fonta commented on GitHub (Jun 21, 2023):
Any arguments on why that would be better?
How about running the scripts on shutdown and startup?
@007revad commented on GitHub (Jun 21, 2023):
There was one person who had the scripts scheduled to run at shutdown and they noticed that after a DSM update they had to run the run script again after it booted up.
It wouldn't hurt to run the scripts at shutdown and bootup.
@Fonta commented on GitHub (Jun 22, 2023):
Configured it to run at boot and shutdown. Better safe then sorry.
Thanks for the info!