a12vman

Members
  • Posts

    85
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

a12vman's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. Never thought about a reboot even though I stopped/started the array- you were right on with that suggestion. Cache disappeared and now I have cache_ssd and cache_nvme as the 2 cache pools. I updated my Krusader config to add paths for cache_nvme and cache_ssd. I updated appdata,domains,and system shares. First set cache to yes to move everything off cache into the array. After mover finished I then update these 3 shares to prefer and set the pool to cache_nvme. After the mover finished I set the cache for all remaining shares to cache_ssd. I stopped Docker. Copied docker.img to cache_nvme, updated docker config to point at cache_nvme for Docker.img. I change the Docker appdata location from /mnt/user/appdata/ to /mnt/cache_nvme/appdata/. I restarted Docker Engine, everything seems fine. Plex is a bit faster than it was before. My issue is that I am seeing a split of appdata for all of my dockers. There is a small(in size) amount of appdata remaining in the old appdata location on cache_ssd(734MB). Appdata on cache_nvme is 43GB. See my Screenshot below of Sonarr and Plex AppData. Why do I have split content and what can I do about it?
  2. I need assistance. I am trying to add a 2nd cache drive(1TB NVME). At present I have a 240gb ssd as my only cache. I renamed my existing cache drive to cache_ssd. I stopped the array added the nvme, formatted it as BTRFS and named it is cache_nvme. Created a 2nd pool and added cache_nvme to this pool. Started the array. Modified cache settings on shares. I set appdata, system and domains to use Prefer: cache_nvme I set all other shares to use cache_ssd. My existing appdata is ~ 45gb I back it up daily to another server. When I open Krusader and look at \Cache it is only showing 46.1 MB. Something is not right. All my dockers are still working fine(like Plex). When I go into Krusader settings under the cache variable(Host Path) and browse /mnt/ I see folders for Cache, Cache_ssd, and Cache_nvme I reviewed SI-1's video on cache pools and how to create them. Clearly I missed a step here. How do I move all references from /Cache as far as AppData goes? This makes me extremely nervous.... My end goal is to have all appdata and system on cache_nvme and the rest of shares caching to cache_ssd.
  3. How much reading/writing takes place against Docker.img? Is it just during the start of the Docker or is it continuous?
  4. I am putting this into General as I can't find a better place for it. SI-1 has posted a how-to guide on tuning Unraid that is very useful. I would like to focus on how to get the best performance from disk as it relates to Dockers and VM's. I currently have my Cache, Appdata, and VM's on a single Crucial 240gb SSD. I have appdata of 40GB and VM's of ~60GB. I would have 1 or 2 VM's running at any given time. Docker.img resides on a 120GB SSD(unassigned device). I have ~ 20TB used inside of a 30TB Array(single parity). Sonarr & Radar Downloads first land in a 4TB Mechanical Drive(unassigned device). Once assembled they are moved to cache and eventually the mover process will commit them to the array. I have 2 Xeon x5675's with 64GB Ram. I was thinking of moving AppData off of Cache to an NVME SSD(as unassigned device) in hopes to gain some performance in Plex. What are best practices of AppData, VM's, and Docker.img locations? Will I see performance improvements if I get these off of Cache and onto separate physical devices?
  5. I didn't re-boot the server but I did remove and re-install this plugin. I am not seeing the errors anymore in the system log. Not sure what that was all about. if it pops up again I will come back with the diagnostics. Thank you.
  6. My Version is 2021.10.10 I went into the parity tuning config. Changed my interval from Monthly to Yearly and clicked apply. The I changed it from Yearly to Monthly and clicked apply. I am still getting these messages in my SysLog: Nov 18 05:48:11 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 18 05:48:11 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 18 05:49:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 18 05:49:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 18 05:56:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 18 05:56:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null
  7. I am seeing this over and over in my system log. How do I resolve? Nov 17 14:57:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 17 14:57:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 17 15:12:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 17 15:12:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 17 15:27:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 17 15:27:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null
  8. Ok I am waiving the white flag. I just stopped the array and did a full reboot, log entries are not coming back. Not sure what that was all about. It had been a long time since I did a re-boot.
  9. mediatower-diagnostics-20211111-1558.zip
  10. Why is my Log in Memory Filling up?
  11. I did that but these entries are still going into SysLog. Where is this coming from? Syslog Server is disabled but I am still writing the File to Flash.... Nov 11 15:50:11 MediaTower rsyslogd: file '/var/log/syslog'[5] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: file '/var/log/syslog'[5] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: file '/var/log/syslog'[5] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: file '/var/log/syslog'[5] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 15:50:11 MediaTower rsyslogd: file '/var/log/syslog'[5] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ]
  12. Can anyone tell me where this is coming from? I already rebooted the server yet it continues to log. This stareted last night when I was preclearing a new drive over USB. I cancelled the preclear as it was painfullly slow yet the messages keep coming. Nov 11 11:14:27 MediaTower file.activity: Starting File Activity Nov 11 11:14:27 MediaTower emhttpd: Starting File Activity... Nov 11 11:14:27 MediaTower rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="29640" x-info="https://www.rsyslog.com"] start Nov 11 11:14:27 MediaTower rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 11:14:27 MediaTower rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 11:14:27 MediaTower rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 11:14:27 MediaTower rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 11:14:27 MediaTower rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Nov 11 11:14:27 MediaTower rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] mediatower-diagnostics-20211111-1128.zip
  13. Ok thanks. I am also using CA Backup/Restore but it stopped working and I haven't figured out why. I wish there was a way to backup dockers without stopping the Docker Engine. /usr/bin/tar: Error is not recoverable: exiting now Starting binhex-delugevpn Starting binhex-krusader Starting binhex-plexpass Starting binhex-sabnzbd Starting binhex-sonarr Starting duplicacy Starting firefox Backup/Restore Complete. tar Return Value: Backup / Restore Completed
  14. Ok the Duplicacy data you are referring to, is it located at \Cache\Appdata\Duplicacy\Cache\Localhost\? Are you suggesting that in event of an Appdata corruption that my Duplicacy functionality would work if I: 1. Re-install duplicacy Docker. 2. Restore Backup DB to Appdata\Duplicacy\Cache\Localhost