-
All replies
-
Helpful answers
-
Dec 14, 2015 10:44 AM in response to CC105by dimitrik_fr,I've digged little more the issue with compression, and seems like Apple simply mentioned that none from "default" configurations are supported anymore since yet back to Yosemite.. So, having compression disabled (or having any other variations around is going off the "supported" perimeter, and just ignored by Apple).. Pretty curious for me as engineering position, because the bit-masks related to compression (and other paging options) are well presented in the kernel code and not ignored -- so, not clear at all for me why then considered as not supported for a final user..
Keeping this all in mind, the most proper fix here will be simply to clean-up your boot options and leave OSX to decide itself what it'll do by default :
$ sudo nvram boot-args=""
Also, curiously for me the update from 10.11.1 to 10.11.2 did not finished correctly -- my MBP was frozen on update reboot and remained blocked somewhere in boot process + having screen blinking periodically.. Was lucky finally to try it on my test HD partition rather on the main one -- was able to solve it again only by erasing the partition, clean install of OSX 10.11.2, then data restore from Time Machine.. The whole process on the test partition already taking easily more than 4 hours (while it's pretty small, only 20GB, mostly apps to test) -- can imagine the time I'll spend if one day I'll need to do the same with my main partition data..
finally found pretty useful "verbose" boot mode (press CMD+V on boot) -- gives at least an idea about each boot phase and where it's blocked (if any) -- preparing to be better armed for the next future freezes ;-)
fro the moment still staying with Mavericks.. - let's see if 10.11.3 update will be any better
Rgds,
-Dimitri
-
Sep 19, 2016 1:27 PM in response to dimitrik_frby happaro,Great! Finally i've found the right answer, it works for me, thank You very much