[GH-ISSUE #68] DS1621+ & dx510

kerem commented

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

Owner

Originally created by @llmogenmo-netizen on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/007revad/Synology_enable_eunit/issues/68

I am trying to connect a DX510 to my DS1621+. The script runs fine & detects the DX510 expansion bay (in both esata slots); the problem is that drives I stick in it (only one thus far) do not show up under Storage Manager.

Storage manager Overview detects the device, but not the drives.

The drive inserted is -not- seen under "Storage". The one drive that is in the expansion bay IS detected in the Control Panel/External Devices tab, though.

I am running the latest DSM (DSM7.3.2.86009)

Originally created by @llmogenmo-netizen on GitHub (Jan 29, 2026). Original GitHub issue: https://github.com/007revad/Synology_enable_eunit/issues/68 I am trying to connect a DX510 to my DS1621+. The script runs fine & detects the DX510 expansion bay (in both esata slots); the problem is that drives I stick in it (only one thus far) do not show up under Storage Manager. Storage manager Overview detects the device, but not the drives. The drive inserted is -not- seen under "Storage". The one drive that is in the expansion bay IS detected in the Control Panel/External Devices tab, though. I am running the latest DSM (DSM7.3.2.86009)

kerem commented

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

Author

Owner

@llmogenmo-netizen commented on GitHub (Jan 29, 2026):

I have left the email alert on when connecting so I get the following message in my email inbox:

Task Scheduler has completed a triggered task.

Task: Enable eunit
Start time: Wed, 28 Jan 2026 17:07:06 GMT
Stop time: Wed, 28 Jan 2026 17:07:07 GMT
Current status: 0 (Normal)
Standard output/error:

Synology_enable_eunit v3.1.25
DS1621+ DSM 7.3.2-86009

StorageManager 1.0.1-1100

Using options: -e --unit=dx510 --autoupdate=3
Running from: /volume2/Surveillance-Station/DX510_enable/syno_enable_eunit.sh

Connected Expansion Units:
Eunit port 1 - DX510

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

DX510 selected

DX510 already enabled in model.dtb
Disable device /dev/sata1 NCQ successfully
Device sata1 NCQ is already disabled (queue depth 1), nothing to be done
Disable device /dev/sata1 NCQ successfully
Device sata1 NCQ is already disabled (queue depth 1), nothing to be done
Disable device /dev/sata1 NCQ successfully
Device sata1 NCQ is already disabled (queue depth 1), nothing to be done
Disable device /dev/sata1 NCQ successfully
Device sata1 NCQ is already disabled (queue depth 1), nothing to be done
Disable device /dev/sata1 NCQ successfully

Finished

@llmogenmo-netizen commented on GitHub (Jan 29, 2026): I have left the email alert on when connecting so I get the following message in my email inbox: Task Scheduler has completed a triggered task. Task: Enable eunit Start time: Wed, 28 Jan 2026 17:07:06 GMT Stop time: Wed, 28 Jan 2026 17:07:07 GMT Current status: 0 (Normal) Standard output/error: Synology_enable_eunit v3.1.25 DS1621+ DSM 7.3.2-86009 StorageManager 1.0.1-1100 Using options: -e --unit=dx510 --autoupdate=3 Running from: /volume2/Surveillance-Station/DX510_enable/syno_enable_eunit.sh Connected Expansion Units: Eunit port 1 - DX510 DX517 is enabled in /etc/model.dtb DX517 is enabled in /etc.defaults/model.dtb DX510 is enabled in /etc/model.dtb DX510 is enabled in /etc.defaults/model.dtb DX510 selected DX510 already enabled in model.dtb Disable device /dev/sata1 NCQ successfully Device sata1 NCQ is already disabled (queue depth 1), nothing to be done Disable device /dev/sata1 NCQ successfully Device sata1 NCQ is already disabled (queue depth 1), nothing to be done Disable device /dev/sata1 NCQ successfully Device sata1 NCQ is already disabled (queue depth 1), nothing to be done Disable device /dev/sata1 NCQ successfully Device sata1 NCQ is already disabled (queue depth 1), nothing to be done Disable device /dev/sata1 NCQ successfully Finished

kerem commented

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

Author

Owner

@007revad commented on GitHub (Jan 29, 2026):

So DSM is still seeing the DX517 as a single eSATA drive.

Have you rebooted since running the script?

Do you see the DX510 in "Storage Manager > Overview" like:

What does the following command return via SSH:

sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $5}'

or run as root in task scheduler:

/usr/syno/bin/syno_slot_mapping | grep 'Eunit port' | awk '{print $5}'

And what does this command return (via SSH or task scheduler)

for f in /tmp/eunitinfo_*; do cat "$f"; done

