The Pegasus: Quirks

I did encounter occasional glitches with the Promise Utility. No show stoppers, but annoying nonetheless. Sometimes when deleting a logical drive I'd get an error telling me that the delete operation failed (even though it didn't):

Refreshing the logical drive page revealed that the drive had been deleted, despite the warning.

Sometimes various fields will be populated with not a number (NaN) instead of the actual data itself. Just as before, refreshing the page in question usually cleared the problem:

The Pegasus itself was most problematic when operating at or near its capacity. In one case I tried filled a 10TB RAID-5 array with 10TB of data. Rather than copy a bunch of large files over and over again, I used Iometer to generate a single 10TB file on the drive. Somewhere around the 9TB marker Iometer stopped writing to the drive. Mac OS X reported a single 10TB file on disk but the actual file was under 9TB in size leaving over 1TB of free space on the drive. I force quit Iometer and tried writing to the drive manually. At this point the drive became incredibly slow to respond. I tried canceling the copy but Finder crashed under OS X. The Pegasus itself actually hung and refused to power down, I had to pull the plug on the device in order for it to power cycle. When I plugged it back in the R6 wouldn't appear under OS X. I had to pull two drives to break the RAID-5 array then delete/recreate the array to get it working again. Of course I lost all of the data I wrote to the drive, thankfully it was just a bunch of repeating bytes created by Iometer. I attempted the same thing again (twice) and couldn't duplicate the issue. I'm going to assume this was an Iometer related issue (or a problem with creating a single ~9TB file on the array), but it's worth disclosing regardless.

The only other time I had an array go bad was when I swapped in four SandForce SSDs and created a giant RAID-0 array. One of the drives simply dropped out of the array, forcing me to delete and recreate the array. As I mentioned earlier, I can't be entirely sure if this is a Promise issue, SandForce issue or a little of both. I never had a drive mysteriously disappear when using the Hitachi drives that came with the Pegasus however.

Other than the issues I've mentioned here, I didn't encounter any problems during my testing of the Pegasus R6.

The Pegasus: Software The Pegasus: Performance
Comments Locked

88 Comments

View All Comments

  • enthios - Thursday, July 28, 2011 - link

    "Ironically isolated from the world around them?" How about wifi and iCloud? With limited storage capacity, there's no need for anything more. iOS devices are simply thin clients - and they work wonderfully as such.
  • NirXY - Friday, July 8, 2011 - link

    Which is 0$
  • Exelius - Friday, July 8, 2011 - link

    Yes, but in this instance, it's not just a dumb wire; there is an IC at each end of the cable. So theoretically, if Intel comes up with an upgraded Light Peak spec, there may well be cables that are capable of faster speeds. I also imagine longer cables become more difficult, and may in fact require fiber optic transceivers built into the cable. This cable also likely costs significantly more to manufacture than a crimped cable, since there's a tiny IC and micro soldering that needs to be done on each cable.

    But yes, in one sense you are right that in a digital bus, higher quality cables do not provide better performance (though I have run into very low-quality HDMI cables that work fine at 720p but refuse to carry a 1080p signal.)
  • repoman27 - Sunday, July 10, 2011 - link

    At the moment, i’m not sure the Thunderbolt host controller has any real legs on the cable. That host controller is already pumping data to each port at the same speeds as the DMI link between the CPU and PCH. Everything in the chain that is connected to it needs to get faster for Thunderbolt to get faster, i.e. PCIe 3.0, DMI 3.0, DP 1.2.

    Also, I’m pretty sure it’s not those little ICs that are making Apple’s Thunderbolt cables cost $49. Like many retailers, Apple knows that cables and accessories (and RAM upgrades) are a great place to stretch profit margins. A quick search of the Apple store for cables and adapters will turn up dozens of genuine Apple offerings ranging in price from $19 on up to $99. So, taken in context, the Thunderbolt cable is actually a mid-priced cable from Apple, not an expensive one. It also means that cheap unbranded alternatives could quite realistically be sold for around $15, ICs and all.

    Regarding your HDMI cable experience, Category 1 or “Standard” HDMI cables are only rated for 1080i60, whereas Category 2 or “High Speed” cables will do 1080p60, 4K, 3D, Deep Color, etc. Older cables weren’t marked as such, and thus YMMV.
  • snakeInTheGrass - Friday, July 15, 2011 - link

    Yeah, the SCSI cables were $75+ easily, you needed terminators, and do you remember the fine SCSI1/2/3 connector differences so you needed adapters or cables with different ends depending on the devices. I still have probably what WAS $500 of cables in my closed.

    Inflation adjusted, these $50 cables are about the equivalent of $15 cables back in those days, so frankly they don't sound too bad, especially considering the fact that it's industry leading performance right now.

    As for comparing to Monster cables, these Thunderbolt cables have controllers built into them and presumably do have to meet tighter tolerances than USB, particularly as they carry 2 x 10Gbps data streams. But you're right that Monster cables are a rip off.
  • flowynn - Friday, July 8, 2011 - link

    I remember those days well. My need for speed SCSI habit was insanely expensive.
  • MonkeyPaw - Friday, July 8, 2011 - link

    It reminds me of FB-DIMMs, an expensive solution that uses additional energy, and the components cost more than devices it replaces. Controllers in the cables AND on the motherboard and peripherals? Maybe the optical solution will make more sense.
  • CrimsonFury - Monday, July 11, 2011 - link

    I thought the initial copper cables didn't need any controllers in them? The impression I got from earlier articles was that Intel said their Thunderbolt implementation could scale to optical in future for greater speeds by releasing optical cables with a copper to optical controller in each end of the cable once controller costs had come down from mass production.
  • MobiusStrip - Tuesday, July 12, 2011 - link

    No, they need optical in the ports and wires.

    By reneging on the light in "Light Peak", Intel effectively killed it. Who knows why they're playing dumb in pretending that they're going to get the industry to adopt Thunderbolt and then turn around and adopt an optical solution right afterward. Just idiotic.
  • André - Friday, July 8, 2011 - link

    I find it especially funny considering that all current Thunderbolt solutions (A/V equipment or storage enclosures) are all in excess of $999 to begin with.

Log in

Don't have an account? Sign up now