Rysz

March 18

On 1/16/2024 at 3:39 PM, hfuhruhurr said:

Thanks so much for your reply. I have tried this several times and unraid still shuts down every two weeks.

The Details screen now shows "battery.charge.low=30"

The log file constantly shows:

"Jan 16 07:34:18 Mongo usbhid-ups[4714]: ups_status_set: seems that UPS [ups] is in OL+DISCHRG state now. Is it calibrating or do you perhaps want to set 'onlinedischarge' option? Some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when offline."

How do I set the "onlinedischarge" option?

I see that you were using the older NUT 2.8.0 backend when you posted your response, is this still a problem with the newer and now default NUT 2.8.1. backend? Also please post in the NUT Support Thread next time so that your answer doesn't go unnoticed as it unfortunately was in this topic.

March 18

7 minutes ago, PilaScat said:

From what I can see the problem started after march 11 release, I'll try to switch backend when I can reboot the server

Thanks - you can also reinstall the NUT plugin after changing the backend if you can't reboot. Interesting would be if it works on "release (2.8.0 stable)" in particular. The issue with that series must be older than March, because NUT 2.8.1. was released 10/2023 and the default backend the plugin uses was compiled from that release by me 11/2023 and has remained unchanged since then.

March 18

Data Volume Monitor (DVM) for UNRAID

"A plugin that lets you monitor and act on your consumed data volume utilizing vnStat."

With much pride I'd like to present my latest project - the Data Volume Monitor (DVM).

Dashboards, footer information, notifications, user actions (on VMs/Docker containers) and custom scripting.

These are a few of the features being offered - all centred around the data volume consumption of your server.

Don't want to your Syncthing container to pull in more than 50 GB a day?

No problem, DVM will stop and restart the container for you within those limits.

Running a few data intensive VMs and want to pull the plug when it's been too much?

No problem, DVM will disconnect and reconnect specific VMs from/to the network.

Want to move around some files and folders when you've pulled in too much data?

No problem, set up a custom script and DVM will execute it for you when it's time.

Please report back if you are experiencing any problems!

This plugin was developed with older machines in mind - it's been tested on 6.8.3 and above.

March 18

6 hours ago, LSL1337 said:

Hello.

I've been away for a few weeks, but here are the debug logs attached.

(I was getting battery replacement warnings on my new APC BX series UPS)

I know I can disable this feature, but i find it very useful, to get notification, when the battery needs replacement eventually, and the UPS has this automatic self test every 2 weeks.

Last time I got the replacement warning was yesterday 9:24PM (march 16th).

Thanks for looking into it!

nut-debug-20240317235549.zip 15.18 kB · 0 downloads

Hello, in the meantime it was discovered there's currently a backend driver bug with the BX series (see post above) which we're working on. Many BX users are reporting false RB or LB states, so it's NUT and not your UPS. I hope there'll be a fix soon, I'll keep you posted.

Same as above, can you please try the other backends with the backend switch in NUT Settings (reboot or reinstall plugin afterwards) to see if it happens on the older backend versions also?

March 17

15 hours ago, PilaScat said:

Hi, today my new UPS (APC BX1200MI-GR) arrived, set it up and charging, but in the notification I'm getting this:

Is not true, it's going to 100%

Other screens:

While making the screens I saw live the percentage going to 0% then back to 99%, triggering the notification
I'm connected to NUT with Home Assistant for automation, but I'm on standalone, it works but is it correct?
Yes I have powertop but I checked and it isn't touching the UPS USB, and it worked the same with the old UPS, same UPS but 950VA

nut-debug-20240316165522.zip 14.74 kB · 0 downloads

Hello!

This is unfortunately a known bug in the NUT backend driver (not the plugin) with that UPS series at the moment, which we're currently investigating. Do you perhaps have a chance to try the other older NUT backends (NUT Settings => Network UPS Tools Backend Switch => ideally reboot or at least reinstall plugin after switching the backend) if it also happens with the older versions? This would help us a lot to close in on what is causing the bug by comparison so we can hopefully fix it in the APC driver as soon as possible.

