[GH-ISSUE #272] Disable non-Synology recommended memory module configurations message. #98

New issue

Closed

opened 2026-03-07 19:15:28 +03:00 by kerem · 20 comments

kerem commented 2026-03-07 19:15:28 +03:00

Owner

Copy link

Originally created by @costispavlou on GitHub (Apr 1, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/272

what is the command to disable this message?

I tried

sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh --ram
Synology_HDD_db v3.4.87
DS1618+ DSM 7.1.1-42962-6
ds1618+_host_v7 version 8046

Using options: --ram
Running from: /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh

HDD/SSD models found: 3
MG06ACA800E,0108
ST14000NE0008-2JK101,EN01
ST6000VX0023-2EF110,SC60

No M.2 drives found

No M.2 PCIe cards found

No Expansion Units found

MG06ACA800E already exists in ds1618+_host_v7.db
MG06ACA800E already exists in ds1618+_host_v7.db.new
ST14000NE0008-2JK101 already exists in ds1618+_host_v7.db
ST14000NE0008-2JK101 already exists in ds1618+_host_v7.db.new
ST6000VX0023-2EF110 already exists in ds1618+_host_v7.db
ST6000VX0023-2EF110 already exists in ds1618+_host_v7.db.new

Support disk compatibility already enabled.

Max memory is set to 32 GB.

Drive db auto updates already enabled.

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.

but still pops up after restart.

Originally created by @costispavlou on GitHub (Apr 1, 2024). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/272 what is the command to disable this message?  I tried ``` sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh --ram Synology_HDD_db v3.4.87 DS1618+ DSM 7.1.1-42962-6 ds1618+_host_v7 version 8046 Using options: --ram Running from: /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh HDD/SSD models found: 3 MG06ACA800E,0108 ST14000NE0008-2JK101,EN01 ST6000VX0023-2EF110,SC60 No M.2 drives found No M.2 PCIe cards found No Expansion Units found MG06ACA800E already exists in ds1618+_host_v7.db MG06ACA800E already exists in ds1618+_host_v7.db.new ST14000NE0008-2JK101 already exists in ds1618+_host_v7.db ST14000NE0008-2JK101 already exists in ds1618+_host_v7.db.new ST6000VX0023-2EF110 already exists in ds1618+_host_v7.db ST6000VX0023-2EF110 already exists in ds1618+_host_v7.db.new Support disk compatibility already enabled. Max memory is set to 32 GB. Drive db auto updates already enabled. DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ``` but still pops up after restart.

kerem closed this issue 2026-03-07 19:15:29 +03:00

kerem commented 2026-03-07 19:15:30 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 1, 2024):

Run the script with -nr or --noupdate --ram

The -n or --noupdate will prevent DSM updating the drive databases when the NAS boots, when you insert a different drive etc.

Is there any reason why your DS1618+ is still on DSM 7.1.1 when 7.2.1 is available?

<!-- gh-comment-id:2030520830 --> @007revad commented on GitHub (Apr 1, 2024): Run the script with `-nr` or `--noupdate --ram` The `-n` or `--noupdate` will prevent DSM updating the drive databases when the NAS boots, when you insert a different drive etc. Is there any reason why your DS1618+ is still on DSM 7.1.1 when 7.2.1 is available?

kerem commented 2026-03-07 19:15:30 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 1, 2024):

so it should be

sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr ?

I haven't noticed there was an update. it shows I'm up to date. any ideas?

<!-- gh-comment-id:2030534550 --> @costispavlou commented on GitHub (Apr 1, 2024): so it should be `sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr ` ? I haven't noticed there was an update. it shows I'm up to date. any ideas? 

kerem commented 2026-03-07 19:15:30 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 1, 2024):

using the above command does nothing

<!-- gh-comment-id:2030546725 --> @costispavlou commented on GitHub (Apr 1, 2024): using the above command does nothing 

kerem commented 2026-03-07 19:15:30 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 1, 2024):

Run the script with -nr or --noupdate --ram

The -n or --noupdate will prevent DSM updating the drive databases when the NAS boots, when you insert a different drive etc.

Is there any reason why your DS1618+ is still on DSM 7.1.1 when 7.2.1 is available?

no idea what's going on..

<!-- gh-comment-id:2030549406 --> @costispavlou commented on GitHub (Apr 1, 2024): > Run the script with `-nr` or `--noupdate --ram` > > The `-n` or `--noupdate` will prevent DSM updating the drive databases when the NAS boots, when you insert a different drive etc. > > Is there any reason why your DS1618+ is still on DSM 7.1.1 when 7.2.1 is available?  no idea what's going on..

kerem commented 2026-03-07 19:15:30 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 1, 2024):

so it should be

sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr ?

Correct.

