WOL (wake-on-lan) with suspend, hibernate and shutdown issues problems OMV5.x & Debian 10.7 "Buster"

Hello forum!

Although I am a complete n00b when it comes to Linux and OMV, I successfully installed OMV 5.x on (top) of my Debian 10.7 installation with some random hardware & a Atlantic AQC-107 10GBE NIC.

I would like to thank you very much for all the excellent guidance and help I have been able to find here and on YT etc. from dedicated OMV users (!)

But one thing makes my life really hard, namely the configuration of any/some energy saving functions and here specifically putting OMV into a form of hibernate and waking it up again with wake-on-lan (WOL).

The whole Autoshutdown via Plugin is not working, rep. is doing nothing for me and somehow interferes or dependent on the configuration of the Debian kernel, the ACPI settings in the BIOS and in Debian-OS, the nic & network manager settings, settings in countless .conf files, services, boot options etc. aso.

What I am trying to say is: Unfortunately, simply checking the "Auto shutdown" checkbox did work for me and it looks to me, that they're many other users who are not able to configure a satisfying energy saving setup...?!

It took me more then a week to figure out how to bring my NAS-PC into hibernate from the cmd-line, but still not within / out of OMV.

Now I am searching for a way to "integrate' the below solution into my OMV installation, but have no clue where to start...

Goal is to hibernate when no one is streaming or doing a backup anything to the NAS.

This is what I like to share with you...so here's what I did:

nexus6@NAS:~$ sudo cat /proc/acpi/wakeup
Device	S-state	  Status   Sysfs node
PCI0	  S5	*disabled  no-bus:pci0000:00
[B]PEX0	  S5	*disabled  pci:0000:00:1c.0[/B]
PEX1	  S5	*disabled
PEX2	  S5	*disabled
PEX3	  S5	*disabled
[B]PEX4	  S5	*disabled  pci:0000:00:1c.4[/B]
PEX5	  S5	*disabled
HUB0	  S5	*disabled  pci:0000:00:1e.0
UAR1	  S5	*disabled
UAR2	  S5	*disabled
IGBE	  S5	*disabled
USB0	  S3	*enabled   pci:0000:00:1d.0
USB1	  S3	*enabled   pci:0000:00:1d.1
USB2	  S3	*enabled   pci:0000:00:1d.2
USB3	  S3	*enabled   pci:0000:00:1a.0
USB4	  S3	*enabled   pci:0000:00:1a.1
USB5	  S3	*enabled   pci:0000:00:1a.2
EHC1	  S3	*enabled   pci:0000:00:1d.7
EHC2	  S3	*enabled   pci:0000:00:1a.7
AZAL	  S5	*disabled  pci:0000:00:1b.0

nexus6@NAS:~$ sudo lspci -tv | grep -i ether
[B]+-1c.0-[02]----00.0 [/B] Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion]

echo enabled > /sys/devices/pci0000:00/0000:00:1c.0/power/wakeup ## looks like both cmd doing the job
echo enabled > /sys/class/net/enp2s0/device/power/wakeup

root@NAS:~# cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
PCI0      S5    *disabled  no-bus:pci0000:00
[B]PEX0      S5    *enabled   pci:0000:00:1c.0[/B]
PEX1      S5    *disabled
snip...

[Unit]
Description=Activate WOL on enp2s0 network card
After=network-online.target # network service started&online?


[Service]
Type=oneshot
ExecStart=/usr/sbin/ethtool -s enp2s0 wol g #set WOL to magic-packet


[Install]
WantedBy=basic.target

...snip


/usr/sbin/ethtool -s enp2s0 wol g # idk, just setting WOL for NIC here again ;-D
echo enabled > /sys/class/net/enp2s0/device/power/wakeup
echo PEX0 > /proc/acpi/wakeup   ## same as "echo enabled > /sys/devices/pci0000:00/0000:00:1c.0/power/wakeup"
echo PEX4 > /proc/acpi/wakeup   ## just in case I got the wrong PCI-slot
echo HUB0 > /proc/acpi/wakeup   ## USB-Hub(?) to test reactivate with usb mouse/keyboard

Thanks for reading all this & sorry for my poor English.

SB

Hello everyone,

I am glad to communicate a solution for the problem, that my OMV-custom NAS didnt go into a suspend or hibernate status, when not used AND couldnt get up running on WOL.

Solution:

I realized the reboot is the result of an not working wake up, beacause of an incomplete hibernation: the image of the hibernation status was not written, so without the last known status, there's no "wake up" possible, just a reboot with "last known good" settings!

Goal: force the a image-write to ram and to hard disk, maybe swap-partition on hibernate ...

and force a load of the image on wake up.

## show disks to potentially write the hibernate image too ##

root@NAS:~# lsblk --output NAME,FSTYPE,LABEL,UUID,MODE
NAME   FSTYPE LABEL UUID                                 MODE
sda                                                      brw-rw----
|-sda1 ext4         1748b395-819b-4356-b2ad-0d2b697199a8 brw-rw----
|-sda2                                                   brw-rw----
|-sda5 ext4         f2a82520-6b55-4a76-b713-204b1655cdd6 brw-rw----
[B]|-sda6 swap         377438db-9374-40a5-8730-0f5827a131ec brw-rw----[/B]
|-sda7 ext4         59361bac-5777-49fe-a8f5-8b0cba191153 brw-rw----
`-sda8 ext4         bc2befe7-2381-4302-b61f-9a4ebf2eaddc brw-rw----
sdb                                                      brw-rw----
`-sdb1 ext4   Video cd5c5260-e0e7-4cff-a7e5-0180323a1bce brw-rw----

OK, my swap-partition is sda6 and here I can see the UUID which I need for the next step.

The GRUB setting can be edited quite simply with the "GRUB Customizer", and/or set. I did it in the GUI via a VNC session, Not the best tool, but it works...

apt-get install grub-customizer

I added the "nomodeset"-cmd to grub-config with the UUID of the swap-partition:

## after editing, the actual writing in in to GRUB ##

root@NAS:~# update-grub

## written in the /boot/grub/grub.cfg after that ##

## cat /boot/grub/grub.cfg ##

GRUB_CMDLINE_LINUX
acpi_osi=Linux nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec

## or open the grub.cfg with an editor ##

[I]...snip[/I]
echo    'Linux 4.19.0-13-amd64 loading ...'
linux    /boot/vmlinuz-4.19.0-13-amd64 root=UUID=1748b395-819b-4356-b2ad-0d2b697199a8 ro acpi_osi=Linux [B]nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec[/B]
echo    'Initiale Ramdisk loading...'


[I]...snip[/I]

## check: is it a actual setting now ##

root@NAS:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-13-amd64 root=UUID=1748b395-819b-4356-b2ad-0d2b697199a8 ro acpi_osi=Linux nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec
[CODE]


## check more ###
[CODE]
root@NAS:~# cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'


GRUB_DEFAULT="0"
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec"
GRUB_CMDLINE_LINUX="acpi_osi=Linux [B]nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec[/B]"


# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"


# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"


# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="640x480"


# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"


# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"


# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_DISABLE_SUBMENU="y"

## After editing, now force hibernation via CMD ##

root@NAS:~# systemctl hibernate

Please see attached pictures, I couldn't found the logs to copy from, so I took screenshots ;-D

System closes programs & some services, writes the image to ram and then to disk and then goes into hibernate.

On start the same thing vice versa...

You'll find you last cmd in the shell, open folders & files in GUI resp. VNC aso.!!!

So, this problem is solved (for me) and I it can be set to SOLVED.

I hope this will help someone else

SB