~~An unrelated question, how are you connected to NUT with Home Assistant when you're using "standalone" NUT mode? Normally that should only work in "netserver" NUT mode.~~ Edit: Nevermind, just tested it and NUT also exposes the general UPS information in "standalone" mode.

https://github.com/networkupstools/nut/issues/2347

Thanks in advance! 🙂

March 16

6 minutes ago, BVD said:

Looks like the release notes are missing:

Checked the github and doesn't appear to be posted there either, though looking at the commits it seems like it should just be something like "verify no LLDP service is running during install/upgrade" I think?

Yeah it was just a very minor change in the positioning of some statements in the installation and removal processes - sorry, I missed the release note. 🙂 I've added the release notes now, you probably won't see them because you've already checked for updates, but other users will see them.

March 16

On 3/15/2024 at 10:26 AM, danielb7390 said:

Hi,

First of all, thanks for maintaining this plugin!

Unfortunately i had 2 power cuts in the last week that lasted more than the normal few seconds, and some weird stuff happened, and i cant figure out exactly whats wrong.
In attachment, debug zip, and print screens.

Sequence of events:
The settings are set to power off when battery.runtime < 300. UPS battery is quite new, and seems to be reporting accurate runtime.

21:30 The power failed
21:26 NUT script decided it was time to shutdown the server. But runtime at that time was >900s left (check last image)

(Somehow the server started back up, unrelated to NUT, i have to check my BIOS settings... i guess wake by USB or something is causing this)
At 21:29, it was back up, and battery runtime was 822.
At 21:39 NUT script decided it was time to shutdown, this time with the correct runtime left.

Not sure how to debug this at all.
I took a look at the scripts and all looks great, the only way i see to this fail is if the upsc command fails, making grep/awk fail causing the -gt comparison to fail somehow (nut-notify@L72), I'm probably way off on this, my bash script skills are 0 to none 🤣

nut-debug-20240315085147.zip 14.86 kB · 1 download

This is fixed now - thanks a lot for your investigation, I've taken the liberty of crediting you in the changelog. If you're interested how I solved this: https://github.com/desertwitch/NUT-unRAID/blob/2b7b5113df28836b68e1089d81cdf6095eec861e/source/nut-dw/usr/sbin/nut-notify#L71-L102

March 15

35 minutes ago, danielb7390 said:

Hi,

First of all, thanks for maintaining this plugin!

Unfortunately i had 2 power cuts in the last week that lasted more than the normal few seconds, and some weird stuff happened, and i cant figure out exactly whats wrong.
In attachment, debug zip, and print screens.

Sequence of events:
The settings are set to power off when battery.runtime < 300. UPS battery is quite new, and seems to be reporting accurate runtime.

21:30 The power failed
21:26 NUT script decided it was time to shutdown the server. But runtime at that time was >900s left (check last image)

(Somehow the server started back up, unrelated to NUT, i have to check my BIOS settings... i guess wake by USB or something is causing this)
At 21:29, it was back up, and battery runtime was 822.
At 21:39 NUT script decided it was time to shutdown, this time with the correct runtime left.

Not sure how to debug this at all.
I took a look at the scripts and all looks great, the only way i see to this fail is if the upsc command fails, making grep/awk fail causing the -gt comparison to fail somehow (nut-notify@L72), I'm probably way off on this, my bash script skills are 0 to none 🤣

nut-debug-20240315085147.zip 14.86 kB · 1 download

Thanks for the detailed information, I think you could be right about your observations. Another possibility is that NUT has lost communication with the UPS for a short time and by in-built backend behaviour NUT always considers a non-communicating UPS that was last seen on battery as critical and immediately sets FSD and shuts down. But since the other computer managed to remain in contact with the UPS a failing command chain is more likely. That script is a 7 years old and could use some general overhauling. I'll introduce some safeguards against any failing upsc-grep-awk chains, which I'm generally not that happy with in their current state, with the next update but it might take a while.

