July 21, 201510 yr Good day Crew, Both of my servers (Tower1/Tower2) are on 6.0.1. Both Have the Folder Caching Plugin installed/enabled. Tower2 is a Mirror of Tower1. Tower1 requires the Disks to spin-up to browse/access any directory while Tower2 does not. The Dynamix Cache Settings between both systems are identical (and I use the stock Go file on both). Tower2 shows Cache as Running while Tower1 shows it as stopped. How do I get Cache Dir working on Tower1? Tower1: Supermicro - X7SPA-HF with 4 GB ram installed. D525. 5 4 TB Seagate drives (1 cache) Tower2: P8H77-V LE with 16 GB ram installed. i5-2500. 5 4 TB HGST drives (1 cache)
July 21, 201510 yr What happens when you enable it? Stop the array and restart it, and check it again. CacheDirs only starts when the array starts. Note to bonienl: might need a note indicating the above, that after applying changes, the array needs to be restarted if already running.
July 21, 201510 yr Author I actually thought this was the issue, so I shutdown and powered on the Tower. Once up, I manually started the array (as it the norm on this setup). I will try stopping/starting the array manually tonight and see what happens.
July 21, 201510 yr Author stopped and started array. No joy: cache_dir still shows as stopped. What can I share to help get this working? FYI it DID work in v5 on the same hardware/array (traditional install)
July 21, 201510 yr stopped and started array. No joy: cache_dir still shows as stopped. What can I share to help get this working? FYI it DID work in v5 on the same hardware/array (traditional install) Just a thought you are using the V6 version not the V5? It's easy to mix them up (I know I have)
July 22, 201510 yr Author @CHBMB - Yup, confirmed file size/attirbutes/version number between both machines - info is the same. Removed the plugin and reinstalled via https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.cache.dirs.plg as listed http://lime-technology.com/forum/index.php?topic=36543.0 (Dynamix - V6 Plugins under development). Now appears to be working. SOLUTION: REMOVED PLUGIN from Plugin Page. REINSTALL Via Plugin Link
Archived
This topic is now archived and is closed to further replies.