SIX OR FIVE YEARS AGO getting a "Network Attached Storage" (NAS) device, that is, a hard drive appliance that you just plug on a network and can be accessed from any machine in your home or office LAN was expensive, very expensive. The first generation devices like Intel's "inBusiness Storage Station" were introduced with a $999 price tag, and those were in fact full PCs in a custom enclosure the size of a small shoe box, just lacking a video card inside. In the case of Intel's NAS, it had a Pentium I MMX cpu and a pair of mirrored 5,400rpm IDE hard drives running FreeBSD. I managed to purchase one of those about three years ago from a closeout store for one fifth of the original price, and I can say that it was one of the best investments I've made.
Introduction, and why standards matter
Sadly for early adopters like myself and luckily for you, these days there are "network attached storage" devices which can be bought for much less money. So when the 30GB FreeBSD powered box started showing the dreaded "disk full" messages, it was time for me to start looking for alternatives. The first units that caught my attention were Ximeta's "Netdisk" products, which are currently selling for as low as $135 greenbacks for a 80 GB model. But I quickly realized that such a low price came with a catch: Ximeta's proprietary and patented "NDAS" technology means its hard drives require special drivers on each machine in your LAN in order to work, so forget about accessing your shared drive from that black sheep machine in your LAN that is running Solaris x86, Netware, OS/2, BeOS or any-other-new-or-ancient-OS not blessed by Ximeta. That is, unless you're comfortable with getting forever-beta drivers for linux (that only work on certain kernel versions), and Mac OS-X as the only supported non-windows OSs. When INQuired about this important issue, a company representative told me "The reason that we do use are own protocol is that our Netdisk does not have a OS or processor that NAS devices have". Oh well...
It was clear for me then that I wanted something standards based. Something based on SMB networking (also known as CIFS on windows or Samba in linux, or NETBEUI in OS/2) would suffice and here's where Broadcom came to the rescue. Last year the company introduced its "NAS on a chip" ("NASOC") solution, a chipset with a 300 Mhz MIPS core that implements both standards based SMB networking (CIFS/SAMBA) and NFS (Network File System) on a chip, thus getting instant compatibility with about every operating system on earth, from obscure/ancient Unix like SCO or AIX to every flavour of linux, FreeBSD, Windows, MacOS-X, Netware, Solaris 10 x86, OS/2, you-name-it.
And among the first companies to release NASOC based storage devices was SimpleTech. So here's my complete review of the affordable and compatible Simpleshare (160GB version), one which has been three months in the making.
The Simpleshare unit and the included "folded poster" setup guide
Beauty, expansion and compatibility
First let's talk about the looks: the unit looks very nice due to its small design (even smaller and thinner than an external cd-rom/cd-rw/dvd-rw enclosure box), its nice aluminium enclosure, its quiet fan-free operation, the ability to place it both vertically using a pair of plastic stands, or horizontally. Expandability is assured due to the unit's pair of USB 2.0 connectors in the back. But more on that below.
Connectors in the back of the Simpleshare
Inside the beast
If you're not a computer geek, feel free to scroll down to the next section. As a computer geek, I call a hardware review done, specially if it's this interesting, without opening it up and taking a look at the guts of the device. In the case of SimpleTech's device, what I saw was beauty and simplicity... there's the IDE hard drive (for the record a Hitachi Deskstar model HDS722516 marked as 7,200 rpm and with size as 164.7GB, made in Thailand in Dec '04 on my unit), the IDE cable, and on the circuit board, a very nice user replaceable clock-type battery -so the unit can keep time and date even when unplugged-, some DRAM, an ALI M5273 USB 2.0 controller chip (which manages the usb ports in the back), an Acard ATP865 IDE controller chip, an AMD AM29lv64 flash memory and finally the main brain of the unit: the Broadcom 4780 "NAS on a chip" square and surface mounted piece of silicon, the size of your big toe's nail. No chips need cooling or heatsinks. Strangely, while I expected to see a heatsink or connection between the hard drive and the aluminium case, yet there is none. There's a tin-based RF-shield, and that's it, there's just "air" between the hard drive and the case exterior.
a full file server PC with SMB and NFS reduced to a single surface mounted chip, look ma, no CPU or heatsink!.
Kudos to Broadcom for their cross-platform, open-standards stance and approach.
One thing which worried me initially was the total lack of cooling for the hard drive, specially considering the one included is a 7,200 rpm one which tend to get very hot. Idea for SimpleTech: why not replace the HDs with Samsung ones like the quiet 5,400 rpm SV1604N, which are not only much quieter and cooler at 5400 rpm, but apparently still being manufactured?. The Simpleshare gets noticeably hot to the touch, undoubtedly thanks to the 7,200 rpm drive -which is overkill since the biggest bottleneck is the 100mbit fast ethernet link- and the lack of fans. Affixing a mercury thermometer for 3 minutes to the aluminium case while a 10 GB file copy was being conducted measured 39.1 degrees -room temperature was at around 25 degrees Celsius-. [Note to our american readers, that's 102.38 and 77 fahrenheit, respectively]. After three months of daily use, the hard drive has not died, so I guess it's operating within the manufacturer's specifications.
One thing to note for the geeks is that there's not much information about the internal file system used by the unit. SimpleTech doesn't give much details about it and I surely looked around for clues. The distinction between "foreign" NTFS and FAT/FAT32 drives made by the documentation and user interface and the "native" (non-foreign) volumes formatted by the unit leads me to believe that it's some proprietary FS implemented by the Broadcom chipset. But this is speculation on my part. Yes I could have gone an extra step and removed the drive and attempted to read it on a PC, but too late, this review was about complete and the drive is now holding 90GB of my precious data. If you have any comments on this point, drop me an email and I'll have the information added as a footnote.
Testing
I divided testing in two parts: compatibility and benchmarking. The Simpleshare exceeds at compatibility on the hardware level, with its "SMB and NFS on a chip" provided by its built-in chipset from Broadcom. On the software level, well, things could have been a little better. The "NASFinder" web-based application included in the CD, however, is coded using ActiveX and thus works only on MSIE, which in turn restricts you to Windows (remember when MSIE 4 used to be available for competing OSs like Solaris? that only lasted until MSFT got the DOJ off his back. Coincidence?). Leaving that aside, the unit can be accessed with ANY web browser (I used a mix of Netscape 7.2 on windows, Firefox in Sun's Java Desktop linux, and Mozilla 1.7.8 in OS/2 to setup and edit its configuration from different machines just by pointing the browsers to the unit's IP address and entering the "simple/share" default username/password. The "NASFinder" application issue however will probably only affect newbies. Anyone which uses Linux or OS/2 or Unix probably doesn't need a "wizard" of sorts, but things don't have to be that way. The reality, however, is that I was able to connect and copy/read files effortlessly to the Simpleshare unit from Windows XP SP2, Sun's Java Desktop System linux (using Samba and the Gnome graphical interface to browse shared drives), and IBM OS/2 (over NFS). So it excelled in the cross-platform test.
SimpleShare disk mounted via NFS from my OS/2 box. Hooray for open standards!
To test its performance, a first basic test was to rip a DVD to the local hard disk from the top-of-the-line Gateway 7422 Athlon64 notebook, then mount the SimpleShare drive over Windows Networking (CIFS) and move the 4.35GB of data comprising the DVD to the NAS drive. To reduce bottlenecks, the Simpleshare unit was plugged into the same 10/100 Linksys switch as the notebook. Sending data to the unit (writing to the drive) took 1032 seconds, which according to my poor math means a 4.21 MB/s performance. Remember this was using the WinXP graphical shell and dragging and dropping a folder from one drive to another, so there's some minor overhead there. Copying back the 4350MB of of data from the Simpleshare drive to the notebook took a mere 871 seconds, which means 4.99 MB/s.
For a more scientific test, I decided to run Passmark Performance Test 5.0 on a shared Simpleshare volume, and repeat the test with my trusty (but five years old) NAS dinosaur: the Intel inBusiness Storage Station which is a PI running FreeBSD unix. The results of the tests can be seen below and were very surprising: the 30GB Intel box got 3.2MB/sec in reads and 2.1MB/sec in writes, and the Simpleshare scored 5.1 in "sequential reads" and 3.0 MB/sec in average sequential writes. I can't explain why the Passmark write score is so much lower than the plain file copy using the WinXP interface. I guess it has to do with the nature of the R/W calls (the Passmark software does cached win32, uncached win32, and raw writes).
Running some tests... drag-and-drop copying of data was somehow faster than these results
In short: the unit is very fast for storage of documents, data, music, and even DVD content played over a LAN. I was expecting it to have more or less the same performance as my trusty old intel box, but clearly the Broadcom "NAS on a Chip" has an edge over the ancient Intel Storage Station and its FreeBSD and Samba 2.x - not to mention the difference in the HDs used on each (the Intel's are ATA33).
On the reliability side, after three months of daily use -which even included leaving a P2P client running, selecting "president speech" as the search string and then leaving the P2P client running over the shared Simpleshare drive -downloading and sharing the speeches 24/7 until today- , the hard drive has not died, so I guess the drive is operating within the manufacturer's specifications. Running P2P applications to a drive is the ultimate survival test, it's a seek intensive process.
I would have appreciated the addition of an optional fan which can be toggled on/off with a switch or even better, the replacement of the drive with a cooler 5400 rpm one. But who am I to say... probably this was a marketing decision, and you and me know that marketing gurus are moved by numbers "the higher the number, the better" with little regard for the implications. Notice how almost all HD makers have moved to 7200 rpm without recognizing the need for quieter, cooler 5400 drives?.
A pair of external USB 2.0 hard disks plugged into the unit (using a different chipset each)
Finally, expandability is great: you can plug up to two external hard disks to the unit's USB 2.0 ports, and such drives will be shared on your lan. Or, you can also plug a printer into one of such USB ports and the Simpleshare will act as a SMB (Samba/Windows Networking) print server on the LAN. When a USB external hard drive formatted with FAT/FAT32 or NTFS is connected to SimpleShare, the disk is immediately recognized and shared on the network. The share name is set by SimpleShare, based on the file system used on the disk. Existing files are not be deleted or modified in any way by SimpleShare. If the disk is later removed from the SimpleShare and attached to another computer, it will still be readable.
The shares created by SimpleShare for legacy disks are referred to as "Foreign Shares". SimpleShare's legacy disk support function makes it easy to attach a USB disk formatted with FAT or NTFS and share its files with other users on the network, with the following restrictions: 1) Disks formatted with NTFS are read-only. 2) Only share level access controls are provided for foreign shares. User base security, domain member and domain controller security controls are not provided for foreign shares. 3) "Legacy" (fat32/ntfs) disks cannot be used for of mirroring. 4) Legacy disks cannot be used for striping.
The good, the bad, and the ugly
The Good:
The bad
The Ugly
NASFinder works great... on MSIE/Windows. Forget it if you use any other browser on a non-windows OS!. :(
The Verdict
I give the Simpleshare-160 from SimpleTech four fernandos in my one-to-five personal rating scale. Initial start-up is very easy and the standards-based design (SMB and NFS) is something that both SimpleTech and Broadcom should be applauded for (unlike Ximeta's proprietary drivers). If all you want is to plug your drive on the lan and start moving content to it, this is for you. No ugly drivers to install or proprietary network protocols. 100% compatible with almost every OS on Earth that has some form of SMB networking or NFS available.
I can only hope that they ditch the activeX based "NASFINDER" or at least offer a Java based configuration utility for the rest of us who run some form or another of a non-Windows OS. The technology is there, they only have to hire a MSFT-free tech head to write the code. But like I said above, most power users can certainly live without the "wizard". This unit will be used @ the INQ's South America labs for work storage, so you'll be the first to know when/if we experience any problems. µ