Espressomatic

I suppose you might say it's the underlying OS Unraid is using, but that's not really here nor there. MacOS in my experience only has issues with Unraid's SMB shares. I've been using NFS shares for years now because nothing I've tried has improved the situation for SMB. Even if I can see a few file transfers at 100MB/s on a 1GBe connection, the fact that a folder listing will hang for 5-30 or more minutes makes it unusable. I've been using Unraid close to 7 years and I just recently mentioned I wanted to split docker and VM out of the array system. I was thinking about using Proxmox and CasaOS webUI on a new system I'm setting up for VM/Docker and keeping Unraid on the general NAS. Maybe I should do it the other way around, and move my Unraid key over to the new system for VM/Docker only and set up TrueNAS Scale for the NAS-only system. ...or maybe I just run Unraid on both systems because everything else out there has a pretty large nightmare component to it... But that damned SMB performance..

If his platforms are showing up it means he followed the github/wiki and there's a master roms folder above all the platforms. That's the recommended way to set up paths according to the docs. The whole path thing is a mess however, and having them hard-coded is just a really bad idea. Even worse is adopting what TWITCH/IGDB uses. It would have been ideal (and pretty easy) to auto-detect a few common possibilities and allow specifying a fully qualified path for each and every system. There's no way I'm changing my game paths to suit this or any other app. I've tried with symbolic links but so far it doesn't appear to work, so I can't fully test this. Uploading a few files just to check the UI is about it. I strongly suggest putting in options to change the font sizes as the defaults are microscopic even on a 14 year old 27" display. Also having a default landing page when clicking the menus on the side - example, clicking "Settings" should take you to Settings, no display another sub-item you have to click on. Anyone else notice that login info becomes corrupted? Logging out it seems to auto login when coming back to the WebUI, except the user name is blank. When it gets to this point have to kill the browser cache/cookies for the domain.

All this musical chairs with drives and extended downtime caused by rebuilding has put the final nail in my decision to split apart my Unraid usage. A single server to host my NAS disks (the array) and VM/Docker (all running on NVMe), isn't what I want/need anymore. Later this summer I hope to set up a smaller system 100% solid state for only VM/Docker onm Unraid, while keeping an array on the current 16-bay system, hopefully using a solution more performant and safer than Unraid. It sucks to have docker and VMs down while the array is in maintenace mode doing a rebuild.

Unassigned Devices uninstalled. Both installed again (as you mentioned, because UDP is automatically removed). I understand that, but I don't know where else to find/see any relevant information. If you have any suggestions (for next time) I'll make sure to try and get better diagnostic info. It'll be time to add another drive sooner rather than later, so I shouldn't so soon forget about this subject.

Same issue today. On top of that I accidentally removed the wrong drive while trying to take out the unassigned one - the Disk Location plugin was flashing the wrong drive and I made the mistake of not shutting down tghe aerray before physically removing it). So now it looks like it's going to be 22+ hours to rebuild the 8TB drive I accidentally removed. Ugh.

Just updated UD to 05.01 and here we go again - pre-clear never gets beyond "starting" on any of 5 drives tested. Uninstalling and re-installing fixed it again. Something's seems wrong with the update process maybe?

Same problem here. I haven't used any type of preclear in years. Today I'm trying it on a brand new 14TB Seagate Mach 2 drive (EXOS 2X14). The preclear log shows only the script invocation and the status just stays on "starting..." This fixed it:

I've been using JDownloader for over 10 years, and the docker for at least 6 and it's always worked very well. I noticed today that I can't open any "explorer" (file open/save) windows in JD. So the options for "add container" or File -> Load Linkcontainer (CTRL-o) do nothing and I can't access my DLC files. When trying to Create DLC, an error pops up instead of the file window and says "Please choose a valid path to save the DLC" Kind of stumped here. I haven't used these features since sometime last year, but I've been using JD pretty steadily the whole time and haven't noticed any other issues come up.

Adguard Home WebUI: Also, delete cookies and cache from the browser and try again.

This is the behavior accessing Unraid shares from MacOS. I've been running Unraid for over 5 years and this has always been the case, especially with SMB shares. It just doesn't work well and when it does work at all, the speed it pretty slow. This is with some 7 or 8 MacOS versions and three completely different Macs, plus always updating Unraid to latest/current versions. Accessing with a Windows system is reliable and pretty fast. There's nothing you can do to improve the situation. No version of Unraid addresses these issues and there are no settings, patches, extra software or anything that will make any difference. The only solution to fast SMB shares from MacOS is to use another NAS instead of Unraid. If you set up a Windows system and share its folders as SMB you'll see how fast it can be. I typically use NFS because SMB can't be used with the Mac on Unraid. It's not great, but at least it somewhat works.

Any changes with 6.12 on this? I moved over to NFS a long while back and now even that's not working. It'll freeze up the finder opening a subfolder with a dozen or so files. I have no issues with SMB if I host shares from a Windows machine or a RasPi. Fast, near-instant updated file lists and stable. With unraid, shares are pretty much unusable from MacOS now.

I have auto update turned on and those notifications still pop up. Great plugin, but I understand not everyone knows how to design for UX.

This is all unfortunate, no notice given in the unraid UI and the plugin wasn't disabled/removed. But thanks to the pinned message and helpful replies I think I have everything sorted. Thank you for attaching ipmi tool as I wasn't able to find it in the search of the linked packages web site. I also managed to download an install 7zip, which required searching for "p7zip" as "7zip" found nothing (each without quotes).

Weird. I'm not using USBIP and it's disabled as far as I know. Also, if I enable it and then disable it, this warning pops up: Doesn't seem right to me that would appear when disabling.

