8Dec/111

OCZ Vertex 3 Fail: “Runtime corruption detected on SSD” and why SSD drives are not safe yet.

After almost 9 months with the OCZ Vertex 3 SATA-6GBPs (read about my OptiBay two-drive setup) and mostly no issues, the drive died on me. Starting with several GSOD (Grey Screens of Death) on my OSX Lion MacBook Pro, the drive became more and more unreliable.

Nov 28 18:30:42 mbp kernel[0]: hfs: FindNextLeafNode: Error from hfs_swap_BTNode (node 9852)
Nov 28 18:30:42 mbp kernel[0]: hfs_swap_HFSPlusBTInternalNode: catalog key #54 too big
Nov 28 18:30:42 mbp kernel[0]: hfs: Runtime corruption detected on SSD, fsck will be forced on next mount.
Nov 28 18:30:42 mbp kernel[0]: hfs: FindNextLeafNode: Error from hfs_swap_BTNode (node 10370)
Nov 28 18:30:42 mbp kernel[0]: hfs_swap_HFSPlusBTInternalNode: catalog record #22 keyLength=32 expected=65568
Nov 28 18:30:42 mbp kernel[0]: hfs: node=10965 fileID=4 volume=SSD device=/dev/disk0s2
Nov 28 18:30:43 mbp kernel[0]: hfs: Runtime corruption detected on SSD, fsck will be forced on next mount.
Nov 28 18:30:43 mbp kernel[0]: hfs: FindNextLeafNode: Error from hfs_swap_BTNode (node 14503)
Nov 28 18:30:43 mbp kernel[0]: hfs_swap_BTNode: record #55 invalid offset (0x9B46)

It was getting slower and slower, reporting tons of errors in the Console.app. Then, it did not reboot anymore. Even in an external USB drive enclosure the drive did not mount anymore. Contacting OCZ about this issue, they sent me an RMA number right away and told me they will replace the drive. Does this mean our data is not safe in SSD? What can we learn from this?

First of all, it is a myth that SSDs are more reliable than hard drives. Secondly, they are not even fully supported on OSX yet (see Should I use Trim Enabler on Lion for the OCZ Vertex 3? No!) - at least if you install the drives yourself (which is also what I would suggest, since Apple does not offer any decent SATA 6GBPs drives yet).

So where is the proof, you ask?

Proof #1: The Hot/Crazy Solid State Drive Scale (via Coding Horror)

Super Talent 32 GB SSD, failed after 137 days
OCZ Vertex 1 250 GB SSD, failed after 512 days
G.Skill 64 GB SSD, failed after 251 days
G.Skill 64 GB SSD, failed after 276 days
Crucial 64 GB SSD, failed after 350 days
OCZ Agility 60 GB SSD, failed after 72 days
Intel X25-M 80 GB SSD, failed after 15 days
Intel X25-M 80 GB SSD, failed after 206 days

As a commenter put it: "Average life of SSD = 227.375 days (based on Wills' data)" - which is also what I can confirm.

SOLUTION: Backup early, backup often. Don't rely on the SSD and make two local backups plus one backup in the cloud.

Proof #2: long-term study of SSD failure rates (via Tomshardware)

SSD vs HDD Failure Chart

SOLUTION: Buy drives that come with a very long warranty. Be prepared to let your drive replace for several times.

I am still waiting for my replacement OCZ Vertex and I will benchmark how fast it will die again. Since OCZ told me, it can take up to three weeks for my replacement to arrive, I bought myself a Seagate ST750LX003 750 GB SATA 600, Momentus XT, 8 GB SLC - it's a hybrid 750GB HDD with an 8GB SLC cache. The drive shifts data that is used often in the 8GB SLC SSD space automatically. While the SSD part of this hybrid drive can also fail, the data won't be lost and it will suffer just some minor speed loss (if it fails, since SLC is said to be more reliable than MLC chips). While this disk is now my main startup disk, i will go back to using the OCZ Vertex 3 again, once the replacement arrives. I just need to backup regularly - the speed gain is really worth the trouble.

29Apr/111

MacBook Pro Early 2011 freezes and kernel panics: revert to 32bit to have a stable system

As we already blogged some time ago, we had severe overheating issues and frequent kernel panics with our early 2011 models of the MacBook Pro Core-i7 quad. Still, after the updates there are crashes from time to time - the early 2011 models are far away from being stable machines to use for serious work.

After days of trying to figure out what is really the issue, we found that most of the times device drivers or other third party apps are mostly causing the crashes - but also CPU-intensive apps such as games sometimes bring the system down. Solution? Yes, there is one: change your system to a 32bit Kernel.

1) The bootup way (temporary solution, great for testing)

If you just want to test if changing to 32bit changes anything, you can reboot your mac and hold down the "3" and "2" keys as soon as you hit the power button. This boots up your Apple in 32bit mode temporarily. If the system

2) The Terminal Way (see the Apple Support Document for more information)

sudo systemsetup -setkernelbootarchitecture i386

if you need to change your system back to normal for any case, you can enter the following command into Terminal.app:

sudo systemsetup -setkernelbootarchitecture x86_64

Just to make it clear: your applications will still run in 64bit mode, you can make sure this is the case by hitting cmd+i on the application icon and see if "Open in 32-bit mode" is checked. See this article from simplehelp with details and images on 32-bit mode. So why should I care then, you might ask: since drivers and 3rd party apps and extensions that are loaded on startup are most of the time the issue with system freezes and hangs, changing to a 32bit kernel did the trick for us and now we have a stable 2011 MBP quad-core system.

[UPDATE] 10.6.8 seems to work with 64bit kernel much more stable than 10.6.7. Still, to be on the safe side we are using the 32bit kernel and had no freezes yet.

27Feb/110

Coded Cultures: Creative Practices out of Diversity (Springer Wien/ New York Edition Angewandte)

Coded Cultures: New Creative Practices out of Diversity (Edition Angewandte)

A fresh book, discussing creative practices of the fields of media arts ("art with media" and "art through media") in europe and asia (mostly japan). To quote the official press statement: "International Authors from Europe and Asia explain the impact of codes and cultures on society". The book is available on Amazon EUROPE and the US Amazon site.

25Oct/090

Vague Terrain 15: .microsound

[Ant Scott / Repetitive Beats (detail) / 2008]
Image: [Ant Scott / Repetitive Beats (detail) / 2008]"]

"Vague Terrain is a web based digital arts publication that showcases the creative practice of a variety of artists, musicians and scholars. The project aspires to apply the focus and methodologies of academic and art journals and the tenacity and specificity of independent record labels to examine contemporary digital culture in an immediate and accessible manner. Content consists of curated visual, audio and written works, and now a companion blog. For better and worse this project is neither peer reviewed nor funded."

The current issue of the journal, #15, focusses on the .microsound community and especially on "sub-atomic" musical aesthetics and a window into this globally distributed community of electronic musicians.

"The promise of technology had failed us, leaving us to choose between two paths: the ivory tower of sterile academia or the seizure-inducing din of the dance club. Both paths, with a few exceptions, had become formulaic and resistant to innovation.
As a result, the musical malcontents among us began to look for ways to disrupt, subvert, and deconstruct digital audio in hopes of finding new ideas and sounds within."