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.

Recover your images from your broken CF/SD card

During our last holiday I recognized that my 4GB CF card was not recognized any more by my camera and my mac. I was looking for a recovery service on the net but the prices charged there were too high, so we accepted that the images from 1 day were lost.

I did not reformat the card because I was interested in recovering or searching for a possibility to recover. Today I sat in front of my screen and recognized that I had a linux server now up and running and that there should be tools to read and rescue the data there. I started a more detailed search session for rescuing data from CF cards using linux and I discovered the tool ddrescue, do not mix up with dd_rescue which is a complete different thing. The packagename for installation is:

sudo apt-get install gddrescue

Afterwards you can use the ddrescue binary on your linux machine. I read this article and concentrated on the part just above point 5 in the text where the different rescue steps are describe. You should read the whole text to understand what ddrescue does, but you don’t have to.

What you need for rescuing:

  1. a linux system
  2. a card reader
  3. a shell
  4. ddrescue installed
  5. time
  6. TestDisk application (download the package you will need the photorec binary)

First you have to find out what device is used for your card. Most cards can not be mounted if there is a logical defect causing the behavior. You should do a

tail -f /var/log/messages

to check which device your card is on. Example entry:

Nov 18 08:18:33 raspberrypi kernel: [864751.809897] sd 1:0:0:0: [sda] 7813120 512-byte logical blocks: (4.00 GB/3.72 GiB)

Within my system the card was recognized as the sda device so I had to use /dev/sda. The below commands have been issued one after another. If you get any errors executing the next statement you sometimes have to eject the card an reinsert and the command will work again. Details for the commands you will find in the aforementioned gnu link.

  • Please replace /dev/sda with your device name.
  • Please replace <destination_image> with the full qualified path to your desired destination where ddrescue should create the rescue image file.
  • Please replace <logfile> with the full qualified path to your desired destination where ddrescue should create the log file.

sudo ddrescue -i0 -s50MiB /dev/sda /home/pi/rescue/hdimage /home/pi/rescue/logfile
sudo ddrescue -i0 -s1MiB /dev/sda /home/pi/rescue/hdimage /home/pi/rescue/logfile
sudo ddrescue -i30GiB -s10GiB /dev/sda /home/pi/rescue/hdimage /home/pi/rescue/logfile
sudo ddrescue -i230GiB -s5GiB /dev/sda /home/pi/rescue/hdimage /home/pi/rescue/logfile
sudo ddrescue /dev/sda /home/pi/rescue/hdimage /home/pi/rescue/logfile
sudo ddrescue -d -r3 /dev/sda /home/pi/rescue/hdimage /home/pi/rescue/logfile

You should be patient the different steps can take quite a while. I have not measured the overall process because I did some searching and testing in between. Afterwards I copied the image file to my mac for further processing. If you install TestDisk on your linux system you do not have to this.

Don’t try to mount the image it is a data image only so there will be no success. This image can now be used for image rescue software like TestDisk – photorec.

If you have downloaded the package, extract it in a desired folder and open the terminal. Go to the folder you put TestDisk to and you will find the binary photorec there. Start photorec (replace <image_file_name> with the path and name to your image ddrescue created:

photorec <image_file_name>

The software openes in a DOS like application window where you can move around using the arrow keys and I followed the onscreen instructions, a few minutes later I had my images back

Steps I did within photorec:

  1. Select the media of media listed
  2. Hit enter on proceed
  3. Select unknown partition
  4. Select other if you card is from a digital camera (FAT/NTFS/HFS+…)
  5. next steps are obvious and bang your images are back

This procedure restored almost all images I thought lost. Only a handful images where damaged. So cool. Saved 100 € minimum.

Erste Erfahrungen mit dem iPhone 4s oder das Batterieproblem ;-)

Seit kurzem bin ich Besitzer des neuen iPhone 4s. Nach aller Freude über das neue Teil, Siri und schneller und überhaupt und so hat sich Akku technisch ganz schnell Ernüchterung eingestellt. Trotz Beteuerungen seitens Apple, dass mit dem 5.0.1er Firmwareupdate Akku Probleme adressiert wurden konnte ich hier leider keine signifikante Verbesserung feststellen. Wie kann man feststellen dass man das Akku Problem hat. Apple beschreibt für die normale Benutzung im Standby Modus einen Verbrauch von ca. 0,5% pro Stunde. Das Akkuproblem macht sich schön im Standby Modus bemerktbar, das Gerät zieht trotz Nichtstun kontinuierlich ziemlich viel Saft. Bei mir waren das so ca. 40% über einen halben Tag hinweg was eigentlich nur 6% hätten sein sollen. Ich habe mich dann durch alle möglichen Foren und Berichte gequält und mir schon gedacht Sch**** das Ding hat ein Problem mit der Antenne und ist defekt, bis ich diesen Artikel gefunden habe wo ein fixes Kerlchen herausgefunden hat, dass es offensichtlich kein Hardware Defekt ist, sondern ein Problem beim restoren von Backups gibt. Vorher hatte ich alle möglichen Hinweise auf diverse Services deaktivieren usw. usf. ausprobiert, ohne Erfolg. Die Neuinstallation mit Anlage als neues iPhone und dann alles händisch neu gesetzt brachte mich dann zum gewünschten Erfolg. Gerät ist neu geladen, war 3 h im Standby und steht immer noch bei 100%, somit für mich gecklückt und froh. Also nix an den Einstellungen herumdrehen, ist reine Zeitverschwendung, neues Gerät sofort mit neuer Firmware neu installieren und dann ja kein Restore von einem Backup machen, sondern alles neu einrichten, bis Apple einen Fix für das Problem hat.

Downgrade ios4 to 3.1.3


nachdem ich mir das ios4 am iPhone 3g angesehen habe und ausser den Ordner (sehr praktisch) und einem etwas schnelleren Safari für 3G Benutzer eigentlich nix bahnbrechendes dabei ist, habe ich aus performance Gründen einen downgrade auf 3.1.3 vollzogen. Achtung das geht nur in Verbindung mit einem jailbreak, wenn beim jailbreak das baseband nicht aktualisiert wurde. Ansonsten alles sehr problemlos, pwnage 3.1.5 Version geladen, firmware erstellt, drauf geflasht, ultrasn0w 0.93 installiert (cydia aktualisieren…, reboot, geht schon), fertig. Das einzige was mühsam ist ist, dass man das backup (vorher gemacht) nicht einspielen kann, da hier keine Abwärtskompatibilität besteht offenbar.

Bei Fragen einfach Kommentar einstellen.