[GH-ISSUE #45] Question about HDD update disabled #21

Closed
opened 2026-03-07 19:14:06 +03:00 by kerem · 9 comments
Owner

Originally created by @aferende on GitHub (Mar 28, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/45

I have a question about disabling Synology update.
As far as I know, this update also serves to check for any new firmware on the individual HDs.

Attempting manual update fails (after running the script).

So we have to give up forever to any updates?

What do you think about?
Ty

Originally created by @aferende on GitHub (Mar 28, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/45 I have a question about disabling Synology update. As far as I know, this update also serves to check for any new firmware on the individual HDs. Attempting manual update fails (after running the script). So we have to give up forever to any updates? What do you think about? Ty
kerem closed this issue 2026-03-07 19:14:06 +03:00
Author
Owner

@007revad commented on GitHub (Mar 28, 2023):

Do you have drives that DSM supports for firmware updates?

I thought DSM only supported firmware updates on Synology drives.

You could restore the db update URL, do the manual firmware version check, then disable the db update URL.

  1. Restore the drive db update URL: sudo -i /path-to-script/syno_hdd_db.sh
  2. Do the manual firmware check.
  3. Then disable the drive db update URL again: sudo -i /path-to-script/syno_hdd_db.sh --nodbupdate
    • or sudo -i /path-to-script/syno_hdd_db.sh -n
<!-- gh-comment-id:1487567564 --> @007revad commented on GitHub (Mar 28, 2023): Do you have drives that DSM supports for firmware updates? I thought DSM only supported firmware updates on Synology drives. You could restore the db update URL, do the manual firmware version check, then disable the db update URL. 1. Restore the drive db update URL: `sudo -i /path-to-script/syno_hdd_db.sh` 2. Do the manual firmware check. 3. Then disable the drive db update URL again: `sudo -i /path-to-script/syno_hdd_db.sh --nodbupdate` - or `sudo -i /path-to-script/syno_hdd_db.sh -n`
Author
Owner

@aferende commented on GitHub (Mar 28, 2023):

OK thank you.
Yes, before running the script it happened that DSM found an updated firmware asking me to restart.
Many of the HDDs I have are Exos and Ironwolf therefore supported. Thanks for the reply

<!-- gh-comment-id:1487632916 --> @aferende commented on GitHub (Mar 28, 2023): OK thank you. Yes, before running the script it happened that DSM found an updated firmware asking me to restart. Many of the HDDs I have are Exos and Ironwolf therefore supported. Thanks for the reply
Author
Owner

@aferende commented on GitHub (Mar 29, 2023):

HI,
I reopen the report because there is perhaps still some problem.

The script to re-enable the HDD update doesn't seem to work.
The first one says the parameter is wrong.
The second runs but does not produce the desired effect.
Trying to update from Synology site I get this error.
Trying to update by hand instead, it seems that the DB doesn't update.

Some idea?
00
01
02
03
04

<!-- gh-comment-id:1488262141 --> @aferende commented on GitHub (Mar 29, 2023): HI, I reopen the report because there is perhaps still some problem. The script to re-enable the HDD update doesn't seem to work. The first one says the parameter is wrong. The second runs but does not produce the desired effect. Trying to update from Synology site I get this error. Trying to update by hand instead, it seems that the DB doesn't update. Some idea? ![00](https://user-images.githubusercontent.com/13355101/228491679-d93df468-4ea9-43c2-9705-7de813519f16.png) ![01](https://user-images.githubusercontent.com/13355101/228491683-38a08945-c591-45e3-9c8e-41b095a8d6e1.png) ![02](https://user-images.githubusercontent.com/13355101/228491685-1f74b97a-0c2f-4b41-a4a3-ed9764485946.png) ![03](https://user-images.githubusercontent.com/13355101/228491686-c52d62aa-cfbd-41a3-82bd-1d3f1caf824e.png) ![04](https://user-images.githubusercontent.com/13355101/228491687-5c4159f3-3909-4573-b4af-f6687c661fe9.png)
Author
Owner

@007revad commented on GitHub (Mar 29, 2023):

I mistyped --nodbupdate. It should have been --noupdate

Both -n and --noupdate disable db updates.

Running the script without -n or --noupdate will re-enable db updates.

  1. Restore the drive db update URL: sudo -i /path-to-script/syno_hdd_db.sh
  2. Do the manual firmware check.
  3. Then disable the drive db update URL again: sudo -i /path-to-script/syno_hdd_db.sh -n
<!-- gh-comment-id:1489141895 --> @007revad commented on GitHub (Mar 29, 2023): I mistyped --nodbupdate. It should have been --noupdate Both -n and --noupdate disable db updates. Running the script without -n or --noupdate will re-enable db updates. 1. Restore the drive db update URL: `sudo -i /path-to-script/syno_hdd_db.sh` 2. Do the manual firmware check. 3. Then disable the drive db update URL again: `sudo -i /path-to-script/syno_hdd_db.sh -n`
Author
Owner

@aferende commented on GitHub (Mar 29, 2023):

Thanks Dave.
However, the problem remains that even by executing the script without parameters (therefore db update enabled), the Synology update check fails with the pop-up already attached to the previous message.

However, manually updating does not update the db.

Any idea?

<!-- gh-comment-id:1489230915 --> @aferende commented on GitHub (Mar 29, 2023): Thanks Dave. However, the problem remains that even by executing the script without parameters (therefore db update enabled), the Synology update check fails with the pop-up already attached to the previous message. However, manually updating does not update the db. Any idea?
Author
Owner

@007revad commented on GitHub (Mar 30, 2023):

Okay. I've found a bug in the code that re-enables db updates. I'm not sure how long it's been there because it used to work.

Until I can fix the script and upload the new version you can use this command to re-enable db updates:

sudo sed -i "s/drive_db_test_url=\"127\.0\.0\.1\"//" "/etc.defaults/synoinfo.conf"

<!-- gh-comment-id:1489622775 --> @007revad commented on GitHub (Mar 30, 2023): Okay. I've found a bug in the code that re-enables db updates. I'm not sure how long it's been there because it used to work. Until I can fix the script and upload the new version you can use this command to re-enable db updates: `sudo sed -i "s/drive_db_test_url=\"127\.0\.0\.1\"//" "/etc.defaults/synoinfo.conf"`
Author
Owner

@aferende commented on GitHub (Mar 30, 2023):

Also after executing this script, syno update doesn't work. Same popup message

<!-- gh-comment-id:1489770297 --> @aferende commented on GitHub (Mar 30, 2023): Also after executing this script, syno update doesn't work. Same popup message
Author
Owner

@007revad commented on GitHub (Mar 30, 2023):

There's an updated version, v1.2.31, to fix your issue.
https://github.com/007revad/Synology_HDD_db/releases/tag/v1.2.31

update-now-working

update-now-disabled

<!-- gh-comment-id:1489903172 --> @007revad commented on GitHub (Mar 30, 2023): There's an updated version, v1.2.31, to fix your issue. https://github.com/007revad/Synology_HDD_db/releases/tag/v1.2.31 ![update-now-working](https://user-images.githubusercontent.com/39733752/228775964-fb522932-35ba-4bf6-881e-84270d65deec.png) ![update-now-disabled](https://user-images.githubusercontent.com/39733752/228776008-b848bc8e-8d7d-4f72-a1fd-daf1d3dad3dc.png)
Author
Owner

@aferende commented on GitHub (Mar 30, 2023):

Ty. It works now!

<!-- gh-comment-id:1489910927 --> @aferende commented on GitHub (Mar 30, 2023): Ty. It works now!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_HDD_db#21
No description provided.