pervin_1

Thank you @Mainfrezzer

Thank you @Mainfrezzer. The upgrade to 6.12.6 went smooth, and the RAM-DISK is working perfectly. I appreciate the effort!

I went ahead and left the checksums from @Mainfrezzer's script unchanged. Its weird that I initially changed the checksums with my own, and the script aborted itself and threw the error code from @Mainfrezzer's original checksum codes, IDK why. Everything it seems to be working now. I still get about ~5Gb writen per day. But without the script, its about 32Gb daily. There are still uncessary writes, but I am very happy. My two cache drives are Pro 980 Samsung 1Tb models, and they are supposed to last about 600TBW. Which means about 300 years lol. Thank you! Thank you!

I am on the 12.4, and updated the compatibility code with my own checksums, and it got aborted upon the boot Error: RAM-Disk Mod found incompatible files: 45361157ef841f9a32a984b056da0564 /etc/rc.d/rc.docker 9f0269a6ca4cf551ef7125b85d7fd4e0 /usr/local/emhttp/plugins/dynamix/scripts/monitor

It’s the same version. I did run without the compatibility check, and everything is working from what I see. The RAM disk shows is created in the logs. But I am gonna update it and run again. I remember we used to change the settings for each docker and added additional parameters. It sounds like is no longer the case with the updated script?

Ran two md5sum checks on rc.docker and scripts monitor, the checksums are different. Which means I should change the compatibility code, correct? Thank you!

Wondering if anyone can help me with questions above? Thanks!

I am on 6.12.4, going to try this script. Was on 6.9.x and the old script worked great. With this new script, do I still need to edit the Paraments on my Dockers individually and extra line of code @mgutt @Mainfrezzer? BTW, how do you get the checksum for this script? I see two unique checksum codes. Thank you!

lol you were right about the PostgreSQL database. Messed up my OnlyOffice docker. Had to rebuild it, was not a big deal. Got it rebuilt even better. I was testing a lot of lately, to the point where I corrupted my Nextcloud MaridDb container and decided to get rid off my Nextcloud and related containers foor good. I wasn't utilizing it's features to justify the time and effort spent maintaining it. Besides, I heavily rely on Google Drive anyway ( I do back up my stuff from G Drive regardless ). Yes, I am also going to mount /tmp to the Ram Disk inside of the containers where is safe.. My understanding containers are not aware that /tmp is not real "Ram Disk". So the writes go to SSD instead. I appreciate the hard work and input! Thank you!

The scripts you shared are working perfectly. TBH, my writes ( I have been monitoring for a good time now ) are not excessive. The first script is barely showing any activiy for my containers. I see some repepetive logs for json files from /docker/containers. But I am assuming this is a RAMDISK for status and logs. Correct me if I am wrong, please. Another question, the appdata is located on my NVMe SSD cache pool. My understanding there will be some kind of writes from dockers regardless, correct? Besides that I left the script to dump the log/status files for safety reason every 30 minutes. BTW, I can see that my writes are basically coming from the OnlyOffice Document server docker ( and some from Nextcloud ). It's connected to my Nextcloud server as a document editor. I am not sure if you are familiar or using it. Edit: Nextcloud was in the tmp folder. Added extra parameter to mount the tmp folder in RAM disk ( not sure if you script handles the tmp in docker containers ). The OnlyOffice, mainly writes go to /run/postgresql every one minute or so. I am assuming is some kind of database system. Do you think it's a good idea to mount it to the RAM disk under the extra parameters?

@mgutt I went ahead and implemented the changes by following the instructions, all went smoothly so far. My cache drives are 2x NVMe A-Data SX8200. I did not change the docker log file size, it wasn't necessary. I double-checked to make sure that your script worked by checking the RAM-disk size and the code itself in different locations as you have explained, all good. I do see 0.00 B/s, but the writes jump up&down ( averages about 200 Kb./s ). Is it normal? Does it mean I have some other dockers in the appfolder writing something ( besides status and log files ) to my cash drives, like Nextcloud, Plex? Thank you!

Excellent and detailed guide, thank you very much! I pretty much completed the first two steps. But did not want to gamble with the third step since I do have sensitive data with the rest of the containers. Not that the 3rd step is hard to follow, but as you mentioned, you don't want to implement these steps with sensitive information like database, Nextcloud and etc. My basic calculation show that my two NVME Adata drives had in average 180-192GB of random writes daily staring from 2018-2019. Glad randomly decided to read this topic delivered to my email box lol. Noneless, always make sure to have a backup. I made some mistakes, experienced some problems with my appdata folder with the "mover" function. Made a few important dockers unusable. Restored the dockers from the backup, boom - ready to Rock & Roll! Again, I appreciate the effort and all time taken to write this guide! You are awesome!

No solution tbh. I am stuck perhaps. We are going to figure this out, eventually. Let me know if you come up with any news or a solution. Would appreciate it!

I also received this message the first time when I tried to TRIM the NVMe drive ( ADATA SX8200 480GB, relatively new SSD) connected directly to the MOBO's M.2 port — using as a cache drive. I upgraded to the latest 6.7 Stable a few days ago, never seen this message before. Diagnostics attached. Thank you! tower-diagnostics-20190609-2320.zip

Anybody have any idea why DuckDNS docker works 99% of times, it always succeeds updating my IP address, but when my internet goes down ( IP change overnight ), it fails to update my address with the usual message something went wrong please check your settings. The only to fix it is to restart the docker; then it works again. I would appreciate any help. Thank you in advance!