PEGASUS2 R6 LOGICAL DRIVE DEGRADED MAC OS X

gavbon86: A leak has a reliable and credible source, a rumour is what someone has seen/heard and regurgitated it.We have been shortlisted and are finalists for ‘Newcomer of the Year’ at this years North Eas… gavbon86: RT LOVELY NEWS ANNOUNCEMENT ☺️.gavbon86: A great man and someone who has been a mentor to me, a good friend over the years, and an inspiration, Dr taught me this.Other than the issues I've mentioned here, I didn't encounter any problems during my testing of the Pegasus R6. I never had a drive mysteriously disappear when using the Hitachi drives that came with the Pegasus however. As I mentioned earlier, I can't be entirely sure if this is a Promise issue, SandForce issue or a little of both. One of the drives simply dropped out of the array, forcing me to delete and recreate the array. 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. 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. I attempted the same thing again (twice) and couldn't duplicate the issue. 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 had to pull two drives to break the RAID-5 array then delete/recreate the array to get it working again. When I plugged it back in the R6 wouldn't appear 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. I tried canceling the copy but Finder crashed under OS X. At this point the drive became incredibly slow to respond. I force quit Iometer and tried writing to the drive manually.

PEGASUS2 R6 LOGICAL DRIVE DEGRADED MAC OS X

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. Somewhere around the 9TB marker Iometer stopped writing to the drive. Rather than copy a bunch of large files over and over again, I used Iometer to generate a single 10TB file on the drive. In one case I tried filled a 10TB RAID-5 array with 10TB of data. The Pegasus itself was most problematic when operating at or near its capacity. Just as before, refreshing the page in question usually cleared the problem: Sometimes various fields will be populated with not a number (NaN) instead of the actual data itself. Refreshing the logical drive page revealed that the drive had been deleted, despite the warning. Sometimes when deleting a logical drive I'd get an error telling me that the delete operation failed (even though it didn't): No show stoppers, but annoying nonetheless. The P4 didn't suddenly get slow or malfunction - the difference is in the benchmark programs.I did encounter occasional glitches with the Promise Utility. You cannot compare the results of one test like AJA to a different test like BlackMagic or QuickBench.Į.g, on my 8TB P1 R4 with 4x2TB Toshiba drives in RAID 5, QuickBench Large gives a read rate of 830MB/sec, yet the AJA 'Read Existing File' test on a 5GB file only gives about 430MB/sec - on the exact same hardware, run within 60 sec of each other. Sometimes it's unclear what the user-adjustable parameters even do.Įven running the same test on different machines means nothing unless that test is configured identically on both machines. So besides the parameters you typically cannot change (such as # of async I/Os and I/O size) there may be user-adjustable parameters you *can* change, such as file size. Oftentimes tests (such as AJA) have many different configuration parameters.

This makes it difficult for users to compare disk benchmarks - you have to run the exact same test, configured the same way. They can vary in number of threads used, I/O size, number of overlapped (async) I/Os, what caching request flags the API submits, etc. The fact that each different benchmark program often produces radically different numbers on the same hardware indicates the source of variability. This more likely reflects the characteristics of AJA System Test, not the P2 R4 capability.

Pegasus2 r6 logical drive degraded