Backing out of update

[dadi_oh]

Well after making the mistake of allowing my Hack to update from 10.6.1 to 10.6.2 before doing some research I ended up with a KP on startup. Seems like I should have deleted sleepenabler.kext before installing the update. The issue is that I have a system with 2 hard drives... one dedicated to Snow Leopard and the other a Windows 7 disk. I just select which disk to boot from the BIOS (although I am spending less and less time in Win7 as I play with SL). The issue is that I can't read the disk from Windows 7 to the level that I would need to repair this issue. I did install Macdrive and that allowed me to see the disk but I'm not sure that I would be able to repair permissions and such.

 

So I have an idea. Why not partition my Mac disk into 2 parts. Install a base level SL on one that will be used as a backdoor in case I screw up the main installation... and another that is the main installation that I play with. I would then just choose which partition to boot (usually the main partition). Then if I mess things up I boot from the backup partition giving me full access to the main partition.

 

Sound like it would work OK or is there something else I should be considering? I do use an external drive for time machine but not sure how I can use that to recover without first reinstalling SL.

 

Open to suggestions.

 

System specs are...

 

P5Q-PRO

Q6600

4GB RAM

500GB Win7 SATA drive

320GB SL SATA drive

DVD-RW SATA

GTX260

[lo-fi]

Hi

 

I do something similar, I have a spare small (40GB) drive that I cloned from my fresh install using 'CCC' (very good free program BTW) So if anything breaks I can just plug it in boot that drive and restore that working image to my main drive. Or use OSX tools from that drive to replace kExts or Kernels etc.

 

Only issue I can see with your plan is how would you repartition your main drive from windows without wiping your existing SL install? Doesnt matter if you dont mind that I spose.

 

Good luck.

 

 

 

If you have a vanilla install did you try booting in safe mode? Non vanilla you would need to boot to a backup kernel or something as the update has overwritten the Kernel. Not sure if any of that would work Im a bit of a noob with Mac stuff even tho Ive been using a hack for a couple of years now.

[dadi_oh]

Hi I do something similar, I have a spare small (40GB) drive that I cloned from my fresh install using 'CCC' (very good free program BTW) So if anything breaks I can just plug it in boot that drive and restore that working image to my main drive. Or use OSX tools from that drive to replace kExts or Kernels etc. Only issue I can see with your plan is how would you repartition your main drive from windows without wiping your existing SL install? Doesnt matter if you dont mind that I spose. Good luck. If you have a vanilla install did you try booting in safe mode? Non vanilla you would need to boot to a backup kernel or something as the update has overwritten the Kernel. Not sure if any of that would work Im a bit of a noob with Mac stuff even tho Ive been using a hack for a couple of years now.

Thanks. That sounds like good advice. I will check into the CCC program. I did clone my drive just using the disk utility in SL but how would CCC be different? I am able to boot successfully from either partition and will just leave the backup one alone so I can always recover to that pristine state. When I broke the installation with 10.6.2 I did try booting in safe mode -x but that didn't work. I ended up just doing a fresh install. A also installed OSXtools and did a backup of my 10.6.1 kernel. That may be another way to back out of any issues. I am indeed using a vanilla install using an excellent guide for the P5Q from IanT on this forum. I went ahead and updated my one machine to 10.6.2 after deleting sleepenabler.kext and fakesmc.kext. Worked fine and I am running 10.6.2 successfully on that machine. So I got bold and decided to try the same thing on my other machine (which is the same motherboard but has a 4870 video card instead of a GTX260). And it didn't work will need to fix that tonight when I get a chance. AFAIK I did everything the same so I'm not sure why it didn't work.