Tony Hock Posted October 20, 2009 Share Posted October 20, 2009 I was getting to "DSMOS has arrived" and then it would just freeze. After using the -s option (which I'm not sure what it actually does), it now goes two more lines: NTFS driver 3.0 [Flags: R/W] NTFS volume name Windows, version 3.1. And then freezes. Usng the -x option, It only gets to: com.apple.launced 1 com.apple.launced 1 *** Verbose boot, will log to /dev/console. *** And freezes. These problems only came up after having to hard reset my computer because of a failed sleep Thanks Link to comment Share on other sites More sharing options...
Tony Hock Posted October 21, 2009 Author Share Posted October 21, 2009 So I tried reinstalling the same way I installed the first time and it is no longer wanting to start up, this is odd. Could something have changed after a hard reset that can't be fixed by a complete reinstall? If anyone has ANY insight on this please share. Thank you Link to comment Share on other sites More sharing options...
Tony Hock Posted October 21, 2009 Author Share Posted October 21, 2009 Talking to myself again, hopefully this helps someone out there... Seems as if the EFI section on my HDD got corrupted while trying to sleep the computer. Each time I had had DiskUtility wipe the disk (while trying to re-install) it would neglect to erase the EFI section. Well I formatted the disk in linux, reinstalled 10.6 retail and here I am again, a working install of 10.6 Not sure if it's possible to fix a messed up EFI section without being able to boot into OSX, maybe someone has insight on this to save anyone else the trouble of having to reformat? It would have been too late for me either way. Link to comment Share on other sites More sharing options...
knutselaar Posted October 27, 2009 Share Posted October 27, 2009 Im guessing its not really messed up, but osx tries to resume a hybernate, I fixed it by booting osx with a bootloader installed on another partition. Once rebooted normally all works fine again. (asus maximus extreme btw) Link to comment Share on other sites More sharing options...
TheOriginalPol Posted February 16, 2010 Share Posted February 16, 2010 Tony, I know this thread is a tad old and at this point I'm sure you've either figured it out or given up -- but I'd like to answer your question regardless, for those who might have the same problem in the future. I was having the same trouble recently, and figured out how to fix it. It's pretty easy... The only thing you need is an alternate way to access your OS X filesystem, such as a Windows installation with MacDrive on it, or a bootable OS X USB flash drive, etc. Once you can access your filesystem, simply delete the file "/var/vm/sleepimage". That's it. The problem lies within an OS X feature called "safe sleep". It is essentially the Mac equivalent of hibernation on a PC. So every time your system sleeps, it creates an image file of the state of your system, so that your machine can completely power off and still resume where it left off. However when sleep fails, and your system freezes halfway through the process, that file becomes corrupt and is unreadable -- which is why your bootloader freezes upon trying to read that file (which it does every single time you boot up). If the file is not there, the bootloader simply continues on with a normal boot. So when you delete the bad sleepimage file, it eliminates the problem. Also a fun fact, you can disable safe sleep altogether, thus not ever having to deal with that problem again, by typing the following commands: sudo pmset -a hibernatemode 0 sudo nvram "use-nvramrc?"=false ...and make sure you delete the sleepimage! Link to comment Share on other sites More sharing options...
ltoolio Posted February 16, 2010 Share Posted February 16, 2010 Tony, I know this thread is a tad old and at this point I'm sure you've either figured it out or given up -- but I'd like to answer your question regardless, for those who might have the same problem in the future. I was having the same trouble recently, and figured out how to fix it. It's pretty easy... The only thing you need is an alternate way to access your OS X filesystem, such as a Windows installation with MacDrive on it, or a bootable OS X USB flash drive, etc. Once you can access your filesystem, simply delete the file "/var/vm/sleepimage". That's it. The problem lies within an OS X feature called "safe sleep". It is essentially the Mac equivalent of hibernation on a PC. So every time your system sleeps, it creates an image file of the state of your system, so that your machine can completely power off and still resume where it left off. However when sleep fails, and your system freezes halfway through the process, that file becomes corrupt and is unreadable -- which is why your bootloader freezes upon trying to read that file (which it does every single time you boot up). If the file is not there, the bootloader simply continues on with a normal boot. So when you delete the bad sleepimage file, it eliminates the problem. Also a fun fact, you can disable safe sleep altogether, thus not ever having to deal with that problem again, by typing the following commands: sudo pmset -a hibernatemode 0 sudo nvram "use-nvramrc?"=false ...and make sure you delete the sleepimage! TheOriginalPol - I know that pmset command sets it to the "basic" sleep, but what does the nvram command do? Link to comment Share on other sites More sharing options...
TheOriginalPol Posted February 18, 2010 Share Posted February 18, 2010 Basically, while the first command is disabling the creation of the sleep image, the second is disabling the searching for and use of it at startup. In theory I guess you could use either one of those two commands to fix the problem, but I figure both is best... "The nvram utility is used to view and set Open Firmware NVRAM variables. Open Firmware, (aka non-volatile RAM), controls system boot options. To change a variable, you must run nvram as root." ~Ctrl+V'd from: http://commandlinemac.blogspot.com/2008/12/nvram.html Link to comment Share on other sites More sharing options...
Culprit Posted March 14, 2010 Share Posted March 14, 2010 Thank you for those terminal commands they worked perfectly. I have an Alienware M9750, can anyone point me to the right direction on fixing my sleep so it completely powers off and on? Any help is much appreciated, thanks. I tried searching but nothing for the Alienware. Link to comment Share on other sites More sharing options...
ProOne Posted March 15, 2010 Share Posted March 15, 2010 Hi. I have the same problem on my Acer Aspire 5920G. Haven`t found a sollution for that yet. I was getting to "DSMOS has arrived" and then it would just freeze. After using the -s option (which I'm not sure what it actually does), it now goes two more lines: NTFS driver 3.0 [Flags: R/W] NTFS volume name Windows, version 3.1. And then freezes. Usng the -x option, It only gets to: com.apple.launced 1 com.apple.launced 1 *** Verbose boot, will log to /dev/console. *** And freezes. These problems only came up after having to hard reset my computer because of a failed sleep Thanks Link to comment Share on other sites More sharing options...
aussie08 Posted April 30, 2010 Share Posted April 30, 2010 Biggest Noob ever , can you please Stupidfyit just a little Assuming that my 1year lost my flashdrive with OSX on it. what would be my next choice? meaning How would i access OSX files to make any type of changes describe above? Link to comment Share on other sites More sharing options...
Beerkex'd Posted April 30, 2010 Share Posted April 30, 2010 How would i access OSX files to make any type of changes describe above? The only thing you need is an alternate way to access your OS X filesystem, such as a Windows installation with MacDrive on it, or a bootable OS X USB flash drive, etc.Once you can access your filesystem, simply delete the file "/var/vm/sleepimage". That's it. Link to comment Share on other sites More sharing options...
Recommended Posts