mirror of
https://github.com/007revad/Synology_DSM_reinstall.git
synced 2026-04-25 12:35:58 +03:00
[GH-ISSUE #9] This script doesn't seem to work on DSM Version: 7.2.1-69057 Update 3 #2
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_DSM_reinstall#2
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 @jowinthe on GitHub (Dec 1, 2023).
Original GitHub issue: https://github.com/007revad/Synology_DSM_reinstall/issues/9
I could not get this script to work on DSM Version: 7.2.1-69057 Update 3. The script exits immediately with no messages.
@007revad commented on GitHub (Dec 1, 2023):
What is the exact command you are typing?
What shell or terminal are you using?
@jowinthe commented on GitHub (Dec 2, 2023):
Hi,
I was running the script via Task Scheduler, as described here:
https://github.com/007revad/Synology_DSM_reinstall/tree/main
I created a task with "root" user and the path to the file /syno_dsm_reinstall.sh
It seems like the script is initiated, but then exits almost immediately.
Den Fri, 01 Dec 2023 11:06:40 -0800, Dave Russell @.***> skrev:
What is the exact command you are typing?
What shell or terminal are you using?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@007revad commented on GitHub (Dec 2, 2023):
When you run a script via task scheduler it appears to finish immediately, but it finishes running in the background.
You can see the output from the script in task scheduler:
@jowinthe commented on GitHub (Dec 2, 2023):
I just ran the new .sh file (with the "# Check script is running as root" mod.). Still no joy. It takes a bit longer to finish, but no messages, and the DSM version remains the same. Still "unable to re-install due to older version" message.
Den Sat, 02 Dec 2023 00:47:29 +0000, "Jon Winther-Hansen" @.***> skrev:
Hi,
I was running the script via Task Scheduler, as described here:
https://github.com/007revad/Synology_DSM_reinstall/tree/main
I created a task with "root" user and the path to the file /syno_dsm_reinstall.sh
It seems like the script is initiated, but then exits almost immediately.
Den Fri, 01 Dec 2023 11:06:40 -0800, Dave Russell @.***> skrev:
What is the exact command you are typing?
What shell or terminal are you using?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@jowinthe commented on GitHub (Dec 2, 2023):
For some reason the Action > View Result is greyed out. I entered my e-mail in the "Send run details by e-mail".
This is what I got:
Task Scheduler has completed a scheduled task.
Task: dsm_fix
Start time: Sat, 02 Dec 2023 02:15:01 +0100
Stop time: Sat, 02 Dec 2023 02:15:58 +0100
Current status: 127 (Interrupted)
Standard output/error:
/bin/bash: /volume: No such file or directory
From DS
My DSM UI seems a bit sluggish after the upgrade from 6 to 7.2.1, and that's why I want to re-install the system. Maybe that has something to do with why the script is not functioning properly?
Den Fri, 01 Dec 2023 17:03:25 -0800, Dave Russell @.***> skrev:
When you run a script via task scheduler it appears to finish immediately, but it finishes running in the background.
You can see the output from the script in task scheduler:
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@007revad commented on GitHub (Dec 2, 2023):
You need to select the dsm_fix task then click Action > View Result
Edit the scheduled task and change /volume/ to /volume1/
@jowinthe commented on GitHub (Dec 2, 2023):
I just ssh into the NAS, and then figured out what you say below, that the "volume 1" should read "volume1" in the path. (even though it's listed as "volume 1" in the Storage Manager...
Thanks for the swift replies, and for the script itself!
Jon
Den Fri, 01 Dec 2023 17:42:27 -0800, Dave Russell @.***> skrev:
Current status: 127 (Interrupted)
Standard output/error: /bin/bash: /volume: No such file or directory
Edit the scheduled task and change /volume/ to /volume1/
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>