starred/Synology_HDD_db
1
0
Fork 0
mirror of https://github.com/007revad/Synology_HDD_db.git synced 2026-04-25 21:55:59 +03:00
Code Issues 102 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #84] Lost access to Storage Manager on DSM 7.2-64561 (DS923+) #534

New issue
Closed
opened 2026-03-11 11:45:24 +03:00 by kerem · 9 comments
kerem commented 2026-03-11 11:45:24 +03:00
Owner
Copy link

Originally created by @fish-2023 on GitHub (May 31, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/84

Hi,

I have ran the syno_hdd_db.sh script on my DS923+ and after reboot I still couldn't create an M2 storage pool. I have then run the script again to restore the previous settings before trying anything else. After another reboot the Storage Manager was gone.
This seems similar to #73 but on the final version of 7.2.

The model is missing within the Info Center: https://imgur.com/a/B8SV4WU

I run get_syno_model.sh and this is the output:

unamee:
synology_r1000_923+

/etc/synoinfo.conf unique:
synology_r1000_923+

/etc.defaults/synoinfo.conf unique:
synology_r1000_923+

/etc/synoinfo.conf upnpmodelname:
DS923+

/etc.defaults/synoinfo.conf upnpmodelname:
DS923+

/proc/cmdline syno_hw_version:
DS923+

/rpco/sys/kernel syno_hw_version:
DS923+

I have also checked to see if the config file was corrupt in some way, but this is the only thing diff could see:

max-admin@SynologyNAS:~$ sudo diff syno_conf_after_first_attempt.txt /etc.defaults/synoinfo.conf
Password: 
204c204
< support_memory_compatibility="no"
---
> support_memory_compatibility="yes"
328a329
>

I have tried the "Restore DSM configurations" from the "Update & Restore" menu but that didn't help...

Do you have any pointers on how to fix my config?
Thank you

Originally created by @fish-2023 on GitHub (May 31, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/84 Hi, I have ran the syno_hdd_db.sh script on my DS923+ and after reboot I still couldn't create an M2 storage pool. I have then run the script again to restore the previous settings before trying anything else. After another reboot the Storage Manager was gone. This seems similar to #73 but on the final version of 7.2. The model is missing within the Info Center: https://imgur.com/a/B8SV4WU I run get_syno_model.sh and this is the output: ``` unamee: synology_r1000_923+ /etc/synoinfo.conf unique: synology_r1000_923+ /etc.defaults/synoinfo.conf unique: synology_r1000_923+ /etc/synoinfo.conf upnpmodelname: DS923+ /etc.defaults/synoinfo.conf upnpmodelname: DS923+ /proc/cmdline syno_hw_version: DS923+ /rpco/sys/kernel syno_hw_version: DS923+ ``` I have also checked to see if the config file was corrupt in some way, but this is the only thing diff could see: ``` max-admin@SynologyNAS:~$ sudo diff syno_conf_after_first_attempt.txt /etc.defaults/synoinfo.conf Password: 204c204 < support_memory_compatibility="no" --- > support_memory_compatibility="yes" 328a329 > ``` I have tried the "Restore DSM configurations" from the "Update & Restore" menu but that didn't help... Do you have any pointers on how to fix my config? Thank you
kerem closed this issue 2026-03-11 11:45:29 +03:00
kerem commented 2026-03-11 11:45:35 +03:00
Author
Owner
Copy link

@fish-2023 commented on GitHub (May 31, 2023):

As an additional note, these are the times I have ran the script.
If I remember correctly, after the restore and the reboot, the Storage Manager was still there.
The 3rd run was to include the "-n" since I thought the first run might have not worked because of that. I hope this is helpful.

  1. sudo ./syno_hdd_db.sh --ram --showedits
Synology_HDD_db v2.2.47
DS923+ DSM 7.2-64561 
Using options: --ram --showedits

HDD/SSD models found: 3
ST4000VN000-1H4168,SC44
ST8000VN004-2M2101,SC60
ST8000VN004-3CP101,SC60

M.2 drive models found: 1
CT1000P3PSSD8,P9CR40A

No M.2 cards found

No Expansion Units found

Backed up ds923+_host_v7.db.new
Added ST4000VN000-1H4168 to ds923+_host_v7.db
Added ST4000VN000-1H4168 to ds923+_host_v7.db.new
Added ST8000VN004-2M2101 to ds923+_host_v7.db
Added ST8000VN004-2M2101 to ds923+_host_v7.db.new
ST8000VN004-3CP101 already exists in ds923+_host_v7.db
ST8000VN004-3CP101 already exists in ds923+_host_v7.db.new
Added CT1000P3PSSD8 to ds923+_host_v7.db
Added CT1000P3PSSD8 to ds923+_host_v7.db.new

Backed up synoinfo.conf

Support disk compatibility already enabled.

Disabled support memory compatibility.

Max memory already set to 32 GB.

M.2 volume support already enabled.

Drive db auto updates already enabled.

    "ST4000VN000-1H4168": {
      "SC44": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

    "ST8000VN004-2M2101": {
      "SC60": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

    "ST8000VN004-3CP101": {
      "SC60": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true,
            "smart_test_ignore": false,
            "smart_attr_ignore": false
          }
        ]

    "CT1000P3PSSD8": {
      "P9CR40A": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.
  1. sudo ./syno_hdd_db.sh --restore
Synology_HDD_db v2.2.47
DS923+ DSM 7.2-64561 
Using options: --restore

Restored synoinfo.conf
Restored rx418_v7.db
Restored rx415_v7.db
Restored rx1214_v7.db
Restored ds923+_host_v7.db
Restored dx513_v7.db
Restored rx1217_v7.db
Restored dx1215ii_v7.db
Restored ds923+_host_v7.db.new
Restored rx1214rp_v7.db
Restored rx1216sas_v7.db
Restored rx1211rp_v7.db
Restored rx1211_v7.db
Restored dx517_v7.db
Restored dx1211_v7.db
Restored dx1215_v7.db
Restored rx1213sas_v7.db
Restored rx1217sas_v7.db
Restored rxd1219sas_v7.db
Restored rx1217rp_v7.db
Restored rx6022sas_v7.db
Restored dx213_v7.db

Restore successful.
  1. sudo ./syno_hdd_db.sh -nr --showedits > 1_log.txt
    output:
Backed up ds923+_host_v7.db
Backed up ds923+_host_v7.db.new
ST8000VN004-3CP101 already exists in ds923+_host_v7.db
ST8000VN004-3CP101 already exists in ds923+_host_v7.db.new

Backed up synoinfo.conf

log:

Synology_HDD_db v2.2.47
DS923+ DSM 7.2-64561 
Using options: -nr --showedits

HDD/SSD models found: 3
ST4000VN000-1H4168,SC44
ST8000VN004-2M2101,SC60
ST8000VN004-3CP101,SC60

M.2 drive models found: 1
CT1000P3PSSD8,P9CR40A

No M.2 cards found

No Expansion Units found

Added ST4000VN000-1H4168 to ds923+_host_v7.db
Added ST4000VN000-1H4168 to ds923+_host_v7.db.new
Added ST8000VN004-2M2101 to ds923+_host_v7.db
Added ST8000VN004-2M2101 to ds923+_host_v7.db.new
Added CT1000P3PSSD8 to ds923+_host_v7.db
Added CT1000P3PSSD8 to ds923+_host_v7.db.new

Support disk compatibility already enabled.

Disabled support memory compatibility.

Max memory already set to 32 GB.

M.2 volume support already enabled.

Disabled drive db auto updates.

    "ST4000VN000-1H4168": {
      "SC44": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

    "ST8000VN004-2M2101": {
      "SC60": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

    "ST8000VN004-3CP101": {
      "SC60": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true,
            "smart_test_ignore": false,
            "smart_attr_ignore": false
          }
        ]

    "CT1000P3PSSD8": {
      "P9CR40A": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.
<!-- gh-comment-id:1569664381 --> @fish-2023 commented on GitHub (May 31, 2023): As an additional note, these are the times I have ran the script. If I remember correctly, after the restore and the reboot, the Storage Manager was still there. The 3rd run was to include the "-n" since I thought the first run might have not worked because of that. I hope this is helpful. 1. sudo ./syno_hdd_db.sh --ram --showedits ``` Synology_HDD_db v2.2.47 DS923+ DSM 7.2-64561 Using options: --ram --showedits HDD/SSD models found: 3 ST4000VN000-1H4168,SC44 ST8000VN004-2M2101,SC60 ST8000VN004-3CP101,SC60 M.2 drive models found: 1 CT1000P3PSSD8,P9CR40A No M.2 cards found No Expansion Units found Backed up ds923+_host_v7.db.new Added ST4000VN000-1H4168 to ds923+_host_v7.db Added ST4000VN000-1H4168 to ds923+_host_v7.db.new Added ST8000VN004-2M2101 to ds923+_host_v7.db Added ST8000VN004-2M2101 to ds923+_host_v7.db.new ST8000VN004-3CP101 already exists in ds923+_host_v7.db ST8000VN004-3CP101 already exists in ds923+_host_v7.db.new Added CT1000P3PSSD8 to ds923+_host_v7.db Added CT1000P3PSSD8 to ds923+_host_v7.db.new Backed up synoinfo.conf Support disk compatibility already enabled. Disabled support memory compatibility. Max memory already set to 32 GB. M.2 volume support already enabled. Drive db auto updates already enabled. "ST4000VN000-1H4168": { "SC44": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { "ST8000VN004-2M2101": { "SC60": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { "ST8000VN004-3CP101": { "SC60": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true, "smart_test_ignore": false, "smart_attr_ignore": false } ] "CT1000P3PSSD8": { "P9CR40A": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ``` 2. sudo ./syno_hdd_db.sh --restore ``` Synology_HDD_db v2.2.47 DS923+ DSM 7.2-64561 Using options: --restore Restored synoinfo.conf Restored rx418_v7.db Restored rx415_v7.db Restored rx1214_v7.db Restored ds923+_host_v7.db Restored dx513_v7.db Restored rx1217_v7.db Restored dx1215ii_v7.db Restored ds923+_host_v7.db.new Restored rx1214rp_v7.db Restored rx1216sas_v7.db Restored rx1211rp_v7.db Restored rx1211_v7.db Restored dx517_v7.db Restored dx1211_v7.db Restored dx1215_v7.db Restored rx1213sas_v7.db Restored rx1217sas_v7.db Restored rxd1219sas_v7.db Restored rx1217rp_v7.db Restored rx6022sas_v7.db Restored dx213_v7.db Restore successful. ``` 3. sudo ./syno_hdd_db.sh -nr --showedits > 1_log.txt output: ``` Backed up ds923+_host_v7.db Backed up ds923+_host_v7.db.new ST8000VN004-3CP101 already exists in ds923+_host_v7.db ST8000VN004-3CP101 already exists in ds923+_host_v7.db.new Backed up synoinfo.conf ``` log: ``` Synology_HDD_db v2.2.47 DS923+ DSM 7.2-64561 Using options: -nr --showedits HDD/SSD models found: 3 ST4000VN000-1H4168,SC44 ST8000VN004-2M2101,SC60 ST8000VN004-3CP101,SC60 M.2 drive models found: 1 CT1000P3PSSD8,P9CR40A No M.2 cards found No Expansion Units found Added ST4000VN000-1H4168 to ds923+_host_v7.db Added ST4000VN000-1H4168 to ds923+_host_v7.db.new Added ST8000VN004-2M2101 to ds923+_host_v7.db Added ST8000VN004-2M2101 to ds923+_host_v7.db.new Added CT1000P3PSSD8 to ds923+_host_v7.db Added CT1000P3PSSD8 to ds923+_host_v7.db.new Support disk compatibility already enabled. Disabled support memory compatibility. Max memory already set to 32 GB. M.2 volume support already enabled. Disabled drive db auto updates. "ST4000VN000-1H4168": { "SC44": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { "ST8000VN004-2M2101": { "SC60": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { "ST8000VN004-3CP101": { "SC60": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true, "smart_test_ignore": false, "smart_attr_ignore": false } ] "CT1000P3PSSD8": { "P9CR40A": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ```
kerem commented 2026-03-11 11:45:40 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (May 31, 2023):

I notice that the ST8000VN004-3CP101 which was already in the .db files contains 2 new lines that weren't in previous DSM version's db files:

            "smart_test_ignore": false,
            "smart_attr_ignore": false

I wonder if the other drives not having those 2 lines is a problem.

There is 1 change that --restore does not undo:
echo 1 > /run/synostorage/disks/nvme0n1/m2_pool_support

You could try the following:
sudo echo 0 > /run/synostorage/disks/nvme0n1/m2_pool_support

I've downloaded the DSM_DS923+_64561.pat file, unpacked it and attached the default synoinfo.conf and disk compatability db files for you - hoping they'll get your Synology working again.
synoinfo.zip
DiskCompatibilityDB.zip

<!-- gh-comment-id:1570010312 --> @007revad commented on GitHub (May 31, 2023): I notice that the ST8000VN004-3CP101 which was already in the .db files contains 2 new lines that weren't in previous DSM version's db files: ``` "smart_test_ignore": false, "smart_attr_ignore": false ``` I wonder if the other drives not having those 2 lines is a problem. There is 1 change that --restore does not undo: `echo 1 > /run/synostorage/disks/nvme0n1/m2_pool_support` You could try the following: `sudo echo 0 > /run/synostorage/disks/nvme0n1/m2_pool_support` I've downloaded the DSM_DS923+_64561.pat file, unpacked it and attached the default synoinfo.conf and disk compatability db files for you - hoping they'll get your Synology working again. [synoinfo.zip](https://github.com/007revad/Synology_HDD_db/files/11612409/synoinfo.zip) [DiskCompatibilityDB.zip](https://github.com/007revad/Synology_HDD_db/files/11612418/DiskCompatibilityDB.zip)
kerem commented 2026-03-11 11:45:45 +03:00
Author
Owner
Copy link

@fish-2023 commented on GitHub (May 31, 2023):

I'll be able to try the suggested steps in a few hours. In the meantime I'm backing up some important data just in case.
Thank you!

<!-- gh-comment-id:1570046806 --> @fish-2023 commented on GitHub (May 31, 2023): I'll be able to try the suggested steps in a few hours. In the meantime I'm backing up some important data just in case. Thank you!
kerem commented 2026-03-11 11:45:50 +03:00
Author
Owner
Copy link

@fish-2023 commented on GitHub (May 31, 2023):

Unfortunately, it didn't work.
I have first tried restoring the whole disk compatibility db, restarted, no change.
I have then copied the synoinfo.conf file, restarted, no change. In this case I see that a few "# Fixed items " sections have appeared at the end of the fine, not sure if it is relevant in any way.

I have then tried to echo 0 > /run/synostorage/disks/nvme0n1/m2_pool_support but I keep getting "Permission denied".

I guess the script didn't change any other files? If that's the case then I'll have to reset and reinstall DSM hoping I won't wipe the data (which seems to be an option).

<!-- gh-comment-id:1570315904 --> @fish-2023 commented on GitHub (May 31, 2023): Unfortunately, it didn't work. I have first tried restoring the whole disk compatibility db, restarted, no change. I have then copied the synoinfo.conf file, restarted, no change. In this case I see that a few "# Fixed items " sections have appeared at the end of the fine, not sure if it is relevant in any way. I have then tried to `echo 0 > /run/synostorage/disks/nvme0n1/m2_pool_support` but I keep getting "Permission denied". I guess the script didn't change any other files? If that's the case then I'll have to reset and reinstall DSM hoping I won't wipe the data (which seems to be an option).
kerem commented 2026-03-11 11:45:56 +03:00
Author
Owner
Copy link

@fish-2023 commented on GitHub (May 31, 2023):

Quick update, I have decided to reset the NAS and reinstall DSM.
I have backed up the settings locally (but they were backed up also on the cloud) and restored them right after the reset. Everything seems to be looking fine 🤞, and I didn't lose any data.

One thing I forgot to mention previously is that I was on 7.1 and I have [manually] updated to 7.2.
This time I have installed 7.2 directly.

Thanks for the support!

<!-- gh-comment-id:1570548362 --> @fish-2023 commented on GitHub (May 31, 2023): Quick update, I have decided to reset the NAS and reinstall DSM. I have backed up the settings locally (but they were backed up also on the cloud) and restored them right after the reset. Everything seems to be looking fine 🤞, and I didn't lose any data. One thing I forgot to mention previously is that I was on 7.1 and I have [manually] updated to 7.2. This time I have installed 7.2 directly. Thanks for the support!
kerem commented 2026-03-11 11:46:01 +03:00
Author
Owner
Copy link

@fish-2023 commented on GitHub (May 31, 2023):

OK, wrapping this up.
I guess I didn't really understand how the script[s] worked...
After the reset, I have run the Synology_HDD_db again, restarted and the ran Synology_M2_volume one.
I have now a working volume on the two m2 drives 🎉

I guess the first time I didn't understand what the 1st script was supposed to do and so I reverted the operation. The "restore" operation must have broken something, but I guess the script did what it was supposed to do...

Thanks again, I bought you a beer 😉

<!-- gh-comment-id:1570977598 --> @fish-2023 commented on GitHub (May 31, 2023): OK, wrapping this up. I guess I didn't really understand how the script[s] worked... After the reset, I have run the Synology_HDD_db again, restarted and the ran Synology_M2_volume one. I have now a working volume on the two m2 drives 🎉 I guess the first time I didn't understand what the 1st script was supposed to do and so I reverted the operation. The "restore" operation must have broken something, but I guess the script did what it was supposed to do... Thanks again, I bought you a beer 😉
kerem commented 2026-03-11 11:46:06 +03:00
Author
Owner
Copy link

@fish-2023 commented on GitHub (May 31, 2023):

The "restore" operation might have caused problems, but on a second run the script[s] worked without any problem.

<!-- gh-comment-id:1570979667 --> @fish-2023 commented on GitHub (May 31, 2023): The "restore" operation might have caused problems, but on a second run the script[s] worked without any problem.
kerem commented 2026-03-11 11:46:11 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jun 2, 2023):

The "restore" operation might have caused problem

Thank you for pointing that out.

I just tested the restore option on a DS720+ running 7.2 and it had the same issues as you. I found a couple of likely causes and edited them by hand. After that I rebooted and everything was back to normal.

I'll have an updated version of the script online soon (after some more testing).

<!-- gh-comment-id:1573212470 --> @007revad commented on GitHub (Jun 2, 2023): > The "restore" operation might have caused problem Thank you for pointing that out. I just tested the restore option on a DS720+ running 7.2 and it had the same issues as you. I found a couple of likely causes and edited them by hand. After that I rebooted and everything was back to normal. I'll have an updated version of the script online soon (after some more testing).
kerem commented 2026-03-11 11:46:16 +03:00
Author
Owner
Copy link

@fish-2023 commented on GitHub (Jun 2, 2023):

I'm happy to hear that reporting the issue is helping. Thanks again for the work you do

<!-- gh-comment-id:1573245832 --> @fish-2023 commented on GitHub (Jun 2, 2023): I'm happy to hear that reporting the issue is helping. Thanks again for the work you do
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
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#534
No description provided.