I haven't noticed there was an update. it shows I'm up to date. any ideas?

If I remember correctly for some older models DSM 7.1.1 did not notify you that DSM 7.2 was available. So people with models older than '20 series needed to download the 7.2 pat.

https://www.synology.com/en-global/support/download/DS1618+?version=7.2#system

<!-- gh-comment-id:2030556193 --> @007revad commented on GitHub (Apr 1, 2024): > so it should be > > `sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr ` ? Correct. > I haven't noticed there was an update. it shows I'm up to date. any ideas? If I remember correctly for some older models DSM 7.1.1 did not notify you that DSM 7.2 was available. So people with models older than '20 series needed to download the 7.2 pat. https://www.synology.com/en-global/support/download/DS1618+?version=7.2#system

kerem commented 2026-03-07 19:15:30 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 1, 2024):

so it should be
sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr ?

Correct.

it doesn't work.. after boot it still sends the same message

<!-- gh-comment-id:2030560202 --> @costispavlou commented on GitHub (Apr 1, 2024): > > so it should be > > `sudo -s /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr ` ? > > Correct. > it doesn't work.. after boot it still sends the same message

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 1, 2024):

no idea what's going on..

That's weird because the Synology website says you can go from 7.1.1 to "7.2.1 (with update 1)"... which actually surprised me because because normally it says things like "7.1.1 to 7.2 to 7.2.1"

Try 7.2
https://global.synologydownload.com/download/DSM/release/7.2/64570-1/DSM_DS1618%2B_64570.pat

Then 7.2.1 (with update 1)
https://global.synologydownload.com/download/DSM/release/7.2.1/69057-1/DSM_DS1618%2B_69057.pat

Then 7.2.1 update 4
https://global.synologydownload.com/download/DSM/criticalupdate/update_pack/69057-4/synology_denverton_1618%2B.pat

<!-- gh-comment-id:2030567109 --> @007revad commented on GitHub (Apr 1, 2024): > no idea what's going on.. That's weird because the Synology website says you can go from 7.1.1 to "7.2.1 (with update 1)"... which actually surprised me because because normally it says things like "7.1.1 to 7.2 to 7.2.1" Try 7.2 https://global.synologydownload.com/download/DSM/release/7.2/64570-1/DSM_DS1618%2B_64570.pat Then 7.2.1 (with update 1) https://global.synologydownload.com/download/DSM/release/7.2.1/69057-1/DSM_DS1618%2B_69057.pat Then 7.2.1 update 4 https://global.synologydownload.com/download/DSM/criticalupdate/update_pack/69057-4/synology_denverton_1618%2B.pat

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 1, 2024):

it doesn't work.. after boot it still sends the same message

Did you clear the old message?

<!-- gh-comment-id:2030569244 --> @007revad commented on GitHub (Apr 1, 2024): > it doesn't work.. after boot it still sends the same message Did you clear the old message?

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 2, 2024):

it doesn't work.. after boot it still sends the same message

Did you clear the old message?

i did yeah.

<!-- gh-comment-id:2031120189 --> @costispavlou commented on GitHub (Apr 2, 2024): > > it doesn't work.. after boot it still sends the same message > > Did you clear the old message? i did yeah.

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 2, 2024):

is it -s or -i ?

<!-- gh-comment-id:2031215320 --> @costispavlou commented on GitHub (Apr 2, 2024): is it -s or -i ?

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 2, 2024):

You can use sudo -i or sudo -s

• sudo -s runs the command as you but with root privileges.
• sudo -i runs the command as root.

You are better off scheduling the script to run at boot up.
https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md

For step 8 in the screenshot, or step 9 in instructions, of setting up the scheduled task you would enter:
/volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr

Did you manage to update to DSM 7.2.1 ?

<!-- gh-comment-id:2031239892 --> @007revad commented on GitHub (Apr 2, 2024): You can use sudo -i or sudo -s - sudo -s runs the command as you but with root privileges. - sudo -i runs the command as root. You are better off scheduling the script to run at boot up. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md For step 8 in the screenshot, or step 9 in instructions, of setting up the scheduled task you would enter: `/volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr` Did you manage to update to DSM 7.2.1 ?

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 2, 2024):

You can use sudo -i or sudo -s

• sudo -s runs the command as you but with root privileges.
• sudo -i runs the command as root.

You are better off scheduling the script to run at boot up. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md

For step 8 in the screenshot, or step 9 in instructions, of setting up the scheduled task you would enter: /volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr

Did you manage to update to DSM 7.2.1 ?

i've found the fix yes, but did not update yet, i'll probably do it today though. I'm just afraid that it will auto update an app (surveillence station) that i do not want to update. But i'll probably reinstall it later since if that happens.

As far as the script goes, does it need to always run at boot? or once and then never again ?

