On positives of negative experience


A comment got to me via friend mentioning why am I suddenly so negative about Apple and Macs, which quite surprised me. True, I have had some serious hardware issues in first two weeks of June, but this negative event was about as much positive experience as hard disk crash can be.

Thinking back what I have learned and discovered from this:

– Time Machine actually works
– it pays to plug in the firewire disk with Time Machine backups every day – the two second operation saves a lot of time in long run
– Carbon Copy Cloner is fantastic tool that makes creating bootable copy of your system disk as easy as possible
– I can easily use multiple bootable disks with various versions of OS-X, not only for backing up but also for trying out new things / installs – a kind of “VM on a disk”

The most pleasant discovery is that separation of system files and user data actually works in OS-X. Before, when I had to reinstall Windows, even when I had backup of my data files, it was always a pain because the only way how to get back customizations of installed applications was to reinstall them and re-customize. If the application supported something like export of customizations (e.g. Eclipse “Export Settings”) or had config files and I was lucky to export these or backup copy after each change, it sort of worked. Sometimes. But if application stored the settings in Registry, good luck. IMHO, if there were a competition for most stupid and disastrous software idea, I bet that Windows Registry would get a medal …

What I did kind of lost trust in, are hard disks, especially high capacity notebook size drives. I am currently reviewing my backup procedures across all systems. I have created bootable clone of my daughter’s Macbook hard drive – just in case and start serious think about buying Drobo later this year.

But on operating system side, I am happily staying with Apple and Macs. It is not perfect solution and is certainly not as rock solid and secure as Apple would like the world to believe – the last year record of security flaws, crowned with latest discovery of first trojan and root access hole in ARD proves it more than enough. But it is still – IMHO – closest thing to that ideal I have seen. To qualify that (before I get email from all my friends that happen to be Linux/BSD/Solaris fanatics enthusiasts: I agree that there are better, faster, safer versions of Unix available – OpenBSD, some Linux distros, etc etc. But using Mac is actually fun and pleasant experience, despite of all shortcomings and you can do with it much more than develop in Java or recompile C programs :-). For example run Photoshop or Textmate – none of which works under Linux.

Therefore – Shane – do not hesitate to get a Mac. If my disk crash story made you reconsider, I am really sorry about that. Coffee sometimes ? Email me.

Back to normal


So, after few days working diskless, I am back to normal operation mode. About time, we are late with last episode of screencast …

The copying of external disk went error free and took almost 5 hours (210 GB). Fortunately, the MBP was usable – I did not want to modify too many files, but it was perfect for Web research and writing in Google Docs.

After reboot, the TimeMachine decided that 85 GB needs to be backed up again. This seems like bug in TimeMachine, because I have not really changed much more than few gigs – 4-5 max during the few days.

Spotlight is also quite busy and completely confused – saying that I need to wait over minus two billion hours until it is done with indexing. That’s pretty long – or pretty fast, depending how you see it 🙂

Diskless Macbook Pro


So, I have positive proof that the file system crash of last week was not a software problem in Leopard, but indeed caused by hardware failure. After restoring system from Time Machine, things looked pretty good – everything seemed to work. I was able to re-render the screencasts I have lost – I mean I have lost converted AVI files and MP4 files, not the “source” MOV files. I worked on Mac over Saturday and Sunday. Because my Time machine does not backup virtual machine images, I had even whopping 65 GB of free space :-). I saw a bit more of beachballs, but I thought (wishful thinking) it is because Spotlight is busy rebuilding index …

In some moment of bliss I have asked my son to get and build for me 250 GB external FireWire disk with this beautiful enclosure and on Sunday evening, I tried for the first time wonderful program Carbon Copy Cloner that duplicated the harddrive to external one, promising bootability.

On Monday morning, at customer location I tried to copy VMWare image from network. System froze with beachball and had to be powered off. Same result for the second and third attempt … with only difference that it did not boot back and hard disk started to make that weird clicking sound.

I brought it to Apple service center which confirmed the problem, took out the disk, ordered replacement part and asked me to come back tomorrow. That would cause a problem, as I am attending few meetings in Montreal in next 2 days and need my notebook with me and in working condition.

Fortunately, the bootable external drive trick worked perfectly. After power on, I need to hold Option key and select the external disk – and everything works just fine. I am actually typing this on my Macbook Pro :-). No observable difference in speed, the only annoyance is that I cannot really use notebook in train or anywhere where there is no power supply for the drive.

