Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


jbartlett last won the day on April 2

jbartlett had the most liked content!

Community Reputation

88 Good


About jbartlett

  • Rank
    John Bartlett
  • Birthday 07/20/1970


  • Gender
  • URL
  • Location
    Seattle, WA
  • Personal Text
    Foster parent for cats & kittens

Recent Profile Visitors

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

  1. I've trapped the error being returned by lsusb but working on polishing up a few things. Then I'll be pushing a release to take it out of beta.
  2. jbartlett

    Dynamix - V6 Plugins

    I manually ran the sensors-detect packed with the Plugin, no errors, no crashes. No sensors either but that's not it's fault. "sensors -A" invoked by the Plugin does return values. Here's the -u output k10temp-pci-00c3 Adapter: PCI adapter Tdie: temp1_input: 27.750 temp1_max: 70.000 Tctl: temp2_input: 54.750 k10temp-pci-00cb Adapter: PCI adapter Tdie: temp1_input: 27.500 temp1_max: 70.000 Tctl: temp2_input: 54.500
  3. jbartlett

    Dynamix - V6 Plugins

    No kaboom.
  4. jbartlett

    Dynamix - V6 Plugins

    I made a backup of my Flash, I'll risk it to test that Perl theory.....
  5. jbartlett

    Dynamix - V6 Plugins

    Forgot that Nerd Pack now has optional stuff that you have to enable manually in it's settings. Enabled Perl via that method. Went through the same process again with uninstalling the System Temp plugin. No crash but no sensors either. The perl install I found was 5.22 and Nerd Pack has 5.26, I wouldn't think that would have been the root cause since it's fairly close in version.
  6. jbartlett

    Dynamix - V6 Plugins

    Typo on Docker/Plugin PLG. I meant Plugin PLG files of course. I'll edit the post to correct that. I had Nerd Pack installed. All plugins were up to date.
  7. jbartlett

    Dynamix - V6 Plugins

    Just had a nasty issue with the System Temps plugin that trashed every plugin except the Community Applications (very fortunate). I just replaced my Threadripper CPU cooler so I was curious about system temps running under Unraid. I saw that I had the System Temps plugin installed so I went to it in the settings but it was disabled saying that Perl needed to be installed. I couldn't find Perl in the CA or a link to it in the first post other than it was needed so I went out and got it from https://slackware.pkgs.org/14.2/slackware-x86_64/perl-5.22.2-x86_64-1.txz.html I went back to System Temps and saw that the Detect button was now enabled. Clicking it immediately refreshed the page with nothing apparently happening. Thinking it needed a full refresh, I uninstalled & reinstalled the plugin from CA. I clicked the Detect button and the server hard crashed. No dump log on the console, no blinking cursor. I hit the reset button and when the system came back up, all the PLG files I had installed (15 in all) ended up in plugin-errors as zero byte files. 17 new FSCK00??.REC files in the root directory. I manually reinstalled 14 of the plugins (couldn't find one) and rebooted for posterity. Everything seems to be OK now. Diagnostic file after the first reboot and before I did anything attached. One thing I thought was odd was that when I reinstalled the System Temps plugin, it reported that it updated the support link for it and many other plugins. nas-diagnostics-20181005-1029.zip
  8. Haha! Yup! Though you can click on the drive labels for the SSD's to hide them so the spinners don't look so pathetic in comparison.
  9. That's a good image. I'll save it to add but you can also add & submit images too 👍 If you haven't already done so and you'd like to check out the feature, view the drive with the image you want to update and click on "Edit Drive", then "Upload New Image". Follow the instructions and you're good to go. Since the capacity is on the image, you don't have to worry about the text overlay to add it.
  10. When trying to start a Win10 VM, I was getting the following error. Editing the VM did not present the device in question. Saving and relaunching did not remove the orphan item and the error persisted. I had to manually remove the following block from the XML in order to launch the VM. If it is not supposed to remove the orphan USB device, I recommend listing items in the XML but not attached to allow them to remain or be removed in the form editor. nas-diagnostics-20180929-2210.zip
  11. jbartlett

    6.6.0 Bug M.2 NVME Issues

    I've got two unraid systems, both with two M.2 NVMe drives as well, VM's running of them and no issues so far. It wasn't quite clear but are the two m.2 drives the same model? If so, check out my DiskSpeed docker app and run a bench mark on both system (assuming you can access both currently) to see if they have similar speed graphs. Just because there's no flags being raised doesn't mean there aren't any.
  12. jbartlett

    6.6.0 Bug M.2 NVME Issues

    Do you think that the m.2 drive failed and it's killing your system? A more descriptive title would be helpful.
  13. jbartlett

    [6.6.0] Docker CPU Usage graphical error

    Originally reported under RC1, linked here for it's information
  14. It looks like this might be the source repo. But due to it's age, it might be a clone. https://github.com/zerovm/glibc/blob/master/iconv/gconv.c
  15. Thanks for your help. I won't be able to fix this error but I can trap it.