Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About master.h

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Clearly I didn't follow step 1 of troubleshooting: search the forums. Thanks for the link @wgstarks. From that link, it doesn't sound like that was the cause of the reboot, just an outdated plugin. I couldn't see anything in the logs that looked like a cause, so I'm assuming something funky with the wiring at my buddy's house.
  2. I manage an unraid server for a friend of mine, recently rebuilt from scratch on some new-to-him hardware. Everything's been fine for a few weeks, but overnight had an unexpected reboot. I got a notification the server started an unscheduled parity check approximately 1:30am CST, and when I checked on it around 6am, it had only been up for something like 5.5 hours. So it definitely rebooted. Normally I'd just attribute it to a small power blip, as he doesn't run it on a battery backup (his whole house is on a backup generator in the event of a true power outage) but I saw several errors in the syslog for "missing csrf_token." Never seen that error before, no idea what it means. I've attached diagnostics, and would appreciate any advice. Thanks! boughserver-diagnostics-20190813-1454.zip
  3. I installed the plugin Community Applications on my server. It will add an "apps" tab to your main Unraid webpage. It's sort of like the iOS app store, or Google Play app store. Search/browse for the docker/plugin you want, and it automatically installs from there. You can download the plugin here: https://forums.unraid.net/topic/38582-plug-in-community-applications/ That's how I install all my dockers. I don't know how to add repos in manually.
  4. I can't remember off the top of my head how to clear logs, I think you can force an update on the docker and it'll wipe all the logs. To prevent it you can add this to the "extra parameters" field week you're editing the docker with the advanced settings button turned on. It will limit your max log size to 50 megabytes --log-opt max-size=50m
  5. It's been a bit since I've installed the docker, but it looks from your screenshot that you're missing some configuration options. Here's what mine looks like. "Host Path 2" is what shares I'm syncing. In my case I passed through /mnt because I'm syncing disk-to-disk between two Unraid systems. EDIT: I see you're actually using the Resilio from the limetech repository, I'm using Linuxserver's repo. Not sure what settings to use or not use on the Limetech version.
  6. Very cool, thanks for reviewing, Squid.
  7. Server has been running latest 6.7.0 since it was officially released, no problems at all. Earlier this morning my system rebooted itself, and I'm not 100% sure why. I was running a movie through Handbrake, which I'm guessing is the culprit, but not sure. Fix Common Problems suggested pulling diags and posting here because of the "Machine Check Events" message. It also said I should install mcelog, which I have done, but I don't know how to pull logs from it, or if I even need to. Diags attached, any advice is appreciated. saidin-diagnostics-20190514-1427.zip
  8. I copied out the resilio log from the link on the unraid docker page, hopefully that's enough to go on. For what it's worth, resilio still is able to copy files from my local system to the destination system, all the while endlessly indexing disk1. resilio_log.txt
  9. I've been using Resilio-sync successfully for quite some time now, but recently it seems to have gotten stuck "indexing" one of my read only shares, which in this case, is /mnt/disk1. Indexing ran constantly overnight, I woke up to over 44 million reads on disk1 at the main unraid management page. I know I can view the logs for resilio on the docker page, but how do I grab those out short of a copy/paste of the log window?
  10. Thanks for the quick response. This motherboard is fairly old, I want to say the last BIOS update was back in 2011... maybe earlier... so I'll disregard that. I'll check on disk6 extended smart test as well and replace if needed.
  11. Fix Common Problems notified me of some call traces that were found on my server; not sure what this means or what I need to do to fix it. I've attached diagnostics from my server for review. I'm also getting warnings about disk6: "offline uncorrectable" and "current pending sector" is 168. I'm assuming this means I have a failing disk; I've attached the smart report for that disk as well. saidar-diagnostics-20171215-0952.zip saidar-smart-20171215-0956.zip
  12. I actually do this very thing myself. For a long time I had both my main and backup server in the same house (literally a foot away from each other) so a simple rsync worked just fine. However now that I've moved my backup server to an offsite location, I use a docker called Resilio. Resilio on the primary server indexes whatever folders I choose to pass through and copies them to my backup server's instance of Resilio, again to whatever folders I choose. It took a bit to set up, and the initial index takes a while (especially if you have tons of file, pictures for example) but now that it's set up it works really well.
  13. I upgraded two systems this morning. My second system was running a VM, Plex, and Reslio-sync. I failed to realize that was about 98% RAM utilization, so when unraid attempted to extract the update after downloading, my system ran out of memory and crashed. Had to hard reboot. Second try I stopped the dockers ahead of time, then all went well. Maybe an FYI for those with smaller amounts of RAM installed.
  14. I understand what you're saying with /sync, /Sync, or sync all being different paths. I'm not sure that is pertinent to this particular situation, though. When you open the webui, there's basically a button for "choose a folder to sync" and then once you navigate to the internal /sync path, all your user shares are presented, and you select Audio (for example) and click OK. An indexer starts running and you moved on to the next one. I don't mean to derail this thread into some sort of resilio troubleshooting thread, there's already one of those. i can post in there for more details/troubleshooting help. Is there a command or set of commands I can use to determine file size of a given docker? Like "du -h /mnt/user/Audio" would give me total size of the Audio user share; is there something like that I could use to find the total size of a docker? I figure if there is something like that, I could get total size of all dockers, wait an hour and run again, then compare results to see which (if any) dockers are growing.
  15. The Docker FAQ was actually my first stop. The FAQ link that seemed to apply to me was "Why does my docker.img file keep filling up still, when I've got everything configured correctly?" That link said you could force dockers to have a max size on log files by adding an Extra Parameter in each of your dockers. I double and triple checked (again just now TeamViewered in to my system, as I'm not at home atm) and none of my dockers were configured to save anything internally. Every host path field in all my dockers was pointed to something on the cache drive. However, I found the offending docker (resilio-sync), but don't know why it was filling docker.img. I wasn't actively using that docker yet, just had the sync folders set up and indexed, so I went ahead and deleted it. Immediately docker.img dropped down to 14GB used instead of like 38GB or whatever it was. So.... why? There's a setting in there for the folder you want to sync, so I passed through /mnt/user (which is mapped internally to /sync) so I could create sync groups for each of my user shares. I mean I guess it filled up because there's a ton of stuff I was trying to sync, but how do I avoid that in the future? I know there's the option to specify internal paths to map to external paths (to the cache drive for instance) but I have no idea where inside the docker Resilio was storing this sync information. Did I configure something wrong?