mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #88] Interesting output after running script #37
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#37
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 @TheCableGuy99 on GitHub (Jun 12, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/88
Hi,
I just updated the script and thought i'd run it then noticed something interesting:
Note it finds my 2 M.2 cards then says immediately after that there are non found. I'm not sure if this is a problem or not, or just a small bug but thought it was best to report it.
Also, have you implemented the auto-update feature yet? If so, how do I enable it please?
Thanks.
@007revad commented on GitHub (Jun 12, 2023):
The HDDs are all showing only the last 4 characters of their firmware version. This is due to a change in DSM 7.2
That is actually referring to PCIe cards that you can install M.2 drives on like the M2D20, M2D18 and E10M20-T1.
I should change the "No M.2 cards found" to "No M.2 PCIe cards found" to make it clearer.
I've fixed the HDD 4 character firmware version issue and added auto-update, but the release is still RC.
https://github.com/007revad/Synology_HDD_db/releases/tag/v2.3.51-RC
The --autoupdate=[age] option requires a digit for the number of days after new version is released to wait before updating. You can use --autoupdate=0 to update right away. The script also reloads itself so when you run it unattended (scheduled) it can update itself and run the new version.
@tmnext commented on GitHub (Jun 12, 2023):
May I just ask here for the "unattended" - do you recommend scheduled tasks as root at shutdown or boot-up when running both hdd_db and enable_m2 script? The guide recommends both depending on script.
@TheCableGuy99 commented on GitHub (Jun 13, 2023):
I didn't actually notice the lack of digits on the firmware version but glad to know it's another bug squished :)
Thanks for confirming what the M.2 line means also :)
And I really like how you've added that it will update itself and then run itself again. I'm going to wait for the official release though to be sure it's good :)
Just to confirm though, when I do set it, my current script is set in Synology Task manager with the script as follows:
/volume1/syno_hdd_db.sh
Would I change this to:
/volume1/syno_hdd_db.sh --autoupdate=0
or does it need to go in some quotes because there's a space like so:
"/volume1/syno_hdd_db.sh --autoupdate=0"
Thanks for all your help :)
@TheCableGuy99 commented on GitHub (Jun 13, 2023):
@70m7E I don't think you need both scripts, I think the syno_hdd_db.sh script does it all.... but i'm not 100% so maybe @007revad could confirm?
I'm running M.2's as volumes and i'm only running the syno_hdd_db.sh script at boot personally.
@007revad commented on GitHub (Jun 13, 2023):
@70m7E Yes, if you need the enable_m2 script I would add it to the same schedule as hdd_db, so you'd have 2 lines in the scheduled task: 1 for each script.
The syno_hdd_db.sh script is all that's needed for most current and recent Synology models.
@007revad commented on GitHub (Jun 13, 2023):
@TheCableGuy99
Yes.
You would need quotes if the path had a space, and then you'd only quote the path/filename part like:
"/volume1/my path/syno_hdd_db.sh" --autoupdate=0
If you want to also use the -n and -f options you'd use:
/volume1/syno_hdd_db.sh --autoupdate=0 -nf
Or
/volume1/syno_hdd_db.sh --autoupdate=0 -n -f