Just an FYI. Don't hold your breath if you have a older Lacie box with In the box support for Mac Sharing via SMB. Lacie has deprecated this. From now on, you must backup your data, and clean install Linux OR spend 1200-2000+ to buy E Z IP. Lacie will no longer support it.
The best I was able to get them to do was send me an FTP image of the ORIGINAL box. We had a failure of a HDD slot (apparently not uncommon in this series, due to hat I have read to be soldering technique). Our regular HDDs would spin up just fine, but we would get a red error LED on the server. We triply confirmed it was the hard drive (first by getting a new HDD sent to us, then by getting a a second box sent to us on a 21 day, ship back the old one or pay for the new one.
Linux Mint 14 on a LiveCD did not pickup the partitions. None of them ran by default. I backed down at that point, because this job was not for me. They spent $1500 on a copy of E Z IP.
Why and when would you need this? You are hosting from a Windows Server 2008 or newer system and have multiple Mac Clients. Microsoft deprecated compatibility with AFB and other Mac additions and as of 6 months ago, Lacie dropped its legacy support. I could share... sometimes... with my Windows 8 box. They no longer have the support for Apple products, and have pegged themselves to Microsoft, according to what I have read. E Z IP seems to have done the same thing. Also, it was originally included on old boxes, but now is not [natively].
So, again, caveat emptor. If you are using multiple Mac clients, it may simply be a lot easier (and way cheaper, especially if SHTF) to run a Linux box since SMB is supported there with Mac sharing.
Final thoughts: at one point we could edit files, and save them. Later on, we could grab files and not save them. On a reboot, sometime between when I last saw it, the configuration somehow changed (this is a new box), and they no longer had the ability to access the drives, even though I previously had them in a working state.
EDIT: I meant to say, we triply checked that it was NOT the hard drive