-
Notifications
You must be signed in to change notification settings - Fork 5
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
looks like they are screwing with the logic somehow. #2
Comments
Hi. Thank you that it worked so far. And it's sad that it won't anymore. |
Have you tried to edit the rule.db files?
It does not appear to exist anymore. The only hope I have is they say DSM 7,1 will have relaxed rules. I'm sure there has been a shit storm over this BS.
On Monday, April 18, 2022, 04:44:34 AM MST, Livedeath2k ***@***.***> wrote:
Hi. Thank you that it worked so far. And it's sad that it won't anymore.
Have you tried to edit the rule.db files? I think if you edit the rule db files as i did and posted it in my repository the DSM won't give a f... about the compatibity database and will work with any drive you put into your NAS.
Best Regards,
Lars
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Tried this on my home use non commercial ds416play, with DSM 7.1-42661 Update 2. |
So used your hack and it worked great for probably 4 months. They pushed a hard drive database on me.
I have 3 drives that are not "compatible". 1 drive in particular is not recognized even after adding it. Have tried multiple ways and something is wrong. The current drives I was using is:
"ST10000VN0004-1ZD101":{"SC60"
"ST12000VN0007-2GS116":{"SC60"
"ST16000NM001G-2KK103":{"SC60"
The 12 and 16tb drives are good. But something about the 10tb drive will not pass. I will have my programmer son look at it, to see if he can figure out if I did something wrong. I'll let you now if I did, but I suspect they are trying to crack down. I heard from a Synology tech, they are going to relax the rigid requirements since I guess it has been a disaster and didn't solve anything.
The text was updated successfully, but these errors were encountered: