mirror of
https://github.com/007revad/Synology_enable_eunit.git
synced 2026-04-25 12:55:55 +03:00
[GH-ISSUE #41] Unable to make a DX213 work with a DS920+ #64
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_eunit#64
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 @Fraudelefix on GitHub (Aug 8, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_eunit/issues/41
Originally assigned to: @007revad on GitHub.
Hello, following up on our chat on reddit, I have a spare DX213 that I would like to make it work with a DS920+
So far, I have been unable to do so.
On the software side:
/volume1/system/scripts/synology_enable_eunits/syno_enable_eunit.sh -e --unit=dx213 --autoupdate=3sudo syno_slot_mappingwhith the DX213 plugged in, I get:sudo syno_slot_mapping | grep 'Eunit port'with the DX213 plugged in, I get nothingOn the hardware side:
Poweris blue, (ii)Statusis off, (iii)eSatais geen, (iv)Disk 1is geen and (v)Disk 2is offAre there other potential failpoints that I have not yet checked ?
Thank you for taking the time to try and help me !
Regards,
@007revad commented on GitHub (Aug 13, 2024):
Which DSM version is the DS920+ using?
There were 3 different hardware versions of DS920+ (the original, revision 2 and revision 3). I'm wondering if yours is a r2 or r3 but the script didn't detect it so it edited model.dtb instead of model_r2.dtb or model_r3.dtb
What do these commands return?
@007revad commented on GitHub (Aug 13, 2024):
And these:
@Fraudelefix commented on GitHub (Aug 13, 2024):
Hello, please find bellow the results of the commands you have asked for.
Let me know if you need more commands to be run.
Edit : The DS920+ is running DSM 7.2.1-69057 Update 5
grep 'dx213' /run/model.dtbls -lh /run/model*ls -lh /etc/model*ls -lh /etc.defaults/model*cat /proc/sys/kernel/syno_hw_revisionreturns nothing
(according to your message here, i guess it is an original)
grep 'support_ew_20_eunit' /etc/synoinfo.confgrep 'support_ew_20_eunit' /etc.defaults/synoinfo.conf@007revad commented on GitHub (Aug 14, 2024):
I was hoping your DS920+ was revision 2 or 3. I just decompiled and compared the DS920+ model.dtb, model_r1.dtb and model_r2.dtb for "DSM 7.2.1 with Update 1" and they all the same. I also compared model.dtb and model_r1.dtb for the other 4 Synology models that have a revision 1 and they were also the same. There differences in the eSATA port setting in DSM 7.2.1 but I'm still investigating why they are different.
Almost everything you are seeing is what I see on my DS720+ (with DSM 7.2.1 update 5) after running syno_enable_eunit.sh and selecting Restore and then rebooting.
Do you see DX213 like in pictures 1, 3 and 4?
The only difference is syno_slot_mapping sees the DX213 on my DS720+
I assume when you ran the script via SSH it did not find your DX213?
Which would be why you scheduled the script with
--eunit=DX213?@Fraudelefix commented on GitHub (Aug 14, 2024):
What i write bellow is true for both when (i) I run the script in SSH to enable the DX213 and (ii) when I run the script and select
Restoresyno_slot_mappingI scheduled the script with --eunit=DX213 before trying to run the script in SSH because I like to avoid enabeling SSH. When I found that I could not make the DX213 work, I tried with SSH.
Even though I assumed the eSata cable to be working, I will try to order a new one from Synology. Maybe there is an extra pin dedicated to detecting enuits (in addition to data pins) ?
@007revad commented on GitHub (Aug 16, 2024):
When your DX213 was with a DS716+II was it using the same cable?
Have you tried the eSATA cable from the eSata dock you got from Amazon?
My DX213 is using a generic eSATA cable. I did buy a genuine Synology eSATA because it has the retaining screws to prevent it accidentally being unplugged, but I haven't used it yet.
@Fraudelefix commented on GitHub (Aug 17, 2024):
Yes it was with the same cable, the original Synology one
No, not yet. I will try on the 19th and let you know (currently away from home)
An eSata cable is an eSata cable. It should not matter from which vendor it comes, I believe the pin layout is standardized.
I was reading the other issue (https://github.com/007revad/Synology_enable_eunit/issues/28) and from what I could understand, it is not the cable that does the check if it is a Synology eunit or a classic eSata dock, there is a check for a vendor ID / device ID done by the NAS. For some reason the DS716+ does the check, but the DS920+ does not even get the info that there is a check to be done (as I dont get the same warning as you in picture 4) >> This has to be eSata port or cable related
@Fraudelefix commented on GitHub (Aug 18, 2024):
I just tried with and without the script activated. Still nothing. I do not understand why :@
I also updated the script with the new update, but same result
@starhw commented on GitHub (Sep 27, 2024):
My DS920 also cannot use DX513, the problem seems to be similar
My English sucks.
@007revad commented on GitHub (Nov 9, 2024):
Did you reboot after running the script?
@Fraudelefix commented on GitHub (Jan 21, 2025):
Hello,
I wanted to delve further on this issue I’ve been facing and add some more details. I want to know if the compatibility with the DX213 could be affected because the volume in my DS920+ originally came from a unit that did not have expansion capabilities (DS416Play).
I removed all the drives from my DS920+ and swapped them with those from the DS716+II mentioned previously. Unfortunately, I encountered the same issue: the DS920+ couldn’t recognize the DX213 after using your script. I also tried a clean install on the DS920+, but it resulted in the same outcome.
Finally, I tested it with a DS1520+, and I was able to see the DS213X and use the drives inside after applying your script.
While I initially assumed the eSATA port on my DS920+ was working—since it recognized the eSATA enclosure from StarTech (the dock from Amazon) even if it couldn’t detect the DX213—I’m now starting to think the eSATA port may be malfunctioning.
It might not be worth investing more money into this, but I am considering trying with a DX517. Additionally, as you mentioned in a previous post, there are different hardware revisions of the DS920+, but I doubt this is the cause of it not detecting the DX213.
@007revad commented on GitHub (Jan 21, 2025):
Apparently some types of eSATA ports provide 12v and 5v power to the connected device, and other types only provide 5v.
It could be that the eSATA port on your DS920+ is not providing power on either the 12v or 5v pin (and that may be the pin the expansion unit uses to detect when it's connected to a NAS and spin up it's drives.