Whilst I no longer have a ShareSpace (returned for refund), I’ve been gathering information about the problems people are having with it. Poor performance seems the obvious one. See this thread which contains some of my comments.
On top of that, I found several disconcerting comments from users suffering from corrupted data that could not be recovered. Notably this long thread at SmallNetBuilder. It seems that recovery/ rebuild all too often results in a cleanly re-striped array. In other words, your data will be gone!! Very clever (not) if true.
My suggestion would be that if you’re stuck with a ShareSpace and running a recoverable RAID configuration, do the test to see if you can actually recover from disaster before committing real data to the storage. We know with the ShareSpace recovery may take several days to complete, but you’d be safe in the knowledge one way or the other.
Thanks for the warning. I’m a loyal customer of WD hard discs, but this warning (I also read the thread you mentioned in Small Net Builder before I saw this warning from you) steered me away from ShareSpace. I almost bought it for my client. Imagine the chaos that can ensue. I’ll still continue to buy WD hard discs, however
I think WD is excellent when it comes to hardware. But I guess, it’s different story when they had to master software. I imagine they had to make their own Linux distro for ShareSpace (which was probably the first for them), and build web interface to Samba from scratch on top of the customised Linux distro. Since I’m quite well versed in Linux, if they had provided telnet (or SSh) on ShareSpace, I’ll probably still have more confidence in purchasing this product and troubleshoot everything the old-fashioned telnet way. But reading a thread in WikiDot, it seems like it’s not that straight-forward at all to telnet ShareSpace
