mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 21:55:59 +03:00
[GH-ISSUE #344] RX1214 expansion unit in combination with RS2421+ #120
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#120
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 @GellyPie on GitHub (Aug 16, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/344
Hello, I have a RS2421+ with a RX1214 expansion unit connected.
When I execute the script it says it cannot find the expansion unit:
It is detected by DSM:
As a test, there are currently 3 disks in the expansion unit.
They show up as eSATA devices but are unusable:
@007revad commented on GitHub (Aug 16, 2024):
I didn't realise that Inifiniband expansion units show up in DSM as eSATA devices.
Give me a few hours and I'll add the RX1214 and other old inifiniband expansion units to my https://github.com/007revad/Synology_enable_eunit script.
@007revad commented on GitHub (Aug 17, 2024):
I've released a new version, v3.0.14, that supports the RX1214.
https://github.com/007revad/Synology_enable_eunit/releases
@007revad commented on GitHub (Aug 17, 2024):
Can you tell what the following command returns:
@GellyPie commented on GitHub (Aug 17, 2024):
I tried v3.0.14 but the message remains, even after a reboot. I tried RX1214 & RX1214RP. (I have an RX1214RP)
The script ran fine and added the rx1214 expansion unit though.
This is what I get after running sudo syno_slot_mapping
@007revad commented on GitHub (Aug 17, 2024):
Okay. So now I'll have a look at the syno_hdd_db script to see why it's not finding your RX1214
Does the following commands find the RX1214?
@GellyPie commented on GitHub (Aug 17, 2024):
It doesn't return anything:
@007revad commented on GitHub (Aug 17, 2024):
Do you have any drives in the RX1214?
@GellyPie commented on GitHub (Aug 17, 2024):
Yes, there are 3 WD Red 6TB drives in it. It shows them in the DSM UI as external devices on top but they can't be used in storage manager:
In storage manager I can only see the 1 disk in the RS2421+:
@007revad commented on GitHub (Aug 17, 2024):
Have you rebooted since you ran Synology_enable_eunit?
@GellyPie commented on GitHub (Aug 17, 2024):
Yes, on the first run the script asked to reboot, which I did.
2nd run it didn't ask to reboot.
edit: just gave it another reboot but same result
@007revad commented on GitHub (Aug 17, 2024):
Has the "incompatible expansion unit" warning gone in storage manager?
@GellyPie commented on GitHub (Aug 17, 2024):
no
@GellyPie commented on GitHub (Aug 17, 2024):
not sure if it matters but it says "RX1214-1" in storage manager:
And in info center it says "Synology-RX1214":
@007revad commented on GitHub (Aug 17, 2024):
RX1214-1 in storage manager is normal. It's because the RS2421 has 2 expansion ports and the RX1214 is connected to expansion port 1.
Have you tried connecting it to expansion port 2?
@GellyPie commented on GitHub (Aug 18, 2024):
There's only 1 port on both the rs2421 as the rx1214.
@007revad commented on GitHub (Aug 18, 2024):
Ah yes, the 24 in RS2421+ means "12 bay NAS + one 12 bay expansion unit".
@007revad commented on GitHub (Aug 18, 2024):
Are you able to copy the following 4 files, zip them, then attach the zip file to your reply.
Change "/volume1/test" to a volume and shared folder on your RS2421+
And tell me what these commands return:
@GellyPie commented on GitHub (Aug 18, 2024):
I've attached the requested files
files.zip
This is the output of the commands:
@007revad commented on GitHub (Aug 19, 2024):
Do you mean you tried connecting the RX1214 & then the RX1214RP and neither worked?
Your model.dtb files only contain RX1214RP and not RX1214
I think this from the script is incorrect, when the model.dtb already contains RX1214RP. The script is looking for "RX1214" but matching on the RX1214 in "RX1214RP".
Can you run this version with the --check option to confirm that it correctly shows that RX1214RP is enabled and does not show that RX1214 is enabled: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.15-RC
If it does not show:
then run it without the --check option and enable RX1214
@GellyPie commented on GitHub (Aug 19, 2024):
Sorry for the confusion, I have and RX1214RP. At first I selected RX1214RP, when that didn't work after a reboot I tried RX1214. But that didn't work either after a reboot.
I'll try the new release now.
@GellyPie commented on GitHub (Aug 19, 2024):
It did not show RX1214 as enabled with the --check option.
After enabling it again with option 11 it shows the drives in Storage Manager and they can be used!
It seems like DSM sees the RX1214RP as RX1214 but that doesn't really matter as the only difference is the redundant PSU.
Thank you very much!
@007revad commented on GitHub (Aug 19, 2024):
Excellent.
I'll change the script so when someone selects an RP model the scripts adds both the RP and non-RP models.
I noticed the original model.dtb file contains both RX1217 and RX1217RP. Maybe RX1214RP identifies itself as a RX1214 and the RX1217RP identifies itself as a RX1217RP.