starred/Synology_HDD_db
1
0
Fork 0
mirror of https://github.com/007revad/Synology_HDD_db.git synced 2026-04-25 13:45:59 +03:00
Code Issues 102 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #413] No Expansion Units found (of course it's wrong) #145

New issue
Closed
opened 2026-03-07 19:16:19 +03:00 by kerem · 9 comments
kerem commented 2026-03-07 19:16:19 +03:00
Owner
Copy link

Originally created by @kevin39 on GitHub (Dec 30, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/413

Hi,
After a reboot + DSM update my expansion unit display now the warning about my non verified disks... (your script was working from a long time ago)

I updated your script, running it again and I show it display "No Expansion Units found". I think there is a bug in a recent update ? No issue for the main unit, the warning is hidden.

What do you need to debug ?
My setup is SA3410 + RX1222sas

best regards

Originally created by @kevin39 on GitHub (Dec 30, 2024). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/413 Hi, After a reboot + DSM update my expansion unit display now the warning about my non verified disks... (your script was working from a long time ago) I updated your script, running it again and I show it display "No Expansion Units found". I think there is a bug in a recent update ? No issue for the main unit, the warning is hidden. What do you need to debug ? My setup is SA3410 + RX1222sas best regards
kerem closed this issue 2026-03-07 19:16:19 +03:00
kerem commented 2026-03-07 19:16:20 +03:00
Author
Owner
Copy link

@kevin39 commented on GitHub (Dec 30, 2024):

SA3410 DSM 7.2.2-72806-2
StorageManager 1.0.0-00502

sa3410_host_v7 version 8037

Using options: --autoupdate=1 --noupdate
Running from: /volume1/homes/xxxxx/Synology_HDD_db/syno_hdd_db.sh

There is a newer version of this script available.
Current version: v3.5.106
Latest version: v3.5.108
Downloading v3.5.108
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 396k 0 396k 0 0 590k 0 --:--:-- --:--:-- --:--:-- 590k

v3.5.108 syno_hdd_db.sh and changes.txt downloaded to: /volume1/homes/xxxxx/Synology_HDD_db

-------------------------------------------------------------------------------
Synology_HDD_db v3.5.108
SA3410 DSM 7.2.2-72806-2
StorageManager 1.0.0-00502

sa3410_host_v7 version 8037

Using options: --autoupdate=1 --noupdate
Running from: /volume1/homes/xxxxx/Synology_HDD_db/syno_hdd_db.sh

HDD/SSD models found: 2
ST18000NM000J-2TV103,SN02,18000 GB
ST18000NM000J-2TV103,SN04,18000 GB

M.2 drive models found: 1
SNV3510-800G,ECEM13.2,800 GB

M.2 PCIe card models found: 1
M2D20

No Expansion Units found

Updated ST18000NM000J-2TV103 in sa3410_host_v7.db
Updated ST18000NM000J-2TV103 in sa3410_host_v7.db
SNV3510-800G already exists in sa3410_host_v7.db
SNV3510-800G already exists in sa3410_m2d20_v7.db
SNV3510-800G already exists in sa3410_m2d20_v7.db.new

M2D20 NVMe already enabled for SA3410
M2D20 already exists in model.dtb

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Drive db auto updates already disabled.

Creating pool in UI on drives in M.2 adaptor card already enabled.

DSM successfully checked disk compatibility.```
<!-- gh-comment-id:2565981510 --> @kevin39 commented on GitHub (Dec 30, 2024): ```Synology_HDD_db v3.5.106 SA3410 DSM 7.2.2-72806-2 StorageManager 1.0.0-00502 sa3410_host_v7 version 8037 Using options: --autoupdate=1 --noupdate Running from: /volume1/homes/xxxxx/Synology_HDD_db/syno_hdd_db.sh There is a newer version of this script available. Current version: v3.5.106 Latest version: v3.5.108 Downloading v3.5.108 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 396k 0 396k 0 0 590k 0 --:--:-- --:--:-- --:--:-- 590k v3.5.108 syno_hdd_db.sh and changes.txt downloaded to: /volume1/homes/xxxxx/Synology_HDD_db ------------------------------------------------------------------------------- Synology_HDD_db v3.5.108 SA3410 DSM 7.2.2-72806-2 StorageManager 1.0.0-00502 sa3410_host_v7 version 8037 Using options: --autoupdate=1 --noupdate Running from: /volume1/homes/xxxxx/Synology_HDD_db/syno_hdd_db.sh HDD/SSD models found: 2 ST18000NM000J-2TV103,SN02,18000 GB ST18000NM000J-2TV103,SN04,18000 GB M.2 drive models found: 1 SNV3510-800G,ECEM13.2,800 GB M.2 PCIe card models found: 1 M2D20 No Expansion Units found Updated ST18000NM000J-2TV103 in sa3410_host_v7.db Updated ST18000NM000J-2TV103 in sa3410_host_v7.db SNV3510-800G already exists in sa3410_host_v7.db SNV3510-800G already exists in sa3410_m2d20_v7.db SNV3510-800G already exists in sa3410_m2d20_v7.db.new M2D20 NVMe already enabled for SA3410 M2D20 already exists in model.dtb Support disk compatibility already enabled. Support memory compatibility already enabled. NVMe support already enabled. M.2 volume support already enabled. Drive db auto updates already disabled. Creating pool in UI on drives in M.2 adaptor card already enabled. DSM successfully checked disk compatibility.```
kerem commented 2026-03-07 19:16:20 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Dec 31, 2024):

There was a change in v3.5.102 related to detecting expansion units.

Changed to use a faster method of detecting if an expansion unit is connected, for models with the syno_slot_mapping command.

The SA3410 does have the syno_slot_mapping command so the script would be using the faster method of detecting expansion units.

What does this command return?

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

If that returns nothing can you tell me what this command returns:

sudo syno_slot_mapping
<!-- gh-comment-id:2566196147 --> @007revad commented on GitHub (Dec 31, 2024): There was a change in v3.5.102 related to detecting expansion units. > Changed to use a faster method of detecting if an expansion unit is connected, for models with the syno_slot_mapping command. The SA3410 does have the syno_slot_mapping command so the script would be using the faster method of detecting expansion units. What does this command return? ``` sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $5}' ``` If that returns nothing can you tell me what this command returns: ``` sudo syno_slot_mapping ```
kerem commented 2026-03-07 19:16:21 +03:00
Author
Owner
Copy link

