• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About d.ohlin

  • Rank

Recent Profile Visitors

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

  1. Just came here to say thank you so much for this. I was seeing this exact same issue recently, only to the tune of 4-600Mbps crushing my bandwidth. Sure enough this fixed it. Thank you!
  2. Another +1 I'd love to see this. Especially in light of the new easy remote access setup this would be slick!
  3. Twitter handle @DavidOhlin, followed Unraid there! Thanks for doing this!!
  4. For what it's worth, here is the version of the script that @zandrsn mentioned that I heavily modified for use with Nut...this is working to pull what I wanted to pull from my USB-connected Liebert GXT3 UPS. Also I'm terrible with this kind of stuff, so this took me several hours last night and there's probably stuff that could be improved LOL but if anyone else can get use out of it then I figure I might as well post it here to share! #!/usr/bin/php <?php $command = "upsc"; $args = "ups"; $tagsArray = array( "battery.charge", "device.model", "ups.status" ); //do system call
  5. Just figured I'd come back to give an update on this as so often people don't post any confirmation of whether their solutions ended up working It would appear that I'm good to go (knock on wood!) as I'm at ~50 hours of uptime so far with no issues, and I just now confirmed again that I can run a scrub on the cache drive without triggering any log errors. Thanks again for all the help!
  6. Hmmmm...alright I'm officially perplexed. In case anyone happens to find themselves running into anything similar, here's exactly the steps I took. So I wasn't completely sure on the best way to format the cache drive (in my case, drives - 2), so I did the following: 1. Stopped the array 2. Unassigned both cache devices 3. Re-assigned the cache devices as add'l. members of the main storage pool 4. Re-started the array (which obviously began clearing these 2 news disks) 5. Cancelling the clearing operation (pretty much immediately) and re-stopped the
  7. @johnnie.black Sorry...noob question time How do I do a manual scrub on those 3 filesystems? EDIT: I found the scrub option under the main cache drive (I have 2) and clicked that...still unsure on the docker and libvirt ones though. EDIT2: The cache scrub above completed with the following: scrub status for f36f83a5-045e-43f6-a2a5-74bde4367eaa scrub started at Mon Oct 30 11:11:08 2017 and finished after 00:00:24 total bytes scrubbed: 6.01GiB with 0 errors However, running the above definitely causes the system to produce call
  8. @johnnie.black My fault...that was dumb of me that makes total sense now that I think about it. I'm hoping it's not a corrupt docker image in this case as I don't run as docker images on my server but what do I know haha Attached is the full .zip diagnostics file, hopefully that's got everything needed. Let me know if I can do anything else. Thanks!
  9. Hey guys...woke up this morning to a new one My fix common problems plugin told me that call traces were found on my server...looking into the diagnostic log it appears the below section is the relevant part. There's more than this but it appears to just endlessly repeat these same basic issues. Can anyone smarter than me tell me what these mean or what is most likely going on, and if there's anything I can do to fix it? I know I don't have the newest hardware, but I haven't had these issues ever before and Unraid has always been super stable in the past. Thank you!!