{"id":177,"date":"2009-10-22T21:09:36","date_gmt":"2009-10-23T05:09:36","guid":{"rendered":"http:\/\/blog.gerrior.com\/?p=177"},"modified":"2011-11-04T09:55:48","modified_gmt":"2011-11-04T17:55:48","slug":"time-machine-thinks-all-iomega-drives-are-the-same","status":"publish","type":"post","link":"https:\/\/blog.gerrior.com\/?p=177","title":{"rendered":"Time Machine Thinks All Iomega Drives Are The Same"},"content":{"rendered":"

A colleague purchased two Iomega 500GB eGo portable hard drives at the Apple Store to use with his new MacBook Pro 15″. \u00a0He set up one drive to be a Time Machine backup drive (Backup<\/em>) and the other as external data storage (Datastore<\/em>). \u00a0The problem was whenever he plugged in Datastore<\/em> the MacBook Pro treated it like Backup<\/em> and would proceed to backup to Datastore<\/em> – the incorrect disk. \u00a0I tried some draconian methods – deleting the .com.apple.timemachine.support, .fseventsd, and the sparsebundle, but Time Machine kept using Datastore<\/em> every time I plugged it in. \u00a0This is in addition to Time Machine using Backup<\/em> every time it was plugged in.<\/p>\n

\n

I fixed the problem by deleting the partition with Disk Utility and recreating the disk partition. \u00a0I believe Iomega has made a mistake in the way they make this product the “Mac Edition”. \u00a0My theory is they are imaging the drive with the same blank image. \u00a0This image contains the token Time Machine uses to identify “what drive is this?” (Time Machine doesn’t use volume name). \u00a0This results in Time Machine seeing every drive in this product line as the same drive. \u00a0When you make a new partition, the drive’s identity token is deleted and a new one created – problem solved.<\/p>\n

Details<\/span><\/h3>\n