[GH-ISSUE #159] Restore seems to be hanging while restoring model databases #780

Closed
opened 2026-03-12 16:52:47 +03:00 by kerem · 1 comment
Owner

Originally created by @kachunkachunk on GitHub (Nov 4, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/159

Trying to run --restore to bring my NAS back to compliance, but I'm finding the script is halting here:

./syno_hdd_db.sh --restore
Synology_HDD_db v3.1.65
RS1221+ DSM 7.2-64570-3 
Using options: --restore
Running from: /volume1/Application Data/synology_scripts/Synology_HDD_db-3.1.65/syno_hdd_db.sh

Restored synoinfo.conf

Restored adapter_cards.conf

Restored rx4_v7.db
Restored dx1215_v7.db
Restored dx213_v7.db
Restored rx1214_v7.db
Restored dx513_v7.db
Restored rx1214rp_v7.db
Restored rs1221+_m2d20_v7.db
Restored rxd1219sas_v7.db
Restored rs1221+_m2d18_v7.db
Restored dx517_v7.db
Restored dx1211_v7.db
Restored dx510_v7.db
Restored rx1211rp_v7.db
Restored dx1222_v7.db
Restored rx1217_v7.db
Restored dx1215ii_v7.db
Restored rx1217sas_v7.db
Restored dx5_v7.db
Restored rx1222sas_v7.db
Restored rx410_v7.db
Restored rs1221+_host_v7.db
Restored rx1217rp_v7.db
Restored rx6022sas_v7.db
Restored fx2421_v7.db
Restored rx1213sas_v7.db
Restored rs1221+_e10m20-t1_v7.db.new
Restored rx2417sas_v7.db
Restored rx415_v7.db
Restored rx1223rp_v7.db
Restored rx418_v7.db
Restored rx1216sas_v7.db
Restored rs1221+_e10m20-t1_v7.db
Restored rxd1215sas_v7.db
Restored rx1211_v7.db

DSM 7.2-64570 Update 3, RS1221+, E10M20-T1

Uh, and hello, it's me from Reddit.

Originally created by @kachunkachunk on GitHub (Nov 4, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/159 Trying to run `--restore` to bring my NAS back to compliance, but I'm finding the script is halting here: ``` ./syno_hdd_db.sh --restore Synology_HDD_db v3.1.65 RS1221+ DSM 7.2-64570-3 Using options: --restore Running from: /volume1/Application Data/synology_scripts/Synology_HDD_db-3.1.65/syno_hdd_db.sh Restored synoinfo.conf Restored adapter_cards.conf Restored rx4_v7.db Restored dx1215_v7.db Restored dx213_v7.db Restored rx1214_v7.db Restored dx513_v7.db Restored rx1214rp_v7.db Restored rs1221+_m2d20_v7.db Restored rxd1219sas_v7.db Restored rs1221+_m2d18_v7.db Restored dx517_v7.db Restored dx1211_v7.db Restored dx510_v7.db Restored rx1211rp_v7.db Restored dx1222_v7.db Restored rx1217_v7.db Restored dx1215ii_v7.db Restored rx1217sas_v7.db Restored dx5_v7.db Restored rx1222sas_v7.db Restored rx410_v7.db Restored rs1221+_host_v7.db Restored rx1217rp_v7.db Restored rx6022sas_v7.db Restored fx2421_v7.db Restored rx1213sas_v7.db Restored rs1221+_e10m20-t1_v7.db.new Restored rx2417sas_v7.db Restored rx415_v7.db Restored rx1223rp_v7.db Restored rx418_v7.db Restored rx1216sas_v7.db Restored rs1221+_e10m20-t1_v7.db Restored rxd1215sas_v7.db Restored rx1211_v7.db ``` DSM 7.2-64570 Update 3, RS1221+, E10M20-T1 Uh, and [hello, it's me from Reddit.](https://www.reddit.com/r/synology/comments/17l62od/micron_7450_pros_as_cache_creation_is_causing_a/)
kerem closed this issue 2026-03-12 16:52:52 +03:00
Author
Owner

@007revad commented on GitHub (Nov 4, 2023):

It's only missing the "Restore successful." message. I'm not sure why that is. I'll have a look at it.

There are 2 things it should have done after "Restored rx1211_v7.db", but they don't print anything to stdout so just in case the script didn't run those commands you could run them:

sed -i "/drive_db_test_url=*/d" /etc/synoinfo.conf
syno_disk_db_update --update
<!-- gh-comment-id:1793362030 --> @007revad commented on GitHub (Nov 4, 2023): It's only missing the "Restore successful." message. I'm not sure why that is. I'll have a look at it. There are 2 things it should have done after "Restored rx1211_v7.db", but they don't print anything to stdout so just in case the script didn't run those commands you could run them: ``` sed -i "/drive_db_test_url=*/d" /etc/synoinfo.conf syno_disk_db_update --update ```
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#780
No description provided.