@007revad commented on GitHub (Jan 29, 2026): So DSM is still seeing the DX517 as a single eSATA drive. Have you rebooted since running the script? Do you see the DX510 in "Storage Manager > Overview" like: <img width="603" height="380" alt="Image" src="https://github.com/user-attachments/assets/30bf361c-7fe3-451e-8fb8-33fd7d9a730d" /> What does the following command return via SSH: ``` sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $5}' ``` or run as root in task scheduler: ``` /usr/syno/bin/syno_slot_mapping | grep 'Eunit port' | awk '{print $5}' ``` And what does this command return (via SSH or task scheduler) ``` for f in /tmp/eunitinfo_*; do cat "$f"; done ```

kerem commented

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

Author

Owner

@llmogenmo-netizen commented on GitHub (Jan 30, 2026):

I see the Expansion unit in Storage Manager- but the drive inside is not green (it's all black/unpopulated) but the drive -itself- shows up in Control Panel/External Devices. I have tried with one spare drive I have in the 2nd slot- the drive still shows up.

When I run "sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $5}'", the system returns the expansion device, DX510

When I run "for f in /tmp/eunitinfo_*; do cat "$f"; done", the system returns the same info.

@llmogenmo-netizen commented on GitHub (Jan 30, 2026): I see the Expansion unit in Storage Manager- but the drive inside is not green (it's all black/unpopulated) but the drive -itself- shows up in Control Panel/External Devices. I have tried with one spare drive I have in the 2nd slot- the drive still shows up. <img width="538" height="455" alt="Image" src="https://github.com/user-attachments/assets/50e3c071-453c-48f0-8960-0a422eb9b504" /> <img width="408" height="231" alt="Image" src="https://github.com/user-attachments/assets/41c74c6c-6b6e-4f4f-b408-2a23cad4b125" /> When I run "sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $5}'", the system returns the expansion device, DX510 <img width="111" height="55" alt="Image" src="https://github.com/user-attachments/assets/172d777e-4da3-480c-b84d-f0b9033614e5" /> When I run "for f in /tmp/eunitinfo_*; do cat "$f"; done", the system returns the same info. <img width="273" height="54" alt="Image" src="https://github.com/user-attachments/assets/c04cd39c-7dc5-432a-9c9d-f5fce8a3fbbc" />

kerem commented

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

Author

Owner

@007revad commented on GitHub (Jan 30, 2026):

I have tried with one spare drive I have in the 2nd slot- the drive still shows up.

Do you mean with 2 drives in the DX510 you still see the first drive (but not the 2nd drive) in Control Panel > External Devices?

Does the following command return "Binary file /run/model.dtb matches"

grep 'dx510' /run/model.dtb

Are the following LEDs On, Off or Flashing?
POWER
eSATA
RAID
STATUS
ALERT
HDD tray

I notice that your drive that is in the DX510 shows it has a partition (in Control Panel > External Devices). DSM often won't show drives in storage manager if they have non-Synology partitions on them. Try connecting the drive to a computer and deleting all the partitions that are on the drive.

@007revad commented on GitHub (Jan 30, 2026): > I have tried with one spare drive I have in the 2nd slot- the drive still shows up. Do you mean with 2 drives in the DX510 you still see the first drive (but not the 2nd drive) in Control Panel > External Devices? Does the following command return "Binary file /run/model.dtb matches" ``` grep 'dx510' /run/model.dtb ``` Are the following LEDs On, Off or Flashing? POWER eSATA RAID STATUS ALERT HDD tray <img width="711" height="536" alt="Image" src="https://github.com/user-attachments/assets/90264a40-1444-4ef3-8078-b2997e0f7051" /> I notice that your drive that is in the DX510 shows it has a partition (in Control Panel > External Devices). DSM often won't show drives in storage manager if they have non-Synology partitions on them. Try connecting the drive to a computer and deleting all the partitions that are on the drive.

kerem commented

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

Author

Owner

@llmogenmo-netizen commented on GitHub (Feb 2, 2026):

I changed the array to 2 larger drives mirrored; so now I have 4 drives I can test with. (your other app Synology-App-Mover is awesome- Will leave a donation over there!)

Regarding the issue at hand:

The eSATA & Status LEDs are solid green. The RAID & Alert are OFF. (Power is on, Solid Blue). Individual drive LEDs are green.
When I run "grep 'dx510' /run/model.dtb" the response is "Binary file /run/model.dtb matches"
The 4 drives pulled from the now removed/disabled array were directly plugged into the DX510, and they all show up as External Devices; they have Synology made partitions.

@llmogenmo-netizen commented on GitHub (Feb 2, 2026): I changed the array to 2 larger drives mirrored; so now I have 4 drives I can test with. (your other app Synology-App-Mover is awesome- Will leave a donation over there!) Regarding the issue at hand: - The eSATA & Status LEDs are solid green. The RAID & Alert are OFF. (Power is on, Solid Blue). Individual drive LEDs are green. - When I run "grep 'dx510' /run/model.dtb" the response is "Binary file /run/model.dtb matches" - The 4 drives pulled from the now removed/disabled array were directly plugged into the DX510, and they all show up as External Devices; they have Synology made partitions. <img width="270" height="330" alt="Image" src="https://github.com/user-attachments/assets/a5294fef-3c18-45d7-bd8d-68669d80df0a" />

kerem commented

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

Author

Owner

@007revad commented on GitHub (Feb 3, 2026):

Thanks for the donation. I'm really proud of syno_app_mover, and it's 3,650 lines of code! GitHub ranks it as my 3rd most popular script, behind syno_hdd_db (2,700 lines of code) and syn_smart_info (1,600 lines of code) . I'm not sure how GitHub determines which is the most popular. It's not the number of stars or readme views.

syno_hdd_db is 3 years old and has 1,057,000 views.
syno_smart_info is only 20 months old and has only 12,000 views.
syno_app_mover only 2 years old and has only 44,000 views.

Searching in the DS1621+'s DSM 7.3.2 for 'dx517' returns these files:

\etc.defaults\model.dtb
\var.defaults\lib\disk-compatibility\dx517_v7.db
\usr\syno\etc.defaults\scemd.xml
\etc.defaults\synoinfo.conf        <--- only contains a setting to say the DX517 can have an extended warranty
\usr\lib\libhwcontrol.so.1
\usr\syno\bin\scemd
\usr\lib\modules\mv14xx.ko

Searching in the DS1621+'s DSM 7.3.2 for 'dx513' returns these files:

\var.defaults\lib\disk-compatibility\dx513_v7.db
\usr\syno\etc.defaults\scemd.xml
\usr\lib\libhwcontrol.so.1

Searching in the DS1621+'s DSM 7.3.2 for 'dx510' returns these files:

\var.defaults\lib\disk-compatibility\dx510_v7.db
\usr\syno\etc.defaults\scemd.xml
\usr\lib\libhwcontrol.so.1
\usr\syno\synoman\webapi\lib\libHardware.so

We've already added the dx510 to model.dtb. So dx510 is missing in:

\usr\syno\bin\scemd
\usr\lib\modules\mv14xx.ko

Without dx510 in scemd you'd only miss out on fan speed control and warnings if the fan (fans?) fail.

mv14xx.ko contains:

%sdeviceid%s=%s%x%serror_handle%s=%s%s%scpld_version%s=%sv%d%sdeepsleep_supportirq_offEMIDDX517Unique%s="%s"
%s="%d"
RX418DX1222DX1215II%s="Unknown"

Since mv14xx.ko and scemd also don't contain dx513 and the dx513 does work with my script I doubt mv14xx.ko or scemd are the problem.

I'm not sure about libHardware.so

For dx513 and dx510 I copied what is in model.dtb for the dx517 and just changed the dx model. Maybe I need to change something else.

@007revad commented on GitHub (Feb 3, 2026): Thanks for the donation. I'm really proud of syno_app_mover, and it's 3,650 lines of code! GitHub ranks it as my 3rd most popular script, behind syno_hdd_db (2,700 lines of code) and syn_smart_info (1,600 lines of code) . I'm not sure how GitHub determines which is the most popular. It's not the number of stars or readme views. - syno_hdd_db is 3 years old and has 1,057,000 views. - syno_smart_info is only 20 months old and has only 12,000 views. - syno_app_mover only 2 years old and has only 44,000 views. Searching in the DS1621+'s DSM 7.3.2 for 'dx517' returns these files: ``` \etc.defaults\model.dtb \var.defaults\lib\disk-compatibility\dx517_v7.db \usr\syno\etc.defaults\scemd.xml \etc.defaults\synoinfo.conf <--- only contains a setting to say the DX517 can have an extended warranty \usr\lib\libhwcontrol.so.1 \usr\syno\bin\scemd \usr\lib\modules\mv14xx.ko ``` Searching in the DS1621+'s DSM 7.3.2 for 'dx513' returns these files: ``` \var.defaults\lib\disk-compatibility\dx513_v7.db \usr\syno\etc.defaults\scemd.xml \usr\lib\libhwcontrol.so.1 ``` Searching in the DS1621+'s DSM 7.3.2 for 'dx510' returns these files: ``` \var.defaults\lib\disk-compatibility\dx510_v7.db \usr\syno\etc.defaults\scemd.xml \usr\lib\libhwcontrol.so.1 \usr\syno\synoman\webapi\lib\libHardware.so ``` We've already added the dx510 to model.dtb. So dx510 is missing in: ``` \usr\syno\bin\scemd \usr\lib\modules\mv14xx.ko ``` Without dx510 in scemd you'd only miss out on fan speed control and warnings if the fan (fans?) fail. mv14xx.ko contains: ``` %sdeviceid%s=%s%x%serror_handle%s=%s%s%scpld_version%s=%sv%d%sdeepsleep_supportirq_offEMIDDX517Unique%s="%s" %s="%d" RX418DX1222DX1215II%s="Unknown" ``` Since mv14xx.ko and scemd also don't contain dx513 and the dx513 does work with my script I doubt mv14xx.ko or scemd are the problem. I'm not sure about libHardware.so For dx513 and dx510 I copied what is in model.dtb for the dx517 and just changed the dx model. Maybe I need to change something else.

kerem commented

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

Author

Owner

@ctl26481 commented on GitHub (Feb 3, 2026):

DS1621+ can definitely do as one have explored DX213 at here.

One thing came to mind is messed up dts, this behavior is similar to XPE when you force disk hotplug option without custom dts.(same disk number appearing in $torage Manager) A dts/dtb dump(DX enabled by script) may be necessary for examination.

@ctl26481 commented on GitHub (Feb 3, 2026): DS1621+ can definitely do as one have explored DX213 at [here](https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3288069129). One thing came to mind is messed up dts, this behavior is similar to XPE when you force disk hotplug option without custom dts.(same disk number appearing in $torage Manager) A dts/dtb dump(DX enabled by script) may be necessary for examination.

kerem commented

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

Author

Owner

@007revad commented on GitHub (Feb 7, 2026):

@llmogenmo-netizen
Can you download a copy of /run/model.dtb and zip it then attach the zip file in a reply here.

@007revad commented on GitHub (Feb 7, 2026): @llmogenmo-netizen Can you download a copy of /run/model.dtb and zip it then attach the zip file in a reply here.

kerem commented

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

Author

Owner

@llmogenmo-netizen commented on GitHub (Feb 7, 2026):

after SSH'ing in, ran "find / -name model.dtb 2>/dev/null", it found 4 model.dtb files. located in different locations.

/.syno/patch/model.dtb
/etc/model.dtb
/etc.defaults/model.dtb
/run/model.dtb

They have all been put in their own respective subdirectories in the file attached.

Model.dtb.zip

@llmogenmo-netizen commented on GitHub (Feb 7, 2026): after SSH'ing in, ran "find / -name model.dtb 2>/dev/null", it found 4 model.dtb files. located in different locations. /.syno/patch/model.dtb /etc/model.dtb /etc.defaults/model.dtb /run/model.dtb They have all been put in their own respective subdirectories in the file attached. [Model.dtb.zip](https://github.com/user-attachments/files/25154665/Model.dtb.zip)

kerem commented

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

Author

Owner

@007revad commented on GitHub (Feb 7, 2026):

/etc/model.dtb, /etc.defaults/model.dtb and /run/model.dtb are all identical (as they should be) and the DX510 section at the end looks okay (the same as DX517 but with dx517 replaced with dx510).

The only thing I'm not sure about is the libata settings which may need to be different for a DX510 (and RX410).

	DX510 {
		compatible = "Synology";
		model = "synology_dx510";

		pmp_slot@1 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x00>;
			};
		};

		pmp_slot@2 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x01>;
			};
		};

		pmp_slot@3 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x02>;
			};
		};

		pmp_slot@4 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x03>;
			};
		};

		pmp_slot@5 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x04>;
			};
		};
	};

@007revad commented on GitHub (Feb 7, 2026): /etc/model.dtb, /etc.defaults/model.dtb and /run/model.dtb are all identical (as they should be) and the DX510 section at the end looks okay (the same as DX517 but with dx517 replaced with dx510). The only thing I'm not sure about is the libata settings which may need to be different for a DX510 (and RX410). ``` DX510 { compatible = "Synology"; model = "synology_dx510"; pmp_slot@1 { libata { EMID = <0x00>; pmp_link = <0x00>; }; }; pmp_slot@2 { libata { EMID = <0x00>; pmp_link = <0x01>; }; }; pmp_slot@3 { libata { EMID = <0x00>; pmp_link = <0x02>; }; }; pmp_slot@4 { libata { EMID = <0x00>; pmp_link = <0x03>; }; }; pmp_slot@5 { libata { EMID = <0x00>; pmp_link = <0x04>; }; }; }; ```