Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Simple Features, unraid goes to sleep (S3) but wakes seconds later

David1312
in User Customizations

Featured Replies

Hi guys,

 

So am I having a some trouble with the Simple Features Sleep (s3) function.

 

The problem is the server goes to sleep as instructed but it goes into wake up mode about a second later.

 

I'm hoping it is a simple problem, something that some nice forum member could point out for me :)

 

I think what is causing the problem is stated in this section of syslog, unfortunately I don't understand what it's saying :/

 

 

Sep 14 00:42:54 Tower s3_sleep: ==============================================

Sep 14 00:42:54 Tower s3_sleep: command-args=-q

Sep 14 00:42:54 Tower s3_sleep: action mode=sleep

Sep 14 00:42:54 Tower s3_sleep: check array=no

Sep 14 00:42:54 Tower s3_sleep: exclude cache=-

Sep 14 00:42:54 Tower s3_sleep: check network=no

Sep 14 00:42:54 Tower s3_sleep: check device=

Sep 14 00:42:54 Tower s3_sleep: check SSH=no

Sep 14 00:42:54 Tower s3_sleep: check TTY=no

Sep 14 00:42:54 Tower s3_sleep: version=2.1.0

Sep 14 00:42:54 Tower s3_sleep: ----------------------------------------------

Sep 14 00:42:54 Tower s3_sleep: killing s3_sleep process 23382

Sep 14 00:43:02 Tower logger: Enter sleep mode

Sep 14 00:43:02 Tower kernel: PM: Syncing filesystems ... done.

Sep 14 00:43:18 Tower kernel: Freezing user space processes ... (elapsed 0.01 seconds) done.

Sep 14 00:43:18 Tower kernel: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.

Sep 14 00:43:18 Tower kernel: Suspending console(s) (use no_console_suspend to debug)

Sep 14 00:43:18 Tower kernel: sd 7:0:0:0: [sdh] Synchronizing SCSI cache

Sep 14 00:43:18 Tower kernel: sd 6:0:0:0: [sdg] Synchronizing SCSI cache

Sep 14 00:43:18 Tower kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache

Sep 14 00:43:18 Tower kernel: sd 3:0:1:0: [sde] Synchronizing SCSI cache

Sep 14 00:43:18 Tower kernel: sd 3:0:0:0: [sdd] Synchronizing SCSI cache

Sep 14 00:43:18 Tower kernel: sd 1:0:1:0: [sdc] Synchronizing SCSI cache

Sep 14 00:43:18 Tower kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache

Sep 14 00:43:18 Tower kernel: sd 1:0:1:0: [sdc] Stopping disk

Sep 14 00:43:18 Tower kernel: sd 3:0:1:0: [sde] Stopping disk

Sep 14 00:43:18 Tower kernel: sd 5:0:0:0: [sdf] Stopping disk

Sep 14 00:43:18 Tower kernel: sd 6:0:0:0: [sdg] Stopping disk

Sep 14 00:43:18 Tower kernel: sd 1:0:0:0: [sdb] Stopping disk

Sep 14 00:43:18 Tower kernel: sd 3:0:0:0: [sdd] Stopping disk

Sep 14 00:43:18 Tower kernel: serial 00:08: disabled

Sep 14 00:43:18 Tower kernel: serial 00:08: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: sd 7:0:0:0: [sdh] Stopping disk

Sep 14 00:43:18 Tower kernel: PM: suspend of devices complete after 1019.808 msecs

Sep 14 00:43:18 Tower kernel: PM: late suspend of devices complete after 0.123 msecs

Sep 14 00:43:18 Tower kernel: ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.2: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: e1000e 0000:00:19.0: System wakeup enabled by ACPI

Sep 14 00:43:18 Tower kernel: PM: noirq suspend of devices complete after 59.935 msecs

Sep 14 00:43:18 Tower kernel: ACPI: Preparing to enter system sleep state S3

Sep 14 00:43:18 Tower kernel: PM: Saving platform NVS memory

Sep 14 00:43:18 Tower kernel: Disabling non-boot CPUs ...

Sep 14 00:43:18 Tower kernel: smpboot: CPU 1 is now offline

Sep 14 00:43:18 Tower kernel: ACPI: Low-level resume complete

Sep 14 00:43:18 Tower kernel: PM: Restoring platform NVS memory

Sep 14 00:43:18 Tower kernel: Enabling non-boot CPUs ...

Sep 14 00:43:18 Tower kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1

Sep 14 00:43:18 Tower kernel: Initializing CPU#1

Sep 14 00:43:18 Tower kernel: CPU1 is up

Sep 14 00:43:18 Tower kernel: ACPI: Waking up from system sleep state S3

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.2: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: PM: noirq resume of devices complete after 224.423 msecs

Sep 14 00:43:18 Tower kernel: PM: early resume of devices complete after 0.093 msecs

Sep 14 00:43:18 Tower kernel: e1000e 0000:00:19.0: System wakeup disabled by ACPI

