Mount a Western Digital NAS Drive guidance

usmany · 2012-05-29 21:45:42

Hi,
I just installed archbang and, I should say that after a year using different linux distros (ubuntu/mint/fedora) this is the one I like the most, even though I just cross the line between a total newbie and a plain newbie.
Now, my wife gave me as a gift a Western Digital 2Tb NAS drive, wich was a wonderful detail from her. The only thing is that even though it is a Debian box, it does not provide any kind of linux support.
So now in arch, I've been reading about NFS and NFSv4 and I still don't get what do I have to do in order to mount the drive.
Can someone please help me do this?
I named the drive T2 -I'm so creative!- and asigned a static ip address (192.168.1.100)

Thanks in advance

darktux · 2012-05-30 03:10:01

Hi usmany,
I have a working NAS drive in my local network, and my steps were the following:

1) install gvfs and gvfs-smb packages ($sudo pacman -S gvfs gvfs-smb)
2) install pcmanfm file manger ($sudo pacman -S pcmanfm)
3) In pcmanfm in the menus go to "Go" and Network

Now you should be able to browse you NAS drive (make sure the NAS drive is running and connetcted to you network)
As a matter of convenience, add your NAS partition as a bookmark in pcmanfm (not mandatory)
Hope this helps.

handy · 2012-05-30 03:56:20

This lot's for setting up your NAS to auto-mount.

I'll have a go here, at least if you hit something that I don't know about someone else with more knowledge (or a better memory) will contribute I'm sure.

I use a Netgear ReadyNAS device which has a cut down version of Debian built into it. I can access its built in Debian system from another machine via SSH (which is not advised) or via the browser interface. With your WD NAS you will not be able to access it from another machine until you can talk to it via your local network. I expect you know that last part, but it gets us started on roughly the same page.

I use NFS to access my ReadyNAS, have you installed the required NFS package on your machine? If not install nfs-utils.

You should NOT have to edit /etc/conf.d/nfs-common.conf .

Edit the /etc/rc.conf DAEMONS() array by adding network rpcbind nfs-common @netfs to it in that order. Mine looks like this, though yours will be different & that's fine:

DAEMONS=(@syslog-ng ufw network rpcbind nfs-common nfs-server @netfs @polipo @crond @sshd @sensors @dbus @alsa @stb-sdmin @gpm @udisks)

You will need to call your drive from fstab if you want to auto-mount it at boot. I use the following for my ReadyNAS:

192.168.1.15:/media	/mnt/NAS-media   nfs  	defaults,hard,intr,noatime  0  	0
192.168.1.15:/media-2   /mnt/NAS-media-2 nfs  	defaults,hard,intr,noatime  0  	0
192.168.1.15:/backup	/mnt/NAS-backup	 nfs  	defaults,hard,intr,noatime  0  	0

You need to create a directory in /mnt for your nfs mount. Name it whatever you choose. You can see the three directories that I created in /mnt above.

Using what you have told me so far, your fstab entry could look like this if you created a /mnt/backup directory called backup: (I feel like a nag!)

192.168.1.100:T2    /mnt/backup    nfs    defaults    0    0

Beyond that, if there are any problems then they are due to requirements that your NAS has which should be in the documentation that came with it.

Good luck, & if you choose to go this way let me know if/when you strike any problems?

Last edited by handy (2012-05-30 04:00:04)

usmany · 2012-05-30 19:29:04

Hi,

Thank you for your quick answer, this is another * to the archbang distro: a forum with quick and to the point answers.

I choose handy's method because it was the path I was trying to follow, but...
I hadn't been able to mount the drive yet :-(
I don't know what I'm missing, here is my rc.conf DAEMONS line:
DAEMONS=(dbus networkmanager network rpcbind nfs-common @netfs nfs-server !dhcdbd ifplugd syslog-ng @alsa)

and the line in the fstab is exactly as you wrote with the exception that the folder I created under /mnt is Public (/mnt/Public)

