Right, I received the 2 messages at shutdown, each a single line
1. "UPS ups - Low battery power"
2. "Automatic logout and shutdown proceeding"
I put more stock in system log files than info I receive via email. I was hoping to find logged confirmation of a proper shutdown, but perhaps Debian does not do such logging. In any event it appears the shutdown worked just fine.
Hi Everyone,
My area had a power outage in the middle of the night that outlasted my UPS battery. As many of you would do, I slept through the outage soundly knowing I am protected by OMV RAID, quality drives and UPS, the nut plug-in, and a backup/restore strategy. I believe my server shut down gracefully when the battery became low, though I'm not sure how to confirm. I was relieved to find no scary fsck 'not clean' or 'fixing this block or the other' warnings upon bootup, but I didn't find any comforting 'booting from graceful shutdown' messages either. How can I confirm a graceful shutdown? Pertinent info and logs follow.
Versions:
openmediavault 6.0.30-1
openmediavault-keyring 1.0
openmediavault-nut 6.0.1-1
openmediavault-omvextrasorg 6.1
<power loss>
Sep 25 02:25:56 vault upsmon[1808]: UPS ups on battery
Sep 25 02:25:56 vault upssched[1946083]: Executing command: notify
Sep 25 02:25:56 vault upssched-cmd: UPS ups - Line Power Fail, system running on battery power
<snip>
Sep 25 02:25:57 vault postfix/smtp[1946099]: 796A01C021B: replace: header Subject: UPS notification from x: Subject: [vault.local] UPS notification from vault
<snip>
Sep 25 04:24:31 vault upsmon[1808]: UPS ups battery is low
Sep 25 04:24:31 vault upsd[1804]: Client monmaster@127.0.0.1 set FSD on UPS [ups]
Sep 25 04:24:31 vault upsmon[1808]: Executing automatic power-fail shutdown
Sep 25 04:24:31 vault upsmon[1808]: Auto logout and shutdown proceeding
Sep 25 04:24:31 vault upssched[1949007]: Executing command: notify
Sep 25 04:24:31 vault upssched[1949012]: Executing command: notify
Sep 25 04:24:31 vault upssched-cmd: UPS ups - Low battery power
Sep 25 04:24:31 vault upssched-cmd: Automatic logout and shutdown proceeding
<snip>
Sep 25 04:24:34 vault postfix/smtp[1949039]: 180B01C015F: replace: header Subject: UPS notification from x: Subject: [vault.local] UPS notification from vault
Sep 25 04:24:37 vault systemd[1]: nut-monitor.service: Succeeded.
Sep 25 04:24:37 vault systemd[1]: nut-monitor.service: Consumed 2min 22.844s CPU time.
Sep 25 04:24:37 vault systemd[1]: Removed slice system-modprobe.slice.
<no further log until power on>
<power on manually>
Sep 25 08:50:39 vault systemd[1]: Finished Coldplug All udev Devices.
Sep 25 08:50:39 vault kernel: [ 0.000000] microcode: microcode updated early to revision 0x59, date = 2023-02-26
Sep 25 08:50:39 vault kernel: [ 0.000000] Linux version 5.14.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.14.9-2~bpo11+1 (2021-10-10)
Thanks,
Steve
Alles anzeigenHello,
I just build-up the CPU using Intel CPU on Asus Motherboard Z-590-A. Boot USB to install however, OMV is unable to detect the Ethernet card.
Appreciate anyone's help to what driver that I could use?
Thanks
I recently had the same problem installing OMV on a new GIGABYTE Z590 motherboard (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)). Turned out Debian 11 (Bullseye) is required to support the ethernet adapter, so I loaded OMV 6, and it's working like a champ.
Now is a great time for US based OMV users to take advantage of the USD favorable exchange with the Euro and donate to OMV development. I did that today - my donation will not buy much more than a bit of encouragement but I am hoping many of you will follow suit, especially if you've never done so (http://www.openmediavault.org/donate.html).
I have no affiliation with OMV aside from being a content user for the last couple of years.
Steve