March 12

6 hours ago, shapeshiftr said:
Unless I'm seeing something different to you, the only place I can see power settings in the NUT config section of Unraid -> Settings is in CLI for "/etc/nut/upsmon.conf"
MONITOR [email protected] 1 monuser monpass master
SHUTDOWNCMD "/sbin/poweroff"
POWERDOWNFLAG /etc/nut/no_killpower
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYCMD "/usr/sbin/nut-notify"
Didn't there used to be a GUI option to configure this, or am I just misremembering?

It's because you're using manual configuration mode where everything is supposed to be configured through the configuration files. You'll have to set manual configuration mode to "No" or "for UPS Driver" (if your UPS needs custom settings to be recognized) in order to see the GUI options. I'm guessing you enabled manual configuration mode because your UPS.CONF file has special directives needed for your UPS, so I'd switch to "for UPS Driver" so that those are kept unchanged but you can still use the GUI.

March 10

7 hours ago, TexasDave said:

You have been a big help - no worries at all. And the plugin is much appreciated.

Question: I assume I can still use my UPS short term? It will just supply power if I lose power but does not have any smarts so unRAID will not shutdown. So all it does now is keep it up and running and I have to hope the power comes back on before it runs out of charge?

Yes, exactly, now it's just a "dumb" UPS.

March 9

9 minutes ago, TexasDave said:

The cables seem fine. I can plug them into a printer and a Windows laptop sees them...

I strongly suspect the usb port on the actual UPC - it seems very "loose" - not sure how that happened.

May be time for a new UPC. 😞

Thanks for the additional information, unfortunately nothing is being picked up by the NUT device scanner either. So it seems to be the USB port on the UPS indeed, especially so if the cable works with other devices. Sorry I couldn't be of more help there.

March 9

Please post in the respective support topic instead:

March 9

2 minutes ago, TexasDave said:

I have had NUT working fine for some time. But to be fair, have not looked for a month or two too see if it was working and had no warnings or alerts. I had to move my server today as we are painting and noticed when bringing it back up, it has stopped working.

My UPC is a APC BX700U Series. Motherboard is Supermicro X10SL7-F

The APC UPS daemon is NOT activated
I have tried two different USB cables and 3 different USB ports. I have ordered a new cable and will try that.
I have tried both the current version and the 2.7.4 version (with restart)

I am attaching my diagnostics. Here is what I am getting in the SYSLOG:

Mar  9 16:42:28 Zack-unRAID root: Writing NUT configuration...
Mar  9 16:42:30 Zack-unRAID root: Updating permissions for NUT...
Mar  9 16:42:30 Zack-unRAID root: Checking if the NUT Runtime Statistics Module should be enabled...
Mar  9 16:42:30 Zack-unRAID root: Enabling the NUT Runtime Statistics Module...
Mar  9 16:42:31 Zack-unRAID root: Network UPS Tools - Generic HID driver 0.55 (2.7.4.1)
Mar  9 16:42:31 Zack-unRAID root: USB communication driver 0.43
Mar  9 16:42:31 Zack-unRAID root: No matching HID UPS found
Mar  9 16:42:31 Zack-unRAID root: Driver failed to start (exit status=1)
Mar  9 16:42:31 Zack-unRAID root: Network UPS Tools - UPS driver controller 2.7.4.1
Mar  9 16:45:56 Zack-unRAID pulseway: First reporting data collection finished
Mar  9 16:51:00 Zack-unRAID root: Fix Common Problems Version 2024.02.29
Mar  9 16:52:02 Zack-unRAID ool www[14520]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Mar  9 16:52:03 Zack-unRAID root: Writing NUT configuration...
Mar  9 16:52:05 Zack-unRAID root: Updating permissions for NUT...
Mar  9 16:52:05 Zack-unRAID root: Checking if the NUT Runtime Statistics Module should be enabled...
Mar  9 16:52:05 Zack-unRAID root: Enabling the NUT Runtime Statistics Module...
Mar  9 16:52:06 Zack-unRAID root: Network UPS Tools - Generic HID driver 0.55 (2.7.4.1)
Mar  9 16:52:06 Zack-unRAID root: USB communication driver 0.43
Mar  9 16:52:06 Zack-unRAID root: No matching HID UPS found
Mar  9 16:52:06 Zack-unRAID root: Driver failed to start (exit status=1)
Mar  9 16:52:06 Zack-unRAID root: Network UPS Tools - UPS driver controller 2.7.4.1

Here is what I am getting in NUT USB Diagnostics...

 ###
### USB DEVICES
###

Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0557:2419 ATEN International Co., Ltd Virtual mouse/keyboard device
Bus 003 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 003 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

###
### USB DEVICES (TREE VIEW)
###

/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
ID 0781:5571 SanDisk Corp. Cruzer Fit
|__ Port 7: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
ID 0557:7000 ATEN International Co., Ltd Hub
|__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
ID 0557:2419 ATEN International Co., Ltd Virtual mouse/keyboard device
|__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
ID 0557:2419 ATEN International Co., Ltd Virtual mouse/keyboard device
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ID 8087:8008 Intel Corp. Integrated Rate Matching Hub

###
### USB POWER MANAGEMENT SETTINGS
### ON: ALWAYS ON / AUTO: SYSTEM MANAGED
###

==> /sys/bus/usb/devices/1-1/power/control <==
auto

==> /sys/bus/usb/devices/2-1/power/control <==
auto

==> /sys/bus/usb/devices/3-1/power/control <==
on

==> /sys/bus/usb/devices/3-7.1/power/control <==
on

==> /sys/bus/usb/devices/3-7/power/control <==
auto

==> /sys/bus/usb/devices/usb1/power/control <==
auto

==> /sys/bus/usb/devices/usb2/power/control <==
auto

==> /sys/bus/usb/devices/usb3/power/control <==
auto

==> /sys/bus/usb/devices/usb4/power/control <==
auto

###
### USB RELATED KERNEL MESSAGES
###

[ 0.381770] usbcore: registered new interface driver usbfs
[ 0.381877] usbcore: registered new interface driver hub
[ 0.381986] usbcore: registered new device driver usb
[ 0.425339] pci 0000:00:1a.0: quirk_usb_early_handoff+0x0/0x63b took 16379 usecs
[ 0.442337] pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x63b took 16475 usecs
[ 1.988551] usbcore: registered new interface driver usb-storage
[ 1.988989] usbcore: registered new interface driver synaptics_usb
[ 1.991126] usbcore: registered new interface driver usbhid
[ 1.991234] usbhid: USB HID core driver
[ 2.208343] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 2.224346] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[ 2.224470] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 2.352117] usb-storage 3-1:1.0: USB Mass Storage device detected
[ 2.352581] scsi host0: usb-storage 3-1:1.0
[ 2.466334] usb 3-7: new high-speed USB device number 3 using xhci_hcd
[ 2.890359] usb 3-7.1: new low-speed USB device number 4 using xhci_hcd
[ 3.002104] input: HID 0557:2419 as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7.1/3-7.1:1.0/0003:0557:2419.0001/input/input1
[ 3.054596] hid-generic 0003:0557:2419.0001: input,hidraw0: USB HID v1.00 Keyboard [HID 0557:2419] on usb-0000:00:14.0-7.1/input0
[ 3.056387] input: HID 0557:2419 as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7.1/3-7.1:1.1/0003:0557:2419.0002/input/input2
[ 3.057039] hid-generic 0003:0557:2419.0002: input,hidraw1: USB HID v1.00 Mouse [HID 0557:2419] on usb-0000:00:14.0-7.1/input1

My concern is it the the USB ports on my server or the USB port into the UPC.

Ideas on what else I can do to try to debug and/or fix this?

zack-unraid-diagnostics-20240309-1631.zip 187.94 kB · 0 downloads

Thanks for the detailed information, it seems your system doesn't see the USB device at all. Can you also post the NUT Debug Package (can be found inside NUT Settings) just for me to have a complete picture there? Do you perhaps have a Windows device (e.g. laptop or whatever) around you could try connecting the UPS to and see if it shows up there at all (Device Manager)? Looking at this my first guess would be the USB cable has gone bad - broken port on the UPS is less likely (but not impossible).

March 9

10 hours ago, syrys said:

The cable that was on the box looks like that, are there variants of the cable that I should be concerned about? Also the cable from my old apc ups also looks like that (this was maybe 8 years old), and I also tested with that cable.

AP9827 is the most common cable and used by almost all APC UPS for USB - I'm pretty sure you have that one if it came with the UPS. But everything in this thread is guesswork at best, what we know for sure so far is that you tried it with two different cables (one of which is known to work with another UPS) on three different computers/OSes. That alone very strongly points to a fault with the UPS itself - I'm sorry I can't be of more help there.

March 8

4 minutes ago, caplam said:

i have an apc ups (smart ups 1000). I have to choose ups type: modbus to be able to pull data.

Yeah that's a ModBus UPS that you're using. His UPS isn't though, so that won't help in his case I'm afraid.

March 8

16 minutes ago, syrys said:

Im just playing around with it on windows. The powerchute software complains that it cant find the device. When i plug it in, sometimes windows device manager's USB section displays nothing new. But sometimes device manager shows "unknown usb device (device descriptor request failed)".

I'm afraid that really looks like something is faulty on the UPS itself and not the devices it's connected to. 😞

March 8

1 hour ago, syrys said:

Unfortunately its not under warranty as far as im aware as i purchased it secondhand (new/unused/unopened but dont have any original paperwork for warranty).

Is damaged USB controller a common issue? do you know if there is anything i can do to make sure that this is the case, or is my debugging basically prove it already? Or do these things have like firmware upgrades sort of thing that i may need to do (never had to do anything like that for the old UPS, but this seems more modern than the old one i have)?

I wouldn't say it's a common issue, but I've certainly seen it happen so it's not impossible. Do you perhaps have a Windows PC that you can try connecting the UPS to and see if it shows up there? Just to rule out that this is a Linux driver issue...

March 8

That sounds a lot like your UPS data port or UPS USB controller is damaged and not sending any information if it's not showing in "lsusb" on two different computers with two different cables. If your UPS is still in warranty I would return it to APC.

March 6

It's not that easy because Unraid has no process supervisor (either systemd or openrc), which k3s would require.

For all that hassle and necessary changes it'd probably be better to set up a Kubernetes server as a VM or on another machine.

March 6

1 hour ago, hollywood said:

I'm also experiencing the same issue with apcupsd and modbus on a SMT2200. Did changing the cable fixed the problem for you?
I've used the SNMP driver as a temporary fix for now and it seems to be very stable but i'm loosing the output current metric and battery temperature and other sensors are rounded up (not that it is a big deal really).

It seems APCUPSD development has been stale for a couple of years now, so wouldn't expect much there.

In the meantime it seems the NUT ModBus implementation seems to work (see above), so might be worth testing that.

March 5

Da brauchst du eigentlich nicht viel machen, wenn ich dich soweit richtig verstanden haben.

Es geht doch eigentlich nur darum eine defekte Festplatte zu tauschen, da übernimmt Unraid die Hauptarbeit.

Selbst musst du da überhaupt keine Formatierung vornehmen oder Daten verschieben.

Der Sinn der Parität ist es ja die Festplatte nahtlos austauschen zu können. 🙂

Foto von der Festplatten-Belegung machen
Server herunterfahren
Alte Festplatte aus dem Server ausbauen
Neue Festplatte in den Server einbauen
Server hochfahren
An Stelle/Position der nun fehlenden/defekten Festplatte die neue Festplatte auswählen
Nochmal mit dem Foto abgleichen das auch alle anderen Festplatten am selben Platz sind
Array starten und die Daten wiederherstellen lassen (passiert automatisch)
Abschließenden nicht korrigierenden Parity-Check machen ob alles richtig beschrieben wurde.

Wenn die neue Festplatte schon im Server ist und läuft, noch einfacher:

Foto von der Festplatten-Belegung machen
Array stoppen
An Stelle/Position der defekten Festplatte nun die neue Festplatte auswählen
Nochmal mit dem Foto abgleichen das auch alle anderen Festplatten am selben Platz sind
Array starten und die Daten wiederherstellen lassen (passiert automatisch)
Abschließenden nicht korrigierenden Parity-Check machen ob alles richtig beschrieben wurde.

https://docs.unraid.net/legacy/FAQ/replacing-a-data-drive/

March 5

4 minutes ago, Kilrah said:

Sounds like OFF is what you'd use if you didn't want it to power back on, e.g. for storage.

Easy to check, do what they say to power it off, then plug it back in... if it stays off until you manually turn it back on that's what would happen on a power loss if it was off.

That's actually a very good idea for a simulation test. So basically shutdown everything, turn off UPS completely by button (not standby), remove mains power cable, wait a minute or two, reconnect mains power cable and see what happens (if it turns on).

March 5

20 minutes ago, Masterwishx said:

i think :

shutdown.return - standby

shutdown.stayoff - shut down

Yeah, I think so too, but with "stayoff" it probably won't be able to turn on again on its own.

Because I found this about standby mode in the 9SX manual which is a similar also online model :

grafik.png.e68b1111112b48cd312f5b4585e430cd.png

And this reads to me like it's only able to wake up again when in standby mode (as opposed to when it's completely off). I'm guessing perhaps it needs to stay in standby for the software in the UPS to recognise that the AC is back.

The driver flag has nothing to do with it, that's just a safeguard so you can't execute the kill command from upscmd and bring down your running system by mistake. But during system shutdown it's executed directly from the driver (and not upscmd) so it's not needed in your case.

March 5

2 minutes ago, Masterwishx said:

Also checked after nut send FSD OB and power down , it has : 01 - Standby Mode

Did you check upscmd for your UPS if there's anything else?

upscmd -l <upsname> should show a list of available commands.

March 5

2 hours ago, Masterwishx said:

@Rysz

if i set 'Disable UPS Power after Shutdown=yes' all working fine , my ups goes to 'Standby' after power loss , and then power up when power return to normal.

but is anyway i can turn OFF completely the UPS ? or it will not power on then if it possible at all?

using Eaton 9E2000i (Online UPS)

NUT has no more control over this behavior except for telling the UPS to turn off the power. How the UPS handles that depends on the implementation on the UPS itself, maybe there's a setting directly on the UPS. Maybe - I'm guessing here - because you have an online UPS (where the power to the devices is never coming entirely from the mains power) it's never going to fully turn off but will just kill the power to the outlets and remain in standby until it it sees that the AC is back online.

I'd check out the user manual and perhaps contact Eaton over this, they are very supportive of the NUT project so I'm sure they'd be able to tell you more about this. For instance my line-interactive Eaton 5P850 turns completely off after shutdown, but that's a line-interactive and not online one.

Is the LCD going dark when it "shuts down" or how do you notice it's actually "shutting down" (or going to standby mode as you described)? Does it cut the power to the outlets?

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by Rysz

Data Volume Monitor (DVM) for UNRAID