Contribute
Register

resuming from encrypted image is unsupported

Status
Not open for further replies.
Joined
Feb 11, 2010
Messages
238
Motherboard
Gigabyte Z170N-Wifi
CPU
Intel i5 6600K
Graphics
MSI GTX 1050 TI 4GT LP
Mac
  1. MacBook Pro
  2. Mac mini
Mobile Phone
  1. Android
  2. iOS
When my computer has been sleeping for a longer time (17hours this time) it wakes from sleep but monitor does not work. So I have to force off the computer by holding the power button. Next time I boot I get the error message shown in the picture.

I cant find the setting for "Use secure virtual memory" under "security" i System Preferences

I have a standard install. No special settings. I have had this problem 2 times. First time I was unable to boot the computer and had to reinstall Yosemite. I did not have this problem while I was running Mavericks
 

Attachments

  • IMG_20141021_174207.jpg
    IMG_20141021_174207.jpg
    547.4 KB · Views: 146
Same issue here. What bootloader are you running? This is happening with clover on my system.
 
Same issue here. What bootloader are you running? This is happening with clover on my system.

Runing on Chimera from Multibeast 7,0

What motherboard do you have?
 
From what I can see in the logs computer went to sleep 23:28 and woke up again at 01:16

2014-10-21 23:28:20,000 kernel[0]: Ethernet [RealtekRTL8111]: Link down on en1
2014-10-22 01:16:19,000 kernel[0]: Wake reason: RTC (Alarm)
2014-10-22 01:16:19,000 kernel[0]: RTC: Maintenance 2014/10/21 23:16:18, sleep 2014/10/21 21:28:20
2014-10-22 01:16:19,000 kernel[0]: Previous sleep cause: 5


Then I see this:

2014-10-22 01:17:07,000 kernel[0]: Wake reason: RTC (Alarm)
2014-10-22 01:17:07,000 kernel[0]: RTC: Maintenance 2014/10/22 01:05:05, sleep 2014/10/21 23:17:07
2014-10-22 03:05:06,000 kernel[0]: RTC: PowerByCalendarDate setting ignored
2014-10-22 03:05:06,000 kernel[0]: RTC: PowerByCalendarDate setting ignored
2014-10-22 03:05:06,000 kernel[0]: Previous sleep cause: 5


And then it tries to hibernate, wish is strange since I have turned off hibernation (hibernatemode 0)

2014-10-22 03:05:54,000 kernel[0]: PM response took 1993 ms (27, powerd)
2014-10-22 03:05:54,000 kernel[0]: hibernate image path: /var/vm/sleepimage
2014-10-22 03:05:54,000 kernel[0]: efi pagecount 226
2014-10-22 03:05:54,000 kernel[0]: hibernate_page_list_setall(preflight 1) start 0xffffff81e986d000, 0xffffff81e9a67000
2014-10-22 03:05:55,000 kernel[0]: hibernate_page_list_setall time: 367 ms
2014-10-22 03:05:55,000 kernel[0]: pages 1740955, wire 254878, act 746757, inact 81336, cleaned 0 spec 15, zf 12755, throt 0, compr 0, xpmapped 0
2014-10-22 03:05:55,000 kernel[0]: could discard act 71024 inact 148371 purgeable 51295 spec 374524 cleaned 0
2014-10-22 03:05:55,000 kernel[0]: hibernate_page_list_setall preflight pageCount 254878 est comp 50 setfile 570425344 min 2147483648
2014-10-22 03:05:55,000 kernel[0]: [0x63499b000, 0x19000000]
2014-10-22 03:05:55,000 kernel[0]: [0x65cd97000, 0x32000000]
2014-10-22 03:05:55,000 kernel[0]: [0x6bc819000, 0x19000000]
2014-10-22 03:05:55,000 kernel[0]: [0x6ecab2000, 0x1c000000]
2014-10-22 03:05:55,000 kernel[0]: [0x0, 0x0]
2014-10-22 03:05:55,000 kernel[0]: kern_open_file_for_direct_io(0) took 1 ms
2014-10-22 03:05:55,000 kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0x0, maxio 2000000 ssd 1
2014-10-22 03:05:55,000 kernel[0]: hibernate image major 1, minor 1, blocksize 4096, pollers 5


This is the output of "pmset -g"
Active Profiles:
AC Power -1*
Currently in use:
standby 1
Sleep On Power Button 1
womp 0
autorestart 0
hibernatefile /var/vm/sleepimage
darkwakes 0
networkoversleep 0
disksleep 10
sleep 10
autopoweroffdelay 14400
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 10
standbydelay 4200
 
I was under the impression that when hibernate mode was set to hibernate=0 it would completely ignore writing to disk and it would store to the active RAM. (Which in turn would cause data to be lost if power went off completely, for example)

What I think is happening is that after a period of time the system will fall back to storage disk and when we try to resume we are running into the encrypted image issue. I am unsure if it is a currently a bug or the way it is intended to work with Yosemite.

Possible (temp) solutions:

1. standbydelay = 4200 variable I am going to assume is the time it will take from the system to transition from RAM to Disk during Hibernation/Sleep mode. < --- I'm not sure about this one, I could be wrong.

Play with that and see what happens, try to increase it or disable it all together.

2. Fix encrypted swap.


I tried sudo defaults write /Library/Preferences/com.apple.virtualMemory DisableEncryptedSwap -boolean yes and also removed /var/vm/sleepimage with the hopes of a corrupted image and still no luck.

I would like to know why we are having a problem with the encrypted image on resume.


Last thing I wanted to say is you can replicate all this without waiting for the delay, just pmset -a hibernatemode 1 and when you try to resume you will see that you will be getting the "resuming from encrypted image is unsupported" error.


My motherboard model is the gigabyte b75m-hd3
Hope that helps,

-JB
 
Hi,
I run Yosemite (chameleon bootloader on a asrock b75m-itx) as a fileserver with access from 3 Macs, xbmc and AppleTV3.

I successfully managed the ugly "Resume from Encrypted image is unsupported" problem by adding
Darkwake=0 in org.chameleon.Boot.plist

Additionally I had to set hibernatmode, standby and standbydelay to 0

You can check your current states in terminal using following commands:

pmset -g |grep hibernatemode
pmset -g |grep standby
pmset -g |grep standbydelay

If you had to change the states you can do this with following commands:

sudo pmset -a hibernatemode 0
sudo pmset -a standby 0
sudo pmset -a standbydelay 0

Now everything work like a charme- no more "Resume from Encrypted image is unsupported" which prevented the wake up occured.
The server goes to sleep and wakes up if any of the client want to access!
 
Status
Not open for further replies.
Back
Top