@kevin39 commented on GitHub (Dec 31, 2024):

Hi,

ash-4.4# syno_slot_mapping | grep 'Eunit port' | awk '{print $5}'
ash-4.4# syno_slot_mapping
System Disk
Internal Disk
01: /dev/sas12
02: /dev/sas6
03: /dev/sas3
04: /dev/sas11
05: /dev/sas5
06: /dev/sas8
07: /dev/sas2
08: /dev/sas10
09: /dev/sas4
10: /dev/sas1
11: /dev/sas7
12: /dev/sas9

Esata port count: 0
USB Device
01:
02:

PCIe Slot 1: M2D20
01: /dev/nvme1n1
02: /dev/nvme0n1
<!-- gh-comment-id:2566212942 --> @kevin39 commented on GitHub (Dec 31, 2024): Hi, ``` ash-4.4# syno_slot_mapping | grep 'Eunit port' | awk '{print $5}' ash-4.4# syno_slot_mapping System Disk Internal Disk 01: /dev/sas12 02: /dev/sas6 03: /dev/sas3 04: /dev/sas11 05: /dev/sas5 06: /dev/sas8 07: /dev/sas2 08: /dev/sas10 09: /dev/sas4 10: /dev/sas1 11: /dev/sas7 12: /dev/sas9 Esata port count: 0 USB Device 01: 02: PCIe Slot 1: M2D20 01: /dev/nvme1n1 02: /dev/nvme0n1 ```
kerem commented 2026-03-07 19:16:21 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Dec 31, 2024):