Sep 14 00:43:18 Tower kernel: e1000e 0000:00:19.0: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: e1000e 0000:00:19.0: irq 46 for MSI/MSI-X

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: usb usb3: root hub lost power or was reset

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: usb usb4: root hub lost power or was reset

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1a.2: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: usb usb5: root hub lost power or was reset

Sep 14 00:43:18 Tower kernel: ehci-pci 0000:00:1a.7: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: usb usb6: root hub lost power or was reset

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: usb usb7: root hub lost power or was reset

Sep 14 00:43:18 Tower kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: usb usb8: root hub lost power or was reset

Sep 14 00:43:18 Tower kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: pci 0000:00:1e.0: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: ata_piix 0000:00:1f.2: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: ata_piix 0000:00:1f.5: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: JMicron IDE 0000:01:00.1: setting latency timer to 64

Sep 14 00:43:18 Tower kernel: serial 00:08: activated

Sep 14 00:43:18 Tower kernel: e1000e 0000:00:19.0 eth0: MAC Wakeup cause - Unicast Packet

Sep 14 00:43:18 Tower kernel: ata8: SATA link down (SStatus 0 SControl 300)

Sep 14 00:43:18 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

Sep 14 00:43:18 Tower kernel: ata6: link is slow to respond, please be patient (ready=0)

Sep 14 00:43:18 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)

Sep 14 00:43:18 Tower kernel: ata2.00: link is slow to respond, please be patient (ready=0)

Sep 14 00:43:18 Tower kernel: ata1.00: link is slow to respond, please be patient (ready=0)

Sep 14 00:43:18 Tower kernel: ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 14 00:43:18 Tower kernel: ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 14 00:43:18 Tower kernel: ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 14 00:43:18 Tower kernel: ata1.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 14 00:43:18 Tower kernel: ata2.01: ACPI cmd f5/00:00:00:00:00:b0 (SECURITY FREEZE LOCK) filtered out

Sep 14 00:43:18 Tower kernel: ata1.01: ACPI cmd f5/00:00:00:00:00:b0 (SECURITY FREEZE LOCK) filtered out

Sep 14 00:43:18 Tower kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out

Sep 14 00:43:18 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out

Sep 14 00:43:18 Tower kernel: ata2.00: configured for UDMA/133

Sep 14 00:43:18 Tower kernel: ata2.01: configured for UDMA/133

Sep 14 00:43:18 Tower kernel: sd 3:0:0:0: [sdd] Starting disk

Sep 14 00:43:18 Tower kernel: sd 3:0:1:0: [sde] Starting disk

Sep 14 00:43:18 Tower kernel: ata1.00: configured for UDMA/133

Sep 14 00:43:18 Tower kernel: ata1.01: configured for UDMA/133

Sep 14 00:43:18 Tower kernel: sd 1:0:0:0: [sdb] Starting disk

Sep 14 00:43:18 Tower kernel: sd 1:0:1:0: [sdc] Starting disk

Sep 14 00:43:18 Tower kernel: ata6: SRST failed (errno=-16)

Sep 14 00:43:18 Tower kernel: ata5: SRST failed (errno=-16)

Sep 14 00:43:18 Tower kernel: ata7: softreset failed (1st FIS failed)

Sep 14 00:43:18 Tower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 14 00:43:18 Tower kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out

Sep 14 00:43:18 Tower kernel: ata6.00: configured for UDMA/133

Sep 14 00:43:18 Tower kernel: sd 6:0:0:0: [sdg] Starting disk

Sep 14 00:43:18 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 14 00:43:18 Tower kernel: ata7.00: configured for UDMA/133

Sep 14 00:43:18 Tower kernel: sd 7:0:0:0: [sdh] Starting disk

Sep 14 00:43:18 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 14 00:43:18 Tower kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out

Sep 14 00:43:18 Tower kernel: ata5.00: configured for UDMA/133

Sep 14 00:43:18 Tower kernel: sd 5:0:0:0: [sdf] Starting disk

Sep 14 00:43:18 Tower kernel: PM: resume of devices complete after 11165.582 msecs

Sep 14 00:43:18 Tower logger: Wake-up from sleep mode

Sep 14 00:43:18 Tower kernel: Restarting tasks ... done.

 

 

I do know that at some time in the past I was able to get SF to make unraid go to sleep correctly (with the sleep button on the main page) and i was able to correctly wake up unraid with a magic package from an android app on my phone. However that was before I added any plugins (sab, cp, transmissions, sickbeard, plex) and before i had a cache drive and when i was using unraid 5.0 beta.

 

However now, when ever I use the sleep button on the main SF unraid webgui page or the automated sleep function, it will go through the process of putting its self to sleep only to wake up a few seconds later.

 

any help would be greatly appreciated.

 

 

also,

 

I am using the latest stable version of unraid server 5.0, and the latest version of simple features.

 

As for Hardware:

 

Mobo = Intel DQ35JO, supports s3 sleep and wol.

cpu= intel core 2 duo e6550 @2.33 ghz

ram= rambo ddr2 2gb (2x1gb)

psu= antec eco neo 400c

HDD= Parity 'WD Red 3TB', Cache 'Seagate bara 2TB 7,200', 'Array 2x 'WD 2TB green' 3x 'WD 3TB red'

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.