Comments (0)

By Johnny, September 5, 2011 1:07 am

Those that work with me or know about my weird obsession with backing up my data and building file storage solution servers will be glad to know that I’ve finally broke the the 1TB mark last month. I’ve finally decided to step up and build a big boy network attached storage (NAS) box. I actually considered buying a Drobo and popping a couple of drives and call it a day. But after helping a friend configure her Drobo, I found the software available for additional features being very lacking for my needs. It was also a pain in the a#$ to configure and relied on the fact that you need special Drobo client software to complete some of the that configuration.

Around the same time, I had helped my brother-in-law build his own NAS box with the extra machine that was lying around at my home. I decided to install FreeNAS 0.7.2 which I’ve played around briefly a few months back. The main reason I went with this version was that it had the ability for him to host movies, pictures, and music files using uPNP (Universal Plug N’ Play) so that he can stream his personal content from the NAS box to his PS3.

For my own purpose, I was thinking about replacing my current file server solution which consists of a Slackware 12.2 server which runs my Samba share for Windows, Fuppes for uPNP for my XBox 360, and LAMP server for my personal Wiki pages. The server contains a 20GB root drive, 250GB mirrored RAID 1 drives, and an externally attached 500GB mirrored RAID 1 drives. It is my primary backup server which serves up movies, photos, & music to the rest of my network. I’ve used up about 80% of my storage on this existing server so far so I think it was a perfect time to think about expanding out. With the possibility of using hardware that was more powerful, energy efficient, and quiet was very appealing.

Unfortunately, I will not be able to do a complete replace of the existing system. The software that I chose to run my NAS box is FreeNAS 8.0. This is the next generation of the software which is primarily built on the ZFS file system. ZFS is a fairly knew concept in which the software uses your hardware and create virtual devices and then device pools to manage your storage needs. It allows you to expand your storage needs similarly to how Drobo does it. This is a huge requirement for my next file server in which it needs to be expandable. I don’t want to go through the trouble of backing things up and replacing hardware and restoring from that backup. The downside of this software is that I lose functionality to share my media to my XBox 360 since uPNP was not available. I’ll also lose LAMP for my Wiki. The only way around this is to add my new build to my server farm of 2.

I carefully picked out my list of parts for the build. I started with four 2TB green drives from Western Digital (WD). I’m usually very hesitant in using WD as my drives but the years that I haven’t been keeping up, Seagate’s quality seem to have withered while WD has made great strides in the large capacity drives. From there I ordered the rest of my system which featured the following items:

• Asus E35M1-I micro ITX motherboard with a passively cooled AMD Dual Core E-350 processor
• 8GB G.Skill RipJaw 4GB x 2 Memory Kit
• Lian-Li PC-Q08 mini tower case which has 6 internal hard drive slots
• Antec 380W ATX power supply
• Verbatim 4GB Store ‘n’ Stay USB Drive

Stay tuned for Part 2 which will explain the build in detail.

Comments (0)

By Johnny, June 18, 2011 2:12 am

I must be a psychic or extremely lucky! After giving away my desktop that I’ve been using for about 1.5 years to my brother-in-law so that he can roll his own FreeNAS server, my RAID 1 hard drive enclosure decided to throw errors in which I was no longer able to access the video files from the mount on the file server. I ran some diagnostic tools and found that one of the drive was not responding well. Perhaps a bad sector or what not.

As if the hard drive Gods gave me a gift, I have the yanked out hard drive sitting on my coffee table for the entire week. Through-out the week, I was figuring what I should do with the extra 500GB but it become more apparent when my 500GB disk array became at risk. I quickly swapped the hard drive out of the tray. The amazing part was that as soon as I popped the drives back in, the enclosure immediately knew what to do to recreate the copy without me doing anything. Apparently, this works because the enclosure checks the timestamp on both disks and the newest one will have their data mirrored. Amazingly enough, the disks were the same exact model and size.

So after I let the enclosure do it’s thing in generating a mirrored drive, I was back in business the next day. I quickly mounted the enclosure back and voila! My data was back and it was redundant again.

I can’t say how glad I am to have a fully redundant data storage system. Big kudos to DAT Optic’s ezRAID enclosure. They really work!

Comments (1)

By Johnny, January 18, 2008 12:09 pm

For those who are technically deficient I recommend turning away from this post. I’m writing this because I couldn’t find any resources regarding this specific problem. Hopefully the spiders creep up on this and puts it out there to help others who are looking for this solution.