What i did was to run the script and then reboot to check if it worked (which it didnt).
I tried both -s and -i. But i did not schedule it to run at boot.

<!-- gh-comment-id:2031261987 --> @costispavlou commented on GitHub (Apr 2, 2024): > You can use sudo -i or sudo -s > > * sudo -s runs the command as you but with root privileges. > * sudo -i runs the command as root. > > You are better off scheduling the script to run at boot up. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md > > For step 8 in the screenshot, or step 9 in instructions, of setting up the scheduled task you would enter: `/volume1/data/Backup/Synology/Synology_HDD_db-3.4.87/syno_hdd_db.sh -nr` > > Did you manage to update to DSM 7.2.1 ? i've found the fix yes, but did not update yet, i'll probably do it today though. I'm just afraid that it will auto update an app (surveillence station) that i do not want to update. But i'll probably reinstall it later since if that happens. As far as the script goes, does it need to always run at boot? or once and then never again ? What i did was to run the script and then reboot to check if it worked (which it didnt). I tried both -s and -i. But i did not schedule it to run at boot.

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 2, 2024):

The script only needs to be run after a DSM update, but it's easier to just schedule it at boot up because DSM can update itself sometimes.

`Do both the following commands return "127.0.0.1" ?
synogetkeyvalue /etc.defaults/synoinfo.conf drive_db_test_url
synogetkeyvalue /etc/synoinfo.conf drive_db_test_url

That should have been do both the following commands return "no" ?

synogetkeyvalue /etc.defaults/synoinfo.conf support_memory_compatibility
synogetkeyvalue /etc/synoinfo.conf support_memory_compatibility

<!-- gh-comment-id:2031328183 --> @007revad commented on GitHub (Apr 2, 2024): The script only needs to be run after a DSM update, but it's easier to just schedule it at boot up because DSM can update itself sometimes. ~`Do both the following commands return "127.0.0.1" ?~ ~synogetkeyvalue /etc.defaults/synoinfo.conf drive_db_test_url~ ~synogetkeyvalue /etc/synoinfo.conf drive_db_test_url~ That should have been do both the following commands return "no" ? ``` synogetkeyvalue /etc.defaults/synoinfo.conf support_memory_compatibility synogetkeyvalue /etc/synoinfo.conf support_memory_compatibility ```

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 2, 2024):

you mean ssh on it and run these two commands?
it's off right now but i will test in an hour or so when it boots and report back with the result of the two commands.
Thanks for your help!

<!-- gh-comment-id:2031353323 --> @costispavlou commented on GitHub (Apr 2, 2024): you mean ssh on it and run these two commands? it's off right now but i will test in an hour or so when it boots and report back with the result of the two commands. Thanks for your help!

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 2, 2024):

you mean ssh on it and run these two commands?

Yes.

I'm wondering if this unique to the DS1618+. Like the DVA1622 and DVA1321 which have the same problem and I had to add an extra command in syno_hdd_db.sh for those models.

Try this command and see if it stops the memory warnings:

sudo -s synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true

<!-- gh-comment-id:2031416750 --> @007revad commented on GitHub (Apr 2, 2024): > you mean ssh on it and run these two commands? Yes. I'm wondering if this unique to the DS1618+. Like the DVA1622 and DVA1321 which have the same problem and I had to add an extra command in syno_hdd_db.sh for those models. Try this command and see if it stops the memory warnings: ``` sudo -s synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true ```

kerem commented 2026-03-07 19:15:31 +03:00

Author

Owner

Copy link

@costispavlou commented on GitHub (Apr 2, 2024):

Try this command and see if it stops the memory warnings:

sudo -s synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true

This worked. Thank you!

<!-- gh-comment-id:2031847751 --> @costispavlou commented on GitHub (Apr 2, 2024): > Try this command and see if it stops the memory warnings: > > ``` > sudo -s synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true > ``` This worked. Thank you! 

kerem commented 2026-03-07 19:15:32 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Apr 2, 2024):

Interesting.

I just checked synoninfo.conf for all 115 NAS models that support DSM 7.2 and 77 of them do not have support_memory_compatibility

So setting support_memory_compatibility="no" only works on 38 NAS models.

The other 77 need synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true

<!-- gh-comment-id:2032986816 --> @007revad commented on GitHub (Apr 2, 2024): Interesting. I just checked synoninfo.conf for all 115 NAS models that support DSM 7.2 and 77 of them do not have support_memory_compatibility So setting `support_memory_compatibility="no"` only works on 38 NAS models. The other 77 need `synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true`

kerem commented 2026-03-07 19:15:32 +03:00

Author

Owner

Copy link

@x-magic commented on GitHub (Jul 14, 2024):

sudo -s synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true

