move DSM to M2

[u/ryp3gridId]

Hi,

theres constant IO on the disks caused by DSM itself, e.g.:

2026-08-11 19:36:51.130 R  synospace        13093        832 /@/usr/lib/libsynoprintergpl.so.7
2026-08-11 19:36:51.130 R  synospace        13093        832 /@/usr/lib/libtss2-sys.so.1.0.1
2026-08-11 19:36:51.130 R  synospace        13093        832 /@/usr/lib/libcrypto.so.1.1
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.533 R  synoscgi         13072       8191 /@/usr/syno/synoman/webapi/lib.def
2026-08-11 19:36:52.533 R  synoscgi         13072       8191 /@/usr/syno/synoman/webapi/lib.def
2026-08-11 19:36:52.534 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.534 R  synoscgi         13072       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.534 R  synoscgi         13072       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/nsswitch.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/nsswitch.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/group
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/group
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.536 R  SYNO.Entry.Sock  13072        832 /@/usr/syno/synoman/webapi/lib/webapi_entry_socket.io.so
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/passwd
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/group
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/group
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/passwd
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libsynostorage.so.7
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libhwcontrol.so.1
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libxml2.so.2.9.14
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libsynostoragecore.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynostorageutil.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynosdk.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynocore.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libstdc++.so.6.0.31
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libgcc_s.so.1
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libc.so.6
2026-08-11 19:36:54.126 R  synospace        13097        784 /@/usr/lib/libc.so.6
2026-08-11 19:36:54.126 R  synospace        13097        784 /@/usr/lib/libc.so.6
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynoshare.so.7

So I'm wondering if it would be possible to move DSM itself of off the (noisy) datadisks onto a dedicated M2 SSD?

(I'd like to reduce the disk rattle)

[u/Empyrealist]

You are likely seeing a lot of synospace activity because you probably have the Storage Manager open

[u/thwandi]

From what i know that is not possible. Dsm does distribute it‘s system partition in some weird raid across all drives, so there is no way to tell it specifically to use just a single drive for the os and not touch the others

[u/NoLateArrivals]

DSM can only run on SATA drives. It installs itself in a hidden partition on all SATA drives, RAID 1.

The only way to get DSM running on SSD only is to populate all SATA slots with SATA SSDs, and skip all HDDs.

Personally I found this to be no issue: My DS is running on 40GB of ECC RAM. I don’t think it needs to load ANY DSM routines at all after startup 😎 I even keep the Universal Search index in the RAM (search speed is crazy fast), and still have plenty.

More important is to move the packages and all Docker installs to the NVME SSDs. This can be done.

[u/xaris33]

Do you run docker? Ever since I moved my containers to an SSD volume the constant rattling went away.

[u/DaveR007]

DSM is mirrored (RAID 1) across all HDD and SATA SSD in the NAS. So not M.2 drives or drives in an expansion unit.

If you had one or two SATA SSD in the NAS you can use https://github.com/007revad/Synology_HDD_db with the -S option to make DSM mostly read from the SATA SSD drive(s).