So syno_slot_mapping does not work for SAS expansion units.

Does this find the drives in your expansion unit(s)?

sudo synodisk --enum -t ebox
<!-- gh-comment-id:2566240852 --> @007revad commented on GitHub (Dec 31, 2024): So syno_slot_mapping does not work for SAS expansion units. Does this find the drives in your expansion unit(s)? ``` sudo synodisk --enum -t ebox ```
kerem commented 2026-03-07 19:16:21 +03:00
Author
Owner
Copy link

@kevin39 commented on GitHub (Dec 31, 2024):

ash-4.4# synodisk --enum -t ebox
************ Disk Info ***************
>> Disk id: 9
>> Slot id: -1
>> Disk path: /dev/sas13
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 32 C
************ Disk Info ***************
>> Disk id: 5
>> Slot id: -1
>> Disk path: /dev/sas14
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 34 C
************ Disk Info ***************
>> Disk id: 2
>> Slot id: -1
>> Disk path: /dev/sas15
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 35 C
************ Disk Info ***************
>> Disk id: 1
>> Slot id: -1
>> Disk path: /dev/sas16
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 33 C
************ Disk Info ***************
>> Disk id: 12
>> Slot id: -1
>> Disk path: /dev/sas17
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 32 C
************ Disk Info ***************
>> Disk id: 8
>> Slot id: -1
>> Disk path: /dev/sas18
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 35 C
************ Disk Info ***************
>> Disk id: 4
>> Slot id: -1
>> Disk path: /dev/sas19
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 35 C
************ Disk Info ***************
>> Disk id: 3
>> Slot id: -1
>> Disk path: /dev/sas20
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 34 C
************ Disk Info ***************
>> Disk id: 11
>> Slot id: -1
>> Disk path: /dev/sas21
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 33 C
************ Disk Info ***************
>> Disk id: 10
>> Slot id: -1
>> Disk path: /dev/sas22
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 32 C
************ Disk Info ***************
>> Disk id: 7
>> Slot id: -1
>> Disk path: /dev/sas23
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 36 C
************ Disk Info ***************
>> Disk id: 6
>> Slot id: -1
>> Disk path: /dev/sas24
>> Disk model: ST18000NM000J-2TV103
>> Total capacity: 16764.00 GB
>> Tempeture: 34 C
ash-4.4#
<!-- gh-comment-id:2566245400 --> @kevin39 commented on GitHub (Dec 31, 2024): ``` ash-4.4# synodisk --enum -t ebox ************ Disk Info *************** >> Disk id: 9 >> Slot id: -1 >> Disk path: /dev/sas13 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 32 C ************ Disk Info *************** >> Disk id: 5 >> Slot id: -1 >> Disk path: /dev/sas14 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 34 C ************ Disk Info *************** >> Disk id: 2 >> Slot id: -1 >> Disk path: /dev/sas15 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 35 C ************ Disk Info *************** >> Disk id: 1 >> Slot id: -1 >> Disk path: /dev/sas16 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 33 C ************ Disk Info *************** >> Disk id: 12 >> Slot id: -1 >> Disk path: /dev/sas17 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 32 C ************ Disk Info *************** >> Disk id: 8 >> Slot id: -1 >> Disk path: /dev/sas18 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 35 C ************ Disk Info *************** >> Disk id: 4 >> Slot id: -1 >> Disk path: /dev/sas19 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 35 C ************ Disk Info *************** >> Disk id: 3 >> Slot id: -1 >> Disk path: /dev/sas20 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 34 C ************ Disk Info *************** >> Disk id: 11 >> Slot id: -1 >> Disk path: /dev/sas21 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 33 C ************ Disk Info *************** >> Disk id: 10 >> Slot id: -1 >> Disk path: /dev/sas22 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 32 C ************ Disk Info *************** >> Disk id: 7 >> Slot id: -1 >> Disk path: /dev/sas23 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 36 C ************ Disk Info *************** >> Disk id: 6 >> Slot id: -1 >> Disk path: /dev/sas24 >> Disk model: ST18000NM000J-2TV103 >> Total capacity: 16764.00 GB >> Tempeture: 34 C ash-4.4# ```
kerem commented 2026-03-07 19:16:21 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Dec 31, 2024):

I'll release a new version with a fix in a few hours and reply back.

<!-- gh-comment-id:2566248061 --> @007revad commented on GitHub (Dec 31, 2024): I'll release a new version with a fix in a few hours and reply back.
kerem commented 2026-03-07 19:16:21 +03:00
Author
Owner
Copy link

@kevin39 commented on GitHub (Dec 31, 2024):

Thank you :)

<!-- gh-comment-id:2566248823 --> @kevin39 commented on GitHub (Dec 31, 2024): Thank you :)
kerem commented 2026-03-07 19:16:21 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Dec 31, 2024):

Try v3.6.110

<!-- gh-comment-id:2566316840 --> @007revad commented on GitHub (Dec 31, 2024): Try [v3.6.110](https://github.com/007revad/Synology_HDD_db/releases/tag/v3.6.110)
kerem commented 2026-03-07 19:16:21 +03:00
Author
Owner
Copy link

@kevin39 commented on GitHub (Dec 31, 2024):

Thank you, your fix works. Good job !

<!-- gh-comment-id:2566324403 --> @kevin39 commented on GitHub (Dec 31, 2024): Thank you, your fix works. Good job !
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
develop
v3.6.125
v3.6.124
v3.6.123
v3.6.122
v3.6.121
v3.6.119
v3.6.118
v3.6.116
v3.6.115
v3.6.114
v3.6.113
v3.6.112
v3.6.111
v3.6.110
v3.6.109
v3.5.108
v3.5.107
v3.5.106
v3.5.105
v3.5.104
v3.5.103
v3.5.102
v3.5.101
v3.5.100-RC
v3.5.99-RC
v3.5.98
v3.5.97
v3.5.96
v3.5.94
v3.5.94-RC
v3.5.93
v3.5.92
v3.5.91
v3.5.90
v3.5.90-RC
v3.5.89
v3.5.88
v3.4.87
v3.4.86
v3.4.85
v3.4.84
v3.4.83
v3.4.82
v3.4.81
v3.4.80
v3.4.79
v3.4.78
v3.4.77
v3.3.73
v3.3.72
v3.3.70
v3.2.69
v3.2.68
v3.2.67-RC
v3.2.66-RC
v3.1.65
v3.1.64
v3.1.63
v3.1.62
v3.1.61
v3.1.60-RC
v3.1.59-RC
v3.1.58-RC
v3.1.57-RC
v3.0.56
v3.0.55
v2.3.54-RC
v2.3.51-RC
v2.3.49-RC
v2.3.48-RC
v2.2.47
v2.3.53-RC
v2.3.50-RC
v2.2.46
get_syno_model
v2.2.46_test
v2.2.45
v2.2.44
v2.2.43
v2.2.42
v2.2.39
v2.2.40
v2.2.41
v2.1.38
v2.1.37
v2.0.35
v1.3.34
v1.3.33
v1.3.32
v1.2.31
v1.2.30
v1.2.29
v1.2.28
v1.2.27
v1.2.25
v1.2.26
v1.2.24
v1.2.23
v1.2.22
v1.2.21
v1.2.20
v1.2.17
v1.2.16
v1.2.15
v1.1.14
v1.1.13
v1.1.12
v1.1.11
1.1.10
v1.1.9
1.1.8
v1.0.7
V1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
Labels
Clear labels   
bug

   
bug

   
bug

   
documentation

   
enhancement

   
enhancement

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
suggestion
No labels
bug
bug
bug
documentation
enhancement
enhancement
help wanted
pull-request
suggestion
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_HDD_db#145
No description provided.