DS1819+ won't work with support_memory_compatibility either. Needs to stop the service to disable the message.

Seems support_memory_compatibility doesn't exist on this model by default:

root@NAS:~# cat /etc/synoinfo.conf  | grep mem
supportmemtest="yes"
mem_max_mb="32768"
support_memory_limitation="yes"
mem_min_mb="4096"
root@NAS:~# cat /etc.defaults/synoinfo.conf | grep mem
mem_max_mb="32768"
mem_min_mb="4096"
support_memory_limitation="yes"
supportmemtest="yes"

<!-- gh-comment-id:2227141792 --> @x-magic commented on GitHub (Jul 14, 2024): > ``` > sudo -s synosetkeyvalue /usr/lib/systemd/system/SynoMemCheck.service ExecStart /bin/true > ``` DS1819+ won't work with `support_memory_compatibility` either. Needs to stop the service to disable the message. Seems `support_memory_compatibility` doesn't exist on this model by default: ``` root@NAS:~# cat /etc/synoinfo.conf | grep mem supportmemtest="yes" mem_max_mb="32768" support_memory_limitation="yes" mem_min_mb="4096" root@NAS:~# cat /etc.defaults/synoinfo.conf | grep mem mem_max_mb="32768" mem_min_mb="4096" support_memory_limitation="yes" supportmemtest="yes" ```

kerem commented 2026-03-07 19:15:32 +03:00

Author

Owner

Copy link

@007revad commented on GitHub (Jul 14, 2024):

@x-magic

I notice that only 11 models have support_memory_limitation instead of support_memory_compatibility

What happens if you disable support_memory_limitation but leave SynoMemCheck.service enabled ?

If the script was run with the -r or --ram option, and support_memory_compatibility does not exist in synoinfo.conf, the script disables the SynoMemCheck.service

<!-- gh-comment-id:2227150597 --> @007revad commented on GitHub (Jul 14, 2024): @x-magic I notice that only 11 models have support_memory_limitation instead of support_memory_compatibility What happens if you disable support_memory_limitation but leave SynoMemCheck.service enabled ? If the script was run with the -r or --ram option, and support_memory_compatibility does not exist in synoinfo.conf, the script disables the SynoMemCheck.service

kerem commented 2026-03-07 19:15:32 +03:00

Author

Owner

Copy link

@x-magic commented on GitHub (Jul 14, 2024):

@007revad I'll try it out. Just not sure when will my NAS reboot next time, but will certainly follow up.

Yup, the notification is gone. DS1819+

root@NAS:~# cat /etc/synoinfo.conf | grep mem
supportmemtest="yes"
mem_max_mb="32768"
support_memory_limitation="no"
mem_min_mb="4096"

root@NAS:~# cat /etc.defaults/synoinfo.conf | grep mem
mem_max_mb="32768"
mem_min_mb="4096"
support_memory_limitation="no"
supportmemtest="yes"

root@NAS:~# cat /usr/lib/systemd/system/SynoMemCheck.service
[Unit]
Description=Memory Rule Check
IgnoreOnIsolate=yes
After=syno-bootup-done.target pkg-synoha-safemode-after.service

[Service]
Type=oneshot
ExecStart="/usr/syno/bin/syno_mem_check"
RemainAfterExit=yes

[X-Synology]

<!-- gh-comment-id:2227151701 --> @x-magic commented on GitHub (Jul 14, 2024): @007revad ~~I'll try it out. Just not sure when will my NAS reboot next time, but will certainly follow up.~~ Yup, the notification is gone. DS1819+ ``` root@NAS:~# cat /etc/synoinfo.conf | grep mem supportmemtest="yes" mem_max_mb="32768" support_memory_limitation="no" mem_min_mb="4096" root@NAS:~# cat /etc.defaults/synoinfo.conf | grep mem mem_max_mb="32768" mem_min_mb="4096" support_memory_limitation="no" supportmemtest="yes" root@NAS:~# cat /usr/lib/systemd/system/SynoMemCheck.service [Unit] Description=Memory Rule Check IgnoreOnIsolate=yes After=syno-bootup-done.target pkg-synoha-safemode-after.service [Service] Type=oneshot ExecStart="/usr/syno/bin/syno_mem_check" RemainAfterExit=yes [X-Synology] ```

kerem referenced this issue 2026-03-07 19:17:29 +03:00

[PR #98] [MERGED] Develop #267

kerem referenced this issue 2026-03-07 19:17:30 +03:00

[PR #102] [MERGED] sync dev #273

kerem referenced this issue 2026-03-12 17:41:54 +03:00

[PR #98] [MERGED] Develop #927

kerem referenced this issue 2026-03-12 17:42:11 +03:00

[PR #102] [MERGED] sync dev #936

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

Subscribe

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#98

No description provided.