Hi Guys,
I was able to configure the autoshutdown plugin for bringing my nas to sleep / hibernate.
Due to my disk is getting full I'm receving mails from monit about disk usage.
And exactly these mails, I'm receving round about each 13 minutes. As soon as I received such mail, I'd login into my omv. The uptime shows , my NAS is running since 2 to 3 minutes.
How to find the source, which is responsible, why my nas will be turned on ?
thanks 
Hi jigg3,
you may want go along Solo's guide "If Autoshutdown doesn't work". This helps to quickly track down several common issues with authoshutdown.
Regards,
topi
What is the nic card brand/model?
You can try and disable WOL (wake on lan, wake on PME) in BIOS. And see if you have the same behaviour.
Will I be able to wake up my nas later on ?
Don't think so, at least not by magic packet. If you press the power button or use rtc alarm maybe
Please install the backports-Kernel via omv-extras. Then test again. It is a driver issue, maybe
If this doesn't work, then please login via SSH/locally on your Server and execute
pm-supend -a
or
pm-hibernate -a
and see, if the error is happening again.
Is this solved then?
no 
pm-suspend and autoshutdown worked till yesterday.
Now, on each pm-suspend command, my system reboots after waking up by magic packets.
what is the output of pm-is-supported --hibernate?
and right after that:
echo $?
Thx
btw: How big is your swap-partition and how much RAM do you have?
Hi guys,
since I experience the above mentioned problems, my NAS is resyncing each 5th or 6th reboot / startup.
Still do not know, how to fix my issue with pm-suspend and the missing wake on image.
Perhaps this is the issue :
ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Google just says, that the system doesn't support sleep states but how to fix this ?
Hi,
you should have a closer look on the suspend resume process.
Is the image created? -> /var/log/syslog
Is the system configured to use your swap partition on resume? -> /etc/initramfs-tools/conf.d/resume should contain the uuid of your swap partition.
Knows the bootloader the location of your image? -> Add the kernel parameter resume=/dev/sda5 to GRUB_CMDLINE_LINUX in /etc/default/grub and update the grub configuration.
Thank you for your reply. I appreciate your help
I was just about to set up my whole OMV up from scratch.
As well I have checked the syslog but it seems if the image has not been created. The SWAP partition is within the resume entry and grub has been updated too.
As soon as I start the system again, my RAID is resyncing, this is also annoying.
PM: Starting manual resume from disk
May 19 14:56:11 NAS kernel: [ 1.548077] PM: Hibernation image partition 8:5 present
May 19 14:56:11 NAS kernel: [ 1.548079] PM: Looking for hibernation image.
May 19 14:56:11 NAS kernel: [ 1.548258] PM: Image not found (code -22)
May 19 14:56:11 NAS kernel: [ 1.548261] PM: Hibernation image not present or could not be loaded.
[ 1.555236] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
May 19 14:56:11 NAS kernel: [ 1.555239] EXT4-fs (sda1): write access will be enabled during recoverySie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!