Well, puzzling. This time it works. Last night, after updating to 6.10.3, no amount of restarts of the VM or entire server brought back the missing USB devices to the VM. Today, everything is looking fine right from the initial reboot after update. So false alarm? I supposed if anyone else comes in here with a similar issue, try reverting the OS and then applying the update again.

I'll install 6.10.3 again to duplicate the issue to grab any details from the log. I'll attach the output as of right now below. As far as the UI goes, everything looked correct (as it usually does, displaying that the devices were attached). Jun 15 20:23:53 TVHD root: plugin: installing: /boot/config/plugins/usb_managerv2beta.plg Jun 15 20:23:53 TVHD root: plugin: skipping: /boot/config/plugins/usb_manager/packages/usb_manager-2022.03.26beta3.txz already exists Jun 15 20:23:53 TVHD root: plugin: running: /boot/config/plugins/usb_manager/packages/usb_manager-2022.03.26beta3.txz Jun 15 20:23:53 TVHD root: | Installing new package /boot/config/plugins/usb_manager/packages/usb_manager-2022.03.26beta3.txz Jun 15 20:23:53 TVHD root: Verifying package usb_manager-2022.03.26beta3.txz. Jun 15 20:23:53 TVHD root: Installing package usb_manager-2022.03.26beta3.txz: Jun 15 20:23:53 TVHD root: Package usb_manager-2022.03.26beta3.txz installed. Jun 15 20:23:53 TVHD root: | Skipping package usb_manager-2022.03.26beta3 (already installed) Jun 15 20:23:53 TVHD root: plugin: creating: /tmp/start_usb_manager - from INLINE content Jun 15 20:23:53 TVHD root: plugin: setting: /tmp/start_usb_manager - mode to 0770 Jun 15 20:23:53 TVHD root: plugin: skipping: /boot/config/plugins/usb_manager/usb_manager.cfg already exists Jun 15 20:23:53 TVHD root: plugin: skipping: /boot/config/plugins/usb_manager/remote_usbip.cfg already exists Jun 15 20:23:53 TVHD root: plugin: skipping: /boot/config/plugins/usb_manager/vm_mappings.cfg already exists Jun 15 20:23:54 TVHD root: usb_manager has been installed. Jun 15 20:23:55 TVHD root: plugin: usb_managerv2beta.plg installed Jun 15 20:24:00 TVHD usb_manager: Info: rc.usb_manager Building Connected Status Jun 15 20:24:38 TVHD usb_manager: Info: rc.usb_manager vm_action Home Assistant prepare begin - Jun 15 20:24:38 TVHD usb_manager: Info: rc.usb_manager Reset Connected Status Jun 15 20:24:38 TVHD usb_manager: Info: rc.usb_manager vm_action HomeBridge prepare begin - Jun 15 20:24:38 TVHD usb_manager: usb_manager virsh called Home Assistant 2 3 Device attached successfully Jun 15 20:24:38 TVHD usb_manager: Info: rc.usb_manager Autoconnect Start 002/003 temp vm: Home Assistant Jun 15 20:24:39 TVHD usb_manager: usb_manager virsh called Home Assistant 2 6 Device attached successfully Jun 15 20:24:39 TVHD usb_manager: Info: rc.usb_manager Autoconnect Start 002/006 temp vm: Home Assistant Jun 15 20:24:39 TVHD usb_manager: usb_manager virsh called Home Assistant 2 4 Device attached successfully Jun 15 20:24:39 TVHD usb_manager: Info: rc.usb_manager Autoconnect Start 002/004 temp vm: Home Assistant Jun 15 20:24:39 TVHD usb_manager: Starting usbip config check... Jun 15 20:24:39 TVHD usb_manager: Start usbipd

Updating my system to Unraid 6.10.3 causes the USB devices to disappear from the VM they're attached to. In my case this is /dev/ttyUSB1 and /dev/ttyUSB2 under Home Assistant OS with a Zooz Z-Wave controller and Sonoff Zigbee Controller that share the same Silicon Labs VID/PID. Reverting to 10.6.2 immediately fixed the issue.

Can anyone recommend a definitive way to hide update notifications for Unassigned Devices along the top banner in the browser? In Notification settings I've already un-checked all Plugin notifications but this doesn't seem to have had an effect for the notifications from Unassigned Devices. This plugin is set to auto-update, but more often than not, I fire up the Unraid web UI between updates and see these banners regularly.

Bitten by the same issue of non-booting (though not trying to make a backup). Problem/fix compounded by not being able to shut down the VM instance while it was stuck in the UEFI Shell - so no ability to edit the XML. Waiting on the whole system to come back after trying to reboot the server via Unraid menu. EDIT. Serious scare when the system came back up. NVMe cache drive holding all VMs didn't show up and made all VMs complete inaccessible. Shut-down and reboot brought it back and everything was as expected. Including the problem VM which was currently set to qcow2 instead of raw disk type. I didn't manually change anything, it just showed up again like it had always been. The entire fiasco is strange.

Damn, I didn't see this reply until today. So the plugin hadn't been working for months and then out of the blue sometime in the past 4-6 weeks it started to work - still the same version of the plugin, no unraid version update. I have plugins and a few dockers set to automatically update but can't think of anything that would have affected IPMI. As I don't regularly access the WebUI, I just happened to see the HDD and CPU temp + fan speed displayed in the footer one day. And it was glorious. Had to run to the basement immediately to confirm everything was whisper quiet again.

Does anyone have any suggestions for OTHER fan control scripts compatible with SuperMicro boards? I don't have much interest in spending any more time with this plugin as I don't see member queries getting any traction and updates to the plugin to fix issues don't seem to be forthcoming. If I can't find anything, I think I'll end up bypassing any software control and move to a completely external control solution.

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.

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.

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.

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: