Rysz

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.

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/

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).

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 : 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.

Did you check upscmd for your UPS if there's anything else? upscmd -l <upsname> should show a list of available commands.

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?

This should happen only directly after updating until you refresh the page, it's because the script location was changed between the updates and the page is still looking for the old script at the old location until you refresh the browser. After you refreshed the page there shouldn't be any more of these messages. Can you confirm there are no more new messages like that after closing your browser page and opening it again?

It is reported either by the UPS or the UPS driver, you can disable the notification itself in the NUT Settings ("Battery Replacement Notification" to "No"), but you'll always see it in the UPS Status (in GUI) if that's what your UPS or UPS driver reports. At least disabling the notification you won't be bothered with e-mail or push notifications from NUT about your battery needing a replacement anymore - so hope that helps a bit! If possible can you also post the NUT Debug Package here (can be found in NUT Settings) so I can take a look at what else might be causing the UPS status to be reported this way? Thanks in advance!

This is because you put the mergerFS mount inside /mnt/user which interferes with the regular Unraid shares. You'll have to put it either in /mnt/addons/ and set up a custom Samba share directive OR create a regular Unraid share e.g. "media" through the GUI and put your mergerFS mount inside that (/mnt/user/media/mini-pc/). Let me know if that worked for you 🙂

Do you perhaps use "powertop" on your system to tune power consumption? This post is regarding NUT but also valid for APCUPSD, might shed some insight on the backgrounds of such issues: Mostly it's a combination of the USB implementation of the driver and one of the controllers either on machine or UPS. Not much one can do about that unfortunately, easiest things to try being another USB port or USB cable...

I was about to write a reply that you should check your powertop settings because I just saw you post about it in another topic. I'm glad to see that you have got it narrowed down to that and working for now in the meantime. But I'm not entirely sure if your disabling of the auto-suspend for that USB device will survive a reboot of your system. So if it happens again, you know what to do and the culprit.

I've integrated this as part of a plugin now available on Community Applications:

LLDP for UNRAID (6.10+) A plugin that integrates a Link Layer Discovery Protocol service into UNRAID systems (speaking LLDP, CDP, FDP, SONMP and EDP). LLDP allows you to know exactly on which port is a server (and reciprocally). LLDP is an industry standard protocol designed to supplant proprietary Link-Layer protocols. The goal of LLDP is to provide an inter-vendor compatible mechanism to deliver Link-Layer notifications to adjacent network devices. What's the most common use case? Image: https://lldpd.github.io/ You have a managed switch with tons of cables and you're not sure which port your Unraid machine is connected to. The plugin allows the Unraid machine to advertise itself to the switch so ideally you'll see that it's connected on port X. How to install? Community Applications. 🙂 or via Direct Link: https://raw.githubusercontent.com/desertwitch/LLDP-unRAID/main/plugin/ulldpd.plg How does it work? After installation LLDP is disabled by default and waiting for your configuration. All necessary steps to configure and use the plugin are explained in the GUI (Settings ➔ LLDP). How to contribute? https://github.com/desertwitch/LLDP-unRAID ... and of most importantly - please do test and report back here!

Configuration looks good and shouldn't cause issues, you'll have to try a new USB cable I'm afraid. Usually is one of these reason if things worked well before and start dropping out (more likely to less likely): NUT settings recently changed around UPS settings recently changed around UPS firmware or NUT backend recently updated USB cable between Unraid machine and UPS faulty or dead USB port on Unraid machine faulty or dead USB port on UPS faulty or dead USB controller on UPS faulty or dead USB controller on Unraid machine faulty or dead Unraid version recently updated & now HW compatibility/driver issue

That's just the device discovery method. Did you try "Reset Config" and "Auto Config" afterwards? It seems to detect the UPS but somehow isn't able to connect to it. Please also post the NUT Debug Package (can be found under "NUT Settings") But I'm pretty sure it's the cable if it worked fine before and suddenly keeps dropping out.

Can you try another USB port and see if it works then - make sure to "Reset Config" first. If it doesn't, perhaps you have another USB cable around that you could try?

Gibt es auch auf Amazon im Nachbau für 15€ oder so. 🙂

My best security practice is don't expose anything directly to the internet and use a VPN to access any services instead. If you trust only people you know on your internal network and use 2FA where possible I'd say you minimized 99% of the risk. Unraid is a OS mostly aimed at storage ease of use rather than security, so there's only so much you can do on the OS itself. Network-wise you can do a lot more, such as separating insecure devices on their own VLANs and set up separation via firewalling. But honestly it always depends on your use case and how much of a target you consider yourself plus the possible vectors of attack. And if you're concerned about all that you're probably better off setting up a more secure VM with your services on top of your Unraid. There's Linux distributions that offer more fine-grained control of access and users compared to running services from your data server. Personally I only run services on Unraid which strictly require access to the data I'm storing on my Unraid system itself. For the rest of my services I'm using VMs which are set up with more fine-grained controls, regular security updates etc.

È normale perché all'inizio la cache di scrittura aiuta a mantenere alta la velocità. Quando è saturo è più lento a causa dell'operazione di parità (lettura file, scrittura parità, verifica parità).

Please post a diagnostics file for us.

Glad you got it to work - probably was just a USB hiccup that caused it the first time.

How do you know it is recognized? Do you also have the APC UPS daemon activated (see "UPS Settings")? If so please make sure to disable it as it cannot function alongside of NUT. Also, have you tried another USB port yet, sometimes another USB port works better? Please post the "NUT Debug Package" here (you can download it under "NUT Settings"). Last (but try everything else first) you can try changing the NUT backend to "legacy (2.7.4 stable") in "NUT Settings" and restart the server afterwards for the change to become effective. Some UPS work better with the older versions of NUT and your UPS was reported working with 2.7.4. according to the NUT website.

Sollte mit dem standardmäßig in Unraid integrierten APCUPSD ("UPS Settings") funktionieren, ansonsten möglicherweise auch mit dem NUT Plugin (bietet mehr Einstellungen). Also einfach mal per USB anstecken und unter "UPS Settings" einrichten, ansonsten das NUT Plugin installieren und mit diesem versuchen. (UPS Driver: "usbhid-ups", UPS Port: "auto"). Hier die Anleitung der USV, zwecks Verbindung mit dem Computer.

Never had any major problems with Syncthing, but I noticed when I skipped updating it for too long performance got a bit impaired at times.

Also check power connections esp. if you are using power splitters or recently changed something around.