[GH-ISSUE #60] DX513 not added #9

New issue

Open

opened 2026-03-07 19:10:55 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 19:10:55 +03:00

Owner

Originally created by @HenkJW on GitHub (Oct 18, 2025).
Original GitHub issue: https://github.com/007revad/Synology_enable_eunit/issues/60

Hello, I managed to run your script at startup but for some reason it does not add the eunit specified by "--unit=" to the list.
In its log output it still seems to keep asking for a number to specify which unit to add.
During an interactive SSH session with no parameters specified I can understand that but during a batch-type execution I cannot enter a parameter. Moreover, in the notes on v2.1.11 in CHANGES.txt is shows

Added ability to schedule the script and specify the expansion unit to enable.
--unit=EUNIT where EUNIT is dx517, dx513, dx213, dx510, rx418, rx415 or rx410

The log output is each time:

Synology_enable_eunit v3.1.24
DS1821+ DSM 7.3-81180

StorageManager 1.0.0-01026

Using options: -e --unit=dx513
Running from: /volume1/_Eerste/Scripts/EnableDX513/syno_enable_eunit.sh

Connected Expansion Units:
Eunit
port
1

DX513

DX517 is enabled in /etc/model.dtb
DX517 is enabled in /etc.defaults/model.dtb

DX517 5) RX418 9) RX1217 13) RX1211 17) Restore
DX513 6) RX415 10) RX1214rp 14) DX1215II 18) Quit
DX213 7) RX410 11) RX1214 15) DX1215
DX510 8) RX1217rp 12) RX1211rp 16) DX1211
Select your Expansion Unit:

Finished

What do I do wrong? How should I indicate my DX513 at startup to have it added to the list?
Thank you for your time to respond.

Originally created by @HenkJW on GitHub (Oct 18, 2025). Original GitHub issue: https://github.com/007revad/Synology_enable_eunit/issues/60 Hello, I managed to run your script at startup but for some reason it does not add the eunit specified by "--unit=" to the list. In its log output it still seems to keep asking for a number to specify which unit to add. During an interactive SSH session with no parameters specified I can understand that but during a batch-type execution I cannot enter a parameter. Moreover, in the notes on v2.1.11 in CHANGES.txt is shows - Added ability to schedule the script and specify the expansion unit to enable. --unit=EUNIT where EUNIT is dx517, dx513, dx213, dx510, rx418, rx415 or rx410 The log output is each time: - - - - - - - - - - - - - Synology_enable_eunit v3.1.24 DS1821+ DSM 7.3-81180 StorageManager 1.0.0-01026 Using options: -e --unit=dx513 Running from: /volume1/_Eerste/Scripts/EnableDX513/syno_enable_eunit.sh Connected Expansion Units: Eunit port 1 - DX513 DX517 is enabled in /etc/model.dtb DX517 is enabled in /etc.defaults/model.dtb 1) DX517 5) RX418 9) RX1217 13) RX1211 17) Restore 2) DX513 6) RX415 10) RX1214rp 14) DX1215II 18) Quit 3) DX213 7) RX410 11) RX1214 15) DX1215 4) DX510 8) RX1217rp 12) RX1211rp 16) DX1211 Select your Expansion Unit: Finished - - - - - - - - - - - - - What do I do wrong? How should I indicate my DX513 at startup to have it added to the list? Thank you for your time to respond.

kerem commented

2026-03-07 19:10:55 +03:00

Author

Owner

@007revad commented on GitHub (Oct 18, 2025):

Thanks. You've found a bug. I'll fix it tonight or tomorrow, and let you know when the new version is online.

@007revad commented on GitHub (Oct 18, 2025): Thanks. You've found a bug. I'll fix it tonight or tomorrow, and let you know when the new version is online.

kerem commented

2026-03-07 19:10:55 +03:00

Author

Owner

@007revad commented on GitHub (Oct 18, 2025):

Okay, the problem was a silly typo: unist_tmp instead of units_tmp on line 129.

But I also want to fix this:

Connected Expansion Units:
Eunit
port
2
-
DX213

which should look like this:

Connected Expansion Units:
Eunit port 2 - DX213

@007revad commented on GitHub (Oct 18, 2025): Okay, the problem was a silly typo: `unist_tmp` instead of `units_tmp` on line 129. But I also want to fix this: ``` Connected Expansion Units: Eunit port 2 - DX213 ``` which should look like this: ``` Connected Expansion Units: Eunit port 2 - DX213 ```

kerem commented

2026-03-07 19:10:56 +03:00

Author

Owner

@HenkJW commented on GitHub (Oct 18, 2025):

Thank you!-- Hoi,Henk Wissink(Vanaf iPhone)Op 18 okt 2025 om 10:05 heeft Dave Russell @.***> het volgende geschreven:007revad left a comment (007revad/Synology_enable_eunit#60)
Thanks. You've found a bug. I'll fix it tonight or tomorrow, and let you know when the new version is online.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

@HenkJW commented on GitHub (Oct 18, 2025): Thank you!-- Hoi,Henk Wissink(Vanaf iPhone)Op 18 okt 2025 om 10:05 heeft Dave Russell ***@***.***> het volgende geschreven:007revad left a comment (007revad/Synology_enable_eunit#60) Thanks. You've found a bug. I'll fix it tonight or tomorrow, and let you know when the new version is online. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

kerem commented

2026-03-07 19:10:56 +03:00

Author

Owner

@007revad commented on GitHub (Oct 18, 2025):

All fixed in v3.1.25

@007revad commented on GitHub (Oct 18, 2025): All fixed in [v3.1.25](https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.25)