Of course I installed the nfs-utils package

Any clue?

thanks again, and thank you very much darktux, I will reserve your method in the case everything fails :-(

darktux · 2012-05-31 02:34:53

Welcome usmany. The handy's method is better as a permanent solution. In my case, as I do not use my NAS drive intensively nor it is 24/7 power on.

I believe handy can help you better, but I not sure you can have both 'networkmanager' and 'network' in your DEAMONS array at the same time. Try to inactivate one of them (with a ! just before the deamon ex: !networkmanager).

Handy, you're the expert ... I'm just learning ...

handy · 2012-05-31 04:33:02

Hell! I'm no expert. <shock>

@usmany: Did you make a folder called /mnt/Public as well as use /mnt/Public in your fstab?

I'm starting with the easiest stuff.

usmany · 2012-06-01 21:18:36

Hi Handy,
Yes I did it , I created the folder Public at /mnt (/mnt/Public).
and I silence the deamon as darktux sugested but when I did that I lost the wireless conecction, so I put the networkmanager deamon at the end and still nothing.
I noticed though that when I shutdown the computer I can read a message that says: "interface undefinend in rc.conf".
Thank you for take the time to help me with this and sorry for the long waitings -I'm working in something that keeps me away from my laptop :-(.
Also thanks for start with the easiest stuff I don't think I can handle the hard ones yet...

handy · 2012-06-01 21:28:37

I just noticed that you have nfs-server in your DAEMONS() array. You don't need that, as your machine only needs to be a client to your NAS device. The reason I have nfs-server in my array is for another reason entirely. So get rid of that for starters.

Did your NAS come with any information on the setup on its side?

usmany · 2012-06-01 21:38:53

No it didn't it does asume that only Windows and Mac users buy stufs!
:-(
I will get rid of the nfs-server right away and will restart the machine.

usmany · 2012-06-01 21:42:10

Ok, I'm back... still nothing

Mr Green · 2012-06-01 22:39:06

Do some background reading if you have not done so already

https://wiki.archlinux.org/index.php/Nfs

usmany · 2012-06-02 17:04:05

Mr. Green,

I did it. I read it and I have done what it says one should do.
I don't know what I'm missing or just doing plain wrong.
That's why I'm looking for help in the community.

For example,
I deleted the deamons from the rc.conf file
I tryied to start the rpcbind and nfs-common daemons at the terminal using
rc.d start
with and without sudo
and get the FAIL message everytime,
I reinstalled the nfs-utils package

Do you think that I should go and use Avahi?
I really don't want to do that unless it is the last resource.

oliver · 2012-06-02 17:22:57

where do you get the FAIL message?

what does this give?

# showmount -e 192.168.1.100

handy · 2012-06-02 17:41:10

@usmany: How do you know the NAS' IP address?

How do you know what it has named its partition(s)?

It is critically important to have accurate information on both of these.

usmany · 2012-06-02 20:05:45

Hi Oliver, Handy
when I run showmount -e 192.168.1.100
after a while, I would say 15 secs, I get this message: clnt_create: RPC: Port mapper failure - Timed out

I know the IP adress because I asigned to it as a static address using the router web interface.
I can see the drive thoughout the web browser and I can get into its web interface, so it is available in my wireless network.
I know the name because I can connect also using ssh, when I connect to it using ssh its prompt says: T2:#

Regards

oliver · 2012-06-02 20:44:35

What happens when you try and start rpcbind? You get the FAIL message?

Do you have a firewall between the devices by any chance?

usmany · 2012-06-02 21:31:59

Yes when I try to start rpcbind I get the FAIL message.
I don't have any firewall between the devices :-(

Mr Green · 2012-06-02 23:10:38

Do you get same errors starting portmap or nfslock?

Dumb question but are you running commands as root/sudo?

handy · 2012-06-02 23:20:59

If you look at the NAS using ssh what is the contents of the following files:

/etc/exports

/etc/hosts

/etc/hosts.allow

/etc/hosts.deny

By the way, I have Avahi installed (though I don't run the daemon). If I were you I'd give it a try & run the daemon, if it solves your problem it will certainly put a smile on all of our faces.

Last edited by handy (2012-06-02 23:24:48)

oliver · 2012-06-03 06:45:25

Can you post the output from the following?

(don't do it if you have manually modified iana-etc for a specific reason)

$ sudo pkill rpcbind
$ sudo pacman -S --quiet --noconfirm iana-etc
$ sudo /bin/bash -x /etc/rc.d/rpcbind start

That last command will generate a *lot* of output

usmany · 2012-06-03 08:51:38

Hi again,

Oliver here is the output of the sudo /bin/bash -x /etc/rc.d/rpcbind start
command:

+ . /etc/rc.conf
++ LOCALE=en_US.UTF-8
++ DAEMON_LOCALE=no
++ HARDWARECLOCK=UTC
++ TIMEZONE=America/Caracas
++ KEYMAP=us
++ CONSOLEFONT=
++ CONSOLEMAP=
++ USECOLOR=yes
++ MODULES=()
++ UDEV_TIMEOUT=30
++ USEDMRAID=no
++ USEBTRFS=no
++ USELVM=no
++ HOSTNAME=yoda
++ DAEMONS=(dbus network rpcbind nfs-common @netfs networkmanager !dhcdbd ifplugd syslog-ng @alsa @dropboxd)
+ . /etc/rc.d/functions
++ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
++ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
++ localevars=(LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL)
++ vconsolevars=(KEYMAP KEYMAP_TOGGLE FONT FONT_MAP FONT_UNIMAP)
++ [[ start == \s\t\a\r\t ]]
++ [[ -n '' ]]
++ export STARTING=1
++ STARTING=1
++ calc_columns
++ STAT_COL=80
++ [[ ! -t 1 ]]
++ [[ -t 0 ]]
+++ stty size
++ STAT_COL='24 80'
++ STAT_COL=80
++ ((  STAT_COL == 0  ))
++ STAT_COL=67
++ [[ -t 1 ]]
++ SAVE_POSITION='\e[s'
++ RESTORE_POSITION='\e[u'
++ DEL_TEXT='\e[71G'
+++ tput colors
++ TERM_COLORS=8
++ ((  0 != 3  ))
++ case $TERM_COLORS in
++ unset TERM_COLORS
++ unset TZ
++ unset LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL
++ declare -a omit_pids
++ NETFS=nfs,nfs4,smbfs,cifs,codafs,ncpfs,shfs,fuse,fuseblk,glusterfs,davfs,fuse.glusterfs
++ ((  RC_FUNCTIONS_HOOK_FUNCS_DEFINED != 1  ))
++ declare -A hook_funcs
++ declare -fr add_hook run_hook
++ declare -r RC_FUNCTIONS_HOOK_FUNCS_DEFINED=1
++ [[ no = [yY][eE][sS] ]]
++ export LANG=C
++ LANG=C
++ [[ yes = [yY][eE][sS] ]]
++ tput setaf 0
+++ tput sgr0
++ C_CLEAR=''
+++ tput bold
++ C_MAIN=''
+++ tput setaf 4
++ C_OTHER=''
+++ tput setaf 0
++ C_SEPARATOR=''
+++ tput setaf 6
++ C_BUSY=''
+++ tput setaf 1
++ C_FAIL=''
++ C_DONE=''
+++ tput setaf 5
++ C_BKGD=''
++ C_H1=''
+++ tput setaf 6
++ C_H2=''
++ PREFIX_REG=::
++ PREFIX_HL=' >'
++ for f in '/etc/rc.d/functions.d/*'
++ [[ -e /etc/rc.d/functions.d/sshd-close-sessions ]]
++ . /etc/rc.d/functions.d/sshd-close-sessions
+++ add_hook shutdown_start sshd_close_sessions
+++ [[ -n shutdown_start ]]
+++ [[ -n sshd_close_sessions ]]
+++ hook_funcs[$1]+=' sshd_close_sessions'
++ pidof -o %PPID /usr/bin/rpcbind
+ PID=
+ case "$1" in
+ stat_busy 'Starting rpcbind'
+ printf ':: Starting rpcbind '
:: Starting rpcbind + printf '\e[s'
+ deltext
+ printf '\e[71G'
                                                                      + printf '   [BUSY] '
   [BUSY] + '[' -z '' ']'
+ /usr/bin/rpcbind
+ '[' 0 -gt 0 ']'
++ pidof -o %PPID /usr/bin/rpcbind
+ PID=1115
+ echo 1115
+ add_daemon rpcbind
+ [[ -d /run/daemons ]]
+ stat_done
+ deltext
+ printf '\e[71G'
                                                                      + printf '   [DONE] \n'
   [DONE] 
+ exit 0

Handy, here is the output of:
/etc/exports :

/nfs *(rw,all_squash,sync,no_subtree_check,insecure,anonuid=99,anongid=1000)

/etc/hosts :
127.0.0.1	localhost.localdomain	localhost T2

/etc/hosts.deny (pure default comments):
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
#                  See the manual pages hosts_access(5) and hosts_options(5).
#
# Example:    ALL: some.host.name, .some.domain
#             ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8) and rpc.mountd(8)
# for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.

# You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
# ALL: PARANOID

Thanks

handy · 2012-06-03 16:57:32

Your exports file looks like it has some of hosts , & hosts.deny in it as well.

Can you post the contents in separate code boxes of each of the files I asked for please?

usmany · 2012-06-03 17:47:19

Sure Handy,
here you are:
/etc/exports:
/nfs *(rw,all_squash,sync,no_subtree_check,insecure,anonuid=99,anongid=1000)

usmany · 2012-06-03 17:49:29

/etc/hosts
127.0.0.1 localhost.localdomain localhost T2

usmany · 2012-06-03 17:52:16

/etc/hosts.deny
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
# See the manual pages hosts_access(5) and hosts_options(5).
#
# Example: ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8) and rpc.mountd(8)
# for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.

# You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
# ALL: PARANOID

By the way, thanks for sharing the monsanto documental... amazing, but comments are off the topic here, thanks thanks thanks for share that

oliver · 2012-06-03 18:52:44

usmany wrote:

Oliver here is the output of the sudo /bin/bash -x /etc/rc.d/rpcbind start

This looks like rpcbind is starting up OK... (i.e. not FAILing)

Does "showmount -e 192.168.1.100" still give the same error?

usmany · 2012-06-03 18:59:04

Oliver

Now this is the message I get while running "showmount -e 192.168.1.100":
clnt_create: RPC: Program not registered

Mr Green · 2012-06-04 00:22:56

Decided to load up nfs on my pi server.

Exports seems ok

ellie@ellie-Aspire-5315:~$ showmount -e 192.168.0.7
Export list for 192.168.0.7:
/home/mrgreen/nfs 192.168.0.7

But mounting is not happening

ellie@ellie-Aspire-5315:~$ sudo mount -t nfs  192.168.0.7:/home/mrgreen/nfs /home/ellie/Public
mount.nfs: access denied by server while mounting 192.168.0.7:/home/mrgreen/nfs

Know this does not help you much but every little helps

Mr Green · 2012-06-04 02:22:52

Ok I made some changes to exports and now nfs mounting works...

/tmp	*(rw,no_root_squash,sync)

make sure you of course exportfs -a to reload config

ssh into your NAS and try

sudo mount -t nfs 127.0.0.1:/tmp /mnt

That should test its working locally

Then try from your client...... replace localhost for ip address

Very handy page if a little dated

http://www.troubleshooters.com/linux/nfs.htm

usmany · 2012-06-05 21:59:59

Hi Mr Green,

I'm sorry to say that I can't figure out what to do with your instructions, I apollogize for my ignorance.
my showmount -e 192.168.100 command spits this:
clnt_create: RPC: Program not registered

I can not start the deamonds
sudo /etc/rc.d/rpcbind start
:: Starting rpcbind [FAIL]

and after changing the /etc/exports on the server at get this message:
sudo mount -t nfs 192.168.1.100:/shares/Public /mnt/Public
mount.nfs: requested NFS version or transport protocol is not supported

Could you please explain me the steps a little bit?

Thanks

Mr Green · 2012-06-06 00:39:39

Think your problems are not with your NAS server, they are your client.

You need to figure out why rpcbind or portmap are not working first.

Am assuming your system is up to date

oliver · 2012-06-06 07:15:08

usmany wrote:

I can not start the deamonds

sudo /etc/rc.d/rpcbind start
:: Starting rpcbind                                                      [FAIL]

I'm thinking that rpcbind *is* running and the failure is because you're trying to run it again without stopping it first.

For example:

$ sudo /etc/rc.d/rpcbind start
:: Starting rpcbind                                                      [DONE] 

$ sudo /etc/rc.d/rpcbind start
:: Starting rpcbind                                                      [FAIL]

Not that this really helps you, just don't get bogged down in rpc if that is the case

Mr Green · 2012-06-06 08:24:50

More to the point are these daemons being started from rc.conf?

handy · 2012-06-06 12:56:40

Mr Green wrote:

More to the point are these daemons being started from rc.conf?

usmany's post_12 says that he removed the nfs daemons from rc.conf... ?

Mr Green · 2012-06-06 23:31:17

Sorry tl;dr

I am more likely confusing the issue, so I will let you take over ....

handy · 2012-06-07 02:16:18

No, I think I've done all I can anyway.

I'm wondering just what role the setup of the Debian based NAS is playing in this, apart from possible user error?

NFS is really such a simple networking system to use providing you have control of all of the pieces in play. Which unfortunately is something that we don't have in this situation.

Mr Green · 2012-06-07 03:18:57

if you can ssh in set up server then test it [localhost] once you know its working set up client.

I fell down because I set up share with NAS ip [doh!] once I sorted that good to go.

Will have to look at config settings, possibly change to a higher port, add more security

handy · 2012-06-07 06:58:44

It is pretty weird that the makers of the NAS set it up to work with windows & OS/X, but give no clues to the Linux users even though the damn thing is running Debian!!!

My Netgear ReadyNAS is supported by a terrific forum that quite quickly will sort out most people's problems. I wonder whether this particular NAS has such a support group?

[edit:] I just did a search for WD NAS forums & there is a number of them there, as an owner of such a NAS I'd certainly have a look at the appropriate forum if it exists as it really should have Linux setup covered.

[edit2:] This is one of WD's sites:

http://community.wdc.com/t5/WD-ShareSpa … sharespace

edit3:] This is the above linked site with a search for "Linux":

http://community.wdc.com/t5/forums/sear … ge?q=linux

Last edited by handy (2012-06-07 07:22:16)

oliver · 2012-06-07 07:05:54

handy wrote:

NFS is really such a simple networking system to use providing you have control of all of the pieces in play. Which unfortunately is something that we don't have in this situation.

NFSv3 was very simple... NFSv4 is rather cumbersome in my opinion but I *thought* that NFSv4 was supposed to be backwards compatible with NFSv3 assuming you use valid v3 options in the /etc/exports file.

I know that giving a mixture of the two will result in failure, but not the "client timeout" thing that usmany is seeing

handy · 2012-06-07 07:14:01

I only have simple needs as far as NFS is concerned so I haven't had to battle with any of the potential cumbersome constructs that may be inherent oliver.

I connect to my ReadyNAS & used to connect to my 2nd Arch box, though since that setup failed with hardware complications that won't allow me to reinstall Arch, my NFS requirements have become even more simplified as I couldn't be bothered setting up NFS to work between my Arch box & the OS/X box, as I really have no need. Both boxes access the NAS so on the rare occasion I need to move something from one to the other I go the long way round.

From my experience so little of the NFS config file editing possibilities had to be touched at all for it to work consistently well.

Last edited by handy (2012-06-07 07:17:17)

Mr Green · 2012-06-07 08:08:55

Have not got a mac but

https://wiki.archlinux.org/index.php/NF … _X_clients

Up until a few days ago I would have used sshfs

Now thinking of backups and a dropbox like local set up on my Pi, I have got an 8gb micro usb drive which to store data on.

Note to self read up about Tails

handy · 2012-06-07 09:23:20

I use Worker for most of my file management (& many other jobs as well), I really like having source & destination directory/file listings to work with, though I appreciate that, that is just a personal taste thing that doesn't suit everyone.

usmany · 2012-06-07 20:30:21

Hi everyone...
I would like to say this issue has been finished but not :-(
I'm loving this distro, light, fast and stable indeed. I had installed everything I need in no time, everything in my machine just works -it is the first distro I've used in wich the backlight keyboard works as it should be, also the only distro where both mics works, the fans are quite and the hdmi output just work.
So this issue with the WD mybook live drive is the only thing I really need to fix. I want to be clear, I don't blame archbang for this issue, the drive has been a headache in every single distro I've used, even in Debian and derivates! which is shocking because the drive itself is a Debian box!
So geting back to the issue, I've read the man pages for nfs and statd, I found that most of the time if one get this error:
clnt_create: RPC: Program not registered
is mostly because the nfs deamon is not running in the server, so I ssh into the server and after issuing:
/etc/init.d/nfs-common status
I got: all daemons running
So the server seems to be ok
I installed avahi and the nonconfiguration browser can see the drive, but I can't mount it.
If I go to network drives you see it:
https://www.dropbox.com/sh/32sjpbmc5ytp … iseeT2.jpg
But If I click it I got this message:
The specified location is not supported

I tryied to get gshare installed -as recommended in the avahi arch page- but it gives me an error also:
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading gshare_0.94-11.diff.gz
Aborting...
The build failed.

So, after all your help, recommendations and my readings I am still lost with this.
I just don't have a clue of what am I doing wrong :-(
At this point I am all ears.
I happyly will sell the drive but it was a gift from my wife... so that is not an option... sadly.

Thank you guys

Mr Green · 2012-06-07 23:24:43

Found manual for T2 not much help

looking on WD community forums it seems that Linux is not supported.

WD own technical support cannot give Linux advice as they simply do not know anything about it.

Let me get this right WD T2 has depain running on it [linux] but you can only connect to it using a Windows pc?

And you can an app for Android ??

Best bet I think in this situation is to join WD community forums and get some advice...

Really tempted to buy one and get ArchBang running on it

handy · 2012-06-08 02:54:19

Mr Green wrote:

--------8<-----
looking on WD community forums it seems that Linux is not supported.
WD own technical support cannot give Linux advice as they simply do not know anything about it.
---------8<------

That's what I saw in one of the links I posted previously.

usmany, you would be best off taking the drive back & swapping it for one that is Linux friendly or finding someone you know who wants to buy it off you & then after researching the subject buy a NAS that is built to work on Linux too.

Bummer I know.

Last edited by handy (2012-06-08 02:55:01)

darktux · 2012-06-08 04:51:21

usmany, have you tried the solution I had suggested in comment #2 ?
Can you also try mount the NAS drive as '-t cifs' instead of '-t nfs' ?

Mr Green · 2012-06-08 05:00:09

http://community.wdc.com/t5/WD-ShareSpa … d-p/181344

After some searching, may not be same device but every little helps... looks read only ;(

oliver · 2012-06-08 06:54:47

Yesterday, Mr Green mentioned sshfs... have you given that a go? Might be worth a try

Mr Green · 2012-06-08 08:06:16

Arch Linux

Announcement

#1 2012-05-29 21:45:42

Mount a Western Digital NAS Drive guidance

#2 2012-05-30 03:10:01

Re: Mount a Western Digital NAS Drive guidance

#3 2012-05-30 03:56:20

Re: Mount a Western Digital NAS Drive guidance

#4 2012-05-30 19:29:04

Re: Mount a Western Digital NAS Drive guidance

#5 2012-05-31 02:34:53

Re: Mount a Western Digital NAS Drive guidance

#6 2012-05-31 04:33:02

Re: Mount a Western Digital NAS Drive guidance

#7 2012-06-01 21:18:36

Re: Mount a Western Digital NAS Drive guidance

#8 2012-06-01 21:28:37

Re: Mount a Western Digital NAS Drive guidance

#9 2012-06-01 21:38:53

Re: Mount a Western Digital NAS Drive guidance

#10 2012-06-01 21:42:10

Re: Mount a Western Digital NAS Drive guidance

#11 2012-06-01 22:39:06

Re: Mount a Western Digital NAS Drive guidance

#12 2012-06-02 17:04:05

Re: Mount a Western Digital NAS Drive guidance

#13 2012-06-02 17:22:57

Re: Mount a Western Digital NAS Drive guidance

#14 2012-06-02 17:41:10

Re: Mount a Western Digital NAS Drive guidance

#15 2012-06-02 20:05:45

Re: Mount a Western Digital NAS Drive guidance

#16 2012-06-02 20:44:35

Re: Mount a Western Digital NAS Drive guidance

#17 2012-06-02 21:31:59

Re: Mount a Western Digital NAS Drive guidance

#18 2012-06-02 23:10:38

Re: Mount a Western Digital NAS Drive guidance

#19 2012-06-02 23:20:59

Re: Mount a Western Digital NAS Drive guidance

#20 2012-06-03 06:45:25

Re: Mount a Western Digital NAS Drive guidance

#21 2012-06-03 08:51:38

Re: Mount a Western Digital NAS Drive guidance

#22 2012-06-03 16:57:32

Re: Mount a Western Digital NAS Drive guidance

#23 2012-06-03 17:47:19

Re: Mount a Western Digital NAS Drive guidance

#24 2012-06-03 17:49:29

Re: Mount a Western Digital NAS Drive guidance

#25 2012-06-03 17:52:16

Re: Mount a Western Digital NAS Drive guidance

#26 2012-06-03 18:52:44

Re: Mount a Western Digital NAS Drive guidance

#27 2012-06-03 18:59:04

Re: Mount a Western Digital NAS Drive guidance

#28 2012-06-04 00:22:56

Re: Mount a Western Digital NAS Drive guidance

#29 2012-06-04 02:22:52

Re: Mount a Western Digital NAS Drive guidance

#30 2012-06-05 21:59:59

Re: Mount a Western Digital NAS Drive guidance

#31 2012-06-06 00:39:39

Re: Mount a Western Digital NAS Drive guidance

#32 2012-06-06 07:15:08

Re: Mount a Western Digital NAS Drive guidance

#33 2012-06-06 08:24:50

Re: Mount a Western Digital NAS Drive guidance

#34 2012-06-06 12:56:40

Re: Mount a Western Digital NAS Drive guidance

#35 2012-06-06 23:31:17

Re: Mount a Western Digital NAS Drive guidance

#36 2012-06-07 02:16:18

Re: Mount a Western Digital NAS Drive guidance

#37 2012-06-07 03:18:57

Re: Mount a Western Digital NAS Drive guidance

#38 2012-06-07 06:58:44

Re: Mount a Western Digital NAS Drive guidance

#39 2012-06-07 07:05:54

Re: Mount a Western Digital NAS Drive guidance