I am still amazed how flexible is the Mac hardware and how capable is the firmware. Being many years Windows user, before this, an idea of cloning disks and booting notebook from external hard disk seemed pretty far fetched. As they say in Germany – man lernt nie aus ….

OS-X near-death experience


It happened on Wednesday afternoon. I knew something is wrong with my MacBook Pro immediately – when I saw semi-dark screen, unresponsive machine – even mouse cursor was frozen – and heard fans blowing full speed, making the strange, clicking noise coming from inside almost disappear …

OS-X does not freeze too often, but it can happen and as a matter of fact, I have seen it happen before during my almost two years with Mac, so I did not panic. As expected, the Alt-Option trick did not work, so all I could do was to force power off.

But then, after reboot and “bang” sound, neither the rotating circle nor the blue screen showed up. I mean the good blue screen, background color of booting OS-X, not THAT blue screen, of course. Instead, screen stayed grayish and showing No-Entry sign … And again and again …

At first I was pretty sure that the hard disk is gone. But after booting up from install DVD (hold C during boot) and running Disk Utilities “verify” and “repair” disk, it did not find anything wrong with it. It was – according to Disk Utility – perfectly good, healthy disk, which only boot stubbornly returned to the No-Entry sign with each and every boot attempt. It was obvious that I will soon have an opportunity to really test out the Time Machine restore capabilities.

Normally, I plug in the Time Machine backup disk every day after unpacking the notebook at home in my home office – and the magic of Leopard takes care of the rest. As Murphy wanted it, I had been working around the house and in the garden in last few days’ evenings, rather than in my home office where the backup disk is. So it happened that last time I had plugged the disk in was around Saturday night and all changes afterwards were not backed up. Bummer.

The system did not allow Archive and Install option (which copies user data away before install) – it was too little space left, so only option was erase the disk and loose last few days worth of data and changes. Most of the chnages was either stored elsewhere as well (Gmail attachmanents) or at least redoable (some rendered screencasts), but last day work was nowhere else 😦

The good fellas at Carbon Computing (my nearest certified Apple service centre) made me aware of the FireWire mode: you press T during boot and Mac makes the hard disk available as external FireWire device, which can be attached to another Mac and read from it as from any external disk. This feature is supported by firmware and does not need any system installed. I tried it and it indeed worked, but the damage to the file system must have been fairly large, because I could not navigate deeper into the home directory.

After I accepted that one and half day of work is lost, the reinstallation of the OS-X from scratch was very smooth and very fast experience – it took about 35 minutes. After booting up, system offered restore from TimeMachine and after another two hours, almost 180 GB of stuff was back on Macbooks harddrive. My Mac was almost exactly like on last Sunday morning .. The “almost” means that Time Machine does not quite restore every bit and piece because after system update check, Mac downloaded about 1 GB worth of patches from Apple side and required restart after install. The size of the patch indicates that it were most likely roll-ups of the updates from 10.5.0 t 10.5.3 – certainly more that could be missing in last few days – which would mean that TimeMachine does not really backup system files. I also had to re-enable root access and modify my /etc/hosts file to enter symbolic names for the VM’s.

Because I have left out the podcast from the backups, it was pretty annoying to get my iTunes subscription back to normal: the downloaded but not yet listened to podcasts all had exclamation marks, because the iTunes library file was referring to non-existent files, but – because they were in the list, it did not re-download them. I had to delete podcast, resubscribe and re-download the episodes. Oh, well …

I am now back up and running and without any lost files other than those who were lost because of my laziness to plug in the disk. I think I start to see selling point for Time Capsule :-). Time machine is still working and I was listening to loud fans for quite couple of hours while Spotlight indexed all restored content again.

I still do not know what caused the crash: I was doing lots of video re-encoding, so maybe overheating together with very little free space (I was twice close to 99.5% full disk). And maybe there is really something wrong with the disk.

I have read somewhere that people that went through the near-death experience often change their priorities and behaviour. This certainly true with me after this cold shower. My trust to hard disks (in general) is even lower than before – and in panic, I have already caught up with delayed backups of the home server to two separate external hard disks. I will be also setting up bootable copy of the Mac disk (using CCC) as soon as Yan builds for me 250 GB external FireWire disk – I do not want risk that the disk will die again .. And in the meantime, my plugging discipline will certainly be flawless 😉

I have chatted about this with a friend and he asked whether I do not consider returning back to Windows, now when Mac disappointed me so badly and did let me down …

Well – combination of OS-X and Apple hardware is pretty solid combination, but certainly not as rock-solid as Apple marketing would like to make the world believe. I have just experienced a real-life proof that it can crash pretty badly. But I still believe that it is by far the best available option currently available. For variety of reasons.

First of all, the most troubles I had, was caused by me not having good enough backup system. Every system is only as good as the weakest link, which is in most cases the human part of the workflow. If I would have used Time Capsule or at least plugged the disk every day, there would be no loss of data, just about 3-4 hours wait until being operable again. Which is much less than I have spent any time while rebuilding Windows machine. With Windows it took me 2-3 hours to install XP  – with all three hundred twenty seven updates, thirteen reboots and lots of surfing to find latest drivers for all devices from vendor’s sites. And then usually at least one full day to reinstall development environments, java, Visual studio, Office, tools etc from scratch.

Secondly, I never had really good backups while working on Windows – mostly because doing backups was never as easy as connecting a hard disk. As result, I had much larger gaps between backups as nowadays. And considering how much work it was to selectively restore the data … To sum it up: if this would happen on Windows machine, I would probably loose week or more of data not 1.5 days and to be back operational would take at least 1-2 days, not few hours.

And third – while the OS-X was being installed, I was working on my old, beaten Fujitsu LifeBook – and I realized I how much I actually I miss the tools and overall user experience of the Macbook Pro.

On the positive side: now I know from the firsthand experience that Time Machine works (including restore) and I have learned couple of new neat features of Leopard. I never completely realized the possibilities of booting and running system from non-local disks. And I have now very good incentive to fix the broken automatic backups to Amazon S3 – at least as plan B until I buy Time Capsule …

Cocoa Programming for Mac OS X, Third Edition is out


as long as you are Safari Books online subscriber – see it here.

Completely updated with XCode 3.x and Objective C 2.0. The screenshots even show the iPhone project templates, indicating the XCode 3.1 in some places. So far the only difference against reality I have found is not covering the XIB resource format (which is generated by default) and sticking with NIB. This blog entry has good explanation of the difference.

If you are fan of dead tree-ware books, the official publication date is May 2008, so expect it any day :-).

Strangely enough, as of May 4th, the author’s web (The Big Nerd Ranch) does not really advertise its availability (yet)

A false “hang” of Finder


Yesterday, I have noticed interesting thing related to Finder and “beach ball of the death”. Suddenly, for no obvious reason, the top menu became unavailable and cursor changed to beachball every time I moved it there. The Bluetooth mouse stopped responding. Finder stopped responding. All symptoms as if Finder would hanging …

The cause of the issue was crash of unrelated application (iShowU, if you are curious), which brought up the crash report window. For some reason – maybe because it happened while changing spaces – the window was not visible. After closing the window, everything came back to life and even mouse reconnected (after disabling and re-enabling Bluetooth).

So next time it looks like an application did hang, make first sure that no windows expecting input are not open and hidden. Do not rely upon jumping dock icon – with bad luck and Spaces enabled, it is easy to switch the notification off.

The dark screen club


It happened few days ago for the first time: after opening the lid on my MacBook Pro, the machine woke up, but the screen stayed dark. Whatever I did, I just could see cursor and nothing underneath. I had to resort to unthinkable – reboot 😦

Some research showed this is known problem – which is from certain point of view good, because many people found hopefully many workarounds. The more information can be found here, here and here. Very helpfull was also this page.

There are speculations about some software that may be related to the problem. As matter of fact, I have installed after some time of not using it one of the suspects: iStat Pro dashboard widget.

What I have done to minimize chances of reoccurence:

– removed the iStat Pro and Polar Clock screen saver (which was also new install)
– switched off the setting ‘Automatically reduce the brightness of the display before sleep’
– started to switch off the bluetooth mouse before closing the lid (so that BT is off when sleeping)

I have also switched off the “safe sleep” mode which is not of much use as my notebook never stays unopened for longer that 12 hours :-).

So far, everything works OK. Let’s keep the fingers’ crossed …