Problems running Qx2 as RAID 5 with eSATA ExpressCard

Question

Level 2

204 points

Problems running Qx2 as RAID 5 with eSATA ExpressCard

I'm having an issue where an OWC Mercury Elite 8TB Qx2, set up as RAID 5, "locks-up" -- becomes unresponsive, won't eject, requiring forced shutdown, etc. -- when connected to my my MBP via my eSATA ExpressCard slot. It usually happens within 5-10 minutes of operation almost always involving a READ cycle.

The ExpressCard eSATA card seems to work fine with other eSATA (single drive) devices, and works fine with the Qx2 set up as either a RAID 0 or RAID 10. The issue only shows up when it it set to RAID 5. I'm using QuickBench, 20-100 MB, 100 cycle, Extended Tests to work through this.

I've been working with OWC (supplier of both the Qx2 and the ExpressCard eSATA card), and have had one evaluation session at an Apple Store Genius Bar (their initial tests found nothing wrong), and In summary, here is what we know, and what has been tried:

MBP - 2.66 i7 (Model ID 6,1) 8GB OWC RAM upgrade, 750 GB Seagate Momentus (OWC) HD upgrade.

Repaired, then replaced Qx2 housing (two RMAs).
Replaced eSATA ExpressCard card (entirely different brand of card)
Replaced eSATA cable
Zapped PRAM (many times, during testing and at Apple Store)
Reloaded OS, then reloaded again off of Combo Update Installer (download)
Ran all other updates.
Ran Onyx - various times, as updates occurred.
Reformatted Qx2 (multiple times, as we tried different RAID settings).

At the moment, it seems to be pointing to a problem with the ExpressCard slot on the MBP -- or some sort of firmware incompatibility with this MBP and RAID 5. The "smoking gun" detector would be to try the same set-up with a different MBP 17", but the Apple Store said they did not have a unit available for diagnostic purposes. It was fairly frustrating because they said since this involved so many third party products, there wasn't a lot they could do.

Has anyone had similar issues with RAID 5 on a MBP through eSATA?

Message was edited by: Jess Smith1

17" MacBook Pro i7 (6,1), 8 GB RAM, 750 GB Seagate HD, Mac OS X (10.6.7), OWC Qx2 8 TB RAID 5; Voyager bare drive reader; 2Wire ATT Uverse Router

Posted on Apr 3, 2011 12:51 PM

Reply

Answer 1

Apr 7, 2011 2:52 PM in response to Jess Smith1

I'm having the same exact issue with a QX2 using a 9 TB RAID 5 setup on a late 2010 iMac with the OWC eSATA port install.

I can sometimes get it formatted to 1 hfs+ volume, but if i try "repair disk" on it, it lists a couple of dirty nodes, says the repair is complete, but the progress bar shows only 50% progress and never ends.

Reply

Answer 2

Jess Smith1 Author

Level 2

204 points

Apr 7, 2011 3:40 PM in response to AppleBoy2345

Interesting..... I wonder, now, if there is SOMETHING about the way the Qx2 does RAID 5 that is not handled well by "add-on" eSATA cards or ports.

I will forward this information to the Technical Support folks that have been helping me at both OWC and Apple -- to see if this points to anything.

Thanks for your input.

Reply

Answer 3

Apr 8, 2011 5:55 PM in response to Jess Smith1

I don't seem to have any problems with other settings - I haven't tried the RAID 5 3 drive + spare setting yet, but I'm using 4 Hitachi HDS723030ALA640 (those are the 7K3000 drives), which are recommended by OWC.

I've called OWC tech support once so far, my first task is to zero out the 12 terabytes of hard drive space - so I'm doing that for now. His first indication was that the QX2 itself doesn't really do that much, the controllers on the hard drives themselves do all the work.

My eSATA port is just the OWC 27" iMac upgrade that connects an eSATA connector to the unused internal one (first is to my internal hard drive, second was unused, 3rd is the SDXC port). But I find it interesting that we both are having problems with RAID 5, unfortunately the preferred setting.

Let me know of any progress, I'll do the same.

Reply

Answer 4

Jun 20, 2011 5:21 AM in response to Jess Smith1

Gents,

did you finally solve your Qx2 issues?

I'm also having problems with a new MBP 17" 2011 / Qx2 in Raid 5 via eSata combination.

