007revad / Synology_enable_eunit

Enable an unsupported Expansion Unit
MIT License
25 stars 5 forks source link

Unable to make a DX213 work with a DS920+ #41

Open Fraudelefix opened 1 month ago

Fraudelefix commented 1 month ago

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:

DX517 is enabled in /etc.defaults/synoinfo.conf RX418 is enabled in /etc.defaults/synoinfo.conf DX213 is enabled in /etc.defaults/synoinfo.conf

DX517 is enabled in /etc/synoinfo.conf RX418 is enabled in /etc/synoinfo.conf DX213 is enabled in /etc/synoinfo.conf

DX517 is enabled in /etc.defaults/model.dtb DX517 is enabled in /etc/model.dtb RX418 is not enabled in /etc.defaults/model.dtb RX418 is not enabled in /etc/model.dtb DX213 is enabled in /etc.defaults/model.dtb DX213 is enabled in /etc/model.dtb

System Disk Internal Disk 01: /dev/sata3 02: /dev/sata4 03: /dev/sata1 04: /dev/sata2

Esata port count: 1 Esata port 1 01:

USB Device 01: 02:

Internal SSD Cache: 01: /dev/nvme1n1 02: /dev/nvme0n1

On the hardware side:

Are there other potential failpoints that I have not yet checked ? Thank you for taking the time to try and help me !

Regards,

007revad commented 1 month ago

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?

grep 'dx213' /run/model.dtb
ls -lh /run/model*
ls -lh /etc/model*
ls -lh /etc.defaults/model*
cat /proc/sys/kernel/syno_hw_revision
007revad commented 1 month ago

And these:

grep 'support_ew_20_eunit' /etc/synoinfo.conf
grep 'support_ew_20_eunit' /etc.defaults/synoinfo.conf
Fraudelefix commented 1 month ago

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.dtb

Binary file /run/model.dtb matches

ls -lh /run/model*

-rw-r--r-- 1 root root 2.6K Aug 8 23:39 /run/model.dtb

ls -lh /etc/model*

-rw-r--r-- 1 root root 2.6K Aug 8 23:40 /etc/model.dtb -rw-r--r-- 1 root root 2.4K Sep 23 2023 /etc/model_r1.dtb -rw-r--r-- 1 root root 2.4K Sep 23 2023 /etc/model_r2.dtb

ls -lh /etc.defaults/model*

-rw-r--r-- 1 root root 2.6K Aug 8 23:40 /etc.defaults/model.dtb -rw-r--r-- 1 root root 2.4K Sep 23 2023 /etc.defaults/model.dtb.bak -rw-r--r-- 1 root root 2.4K Sep 23 2023 /etc.defaults/model_r1.dtb -rw-r--r-- 1 root root 2.4K Sep 23 2023 /etc.defaults/model_r2.dtb

cat /proc/sys/kernel/syno_hw_revision returns nothing (according to your message here, i guess it is an original)

grep 'support_ew_20_eunit' /etc/synoinfo.conf

support_ew_20_eunit="Synology-DX517,Synology-RX418,Synology-DX213"

grep 'support_ew_20_eunit' /etc.defaults/synoinfo.conf

support_ew_20_eunit="Synology-DX517,Synology-RX418,Synology-DX213"

007revad commented 1 month ago

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.

DX213 LEDs
Status  off     <---
eSATA   Solid Green
DISK 1  Solid Green
DISK 2  off     no drive in bay 2
Power   Solid Blue

Do you see DX213 like in pictures 1, 3 and 4?

image

image

image

image

The only difference is syno_slot_mapping sees the DX213 on my DS720+

~# syno_slot_mapping
System Disk
Internal Disk
01: /dev/sata1
02: /dev/sata2

Esata port count: 1
Eunit port 1 - DX213

USB Device
01: /dev/usb1
02:

Internal SSD Cache:
01:
02:

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 1 month ago

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 Restore

I 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 4 weeks ago

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 4 weeks ago

When your DX213 was with a DS716+II was it using the same cable?

Yes it was with the same cable, the original Synology one

Have you tried the eSATA cable from the eSata dock you got from Amazon?

No, not yet. I will try on the 19th and let you know (currently away from home)

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.

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 3 weeks ago

Have you tried the eSATA cable from the eSata dock you got from Amazon?

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