Keeping in mind that the RAIDFrame was designed for disk to disk backups, I tried to look at it from a hardware enthusiast’s perspective. With that said, the whitebox-like design of the chassis is appreciated. Being able to open the case and seeing how simple the system is gives you the impression that the RAIDFrame is easily supportable by whoever buys one. In fact, you can probably build a device similar to the RAIDFrame, but for the effort already invested in the design and assembly of the RAIDFrame and RAIDPac devices, getting something as portable and redundant as the RAIDPacs would be difficult.
Overall, I like the device. The one thing I would have liked even more would have been a tool-less design that provides an easier assembly and disassembly of the unit. It only takes three screws to remove the top cover; however, it would be nice not to have lift a screwdriver to get inside the case. On the other hand, in order to access the disk drives inside a RAIDPac requires the removal of twelve screws (six on top and six on the bottom) that attach the RAIDPac’s outer sleeve to the plastic inner core. Removing all twelve screws is a must if you need to replace a disk drive. Simply be careful not to lose a screw or over-torque the screwdriver and strip the plastic threads holding the case in place. Once removed, you can access the drive cartridges from the front of the RAIDCore’s plastic case. Also take care not to damage the SATA cable linking the drives to the external connector. I realized this as I stripped some insulation off of one of the data cables as I re-attached the rear face plate on one RAIDPac.
Still, with all the screws used to keep the all metal RAIDFrame chassis and its components together, the construction of the device overall is sturdy. From the metal levers used to release the RAIDPacs from the chassis to the snugness of the RAIDFrame’s railed slots, we're impressed with the manufacturing standards Highly Reliable follows in sourcing the parts for this product.
To remove a RAIDPac, you need to push the black release lever located above each of the docking bays on the RAIDFrame.
With regard to physical security, the RAIDFrame provides tiny eyelets on the levers used remove the RAIDPacs from the chassis. The holes are small, and you need provide your own locks to secure the RAIDPacs in their slots. However, the simplicity and accessibility of this design prevents removal by blocking the lever from being pushed into the RAIDFrame. This is a sensible implementation, but you need to find the right sized locks. As of this writing, these are not available through Highly Reliable.
Somewhat related to security, a feature that I wasn’t too keen on was the use of a "key" to remove the drive trays from the RAIDPac’s plastic shell. The provided key is a cylindrical pin inserted into the front panel of the exposed RAIDCore. Inserted, the pin releases the locking mechanism that holds the disk cartridges in place. I’m not sure how much additional security this unlocking measure can provide, especially if you just need a jumbo sized paperclip to get the drive out. After all, you just had to remove twelve screws to get this far.
In order to access the hard drives inside the RAIDPac, you need to insert the provided “key/pin” into the designated hole and push up. When needed, I found a paper clip was just as useful.
One small drawback that I ran into when I first started up the RAIDFrame was a power-related problem caused by shaking during the unit’s shipping. Every time I inserted the second RAIDPac, the first RAIDPac would shut off. As it turns out, the Molex power connectors that come with the included power supplies got a little loose as the system was sent from Reno to Los Angeles. After a quick email from tech support, it was a simple matter to unscrew and lift the top cover off of the RAIDFrame and tightly re-attach the loosened connector to the plastic receptacle that sits behind the RAIDPac bays. For a do-it-yourself type of user, this shouldn’t be a big deal. For a tech novice or someone who doesn’t expect to get their hands a little dirty after buying a storage system, this could be a problem. Still, once re-attached, I haven’t had to re-open the RAIDFrame enclosure.
Molex and SATA connections plugged into the RAIDPac docking boards from within the rear compartment of the RAIDFrame. Though the connections are in place, we had one molex connector that was loosened during shipping.
In the time that I had the RAIDFrame in my possession, I also experienced a drive failure. One of the RAIDPac’s Seagate Barracuda drives included with the system stopped working at start-up. The drive would spin up, but the drive’s cartridge’s indicator light would go red as the RAIDPac continuously beeped. The good thing is that the test data was still accessible on the RAIDPac’s remaining two drives (given its RAID 5 configuration). After several attempts to restart, reinitialize, and rearrange the drives, I confirmed the drive was not coming back by any simple means. Suspecting that the bad drive could be one of the 1TB drives that caused so much commotion earlier this year, I called Seagate support and they directed me to the serial number verification page. After punching in the drive’s serial number, I was forwarded to the firmware update page for this particular model. After downloading the .iso and booting up the test system off of the burned CD, the firmware update still could not find the drive. To keep things going, Highly Reliable sent me an entirely new RAIDPac.
During the testing process, the center hard drive in RAIDPac #2 failed to come up.
As mentioned earlier, one of the nice pluses I give the RAIDFrame Backup System is the Field Service Access feature, where you can take any RAIDPac and plug it directly to your computer just as you would a second hard drive. I went ahead and shut down my test machine, disconnected all other drives except for my boot drive, removed the metal sleeve and rear panel from one of the RAIDPacs, and plugged an available Molex power connector and SATA connecter into the exposed RAIDCore. After booting up the test system, the drives in the RAIDCore spun-up, beeped, and were accessible via the Windows Explorer. Since the RAIDPac was configured for this machine, the assigned drive letter came up according to the HRDM2.ini file. As a quick confirmation, I was able to create a directory on the newly-attached drive and add a text file to confirm write functionality.
One of the RAIDPacs was set up and connected directly to our test PC’s motherboard. Field Service Access (FSA) would be a handy feature to have if you don’t have access to the rack-mountable RAIDFrame.