memoryloot

Another post inspired by the lack of information on the Internet. Here’s some background information. I run a Linux file server at home for about 5 years now. I recently hit the 80% capacity of a 200GB hard disk and was looking for more storage on my file server. The file server is a dual processor Celeron 500Mhz with the 200GB in a RAID 1 configuration and about 768MB of memory. That means my data is being mirrored between both drives. In theory if one should fail, I still have the other one. I also have an extensive back-up procedure using 2 external hard drives. I’ll go over that at a later time.

At first I wanted to rebuild my entire system and stick in a couple of higher capacity drives. That didn’t seem feasible since that may cost me a chunk of change and in reality, I don’t need a faster system. Just more storage. I had opened up my system and realized I couldn’t even add another disk controller since I am out of PCI slots. Since I have a Firewire card in the machine and my external drives are attached that way, I decided to see if there are any possibilities of getting a hard drive enclosure with Firewire (IEEE1394a specifically), RAID capabilities, and SATA drive interface. There were many that fulfilled 2 of the 3 features but there was only 1 that had all these requirements met. I even posted a question on LinuxQuestions.org to see if anybody had used this before. Unfortunately no one responded. Instead I was asked to see if I can provide some feedback. So here it is!

I snatched one up at FireWire Depot’s website. I also bought 2 500GB hard drive from Fry’s Electronics which was mentioned in the previous post. For $.18 per GB, it was the cheapest deal around. I was so tempted to get the 1TB drive but decided to save some money. That’s still plenty of storage for awhile.

The enclosure finally was delivered today. So I spent sometime installing and documenting the setup. But first let’s see what is included:

Here are a couple of pictures of the box that arrived

A bit fuzzy but here are the front and rear of the enclosure. The box seems very well built.

Here is what’s included. You get a power cord, Firewire cables (both 400 & 800), USB cable, some screws with the disk lock key, and a sheet of instructions. Pure and simple.

The ports in the back reveals 2 Firewire connections and a USB connection.

Here are both of the disk rack removed from the enclosure.

The enclosure without the racks.

Under each disk rack, there is a fan for cooling.

Empty disk rack. A view from the rear.

Front of the rack with a display and some buttons.

Ok, enough eye candy for now. Let’s see what is needed to get things setup on my Linux Slackware 10 system.

1. I changed the setting on the enclosure to make sure that it treats the disks as a RAID 1 setup and nothing else. The number was suppose to be “0”. You do that by simply pressing on little “-” and “+” buttons with a pen or pencil tip.
2. I changed the jumper settings on my disk to SATA I opting for reliability than performance. Even though the company I bought it from stated that SATA II was supported, the literature did not mention SATA II anywhere. Seeing that so many people are having DOA disk, it seems that they are using the disk in default setting of SATA II enabled.
3. I installed both disk into the drive racks. It took 6 screws to hold a snug fit. The rack had a heat sensor that I had to slip in there. Fairly straight-forward.
   
4. Plugged the drives back into the enclosure and connected the enclosure to my laptop. I powered the enclosure and the laptop on with System Rescue CD booting up (If you haven’t done so, I highly recommend downloading this and burning it onto a CD to add to your arsenal of tools for techie problems.).
   
   Shiny blue lights!
5. Start X-windows and launched gparted. I used this tool to an upgrade of my laptop hard drive a couple of months ago. Excellent tool. It had no problems recognizing the single device. Remember, the OS has no idea that this enclosure is RAID 1.
   
6. Gparted asked me to create a disk-label. I selected MS-DOS, which was default. I did some research and found that this is correct for Linux systems.
7. It then let me create a partition. I selected ext3 since my other drives on the box was ext3. It had no problems creating this partition.
8. I then quit out of System Rescue CD and powered down everything.
9. The enclosure was attached to the file server finally. Before I powered it on, I had to unmount and turn off the other enclosures. I also had create an entry of the /etc/fstab file and create the new mount point.

   /dev/sda1 /u2 ext3 defaults 1 2

   You may notice that this was created on the sda device. Depending on which devices is plugged in and powered first, it will get the first device name. This means the RAID enclosure must always be the first Firewire device plugged in and powered before any of the other enclosures.

10. I finally powered the RAID device on. Unfortunately the system didn’t see the device. I had run the rescan-scsi-bus.sh script. Slackware 10 apparently has a bug that it won’t detect hotplugged Firewire drives without rescanning for it. I had to add the script call in my /etc/rc.d/rc.local file as well as the mount to the enclosure so that it boots up mounted. Why not upgrade to the recent Slackware? Nah! Upgrading to another version is a waste of my time when Slack 10 has been great. It may not be an elegant solution but it’s been working for 5 years now!
11. Rebooted the system to double-check that the enclosure comes up. It did!
    
    Here’s my server with the ezRAID enclosure sitting on top.

All-in-all a very simple implementation. I’m still testing the enclosure by transferring items into and out of it. Symbolic linked a couple of folders that I access through Samba and testing on both a PC and OS X system. I am streaming videos and music off of it. So far so good. Hopefully no dead hard drives. If so I’ll note it in another post.

**Edit 01/20/2008: This post is linked from the following website: http://technology.anything08.com/setting-up-an-ezraid-enclosure/. This looks like a generic blog that someone put together that takes posts from various blogs online. It thinks that this site is called Patrickâ??s Notebook? I did a quick whois search and found that it is owned by NameCheap.com. Looks like a parked site from a domain company.

This entry was posted on Sunday, January 20th, 2008 at 2:13 am and is filed under Technology, How-To. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.