Tiring problem with failed bluetooth reactivation after sleep in osx yosemite

Some of you experience the problem of bluetooth devices which can not reconnect after a sleep period of osx yosemite. This is a known problem a bluetooth kext unload and load solves the problem (like bluetooth subsystem restart) but there is no path from Apple there until now. Some of you have built up some shell scripts and are using sleepwatcher and so on but some of you just want to get it to work again. Therefore I have built up a little application which is just an automator wrapper around the following two shell script lines:


sudo kextunload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport
sudo kextload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport

which does the trick for you. You can fully trust this and you can also look into the package, no hidden hocks there. Drop the application to your app folder and everytime you experience the problem start the app, the bluetooth will go away and come back again reconnecting all your devices. Link to 7zip archive with app. Please download the prior link by right click and download linked file to…

Best Regards.

Restoring a hanging osx system with all your data

Hi I had a problem recently with the osx system of my daughter. The SSD disk I built in 1 year ago started to get corrupted file systems. Long boot times (gray progress indicator), failing fck calls have been the result plus at last a system which won’t boot any more. I had no current backup of the system so there was also the problem of the data.

Luckily I had a ccc (carbon copy clone) of my own system. So all you need is the following:

  • usb disk/stick with a ccc clone of a working osx
  • usb disk/stick for the clone of the broken system
  • a little time at your hand
  1. Boot up the system holding the „shift“ key on startup. Afterwards you will get a list of volumes to boot from, select the ccc clone of your working system.
  2. When the system is booted open up ccc and create a recovery partition on the destination usb disk you will use for the clone of the broken system, remind to select the matching osx version.
  3. Clone the entire disk content using ccc from the broken system to your prepared destination usb disk, this may take a while regarding the amount of data you have on your broken system.
  4. After cloning succeeded, open up disk utility and reformat the disk of the broken system. Remind to check the GUID partition table option and use the journaled HFS filesystem type.
  5. Now open up ccc again and clone the content from the prior cloned broken system back to the new formatted harddisk of the system. After finishing this, reboot the system.
  6. Hold down „CMD“ + „R“ to boot into recovery mode. Once there select „Reinstall OSX“, this will again take a little time but afterwards you will be rewarded by a system working the same way as it has before stopping booting. No user data lost, no settings lost, everything is fine.

Corrupted OSX filesystem – mac constantly shutting down on startup

Hi if you have experienced the following behavior of you mac there has to be something wrong with your filesystem:

the grey progress bar is coming up on startup (fsck is running long in the background)

a little later (days, weeks) the mac is shutting down short after progress bar appears

you may have a corrupt BTree in your filesystem. This is normally a sign that your hard disk fails and will soon die. But you want to make a backup but can’t right?

Then do the following:

  1. Right after switching on press CMD + S for entering single user mode
  2. on the command line enter: fsck -f
  3. mount the filesystem: mount -uw /
  4. check what name your disk device has by entering: df -hl (there should be an entry like /dev/disk0s2, note it down)
  5. reboot into safe mode
  6. type the following: fsck_hfs -y -rc -d /dev/disk0s2 (what you noted down earlier)
  7. wait for the process to complete. If the message „The volume…. could not be repaired after 3 attempts“ appears repeat step 6 until you get the message „The volume…. was repaired successfully“
  8. reboot your system
  9. Voila