This week, Fry’s Electronics brick and mortar store had the Western Digital Cavier SE16 500GB SATA WD5000AAKS drive on sale for $90 a piece. I picked up two for a RAID 1 configuration only to realize from people all over the Internet that this drive has TLER (Time-Limited Error Recovery) disabled. This means that the drive self-corrects errors at a much longer time than normal. These drives are considered consumer drives which are designed for the desktop use. Western Digital would rather have the consumer spend more money on purchasing the RE drives which are more for server environments. The difference in TLER means that one that has it disabled, will correct the errors at a longer interval of time (~2 minutes) compared to others that have it enabled and set for a shorter interval of time (usually 7 seconds). This means that if you have a RAID configuration and your drive has TLER disabled, it will take a much longer time to respond if it is in error correction mode and thus tell the RAID controller that your redundant disc array has failed. This is well documented in some customer feedback on the NewEgg product page.

After further digging, I found that other models such as the RE line of drives have this utility for you to change that TLER values. Western Digital offers this utility on a as needed basis. You would have to get in contact with their support to get it. Luckily, I found this posting that had information on getting this. It also has links to creating a bootable jump drive should you need it.

I tested and confirmed that you can enable the TLER using the utility on the WD5000AAKS drive.

Comments (0)

By Johnny, September 23, 2007 5:46 pm

I got my Seagate 160GB laptop hard drive on Friday in the mail. Needless to say I was looking forward to bump my storage needs from a maxed out 25GB factory drive. I bought the drive refurbished from Computer Geeks online. It cost me about $100 which was alot cheaper than many of newer drives out there even in eBay. What began as a task that I was looking forward to in the week, finally ended now at Sunday evening. Copying a hard drive may seem to be a trivial task, since many people would just reformat and reinstall the operating system and all your software. I didn’t want to do that. I wanted to retain the same exact settings from my previous hard drive and did not want to go through reinstalling. I hate starting over when I don’t have to.

Back when I first worked as a System Administrator, I use to configure and build out similar laptops by first installing and setup 1 laptop with the exact software and settings required. I would then use, at the time, Norton Ghost to image the entire hard drive and saved the image on a server somewhere on our network and then use that image to duplicate on laptops with the same hardware. It was the coolest thing back then and would save alot of time versus setting up and installing manually. I did a quick Google search for “free hard drive cloning” which yielded several references to 2 free Linux-based solutions: Gparted and Partimage. They were both part of a live CD called SystemRescueCD. You use Gparted to setup your new hard drive’s partition and use Partimage to clone and restore a partition.

I could go through the excruciating tasks I had to endure but I’ll save that pain and give you a brief summary of what worked for me.

1. Cloned all three of my partitions from my smaller hard drive to my Linux file server. I did this by booting up the live CD and issuing the following commands:

   mkdir /mnt/samba

   mount -t smbfs -o username:johnny //192.168.0.xxx/johnny /mnt/samba

   partimage -z1 /dev/hda1 /mnt/samba/location/to/image/folder/clonefilename.gz

   I had to turn on DHCP on the rescuecd start-up prompt by executing the command rescuecd dodhcp

2. Physically installed my new hard drive.
3. Executed the following command at the start-up prompt:
   rescuecd dodhcp dostartx This started the X-Windows with a valid network connection.
4. I then used Gparted to partition all my partitions exactly the same as my previous hard drive. This step is important since I actually jumped the gun and partitioned the main boot drive to fill-up the disc’s maximum capacity. This rendered the partition unreadable from Windows XP. It only saw the original 25GB and not the 140GB. I also turned on the “boot” flag for the main partition that had Windows XP and turned the “hidden” flag on the other 2 partitions that wasn’t there in my original drive.
5. I then started the x-term window and executed the command: partimage restore /dev/hda1 /mnt/samba/location/to/image/folder/clonefilename.gz.000. I did this for each 3 partitions.
6. After all my data was restored, I rebooted the system into Windows XP.
7. Windows XP sees the new drive and ask to reboot the system once again after it automatically installed the drive.
8. I reboot again into SystemRescueCD and ran the previous command to start X-windows and DHCP.
9. I opened up Gparted and chose to resize my partition from 25GB to the remaining unallocated disk space.
10. I rebooted to XP again.
11. XP automatically jumped into CHKDSK mode and revalidated the hard drive space.
12. XP then boots into the operating system and finds the new hard drive. I then asked for me to reboot my system once again. I obliged.
13. Voila! My new C: drive is now 140GB.

I probably left out alot of details but the general idea is captured here. I tried so many ways of setting this up which included an attempt to use 1 large partition, setting up a larger partition for the boot partition, etc. All this did was give me blank screens with a flashing prompt. I was never able to boot-up using the other methods. But when I finally followed the steps above, I was successful.

Just a bit of a warning. I’ve been using Linux for over 8 years now so I know my way around the operating system. Doing this requires alot of patience. Hopefully I did most of the grunt work for those who stumble upon this post to use.

My laptop is a Dell Inspiron 8600. The other 2 partitions are backup crap that Dell installs with every new laptop. I tried so hard to not include them in my new hard drive. Unfortunately, I was not able to do that. C’est la vie.