-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Support 2.5 Cache Drives RS3413xs+ #157
Comments
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. Can you tell me which of the drives that command returned are the SSDs in the cache trays? |
Do you want to setup those SSDs as RAID 1, RAID 0 or 2 separate single volumes? |
These are the two installed SSDs currently: /dev/sdk SSDSC2BA200G3 BTTV322101WW200GGN |
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. |
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. |
I believe it will work. |
Another alternative is:
or if you also want DSM to do a drive check after creating the storage pools:
You'd then create the volumes in storage manager. |
Is there any way to add support for 2.5in SSDs in the cache trays of a Synology Rack Server?
The text was updated successfully, but these errors were encountered: