December 2, 20241 yr I've recently moved my IOT devices to an isolated subnet on a WiFi SSID which is different to the subnet on the Unraid. As a result I can no longer wake Unraid form its S3 Sleep state as the IOT devices are not on the same subnet and Alexa / https://www.virtualsmarthome.xyz/url_routine_trigger/ / WOL Skill can no longer nudge the Server with a WOL packet! As a result I have had to change the S3 Sleep plugin from sleep to shutdown and to use a smart plug to turn the power off to the server after shutdown and then to 'wake' it up by putting power on. But the boot up is obviously not as quick as resuming from sleep. I was wondering if there was an Unraid equivalent of Windows 'hibernate' to shutdown the server for a faster startup. Perhaps! It's not critical, but it just piqued my curiosity!
December 3, 20241 yr Community Expert Solution i don't think so. I think there a dynmax plugin for sleep though. Unraid, as it stands, does not natively support a true "hibernate" option like in Windows. Hibernate in Linux is essentially the process of suspending to disk, where the system's state (RAM contents) is written to a swap partition/file and then restored upon boot. Unraid's underlying Slackware base does not include native support for this functionality out of the box, and implementing it would come with challenges. Why Hibernate Isn't Common on Unraid No Swap Partition: Unraid is designed to run entirely from RAM after boot, and the default configuration lacks a swap partition or file, which is essential for hibernation. Array Management Complexity: Managing the state of the array during hibernation would require additional safeguards to ensure parity integrity. Use Case Misalignment: Unraid is typically intended for 24/7 operation, and features like hibernation aren't a priority for most users. Alternatives and Workarounds 1. Wake-on-LAN on Isolated Subnets The root issue is that your IoT devices can't send WOL packets across subnets. Solutions: Use a router/firewall that supports forwarding WOL packets across subnets (e.g., pfSense or Ubiquiti devices). Configure a relay or intermediate device (on the same subnet as Unraid) to send the WOL packet. For example, a Raspberry Pi or a small VM can act as the WOL relay. 2. Fast Startup Without Sleep or Hibernate Use an SSD for the Unraid boot drive (or a faster USB stick) to minimize boot time. Ensure BIOS is configured for fast POST. 3. Home Automation Tweaks Use a network-connected smart plug with automation rules to turn on the server after shutdown. Some devices can integrate with Alexa or other home assistants to schedule power-on events. Use a Nut/SNMP setup to manage power states intelligently. 4. Suspend-to-RAM (S3) Alternatives While hibernation isn’t supported, Suspend-to-RAM (S3 sleep) might still be an option if you can find a way to wake Unraid: Keep a device on the same subnet as Unraid to send WOL packets. Use an intermediate device to bridge the subnets (e.g., a small firewall rule or a static route). The Bottom Line While Unraid lacks native hibernation, the core problem seems to be around network configuration rather than Unraid's limitations. Addressing the WOL packet issue across subnets is likely the most practical solution. Alternatively, simplifying the boot process can make shutdown and startup less disruptive. Edited December 3, 20241 yr by bmartino1
December 3, 20241 yr Community Expert I would explre home automation with esp32 with a wired to motherboard option. to send a smart home comand to compelte teh power button circut for wake words... esp32 and esp home. there are some project floating to wake machine with esp32 and esp home example: https://tristam.ie/2024/1126/ https://esphome.io/components/deep_sleep.html
December 3, 20241 yr Author 9 hours ago, bmartino1 said: i don't think so. I think there a dynmax plugin for sleep though. Unraid, as it stands, does not natively support a true "hibernate" option like in Windows. Hibernate in Linux is essentially the process of suspending to disk, where the system's state (RAM contents) is written to a swap partition/file and then restored upon boot. Unraid's underlying Slackware base does not include native support for this functionality out of the box, and implementing it would come with challenges. Why Hibernate Isn't Common on Unraid No Swap Partition: Unraid is designed to run entirely from RAM after boot, and the default configuration lacks a swap partition or file, which is essential for hibernation. Array Management Complexity: Managing the state of the array during hibernation would require additional safeguards to ensure parity integrity. Use Case Misalignment: Unraid is typically intended for 24/7 operation, and features like hibernation aren't a priority for most users. Alternatives and Workarounds 1. Wake-on-LAN on Isolated Subnets The root issue is that your IoT devices can't send WOL packets across subnets. Solutions: Use a router/firewall that supports forwarding WOL packets across subnets (e.g., pfSense or Ubiquiti devices). Configure a relay or intermediate device (on the same subnet as Unraid) to send the WOL packet. For example, a Raspberry Pi or a small VM can act as the WOL relay. 2. Fast Startup Without Sleep or Hibernate Use an SSD for the Unraid boot drive (or a faster USB stick) to minimize boot time. Ensure BIOS is configured for fast POST. 3. Home Automation Tweaks Use a network-connected smart plug with automation rules to turn on the server after shutdown. Some devices can integrate with Alexa or other home assistants to schedule power-on events. Use a Nut/SNMP setup to manage power states intelligently. 4. Suspend-to-RAM (S3) Alternatives While hibernation isn’t supported, Suspend-to-RAM (S3 sleep) might still be an option if you can find a way to wake Unraid: Keep a device on the same subnet as Unraid to send WOL packets. Use an intermediate device to bridge the subnets (e.g., a small firewall rule or a static route). The Bottom Line While Unraid lacks native hibernation, the core problem seems to be around network configuration rather than Unraid's limitations. Addressing the WOL packet issue across subnets is likely the most practical solution. Alternatively, simplifying the boot process can make shutdown and startup less disruptive. Thanks for the thorough explanation. #1 Will look into that. I've just recently implemented a GL-iNET router which is based on Openwrt, so there may be some mileage in your suggestion. But there's something at the back of my mind that it cannot forward a Multicast and that is a challenge across subnets. I could be wrong on that though! #2 Already have that in place #3 Already doing that as my lack-of-wol-from-S3-sleep 'workaround' using a Meross Energy Monitor plug thingy! Works fine but needs Unraid to be powered off, not Sleep. #4 The router can send out WOL packets, but I can't find a way to trigger that like I can using a URL via virtualsmarthome.xyz linked through Alexa. This approach means that Unraid can be woken by anyone from anywhere with the right URL! It's a cool way to automate remotely! Thanks.
December 3, 20241 yr Author 9 hours ago, bmartino1 said: I would explre home automation with esp32 with a wired to motherboard option. to send a smart home comand to compelte teh power button circut for wake words... esp32 and esp home. there are some project floating to wake machine with esp32 and esp home example: https://tristam.ie/2024/1126/ https://esphome.io/components/deep_sleep.html .... or one of these fingerbot thingys. ...... 😄 That would bring the server out of S3 sleep!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.