Espressomatic

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by Espressomatic

  1. Been running this plugin successfully on my Super Micro X9DRI-LN4F+ for a couple of years but just noticed today that it's not working. No status displays, no content on the readings tab. I don't know when it stopped working, but it couldn't have been that long ago as the slightly louder and faster fan speed just stuck out audibly to me today. Log output after restarting system: I've previously noticed an issue where the plugin doesn't seem to function when the system comes up from a power failure. We did just have such a power failure a few days ago, but I've since powered down the server, unplugged the power supply and then brought it back up. No sensors seem to come up in the IPMI plugin settings anymore. In Display Settings, both Global and Dashboard have only "Select all" with no sensors listed and the only choice in the pop-up menu for footer display is "none" - I'd previously had multiple items selected for footer display, including temps and fan speeds.
  2. Settings are sticking after I edited manually, thanks again. I was only updating the thread to mention that 6.9.2, which was supposed to fix the issue of web UI settings not saving, didn't appear to fix this for me, and I described exactly what's happening to the contents of the file.
  3. Maybe I wasn't clear. I have 2 cache drives. If I change the SMART monitoring on one of them, that gets written to the configuration file. If I go and change the settings on the second drive, the configuration file is not appended to, it is overwritten with only the settings for this new drive. Using the web UI, it's not currently possible to get configuration data into that file for more than a single drive - on my system. Because of this, the system will continue to complain about pending sectors. Only manually editing the configuration to include both drives prevents the errors.
  4. Doesn't work. Because every time you touch a particular disk's settings, it wipes the file out and writes only the settings for that ONE disk.
  5. Unfortunately, still happening with 6.9.2. What's happening is that any time a disk's settings are changed in the UI, the config file is overwritten with only the settings for that single disk. Editing manually as you suggested should work - until you do anything in the UI elsewhere to overwrite it.
  6. All hibernate/sleep options are turned off, performance set to max, etc. I believe the issue may be specific to a particular application. I wrote a small batch script to output the time to the command prompt every 30 seconds and that never stops or misses a beat, indicating the VM isn't suspending. So, doesn't seem related to this thread.
  7. Necropost. Anyone else have anything to offer on this subject? If I'm connected via RDC or VNC (Splashtop) then the Win10 VM works fine. If I close the connection, the system won't run headless - it'll suspend/sleep within 30 minutes. I've got a long multi-day batch file conversion process running and needless to say, it's not going well because of this.
  8. Unaid 6.9.0/6.9.1 seems to break turning OFF reporting of pending sectors. Check-box came back "ON" after update and it won't save in a turned off state.
  9. I can access the docker UI and some plugins work fine, others are problematic or require different versions of underlying dependencies. The lack of updates to this docker make the situation untenable. If you're just jumping on this thread now and wanting HOOBS for the first time or simply for the first time in Unraid, save yourself long-term issues. SKIP THIS DOCKER. Refer to the instructions above and go with a VM instead which will let you stay up to date - which is required for some plugins.
  10. Can anyone recommend a USB card that's still readily available that will work in pass through for MacOS? That's really the only thing I want to pass through at the moment as this VM otherwise runs headless. Hot-plug USB support and the ability to keep hold of USB-connected devices all the time are high priority for me. Running on a Supermicro server mainboard, which I recall may have some issues with certain chipsets.
  11. I can access the WebUI at port 80 simply by giving the docker a fixed IP. This doesn't match what's defined in the docker as there's nothing in the config that I can see to allow it to work on 80. Seems to me that this template is fundamentally broken and because it's defaulting to 80 it won't work without changing the default IP. That's how it looks anyway. As an aside, before "just trying it," I had been attempting to follow the directions to edit the port (or add a new one after removing the original) without any luck. The setting for Container Port simply doesn't appear even when viewing in advanced mode (Unraid 6.8.3) Or even after removing the original port:
  12. It's not downloading Snow Leopard. The file you see in the log is a 6.5MB XML PLIST file - an indexed catalog of software release downloads for every OS in any number of languages. The next line tells you what OS it has selected. "001-86606". And that's Big Sur, a release from 2020-12-14. Confirmation (without looking into the catalog file): https://www.google.com/search?q=macos+001-86606
  13. You should be able to connect to Mac Screen Sharing with a VNC client on Windows if you allow that from the Mac side. Also, this solution claims to be the best (and may work without the above option), Remotix: https://remotix.com/remotix-win/
  14. One can always use Airfoil to re-route audio if you're on the LAN. Not using it myself for that purpose as I don't want/need audio with my primary Mac VM. I also use some client-server type apps in that VM, so most of the time I can interact with specific software without using VNC/Screen-Sharing at all.
  15. Why would you run Linux or Windows in a VM? Because you want access to a second, third, fourth, etc. machine running that OS for whatever reason, including testing as you mentioned. So in other words, this VM is useful for the same reason ANY VM is useful. And Macinabox especially useful because it makes deployment easy in a few clicks - getting a Mac VM up otherwise is a royal PITA. As far as having a monitor connected, have you ever put together a bare-metal CustoMac or Hackintosh? The VM route is a lot easier to deploy and maintain. And lastly, connecting to a Mac VM (or any Mac) remotely: Use the Mac's built-in screen sharing. It works well. Enable it in the Sharing pref-pane inside System Preferences. From Windows use RealVNC or other client to connect to your Mac. From another Mac, just browse the remote machine from Finder's Network path and then click the "Share Screen" button that should appear. As far as Big Sur goes, I run it on my new M1-powered Mac, but I'd avoid it on Intel machines for now, unless you're developing and need to test solutions on that target. Stick with Mojave or Catalina for day-to-day and consumer-use. Big Sur has quite a few issues at the moment even on Apple hardware and it's a good idea to let those shake out over the next 4-6 months.
  16. Is there any way to disable the reporting/notifications for (specifically) plugin and docker update availability?
  17. I don't know why, but in my case, the scripts only appeared AFTER the Catalina ISO finished downloading. So it's not possible to perform the step in the video of launching the VM_Ready_Notify script until afterwards - it then (obviously) reports that it's ready.
  18. Interestingly, I'm seeing a warning reported for a disk that's just about at the threshold (70%) but never seeing such warnings for disks which are over their thresholds (all disks set to same defaults).
  19. Samba performance from a Mac running an older OS (10.11) is unusable on large directories. No such issues exist accessing Microsoft SMB shares hosted in Windows. Opening a directory with 1000-2000 files can take multiple minutes.