SmallNetBuilder Forums
Go Back   SmallNetBuilder Forums > NAS > NAS Article Discussions

Thread Tools Search this Thread Display Modes
Old 11-28-2010, 12:22 AM
Posts: n/a

Hey there,

still donīt know what exactly went wrong so that the http connection error
occurs but at least there is one way to solve the problem more or less:

If the system crashes or if you crash the system by playing with the linux
system just format the hard drives, all four of them and put them back into
the system. Restart and the system will start to build up itself from the flash
memory, works like a charm afterwards. Draw back is that it puts the system
back to RAID 5, takes 15-20 hours until its done.
Not really comfortable if you play around and end up crashing the system time
by time....



Is it work? i'm newbiz......anybody can help?...
Reply With Quote
Old 12-04-2010, 09:28 AM
Posts: n/a
Default I got my data back with console in internal linux

I read a lot about problems in this forum, thanks for all info here. Perhaps this will help everybody who still can access over HTTP to the device, but the RAID no more provide shares.

In /tmp there is a file raid.log that show the last configuration. There I saw that /dev/md2 was used as RAID5 with sd[a-d]4 partitions. My confuguration show, that 2 drives are missed in configuration. You can check that with "cat /proc/mdstat", I got then as result: "md2: active raid5" and only 2 device.

A RAID5 only can start here with 3 devices. So I try to add use only 3 drives, and it works with following! "mdadm --assemble --force -v /dev/md2 /dev/sd[abc]4" -> /dev/md2 has been started with 3 drivers (out of 4).

After that I add the missing drive by "mdadm /dev/md2 -a /dev/sdd4 -> hot added /dev/sdd4. Now "cat /proc/mdstat" show that raid starts recovering the data to synch all drives. 0.0% (320768/975097920) finish=911.5min speed=17802K/sec.

After that it was needed to make logival volumes. See in previews posts how to use: pvscan, pvcreate, vgcreate, lvcreate. The lvcreate says me that not 714329 are able to use (some smaller value will printed in error message). So I simply use the value that is show and repeat lvcreate to define the volume.

fsck.ext3 shows some errors in system because volume is smaller now, journal and data are checked. I loose no data at all and I can now recover by myself (no additional cost). After that mount the new device and your data can be accessed successfully, finish!

Now after I store all data to an other external drive, I will reset to factory defaults the device if the next reboot shows me still no data (if internal linux is still not able to provide data from RAID5).

To prevent this I have also updated to last firmware for the WDShareSpace 4TB. This I will see after next 4 hours when the recovery is finish and a reboot is done.

I know that this info is not usable for people with zero linux experiences, but I hope that this info is useful for anybody that knows linux a little like me: give you a try to recover the data by yourself!, it's not possible to damage the filesystem if you use command that I write in this thread.
Reply With Quote
Old 02-15-2011, 02:23 PM
Posts: n/a
Default cesspools madstr

Where can i find the latest firmware? Can I updadate from linux console?

Reply With Quote
Old 07-06-2011, 06:10 AM
Posts: n/a
Angry WD Sharespace built-in update FAIL.

Originally Posted by Agradecido View Post
Where can i find the latest firmware? Can I updadate from linux console?

Hi, hope you have not used the built-in update function yet!

If you have, you'll now be sitting with a slow AND crippled NAS, not just slow...
Reply With Quote
Old 09-23-2011, 02:55 PM
adisor19 adisor19 is offline
New Member
Join Date: Feb 2009
Posts: 6
Thanks: 1
Thanked 0 Times in 0 Posts
adisor19 is just starting out
Thumbs down

I updated mine to the latest version and while i didn't brick it.. it's slow as hell now..

Seriously, this is absolutely the worst NAS ever.


Edit : after a NAS reboot, speed recovered somewhat to around 10 - 14 Mbps.. still nothing even remotely close to what the package advertised.

Last edited by adisor19; 09-28-2011 at 11:39 PM.
Reply With Quote
Old 01-04-2012, 08:07 PM
Patrick E (B)
Posts: n/a
Default Workaround for Windows 2008 domain (AD)

I've had my adventures with Sharespaces as well, 4TG and 8TB. Installed two at a client's site (mirrored using SyncBack - NEVER rely on a single drive!), and within months one of both already came down with a thrashed RAID5, was replaced under warranty, and if I remember well, the second one also had to be replaced very short afterwards. Now they have been running for about 2 years without a glitch.

Keeping in mind that it may be a non-stable product, that it has its flavour of Linux buried inside with quircks when connecting to Windows, and that you're on your own regarding support, I still find it a workable solution for cheap archival storage, provided that you keep them mirrored at any time, and never update the firmware (horror stories on this thread have kept me from updating firmware, wisely so I believe).

I have just successfully connected the pair of ShareSpaces to a new server running SBS 2011 (= Windows 2008 R2). Ok, logging on using AD domain credentials did not work, "Access denied etc."

The workaround is: take it out of AD.

How ? (this is for a totally open network environment in which all users have access to everything on the NAS)

1. Open the ShareSpace GUI, Advanced mode,

2. remove the domain settings and put it in a workgroup mode : Network > Workgroup, Mode: (o) Workgroup + Submit (you can enter any workgroup name, won't be needed in following steps)

3. create a user+password: Users > Users, click the + icon, fill in username and password, enable [v] CIFS and [v] FTP depending on how to plan to access it

4. allow public access on all shares: Users > Folder Share Permissions, click on the pencil icon next to each share, Public Access: [v] Enable + Submit

Now in Windows map a drive letter to the NAS:
- open a command prompt (start-run-cmd)
- enter this command:
net use \\\sharename ( is the Sharespaces IP address, 'sharename' is an existing data share on the NAS).
- next you will be asked a username and then a password. Enter what you defined in step 3.


The only drawback in my situation is that Syncback gets access denied errors when copying from the NAS, and I have to have it use explicit network credentials (using the same username and password as defined in step 3 above).

Also, we are unable to delete directories from the Sharespace, only files.
Reply With Quote
Old 01-14-2012, 06:32 AM
Patrick E (B)
Posts: n/a
Default Sharespace security : under the hood

Upgraded a 4GB and 8TB ShareSpace from 2.1.3 / MioNet 14/05/2009 to firmware 2.3.01 with MioNet 01 Sep 2011.
No issues whatsoever, correct speed, correct accessibility.

The access problems I was having (unable to delete folders except through FTP) also has been solved.

Before the firmware upgrade, all folders on the drives (created when both drives were added to a Windows 2003 domain), showed security as follows from Windows explorer:
Everyone : special,
two unknown GUID's {S-xxx-xxxxx} : special.

The "special" came down to a combination of R/W rights I forgot to take note of, but it wasn't full control, because we got "Access denied" errors when deleting folders.

After the firmware upgrade, without having us modify any file of folder permissions on the NAS, all existing folders and files now show the following security when viewed from Windows explorer:
Everyone: special
10000 (Unix User\10000): special
jewab (Unix group\jewab): special
Drilling down on "special", it consists of all permissions, so effectively: full.

Apparently the two unknown GUID's showing as {S-xxx-xxxxxxxxx} before the firmware upgrade now are resolved to "10000" and "jewab".

At this moment, with nothing changed in the drives' network settings (ShareSpace still part of workgroup, not of domain, and Public access enabled) we again have full write and read permissions on everything from Windows.

I found this out by going into the Sharespace Unix/Linux.
With the new firmware you first need to enable SSH in the ShareSpace management GUI:
Advanced Mode - System - Advanced: ssh [x] Enable,
and than you can login using a freeware tool like putty with username "root" password "welc0me".

From there on go into the data space using the following commands:
cd /DataVolume
ls -l shows a.o. all defined Shares
cd <sharename>

From a sharename, ls -l is showing us or all folders and files in this share:
-rwxrwxr-x 10000 jewab.

If I interpret correctly, this would mean:
user 10000 has full access (as owner)
group jewab has full access (as group)
others have read and execute access

I'm guessing that the owner '10000' was the domain username within the ShareSpace under which it previously created all our user files and directories, when it was still under the old firmware and connected via AD to our Windows 2003 server.

Looking in /ect/groups and /etc/passwd, this username 10000 is not listed anymore, so probably got deleted when taking the ShareSpace out of the AD domain ?

The workgroup user account we now created on the ShareSpace and with which we now access them from our workstations is now the creator of all new files and folders.
Since this new user name is listed in the 'jewab' group, it apparently also can delete and modify files created by the previous AD user account '10000', because they belong to the same group, and the group has also rwx permissions.

So we have full permissions on all files and folders on the ShareSpace again, which is wat we were looking for.
Reply With Quote
Old 02-02-2013, 11:33 AM
Master_RD Master_RD is offline
New Member
Join Date: Feb 2013
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Master_RD is just starting out
Default Forget it

I have this NAS 2 years now (4 times 2 TB ) and the 3e HD failed right now.

In my opinion the used HD are garbage. The Green HD used are only good for slow PC's not for raid arrays. I have among other computers 2 Compaq proliant 1500 servers running 24/7 after 15 or more years with raid arrays and I only had a drive failed once. Rebuilding is time consuming on them too but it works.

It is time that the biggest HD supplier takes a lesson from this and supply all users with Black versions of the disks that they originally bought in their NAS and re-engineer the software to an acceptable level for all user
Otherwise a lot of people will not ever want to have WD disks / Hardware again.

Reply With Quote
Old 02-02-2013, 01:37 PM
stevech stevech is offline
Very Senior Member
Join Date: Mar 2010
Location: San Diego
Posts: 5,324
Thanks: 1
Thanked 386 Times in 373 Posts
stevech is just starting out

Not a good idea to buy a NAS from WD or Seagate or Netgear rather than QNAP, Synology, Thecus - who do one thing well
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

All times are GMT -4. The time now is 12:26 AM.

Top 10 Stats
Top Posters* Top Thanked
RMerlin  505
L&LD  244
stevech  147
jegesq  125
john9527  124
System Error...  102
azazel1024  93
Samir  90
Rankdropper84  85
dfran1  69
RMerlin  7400
john9527  764
stevech  385
ryzhov_al  318
L&LD  303
TeHashX  279
RogerSC  216
hggomes  206
sinshiva  161
azazel1024  148
Most Viewed Threads* Hottest Threads*
Old Asuswrt-Merli...  109034
Old Asuswrt-Merli...  42560
Old Login...  31792
Old Entware-arm...  5528
Old Asuswrt-Merli...  4055
Old Home Mesh...  3756
Old ASUS...  3193
Old AC3200 worth...  2725
Old At what...  2562
Old End of the...  2178
Old Asuswrt-Merli...  617
Old Asuswrt-Merli...  271
Old Entware-arm...  57
Old Forgo...  44
Old Asuswrt-Merli...  44
Old Home Mesh...  42
Old ZyXEL...  39
Old Fear and...  38
Old AC68U cannot...  36
Old Lag issues...  35

Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.
© 2006-2015 Pudai LLC All Rights Reserved.