NewerTech / Vantec GUID problem solved

Okay, it turns out that NewerTech just left one tiny, but significant little tidbit out of their instructions for fixing the non-unique GUID problems with their Voyager Q drive docks (see this post).  You have to manually change the GUID yourself.  Problem solved.  So you can follow their instructions (except be sure not to have a Windows-formatted disk mounted when you do it—see this post) all the way up until they tell you to "select exit".  Before exiting, you should do the following.  (You might have to rescan the USB bus before doing this; I don't know because I never did this all in one setting.)

• Click "Modify Configuration Information"
• Change "Chip ID Lo" from 45647 to numbers of your choosing
• Click "Upload Changes"

I chose to change a couple of digits in the first part of the number, set the lowest digit to zero on the first unit I flashed, and then increment it by one for each additional unit.  It doesn't really matter what you do as long as you never use two units with the same number.

I probably should have thought of this on my own, but a helpful person at NewerTech technical support asked, as his very first question once I'd explained how my update had succeeded but failed to fix the problem, "Did you change the GUID?"  I mentioned they probably ought to add this step to their instructions.

Yay!

Vantec NexStar drive dock firmware

One final tidbit (for now) on the whole drive dock, non-unique GUID debacle...

Despite the Vantec NexStar dock using an Oxford 934DSA bridge and the NewerTech Voyager dock using an Oxford 934DSB bridge (note A vs. B), applying the firmware update provided by NewerTech to the Vantech dock doesn't hurt anything.  Nor does it help.  Before I found out that the update doesn't actually work, I decided to risk bricking one of my Vantecs to see if it could be updated too (having noticed that the binary firmware image did not mention A or B), and luckily it worked.  Well, it didn't hurt anything.  The GUID remains unchanged (just as for the NewerTech dock) at 0x30E002E0454647 and trying to attach multiple docks via Firewire still fails.  Maybe if Oxford Semiconductor and NewerTech ever actually produce a fix that works, it can be applied to the Vantec units as well.  I live in hope.

Update:  See this post for the solution to the NewerTech problem, and, happily, it does work for the Vantec problem.  If you don't want to risk upgrading the Vantec's 934DSA firmware with the 934DSB firmware provided by NewerTech, you could probably change the GUID alone, using the instructions in that post.

Warning about updating firmware in NewerTech Voyager Q

In addition to the firmware update process for the NewerTech drive dock GUID problem (see previous post) needing a few extra steps (see this post), it can also brick your dock (make it completely non-functional), even if you follow their instructions precisely.  Here's how:

You must have a drive inserted in the dock when doing the firmware update, as clearly stated by their instructions. What the instructions don't tell you is that the drive must NOT be mounted on the Windows system being used for the update.

Since my drives are normally formatted HFS+ (journaled) I probably would never have known, except for my using a still unformatted, but coincidentally DOA drive, to do my initial firmware updates.  Due to some other coincidental problems using one of the docks and my having noticed that the drive I'd used previously was DOA (it wouldn't even spin up), I tried formatting a new drive FAT 32 and carrying out the same procedure on the final NewerTech dock I needed to update.  The update failed, after wiping the firmware on the dock, officially turning it into a brick.  Actually, it went into a USB upload mode and awaited firmware flashing as if from scratch.  Fortunately, I was able to find out the flash vendor, type, speed, and burst read setting from another working Voyager device, and I was able to find the appropriate config_934DSB.txt file from the data installed with the firmware uploader app, and after switching back to the damaged, non-mounting disk, I successfully flashed the device's firmware and recovered it completely.  But it was scary and I was borderline clueless when I started that process.  It may be sufficient to unmount the drive (make it "safe to remove") before flashing, but I'm not going to try it.  If you use an unformatted or HFS+ formatted disk it shouldn't be an issue.

If you find yourself with a bricked drive dock, to recover, use the same Oxsemi Uploader.exe app that caused the problem.  Click "Select Flash" and enter the following values for the NewerTech Voyager Q [Vantec NexStar NST-D100UFS values in square brackets]:

• Flash Vendor:  Silicon Storage Technology
• Flash type:  SST39xF020 - 8 bit
• Speed:  70 ns [50ns]
• Enable burst read:  on [off]

Click "OK".  Then click "Upload/Upgrade Firmware".  At the first dialog, navigate to and select the "config_934DSB.txt" file (probably in C:\Program Files\Oxford Semiconductor\Oxsemi Uploader\Data\UF934DS).  [Use the "config_934DSA.txt" file for the Vantec.]  At the next dialog, select the firmware update file, per NewerTech's original instructions.  Let the upgrade finish, and you should have a functioning drive dock again.  Then follow the instructions in this post to actually change the GUID and you've finally solved the problem that started all this.

GUID problems with NewerTech and Vantec drive docks

[Update:  There is a solution for this problem described in this post.  The firmware update is fine, but NewerTech's instructions were just a little incomplete.  I'll leave the rest of this here to document the problem and the process.]

Drive docks, a relatively new innovation, that let you slot a bare SATA disk drive into a dock that looks like a toaster and immediately begin using the drive, without need for a permanent enclosure, are popular amongst the technorati for many good reasons.  They're effortless to use, they avoid duplication of expensive enclosures, and the best of them are highly flexible, allowing you to use any of several connection types (USB, Firewire 400, Firewire 800, and e-SATA).

However, two of what should be the best of these—the NewerTech Voyager Q and the Vantec NexStar NST-D100UFS—were released with the exact same embedded GUID (0x30E002E0454647).  This GUID needs to be unique for each device, or else both Macintosh and Windows machines will barf as soon as two of them are connected.  The problem with the NewerTech docks was noticed and diagnosed as resulting from the non-unique GUIDs over on hivelogic.  I discovered the same GUID lurking in the Vantec docks.  NewerTech / MacSales.com / Other World Computing responded on hivelogic with an announcement of a firmware update that would fix the problem.  I contacted custserv@macsales.com, per their instructions, downloaded the firmware updater at the URL they provided, had to use a Windows box to do the update (Grrrr!), only to discover that the update doesn't help in the least.

The update doesn't seem to hurt the drive dock, but it doesn't change the GUID and it doesn't allow two units to be attached to the same computer by Firewire, either in parallel or daisy-chained.  The email I received from MacSales Customer Service with the link to the update stated that "it will assign a unique ID to each unit".  But it doesn't.   I followed the instructions carefully.  The firmware uploader tool reported success.  Scanning the unit a second time reports V1_20 instead of V1_10.  Attaching it to a Mac, System Profiler reports 0x120 instead of 0x110.  It's clear that the upload worked and the firmware was updated.   But the GUID is the same problematic 0x30E002E0454647 in every unit.  And the problem with instant, error-producing dismounts when attaching two units is unchanged, whether the units are attached to two different Firewire ports or they are daisy-chained into one.   (In fact, now the Mac has to be rebooted before even a single drive can be seen and mounted, after one of these conflict events; I don't believe that was the case previously.)

Unless NewerTech or Vantec provides a solution for this, my only recourse is to return the units for a refund.  Grrrr!