Contribute
Register

Resume 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
I successfully managed to install Yosemite yesterday and had everything working fine.

I then set the computer to sleep and the went to sleep myself. When I woke up the computer had rebooted and was stuck on this message:
resume from Encrypted image is unsupported
Press any key to proceed with normal boot

I then press a key and the computer start to but but very slowly. And then stops with a grey screen with a prohibitory sign.

I tried to boot verbose, single user and boot from Unibest USB but none of it worked. So I gave up and is now reinstalling my computer

But what do I do to stop this happening again?
 
Same problem here. Was there ever a solution for this?
 
I put Darkwake=0 in org.chameleon.Boot.plist and now it works for me.

But I have an other problem now. See this thread:
http://www.tonymacx86.com/yosemite-desktop-support/146091-can-only-boot-ignoring-caches.html


I was able to solve mine setting both standbydelay and standby to = 0

I think this prevented the hibernate function from writing to disk (SSD) after a certain period of time, even tho technically setting hibernatemode = 0 should have taken care of that.

Hibernatemode 0 = Active RAM only.

Hibernatemode 3 = Active RAM + Physical disk

Either a bug or this was intended with Yosemite?

I will try your method next, but I run clover as my bootloader. Thanks! :)
 
I was able to solve mine setting both standbydelay and standby to = 0

I think this prevented the hibernate function from writing to disk (SSD) after a certain period of time, even tho technically setting hibernatemode = 0 should have taken care of that.

Hibernatemode 0 = Active RAM only.

Hibernatemode 3 = Active RAM + Physical disk

Either a bug or this was intended with Yosemite?

I will try your method next, thanks! :)

I've been thinking about your solution as well. Cant hurt to do both fixes.

And as you say it must be a bug, or?

But I think it's strange that there is not more people with this problem
 
Well, hibernatemode set to 0 is suppose to completely ignore writing to disk.

So both standby and sleep delay should not be applied in this case.

As I understand it:

standby = Write to disk 0 = no, 1 = yes

standby delay = time before it dumps from RAM to Disk.

So yeah, a bug or I am missing something.
 
I've been thinking about your solution as well. Cant hurt to do both fixes.

And as you say it must be a bug, or?

But I think it's strange that there is not more people with this problem


Darkwake=0 did not help for EFI clover.
 
I disabled LAN to wake and also disabled virtualization technology and the problem seem gone. Not sure if this fixed it, but maybe others care to also try? I'm running 10.10.1
 
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- the server goes to sleep and wakes up if any of the client want to access!
 
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- the server goes to sleep and wakes up if any of the client want to access!

None of these suggestions fixed this problem for me.

In fact after the next reboot - have to do so manually - I find that standby mode is back on, i.e. it is again set to 0, and standby delay is back to 4200.
 
Status
Not open for further replies.
Back
Top