[GH-ISSUE #208] Update of script fails with code errors #83

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

Originally created by @herbingk on GitHub (Jan 9, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/208

Update of script fails with code errors. Seems like the chmod für CHANGES.txt wasn't updated to the new name and some trouble with closing fi

chmod: cannot access '/volume1/admin/Synology_HDD_db/CHANGES.txt': No such file or directory
ERROR Failed to set permissions on:
/volume1/admin/Synology_HDD_db/CHANGES.txt
ERROR Failed to cd to /tmp!
/volume1/admin/Synology_HDD_db/syno_hdd_db.sh: line 466: syntax error near unexpected token `fi'
/volume1/admin/Synology_HDD_db/syno_hdd_db.sh: line 466: `            fi'

Originally created by @herbingk on GitHub (Jan 9, 2024). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/208 Update of script fails with code errors. Seems like the chmod für CHANGES.txt wasn't updated to the new name and some trouble with closing fi ``` chmod: cannot access '/volume1/admin/Synology_HDD_db/CHANGES.txt': No such file or directory ERROR Failed to set permissions on: /volume1/admin/Synology_HDD_db/CHANGES.txt ERROR Failed to cd to /tmp! /volume1/admin/Synology_HDD_db/syno_hdd_db.sh: line 466: syntax error near unexpected token `fi' /volume1/admin/Synology_HDD_db/syno_hdd_db.sh: line 466: ` fi' ```
kerem closed this issue 2026-03-07 19:15:14 +03:00
Author
Owner

@007revad commented on GitHub (Jan 9, 2024):

I know what caused the chmod error.

It obviously changed directory to temp okay or it would not have got to the chmod error. So I'm not sure why it ended up at line 465 and 466.

<!-- gh-comment-id:1882740594 --> @007revad commented on GitHub (Jan 9, 2024): I know what caused the chmod error. It obviously changed directory to temp okay or it would not have got to the chmod error. So I'm not sure why it ended up at line 465 and 466.
Author
Owner

@007revad commented on GitHub (Jan 9, 2024):

Do you want to run it again, and let it update itself to v3.4.79 if see if those errors are gone.

If you still get the syntax error near unexpected token 'fi' error can you:

  1. Edit the version number in syno_hdd_db.sh to make a lower number.
  2. Run it with the --debug option.
  3. Report back with the output.
<!-- gh-comment-id:1882752785 --> @007revad commented on GitHub (Jan 9, 2024): Do you want to run it again, and let it update itself to v3.4.79 if see if those errors are gone. If you still get the `syntax error near unexpected token 'fi'` error can you: 1. Edit the version number in syno_hdd_db.sh to make a lower number. 2. Run it with the --debug option. 3. Report back with the output.
Author
Owner

@herbingk commented on GitHub (Jan 9, 2024):

3.4.78 brings the same error when updating to 3.4.79.
3.4.79 seems to have fixed the problem. When editing the version no back to 3.4.78, running the update again, it does without problems.

<!-- gh-comment-id:1882781820 --> @herbingk commented on GitHub (Jan 9, 2024): 3.4.78 brings the same error when updating to 3.4.79. 3.4.79 seems to have fixed the problem. When editing the version no back to 3.4.78, running the update again, it does without problems.
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#83
No description provided.