background preloader

Mac HD fix

Facebook Twitter

Time Machine - cant boot after full system restore. After two days parsing forums, i solved this problem!

Time Machine - cant boot after full system restore

Extract attached file on FAT or FAT32 flash drive and name it "FLASHKA" (you can use another name After time machine restore, boot again from install DVD, insert flash drive "FLASHKA", run Terminal and type: diskutil list Found in this list your leopard restored partition (For me is "disk0s2" and named "MacHDD") Making partition active (2 - is my patition number (disk0s2) fdisk -e /dev/rdisk0 update f 2 w q. Startup key combinations for Intel-based Macs. Snow Leopard clean install + restore from Time Machine. I've just installed Snow Leopard (OS X 10.6) on my Unibody 13.3" MB.

Snow Leopard clean install + restore from Time Machine

Everything works perfectly fine. What I did step by step: Updated Time Machine backup (on external USB 2.0 HDD).Booted from Snow Leopard retail ($29) installation disk (I had to hold "C" key during boot to force boot from DVD)Ran Disk Utility (from Utilities menu) and erased my Macintosh HD partition.Ran standard installation on clean partition.Created user test.Installed X11 and XCode from installation DVD.Installed iLife from my Leopard 10.5 installation DVD (bundled with my MB).Updated everything to recent version (I'm still stuck with iLife 2008).Installed software that I use (mainly VMware Fusion, Textmate, Transmit, NeoOffice and macports stuff).Ran Migration Assistant and restored my user and system settings (without applications) from my Time Machine backup.Removed user test. Everything works 2x faster. VMWare Fusion works with my 64-bit guest systems. iPhone syncs ok.

Making a USB Key Bootable in OS X. Hi, I was trying to do exactly the same thing and i did this in order to create my TD from an .ISO file. In TERMINAL: --------------------------------------------------------------------------------------- $ mount --------------------------------------------------------------------------------------- (you will get a list of volumes that are mounted, you will be looking for your thumb drive, yours might look something like this) /dev/disk1s1 on /Volumes/UNTITLED (local, nodev, nosuid) In my case the TD was "/dev/disk1s1" so i'm going to use this for the terminal commands in this example. --------------------------------------------------------------------------------------- $ diskutil umountDisk /dev/disk1 --------------------------------------------------------------------------------------- For people like me that are new to terminal you can actually drag and drop the .iso file on the terminal window once you're at the point where you need to enter in the path for your .iso.

Help: Macintosh HD could not be repaired. OS X - Repair disk errors like invalid node structure. If you're an OS X user you may have run into a problem like this before. When you power on the machine it just sits on the Apple logo screen but won't get any further. Other boot up problems may be fixed by this as well. If you try to boot from the install CD and run disk utility to repair permissions or repair the disk, you may get an error such as invalid node structure or something similar that will cause the repair to fail. One solution to this is to reformat the hard drive, reinstall the OS, and then reinstall all the programs.

This is time consuming, and you'll lose all of your data if it hasn't been backed up. 1. At this point your problem should be gone and the system should act normally. A DIY solution to an invalid node structure problem. Background. About a month ago, I ran into a problem with Dashboard behaving oddly and after posting a question on the Apple forum, the very helpful Dr Smoke advised me to clear my caches and to run the 'repair disk' feature of Disk Utility while booted from the installation CD. (This because I reported that a couple of times I had to do a hard reset.) I got Dashboard fixed, but discovered that my disk had serious errors in the directory structure, reported as "invalid node structure," which Disk Utility could not repair. The laptop was running perfectly, but several people posted advice that I should not leave this problem unattended to. Reporting this crisis again on the forum, I was advised to buy Disk Warrior for what might be a once-in-a-lifetime problem, or else I should back up my data and re-install everything.

[robg adds: What follows will seem simple and obvious to those who have cloned and restored systems before. Here are all the steps I used to clone and restore my system: