By Joe Wilcox, Betanews

My March started off badly today.

When I was a school kid in Maine, teachers said that if March roared in like a lion, meaning snowy stormy, it would go out like a lamb -- and vice versa. I got the storm in a faulty Snow Leopard rather than the Lion. This morning my 11.6-inch MacBook Air crashed and wouldn't reboot. If not for moving my computing life to the cloud, I would have lost an important day of productivity and lots of valuable data.

My problems started five days ago. Before driving up to the North County area of San Diego for a Sony event, I did something rare: Turn off my computer rather than put it to sleep. When I later hit the power button, I observed something not seen since the hard drive failed in a first generation MacBook Air -- June 2008: A grey screen with Apple logo and progress bar indicating a file system/disk check/repair. The Mac took about five minutes to boot up, because of the check, rather than the more typical 13 seconds.

Of Air and Clouds

Real trouble started a day later and escalated, through several stages of disturbing quirky behavior. Twice during the weekend, the computer shut down without warning; there was no Kernel panic. My main application, Chrome 10 beta, began behaving badly. Early on, tabs would crash, then the problem spread to the whole browser, which by Monday crashed quite frequently. Yesterday I tweeted: "I've never had a beta browser crash as often as Chrome 10. Anyone else? It's horrible on a Mac." But Chrome wasn't the problem.

By yesterday afternoon, other programs crashed, over and over. Everything about the problems felt like a drive failure. But how could that be? The Air has flash memory; there are no moving parts. This morning, I awoke the Air, quickly edited an informative Larry Seltzer story about QuickBooks and prepped it for posting. When I clicked the media pop-up window to add a photo, the computer locked up, except for the mouse/trackpad cursor. It was a frightening d