I had built an awesome FreeNAS 8.04 box, but little I knew that this was the beginning of all the problems, and these problems had bugged me for two days straight. Noticing how I had not updated my blog in two days? Anyway, it all started with I bought three 3 TB 72000 RPM non-spin down Seagate hard drives, and I installed these three hard drives into an HP Pavilion desktop computer which I had not touched for at least two years. The HP Pavilion desktop computer has had the spec for making a fine FreeNAS box. It got 6 GB of DDR2 SDRAM 800 MHz, a quad core, and everything else wasn’t that important in building a FreeNAS box besides the three 3 TB Seagate hard drives I bought for the sole purpose of starting the building of a FreeNAS box. Before, I had only experienced FreeNAS through virtualization technology (e.g., VirtualBox, VMware, Parallels), and so I had always been eager to start a real FreeNAS box. It was about time, I guess. So, it was a breeze for me to install three 3 TB Seagate hard drives into the HP Pavilion desktop computer, and the installation of FreeNAS 8.04 onto a USB flash drive was also just as easy.
With everything was in place before my FreeNAS set sail, I thought man I got this! Sure, I had it but… Here is the but… I had forgotten that there was a reason for me not to have played with the HP Pavilion desktop computer all along until now. Since the day I had this computer off of Windows 7 addiction and I was too lazy to put Windows 7 back on so I could flash the updated BIOS for it, but without a newer BIOS this computer would freeze on reboot or fresh boot — the BIOS could not even get the chance to boot up and the whole computer would freeze at a black screen. This problem was obviously given me a hard time in putting Windows back on, because 9 out of 10 times, the computer would freeze before the BIOS could even boot, therefore I would not even have the chance to let the computer read the Windows 7 installation disk or USB flash drive. Luckily, I was persistent and finally got the computer to start the BIOS. I quickly installed Windows 7 and crossed my fingers that it would allow me to boot into Windows 7 so I could update the BIOS. This too was a lucky shot, and eventually I had the BIOS updated.
After the BIOS mess was over, I thought now I could use my awesome FreeNAS box with joy. Such joy was never to last, because I kept on asking myself why on earth it took the Macbook Pro over eight or nine hours just to backup around 10 GB worth of data to FreeNAS AFP ZFS share volume. This second incident had me pulled my hair and cursed foully. I should have known better to do the right things first by making sure the basic elements of the problems weren’t the root of the problems. Instead of such I went on impatiently, fixating on that it had to be FreeNAS problem from the start. It took so much of my precious time to diagnose FreeNAS box and so on just to find out my last ditch effort was what I should have done from the very beginning. It was the router’s configuration that had my MacBook Pro sent 1MB worth of data per second. Considering I’m on a Gigabit network, 1 MB per second worth of data transfer had to be one of the lamest things I had ever seen. After readjusted the router’s configuration, I was glad to see that even through WiFi, my MacBook Pro was able to send 14 or 15 times faster (i.e., ethernet connection would be much much faster).
The moral of this story is that you have to think it through before you actually embark on fixing things. Things could be a lot simpler in regarding to fixing computing and networking related matter, but sometimes you might gloss over simple elements and miss the whole show. I had done just that and it was exhausting. To end this blog post of mine, I like to end it with a tip in regarding to how one would go about knowing the data transfer speed between one’s computer and a FreeNAS box. The idea is to use an FTP program like FileZilla and monitoring the upload data rate/speed of a very large file (preferable in Gigabytes) that got transferred from a computer to the FreeNAS FTP volume (i.e., FTP ZFS dataset).
- Setting Up iSCSI With FreeNAS So Any Computer Can Have Additional Virtual Internal Hard Drives (essayboard.com)
- Windows 7 Home Premium And CrashPlan Won’t Support Network Attached Storage As Backup Solution? No Problem! Using FreeNAS ISCSI To Trick Both Into Thinking Network Attached Storage’s Volumes/Partitions As Local Devices So Backup Can Be Done! (essayboard.com)
- How to convert an old PC into a modern server (howto.techworld.com)
- Using FreeNAS With VirtualBox To Create A True Personal Storage Cloud? (essayboard.com)
- Using FreeNAS’s CIFS Service To Allow Local Computers (e.g., Mac, Windows, Linux) To Share Data Within A Local Network (essayboard.com)
- Configuring FreeNAS To Host Time Machine Volume, Allowing Mac Users To Backup Data Across Network Using Time Machine (essayboard.com)
- I Don’t Need A World Backup Day To Remind Me To Do Backups, Because I Rely On Automation! (essayboard.com)
- Free Up Some Hard Drive (Or SSD) Space For Your Mac By Having Spotify Stores Offline Playlists On A NAS Volume (essayboard.com)
- Upload Any File To iCloud, But You Got To Manually Rename The Upload File Correctly! (essayboard.com)
- Tutorial: How to turn old hard drives into a secure file server (techradar.com)