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

Determining if the system is under s3 sleep or s1

newbie_dude
in General Support

Featured Replies

Hopefully this is the right spot for this question! I'm using an ASrock 970 Extreme3. When I use the S3 Sleep Plugin to put the system to sleep, the front LED blinks. According to The Manual blinking means S1 Sleep. 

PLED (System Power LED): 
LED is on when the system is operating.
The LED keeps blinking when the system is in S1 sleep state.
The LED is off when the system is in S3/S4 sleep state or powered off (S5).

This seem to indicate the system is in S1 sleep and not S3. This would explain why I can't wake it up using 

etherwake -i eth0 xx:xx:xx:xx:xx:xx

From my raspberry pi. Is there a way to verify what sleep state it's in? I have "Suspend to Ram: Auto" (manual page 50) Selected in BIOS. Or why my Wake on Lan isn't working? I do have "PCI Devices Power On"(manual page 50) enabled in the BIOS as well.

 

Thank you!  Below is an excerpt of the s3_sleep log.  Not sure if it would shed any light:

  

Jan 19 20:00:42 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:00:43 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:00:45 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:00:45 Tower s3_sleep: ----------------------------------------------
Jan 19 20:00:45 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -m 30 -e eth0 -N 0 -D 0
Jan 19 20:00:45 Tower s3_sleep: action mode=sleep
Jan 19 20:00:45 Tower s3_sleep: check disks status=no
Jan 19 20:00:45 Tower s3_sleep: check network activity=no
Jan 19 20:00:45 Tower s3_sleep: check active devices=no
Jan 19 20:00:45 Tower s3_sleep: check local login=no
Jan 19 20:00:45 Tower s3_sleep: check remote login=no
Jan 19 20:00:45 Tower s3_sleep: version=3.0.6
Jan 19 20:00:45 Tower s3_sleep: ----------------------------------------------
Jan 19 20:00:45 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl
Jan 19 20:00:45 Tower s3_sleep: excluded disks=sda
Jan 19 20:00:45 Tower s3_sleep: ----------------------------------------------
Jan 19 20:00:45 Tower s3_sleep: s3_sleep process ID 9973 started, To terminate it, type: s3_sleep -q
Jan 19 20:00:46 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:00:47 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:00:48 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token


Jan 19 20:02:17 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:02:18 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:02:19 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:02:21 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:02:21 Tower s3_sleep: ----------------------------------------------
Jan 19 20:02:21 Tower s3_sleep: command-args=-q
Jan 19 20:02:21 Tower s3_sleep: action mode=sleep
Jan 19 20:02:21 Tower s3_sleep: check disks status=no
Jan 19 20:02:21 Tower s3_sleep: check network activity=no
Jan 19 20:02:21 Tower s3_sleep: check active devices=no
Jan 19 20:02:21 Tower s3_sleep: check local login=no
Jan 19 20:02:21 Tower s3_sleep: check remote login=no
Jan 19 20:02:21 Tower s3_sleep: version=3.0.6
Jan 19 20:02:21 Tower s3_sleep: ----------------------------------------------
Jan 19 20:02:21 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl
Jan 19 20:02:21 Tower s3_sleep: excluded disks=sda
Jan 19 20:02:21 Tower s3_sleep: ----------------------------------------------
Jan 19 20:02:21 Tower s3_sleep: killing s3_sleep process 9973
Jan 19 20:02:22 Tower s3_sleep: ----------------------------------------------
Jan 19 20:02:22 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -a -m 30 -n -e eth0 -N 0 -D 0
Jan 19 20:02:22 Tower s3_sleep: action mode=sleep
Jan 19 20:02:22 Tower s3_sleep: check disks status=yes
Jan 19 20:02:22 Tower s3_sleep: check network activity=yes
Jan 19 20:02:22 Tower s3_sleep: check active devices=no
Jan 19 20:02:22 Tower s3_sleep: check local login=no
Jan 19 20:02:22 Tower s3_sleep: check remote login=no
Jan 19 20:02:22 Tower s3_sleep: version=3.0.6
Jan 19 20:02:22 Tower s3_sleep: ----------------------------------------------
Jan 19 20:02:22 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl
Jan 19 20:02:22 Tower s3_sleep: excluded disks=sda
Jan 19 20:02:22 Tower s3_sleep: ----------------------------------------------
Jan 19 20:02:22 Tower s3_sleep: s3_sleep process ID 10561 started, To terminate it, type: s3_sleep -q
Jan 19 20:02:22 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:02:23 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:02:24 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jan 19 20:02:25 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token



Jan 19 20:23:25 Tower root: plugin: running: anonymous
Jan 19 20:25:49 Tower kernel: i2c /dev entries driver
Jan 19 20:27:28 Tower s3_sleep: ----------------------------------------------
Jan 19 20:27:28 Tower s3_sleep: command-args=-q
Jan 19 20:27:28 Tower s3_sleep: action mode=sleep
Jan 19 20:27:28 Tower s3_sleep: check disks status=no
Jan 19 20:27:28 Tower s3_sleep: check network activity=no
Jan 19 20:27:28 Tower s3_sleep: check active devices=no
Jan 19 20:27:28 Tower s3_sleep: check local login=no
Jan 19 20:27:28 Tower s3_sleep: check remote login=no
Jan 19 20:27:28 Tower s3_sleep: version=3.0.6
Jan 19 20:27:28 Tower s3_sleep: ----------------------------------------------
Jan 19 20:27:28 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl
Jan 19 20:27:28 Tower s3_sleep: excluded disks=sda
Jan 19 20:27:28 Tower s3_sleep: ----------------------------------------------
Jan 19 20:27:28 Tower s3_sleep: killing s3_sleep process 10561
Jan 19 20:27:28 Tower s3_sleep: ----------------------------------------------
Jan 19 20:27:28 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -a -m 30 -n -e eth0 -N 62500 -D 0
Jan 19 20:27:28 Tower s3_sleep: action mode=sleep
Jan 19 20:27:28 Tower s3_sleep: check disks status=yes
Jan 19 20:27:28 Tower s3_sleep: check network activity=yes
Jan 19 20:27:28 Tower s3_sleep: check active devices=no
Jan 19 20:27:28 Tower s3_sleep: check local login=no
Jan 19 20:27:28 Tower s3_sleep: check remote login=no
Jan 19 20:27:28 Tower s3_sleep: version=3.0.6
Jan 19 20:27:28 Tower s3_sleep: ----------------------------------------------
Jan 19 20:27:28 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl
Jan 19 20:27:28 Tower s3_sleep: excluded disks=sda
Jan 19 20:27:28 Tower s3_sleep: ----------------------------------------------
Jan 19 20:27:28 Tower s3_sleep: s3_sleep process ID 18608 started, To terminate it, type: s3_sleep -q
Jan 19 20:37:19 Tower emhttpd: req (3): startState=STOPPED&file=&csrf_token=****************&cmdStart=Start
Jan 19 20:37:21 Tower emhttpd: shcmd (2755): /usr/local/sbin/set_ncq sdb 1
Jan 19 20:37:21 Tower kernel: mdcmd (46): set md_num_stripes 1280

 

  • 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.