autumnwalker

I have a couple of H220 HBAs that I want to put into my Unraid box. As far as I know from HP these are SAS2308's in IT mode. Is there any reason to flash / update these cards? Is there a way to validate which mode the cards are currently in?

I think this is what I'm after. Is there anything I can do now to set my self up for success when this is implemented? e.g. qcow2 vs. raw? Thanks!

This looks like an intersting option for VM snapshots! Will there be a capability to snapshot a running VM in future (without shutdown / suspend)?

+1 one for this.

The workaround in the HA community worked for me too. Do we have any idea why this is required with Unraid? It was no issue for me to pass the same stick through with Proxmox previously.

Having the same issue as Dro. On reboot it's as if the SNMP plugin was never installed / never existed.

Lol not my intent here! Is there some other way I could get a VM or something to trigger Unraid to shutdown based on it being shutdown by this client? Like a bash script? I know enough about some of this stuff to think it could be done, but not familiar enough with how to do it.

Understood. Hadn't considered that. Slackware is nothing like Ubuntu or RedHat, is it? As in - the chance of "it might work" is low?

Not exactly what I'm going for. I want Unraid itself to be able to talk to the UPS via this software with a plugin (or something). Like someone else has done for NUT. End goal is I want to be able to cleanly shutdown Unraid via the software / UPS in the event of a power outage. Software is Vertiv Power Assist. Freely available here: https://www.vertiv.com/en-us/support/software-download/software/vertiv-power-assist-software-download/

Hello, I have a UPS which does not work with apcupsd or NUT. The vendor does provide a free suite of software which will run headless under Linux. Is it possible to create some sort of plugin (like NUT) so that I can use this software with Unraid? Thanks!

I flipped hardlinks off a couple of weeks ago and it seems to have resolved my issues ... noting this is not a workable solution for others. At least we are getting somewhere with root cause.

Turns out this feature is enabled! I could have sworn I disabled it. Once parity check is finished I'll try disabling and see if it solves the issue for me. I'm still a way's away before getting my homelab back up so I won't be able to fully test until later.

My server is currently offline so I will have to validate later, but I'm pretty sure I have this off on my box as well. I'll double check and confirm.

So it has been close to one month now with cache disabled on the shares. Have not had a single instance of "stale file handle" across CIFS or NFS. Clearly there is a relation to cache / mover.

Thanks! I see that now. I zoomed in on the "version too high" message I guess.

Full output below, it's still saying 2.7.4. plugin: updating: nut.plg +============================================================================== | Skipping package nut-2.7.4.20181125-x86_64-1 (already installed) +============================================================================== plugin: skipping: nut-2.7.4.20171129-x86_64-1.txz - Unraid version too high, requires at most version 6.4.99 +============================================================================== | Skipping package net-snmp-5.7.3-x86_64-4 (already installed) +============================================================================== plugin: downloading: https://raw.githubusercontent.com/dmacias72/NUT-unRAID/master/archive/nut-plugin-2020.03.17-x86_64-1.txz ... done plugin: downloading: https://raw.githubusercontent.com/dmacias72/NUT-unRAID/master/archive/nut-plugin-2020.03.17-x86_64-1.md5 ... done +============================================================================== | Upgrading nut-plugin-2019.02.03-x86_64-1 package using /boot/config/plugins/nut/nut-plugin-2020.03.17-x86_64-1.txz +============================================================================== Pre-installing package nut-plugin-2020.03.17-x86_64-1... Removing package: nut-plugin-2019.02.03-x86_64-1-upgraded-2020-04-13,11:58:45 --> Deleting /usr/local/emhttp/plugins/nut/NUTsummary.page Verifying package nut-plugin-2020.03.17-x86_64-1.txz. Installing package nut-plugin-2020.03.17-x86_64-1.txz: PACKAGE DESCRIPTION: # NUT - Network UPS Tools (a collection of ups tools) unRAID Plugin # # The Network UPS Tools is a collection of programs which provide a # common interface for monitoring and administering UPS hardware. It # users a layered approach to connect all the components. Drivers are # provided for a wide assortment of equipment. The primary goal of # the NUT project is to provide reliable monitoring of UPS hardware # and ensure safe shutdowns of the systems which are connected. # This package includes the tools needed to monitor your UPS over the # web and it also includes the upsclient library. # # https://github.com/dmacias72/unRAID-plugins Executing install script for nut-plugin-2020.03.17-x86_64-1.txz. Package nut-plugin-2020.03.17-x86_64-1.txz installed. Package nut-plugin-2019.02.03-x86_64-1 upgraded with new package /boot/config/plugins/nut/nut-plugin-2020.03.17-x86_64-1.txz. stopping services... Writing nut config Updating permissions... Stopping the UPS services... Network UPS Tools - UPS driver controller 2.7.4.1 checking network ups tools configuration... ----------------------------------------------------------- nut has been installed. Copyright 2015, macester Copyright 2020, gfjardim Copyright 2015-2020, dmacias72 Version: 2020.03.17 ----------------------------------------------------------- Updating Support Link plugin: updated AFAIK that's the latest version of NUT (outside of Git / dev).

Just updated the plugin and noticed this in the log: plugin: updating: nut.plg +============================================================================== | Skipping package nut-2.7.4.20181125-x86_64-1 (already installed) +============================================================================== plugin: skipping: nut-2.7.4.20171129-x86_64-1.txz - Unraid version too high, requires at most version 6.4.99 Specifically, "Unraid version too high". Thoughts on this?

I'd like to see this feature as well. I know when setting up a Time Machine share via AFP previously I could set a max size. I just went to do it on a regular SMB share and realized you couldn't.

Reflecting further on this - I don't think the issue is actually with CIFS. I have the same behavior using NFS if cache is enabled on the share. So perhaps vers=1.0 does something with CIFS to suppress the problem, but it's not strictly a CIFS issue.

I think this is the key part. @sjaak had suggested that earlier I believe. I have not validated this myself, but I have flipped netbios back on within Unraid so it is available.

This is exactly what I am seeing. NFS / CIFS makes no difference. Disabling cache on the share and the problem has stopped. I think it's related to mover.

I saw that - it's not clear to me if that "enables" SMB v1 or if it "forces" SMB v1.

How are you forcing the protocol to v1?

Any luck @darkside40? I've not flipped on the verbose logging yet as I'm being lazy and not wanting to stop the array and take down my dependent servers.

So what's my best bet? It seems to occur on any of my servers (Linux based) and is not specific to Proxmox (as my OOM thread had thought). Bump up verbosity on Samba and see what hits?