Jump to content

Synology DSM 7 drive lock bypass

Peppershade
 Share

Hallo
 

Welchen Dienst muss ich neu starten, damit ich nicht die gesamte Diskstation neu starten muss?

Ich möchte dies mit einem Skript automatisieren.

Sie können das Update in der GUI durchführen. Man müsste nur herausfinden, welcher Befehl ausgeführt wird. Unter Speicher-Manager -> HDD/SSD -> Einstellungen unten Laufwerksdatenbank aktualisieren.

Wenn ich die Schaltfläche verwende, wird die Datei mit dem Original überschrieben.

"disk_compatbility_info":{"MG08ACA16TE":{"0102":{compatibility_interval":[{"compatibility":"support"}]},"default":{"compatibility_interval":[{"compatibility":"support"}]}},"nas_model":"ds3622xs+"}
 

Link to comment
Share on other sites

Link to post
Share on other sites

  • 2 weeks later...

Hello!

I could use some help with editing the files for my 2421+.  I'm not a Linux guy and would love some guidance!  TIA!

Link to comment
Share on other sites

Link to post
Share on other sites

  • 3 weeks later...

Does anybody know which database file is used on Synology NAS so that newer Seagate IronWolf disks are recognized in the section IronWolf Health in Health Info on the Storage Manager? So I can add a newer IronWolf disk to it.

 

For example Seagate IronWolf 10TB ST10000VN0008-2JJ101 is recognized there, but the newer version ST10000VN0008-2PJ103 is not.

 

image.png.336457d96f3b01470632ed89d84a1245.png

Link to comment
Share on other sites

Link to post
Share on other sites

  • 3 weeks later...

I have been using NETGEAR Readynas Boxes in my home office for many years.
Was looking for another RN628x Box as a Backup System - to find out that NETGEAR
is out of this business - all NAS systems are EOL (end of life) 😞
Like other members of this forum, I have dozens of Enterprise Class Disks which I intended
to use in a SYNOLOGY RS4021xs (diskless).
I am not willing to throw away all the good disks and will use the "config file hacks" discussed here.
(I found hints in other forums but the only info was  "a hack in DSM is needed")

Thanks to Peppershade who provided *real* help here!

Link to comment
Share on other sites

Link to post
Share on other sites

Found an easier way to do this thanks to this comment here - 

Edit the file:

/etc.defaults/synoinfo.conf

Then find the option support_disk_compatibility and change it from yes to no

support_disk_compatibility="no"

Then reboot.

 

Side note: If anyone else is using this to make the E10M20-T1 work with unverified SSDs I find I often have to cold boot the NAS (RS2421+) to get the SSDs cache to show up.

 

Link to comment
Share on other sites

Link to post
Share on other sites

Thank you for this find. Lets see if this survives an update.

But even if not, this change is less of a hassle!

Link to comment
Share on other sites

Link to post
Share on other sites

  • 4 months later...

Hi guys, I wrote a little python script to adjust the drive compatibility list by a scheduled task.

Feedback is highly appreciated.

 

#!/usr/bin/env python
# -*- coding: utf-8 -*-

"""
    Python script to add unsupported drives to the synology compatibility lists
    (c) 2022 Kevin Schmitt
"""

import json
import os

# Add your desired models with firmware here
models = {
    'ST16000NM001G-2KK103': ['SN03'],
    'CT2000MX500SSD1': ['M3CR045']
}

compatibilityDirectory = '/var/lib/disk-compatibility/'
#compatibilityDirectory = '/var/services/homes/mdadmin/disk-compatibility/'


for file in os.listdir(os.fsencode(compatibilityDirectory)):
    filename = os.fsdecode(file)
    if filename.endswith(".db") or filename.endswith(".db.new"): 
        compatibilityFileName = os.path.join(compatibilityDirectory, filename)

        fileHandle = open(compatibilityFileName)
        jsonObject = json.load(fileHandle)
        fileHandle.close()
        
        if not 'disk_compatbility_info' in jsonObject:
            continue
        
        print('Found compatbility file: ' + compatibilityFileName)
        compatibilityList = jsonObject['disk_compatbility_info']

        for model in models:
            print('Checking model presence: ' + model)
            if not model in compatibilityList:
                print('Model is not on the compatibility list, we add it now.')
                compatibilityList[model] = {
                  "default":{
                     "compatibility_interval":[
                        {
                           "compatibility":"support"
                        }
                     ]
                  }
               }
               
            for firmware in models[model]:
                print('Checking firmware presence: ' + firmware)
                if not firmware in compatibilityList[model]:
                    print('Firmware is not on the compatibility list, we add it now.')
                    compatibilityList[model][firmware] = {
                        "compatibility_interval": [
                            {
                               "compatibility":"support"
                            }
                        ]
                    }
                    
        with open(compatibilityFileName, 'w') as outfile:
            json.dump(jsonObject, outfile)

 

Link to comment
Share on other sites

Link to post
Share on other sites

  • 2 weeks later...

To make DSM recognize the changed DB without reboot:

 

/usr/syno/sbin/synostgdisk --check-all-disks-compatibility

 

@kevinschmitt maybe you can add it to your script, this would make it work without reboot

Link to comment
Share on other sites

Link to post
Share on other sites

  • 2 weeks later...
On 8/3/2022 at 1:25 AM, Neonkoala said:

Found an easier way to do this thanks to this comment here - 

Edit the file:

/etc.defaults/synoinfo.conf

Then find the option support_disk_compatibility and change it from yes to no

support_disk_compatibility="no"

Then reboot.

 

Side note: If anyone else is using this to make the E10M20-T1 work with unverified SSDs I find I often have to cold boot the NAS (RS2421+) to get the SSDs cache to show up.

 

This solution worked for me on the DS3622xs+ main unit but not on its DX1222 extension. Have any of you found a solution for the error that remains on the expansion units? thank you all

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×