[GH-ISSUE #157] [Feature Request] Support 2.5 Cache Drives RS3413xs+ #36

Closed
opened 2026-03-07 19:19:46 +03:00 by kerem · 8 comments
Owner

Originally created by @bradkeller on GitHub (May 19, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/157

Originally assigned to: @007revad on GitHub.

Is there any way to add support for 2.5in SSDs in the cache trays of a Synology Rack Server?

Originally created by @bradkeller on GitHub (May 19, 2024). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/157 Originally assigned to: @007revad on GitHub. Is there any way to add support for 2.5in SSDs in the cache trays of a Synology Rack Server?
kerem closed this issue 2026-03-07 19:19:46 +03:00
Author
Owner

@007revad commented on GitHub (May 19, 2024):

So DSM 7.1.1 won't let you create a storage pool on 2.5in SSDs in the cache trays?

I notice that the RS3413xs+ manual says you must install 2 identical SSDs in the cache trays in order to mount SSD cache. So it sounds like it only supported a read/write cache.

What does the following (insanely long) command return? It's 1 line.
for s in /dev/sd?; do echo -ne "$s "; cat "/sys/block/$(basename -- $s)/device/model" | tr -d '\n'; cat "/sys/block/$(basename -- $s)/device/syno_disk_serial" | xargs; done

Can you tell me which of the drives that command returned are the SSDs in the cache trays?

<!-- gh-comment-id:2119120482 --> @007revad commented on GitHub (May 19, 2024): So DSM 7.1.1 won't let you create a storage pool on 2.5in SSDs in the cache trays? I notice that the RS3413xs+ manual says you must install 2 identical SSDs in the cache trays in order to mount SSD cache. So it sounds like it only supported a read/write cache. What does the following (insanely long) command return? It's 1 line. `for s in /dev/sd?; do echo -ne "$s "; cat "/sys/block/$(basename -- $s)/device/model" | tr -d '\n'; cat "/sys/block/$(basename -- $s)/device/syno_disk_serial" | xargs; done` Can you tell me which of the drives that command returned are the SSDs in the cache trays?
Author
Owner

@007revad commented on GitHub (May 19, 2024):

Do you want to setup those SSDs as RAID 1, RAID 0 or 2 separate single volumes?

<!-- gh-comment-id:2119122181 --> @007revad commented on GitHub (May 19, 2024): Do you want to setup those SSDs as RAID 1, RAID 0 or 2 separate single volumes?
Author
Owner

@bradkeller commented on GitHub (May 19, 2024):

So DSM 7.1.1 won't let you create a storage pool on 2.5in SSDs in the cache trays?

I notice that the RS3413xs+ manual says you must install 2 identical SSDs in the cache trays in order to mount SSD cache. So it sounds like it only supported a read/write cache.

What does the following (insanely long) command return? It's 1 line. for s in /dev/sd?; do echo -ne "$s "; cat "/sys/block/$(basename -- $s)/device/model" | tr -d '\n'; cat "/sys/block/$(basename -- $s)/device/syno_disk_serial" | xargs; done

Can you tell me which of the drives that command returned are the SSDs in the cache trays?

These are the two installed SSDs currently:

/dev/sdk SSDSC2BA200G3 BTTV322101WW200GGN
/dev/sdl SSDSC2BA200G3 BTTV322101WZ200GGN

<!-- gh-comment-id:2119124736 --> @bradkeller commented on GitHub (May 19, 2024): > So DSM 7.1.1 won't let you create a storage pool on 2.5in SSDs in the cache trays? > > I notice that the RS3413xs+ manual says you must install 2 identical SSDs in the cache trays in order to mount SSD cache. So it sounds like it only supported a read/write cache. > > What does the following (insanely long) command return? It's 1 line. `for s in /dev/sd?; do echo -ne "$s "; cat "/sys/block/$(basename -- $s)/device/model" | tr -d '\n'; cat "/sys/block/$(basename -- $s)/device/syno_disk_serial" | xargs; done` > > Can you tell me which of the drives that command returned are the SSDs in the cache trays? These are the two installed SSDs currently: /dev/sdk SSDSC2BA200G3 BTTV322101WW200GGN /dev/sdl SSDSC2BA200G3 BTTV322101WZ200GGN
Author
Owner

@bradkeller commented on GitHub (May 19, 2024):

Do you want to setup those SSDs as RAID 1, RAID 0 or 2 separate single volumes?

Is it the same amount of work to have multiple options? I wouldn't mind all of those options being available all being equal. Otherwise currently I would just be happy moving the SSDs I have in the 3.5in bays to the 2.5in bay and using them as separate single volumes.

<!-- gh-comment-id:2119125184 --> @bradkeller commented on GitHub (May 19, 2024): > Do you want to setup those SSDs as RAID 1, RAID 0 or 2 separate single volumes? Is it the same amount of work to have multiple options? I wouldn't mind all of those options being available all being equal. Otherwise currently I would just be happy moving the SSDs I have in the 3.5in bays to the 2.5in bay and using them as separate single volumes.
Author
Owner

@007revad commented on GitHub (May 19, 2024):

So the SSDs are currently in 3.5in bays. You can create the volume, or volumes, on them while they are in the 3.5in bays, then shut down the NAS and move the SSDs to the 2.5in cache trays.

<!-- gh-comment-id:2119130013 --> @007revad commented on GitHub (May 19, 2024): So the SSDs are currently in 3.5in bays. You can create the volume, or volumes, on them while they are in the 3.5in bays, then shut down the NAS and move the SSDs to the 2.5in cache trays.
Author
Owner

@bradkeller commented on GitHub (May 19, 2024):

So the SSDs are currently in 3.5in bays. You can create the volume, or volumes, on them while they are in the 3.5in bays, then shut down the NAS and move the SSDs to the 2.5in cache trays.

The two installed SSDs are currently uninitialized in the 2.5in cache trays. You think I can move them to a 3.5 tray and create volume(s) and then move them back? I can give it a go.

<!-- gh-comment-id:2119136285 --> @bradkeller commented on GitHub (May 19, 2024): > So the SSDs are currently in 3.5in bays. You can create the volume, or volumes, on them while they are in the 3.5in bays, then shut down the NAS and move the SSDs to the 2.5in cache trays. The two installed SSDs are currently uninitialized in the 2.5in cache trays. You think I can move them to a 3.5 tray and create volume(s) and then move them back? I can give it a go.
Author
Owner

@007revad commented on GitHub (May 19, 2024):

I believe it will work.

<!-- gh-comment-id:2119137447 --> @007revad commented on GitHub (May 19, 2024): I believe it will work.
Author
Owner

@007revad commented on GitHub (May 19, 2024):

Another alternative is:

sudo synostgpool --create -t single -l basic /dev/sdk
sudo synostgpool --create -t single -l basic /dev/sdl

or if you also want DSM to do a drive check after creating the storage pools:

sudo synostgpool --create -t single -l basic -c /dev/sdk
sudo synostgpool --create -t single -l basic -c /dev/sdl

You'd then create the volumes in storage manager.

<!-- gh-comment-id:2119139021 --> @007revad commented on GitHub (May 19, 2024): Another alternative is: ``` sudo synostgpool --create -t single -l basic /dev/sdk sudo synostgpool --create -t single -l basic /dev/sdl ``` or if you also want DSM to do a drive check after creating the storage pools: ``` sudo synostgpool --create -t single -l basic -c /dev/sdk sudo synostgpool --create -t single -l basic -c /dev/sdl ``` You'd then create the volumes in storage manager.
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
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_M2_volume#36
No description provided.