(2021-11-13, 17:13)dpar Wrote: Just to throw it out there, I'm running DSM 7 on my DS1819+ using MariaDB 10, and don't have any issues whatsoever. I've been running it this way since DSM 7 came out. I'm also using SMB. So I would assume you had some type of issue with the DSM upgrade initially?

Certainly no issues with the DSM 7/MariaDB/SMB combination in general. In fact if anything I would say performance seems better in DSM 7 vs DSM 6.

(2021-11-13, 23:07)gibxxi Wrote:

(2021-11-12, 20:38)davesdeadcat Wrote: Just to close the loop on this issue, I've now successfully rolled back my Synology to DSM6 using this excellent guide :
https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/

After following Dan's tips on tweaking MariaDB (thanks again Dan) I now have a fully working and much snappier KODI setup. Queries and traversals between TV shows etc are much much quicker than before all this started so I'm happy now, although somewhat disappointed I couldn't get to the root of the problem. All KODI clients now running 19.3 and working fine so KODI itself doesn't seem to be the issue.

Only concern is that DSM6 is likely to go out of support some time in the next year or so and upgrading back to DSM7 is now something I'm going to avoid for as long as possible. 

Thanks for all the comments & suggestions.

Great to hear that your up and running again @davesdeadcat . I would advise you to keep an eye on your OS partition utilization going forwards, and keep Kodi database versions you keep on the MariaDB server to a maximum of 2 (One active, one old version).

You won't gain much by emptying the /TMP/ folder for example, as this is nailed-on to be a RAMdisk and will be cleared at reboot anyway. But do check the thing and make sure you've not been infected with some kind of malware, and that the add-ons you are running were installed by your good self, and are not causing issues in and of themselves. QNAP had a major security issue with ransomware a while back and a lot of people were affected. Thankfully I wasn't one of them, but proof if any were needed, that essentially, these NAS boxes are just 'computers' with a singular purpose (in the main), and can be compromised just as easily.

These NAS devices all run the same tricks to get to an end result. There maybe subtle differences between manufacturers in terms of the overall file system layout, but I know (having owned models by Netgear, Asustor and now QNAP) that none of these companies are going to go and re-invent the wheel. The 'innovation', if you can call it that, is leveraged elsewhere. So they all have the same advantages and pitfalls to a degree.

It's quite possible, that in Dave's case there wasn't enough remaining room on the OS partition to extract / process the firmware update properly for example, given the number of old databases he had on there. Remember, the amount of global space you have in terms of HDDs is irrelevant. The OS partition(s) will be of a set, limited size, and if filled will result in problems. It all appears via SSH as a single folder tree, but that's just massive amounts of symbolic linking hiding the true nature and layout of the partitions / volumes / drives from the end user, and to make things easier for the host OS to manage.

Dan / Gib.

• Created a new Static IP address on the NAS
  
• Created an identical folder structure as that of the DS412+ and copied all of my data onto DS1621+
  
• Installed and configured MariaDB 10.3.29 <Port 3307>, created a New User XBMC10 / password (containing: UPPERCASE, lowercase, number and special character), created 2 new Databases MyMusic82 & MyVideos119 and provided ALL privileges to New User XBMC10
  
• Modified the Advancedsettings.XML appropriately and copied them into the relevant Userdata folders of both Android Media boxes (kept a backup of both of the original ones)
  

(2021-12-27, 17:37)ARAM10 Wrote: I have now given up on sharing the library and each device runs perfectly independently.
I wonder if the next release of DSM 7.1 will indeed address / fix this issue.

(2021-12-27, 17:37)ARAM10 Wrote: I have now given up on sharing the library and each device runs perfectly independently.

I wonder if the next release of DSM 7.1 will indeed address / fix this issue.

(2023-12-25, 04:23)lessHairwithCodi Wrote: my.cnf

(2024-01-07, 15:55)ARAM10 Wrote:

(2023-12-25, 04:23)lessHairwithCodi Wrote: my.cnf

Hi, many thanks for your reply.

However, please excuse my ignorance. Where do I find "my.cnf" ?

(2024-05-18, 12:34)ARAM10 Wrote: Many thanks to everyone.

I have now resolved this issue by carrying out a full and complete reinstallation on all my devices and updated to Kodi 21.

I have fully documented all the steps (long document) if anyone is interested, I am happy to share it