After initial eSata issues OWC sent me a replacement Slim Cardwhich now mounts correctly without drivers.

And only now am I able to evaluate Qx2 write / read transfer speed using the SpeedTools application.

The values recorded are terrible, even below FW800 standard. OWC recommended resetting one Qx2 (I have two Qx2 enclosures) and erasing.

This resulted in much improved values although still below expectations. I returned the 1.6TB of data back to the Qx2 and was disappointed to see the old
low values being recorded again. However, when I removed and replaced the eSata card the new improved values temprarily returned.

These tests also apply to FW800 where OWC acknowledged that the 27MB/sec read values were too low.

I don't know what to do next. I'm intouch with AppleCare who believe the MBP is in order and I'm also in contact with OWC.
Interestingly, I hooked up my old MBP 15" via eSata to the Qx2 and got quite good results although not optimal. And I also connected the new MBP 17" to an old FW800 drive which returned better results than the Qx2.

Quite frustrating to have this top end system not performing.

Let me know if you have had any developments please?

Reply

Answer 5

Jun 21, 2011 5:54 PM in response to Jackson Cage

I finally gave up on using the Qx2, got a refund. Now I am having problems with a Lacie big4 Quadra 8 TB that I'm trying to run as a 6 TB RAID 5 - and am running into the same exact problems I was having with the Qx2 - apparently my problem lies either with the eSATA upgrade or some obscure OS X problem, and I've pretty much given up on trying to get it fixed - not really willing to send the iMac back to OWC again.

Both items ran great via Firewire 800, though - which means unless you want RAID 1 redundancy, there is no point in these items (for me, at least). I had no problems with another 2 TB Lacie Big Disk Quadra connected to the eSATA port - so maybe the issue is with port multiplication and the iMac SSD sata connector.

Reply

Answer 6

Sep 3, 2012 7:14 AM in response to AppleBoy2345

Late to the party, I know, but I've had major issues with the Qx2 units we have at work as well. I've used them with a Mac Pro over eSATA and an XServe over eSATA and FW800. I have constant random drive failures (that aren't really failed drives) and have the same "won't mount" and "won't eject" issues.

I've always used them as RAID5 (4 drives) but I'm going to try RAID1 next (as close to JBOD and I can get) and see if they're any more or less reliable.

These units are out of warranty so I can't return them. (Purchased by the previous admin here, but they were in sealed boxes when I implemented them)

Major headaches and $1,000+ down the drain, apparently. I would run away screaming from these units if you're in the market for big storage.

Reply

Answer 7

Pixim

Level 1

0 points

Sep 14, 2012 8:23 PM in response to Brian Dieckman

I also have constant random drive failures (that aren't really failed drives) and have the same "won't mount" and "won't eject" issues.

I'm running the unit with four WD 1TB Black. But after a lot of failed disk, I decide to chage all of them.

I put 4 x Hitachi 3TB Desktar 7200 RPM. I'm not able to see the unit in OSX. The QX2 sync light is always blinking (14 hour)... My RAID5 is under construction....

How many time your device need to create your array ?

Reply

Answer 8

Sep 20, 2012 12:51 PM in response to Pixim

After a LOT of communication with OWC we finally came up with a method that appears to work. I have one enclosure functioning after following this procedure but I warn you: it takes a LONG time...

First, make sure all your drives are the EXACT same model. Also, make sure they all have the EXACT same firmware. (This is important)

Second, install the drives, select one of the configurations that you DON'T want to use the drive in. (So if you want to use them as RAID5, choose RAID10. Power on the unit and let it configure the drives.

Third, do a low-level format of the entire volume. (write 0's all over the volume) For my 3TB drives it took 5 days.

Fourth, re-set the unit for the configuration you want.

Fifth, repeat step 3.

The unit has been running without a failed drive for about two weeks now. (3 days was the max before)

That's the only advice I have for you, I hope it works!

Reply

Answer 9

Sep 20, 2012 12:56 PM in response to Pixim

I just noticed that you said the sync (rebuild?) light is flashing for many hours? This should not take very long with blank drives.

This happened to me once when I installed a "spare" drive. I had to take all four drives out of the enclosures, wipe out any partitions that were on the disks then re-installed them.

Reply