Added a WD Mycloud Ultra NAS to my local network. Some variant of NFS is used. There are two shares, one designated as public for access by all systems on the network and one with a user and password.
Both are accessible on Windows systems on the network. The public share can be mounted on Fedora 33 with the command--
-----
~]# mount -t nfs 192.168.1.248:/mnt/HD/HD_a2/Public /mnt/Public
Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.
-----
If the same type of command is used for the other share
-----
~]# mount -t nfs 192.168.1.248:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: Protocol not supported
-----
I don't see anyway to specify the user/password. Things I find with search seem to be quite out of date.
Another mode of access is supposedly
nfs://192.168.1.248/nfs/mcstuffy
using this in a mount command gets NFS URL not supported. dolphin and konqueror do not see it either.
Any help would be appreciated
On 07/03/2021 13:44, Robert McBroom via users wrote:
~]# mount -t nfs 192.168.1.248:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: Protocol not supported
I don't see anyway to specify the user/password. Things I find with search seem to be quite out of date.
Another mode of access is supposedly
nfs://192.168.1.248/nfs/mcstuffy
using this in a mount command gets NFS URL not supported. dolphin and konqueror do not see it either.
It sounds more like /mnt/HD/HD_a2/mcstuffy is more likely a cifs exported file system than nfs. I've never configured nfs to use usernames/passwords. To do so, I think one needs kerberos configured.
Is your username on the Mycloud the same as on your linux system? If so, what happens when you do....
smbclient -L 192.168.1.248
You should be prompted for your password on the Mycloud
On Sun, 7 Mar 2021 at 01:44, Robert McBroom via users < users@lists.fedoraproject.org> wrote:
Added a WD Mycloud Ultra NAS to my local network. Some variant of NFS is used. There are two shares, one designated as public for access by all systems on the network and one with a user and password.
Both are accessible on Windows systems on the network. The public share can be mounted on Fedora 33 with the command--
~]# mount -t nfs 192.168.1.248:/mnt/HD/HD_a2/Public /mnt/Public
Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.
If the same type of command is used for the other share
~]# mount -t nfs 192.168.1.248:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: Protocol not supported
NFS may not be enabled for the other share. Use "showmount -e <NAS>" on the client. You can "-v" to get more information from the mount command.
I don't see anyway to specify the user/password. Things I find with search seem to be quite out of date.
NFS may rely on the client system's user authentication. In the past it was necessary to assign consistent ID's (user and group) across machines, now there is ID mapping on some systems, but I have never used it.
Another mode of access is supposedly
nfs://192.168.1.248/nfs/mcstuffy
using this in a mount command gets NFS URL not supported. dolphin and konqueror do not see it either.
This form was used at one time on macOS (my last contact with macOS was several years ago).
Any help would be appreciated
Some internet posts say you can log in an "admin" via ssh, but that you don't get full "root" privileges. You can check for a "sudo" command, see if you are allowed to view log files, and maybe figure out what OS is used .
On 3/7/21 1:17 AM, Ed Greshko wrote:
On 07/03/2021 13:44, Robert McBroom via users wrote:
~]# mount -t nfs 192.168.1.248:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: Protocol not supported
I don't see anyway to specify the user/password. Things I find with search seem to be quite out of date.
Another mode of access is supposedly
nfs://192.168.1.248/nfs/mcstuffy
using this in a mount command gets NFS URL not supported. dolphin and konqueror do not see it either.
It sounds more like /mnt/HD/HD_a2/mcstuffy is more likely a cifs exported file system than nfs. I've never configured nfs to use usernames/passwords. To do so, I think one needs kerberos configured.
Is your username on the Mycloud the same as on your linux system? If so, what happens when you do....
smbclient -L 192.168.1.248
You should be prompted for your password on the Mycloud
~]# smbclient -L 192.168.1.248 Enter WORKGROUP\root's password:
Sharename Type Comment --------- ---- ------- Public Disk WDdata SmartWare Disk WDdata TimeMachineBackup Disk mcstuffy Disk Transmission Disk Anti-Virus Essentials Disk rm3 Disk Share_Aggregation Disk Samba MSDFS Server IPC$ IPC IPC Service (2-Bay NAS) SMB1 disabled -- no workgroup available
~]# showmount -e 192.168.1.248 Export list for 192.168.1.248: /mnt/HD/HD_a2/mcstuffy * /mnt/HD/HD_a2/SmartWare * /mnt/HD/HD_a2/Public *
Apparently both smb and nfs access are provided to the shares. As was suggested in another response adding the user and password of the client system to the NAS allowed access. Also it was suggested that ssh access had been noted elsewhere. The web page for the NAS provides a check box to enable ssh access with a disclaimer about any changes voiding the warranty. To be explored.
On 09/03/2021 00:33, Robert McBroom via users wrote:
~]# smbclient -L 192.168.1.248 Enter WORKGROUP\root's password:
Sharename Type Comment --------- ---- ------- Public Disk WDdata SmartWare Disk WDdata TimeMachineBackup Disk mcstuffy Disk Transmission Disk Anti-Virus Essentials Disk rm3 Disk Share_Aggregation Disk Samba MSDFS Server IPC$ IPC IPC Service (2-Bay NAS) SMB1 disabled -- no workgroup available
~]# showmount -e 192.168.1.248 Export list for 192.168.1.248: /mnt/HD/HD_a2/mcstuffy * /mnt/HD/HD_a2/SmartWare * /mnt/HD/HD_a2/Public *
Apparently both smb and nfs access are provided to the shares. As was suggested in another response adding the user and password of the client system to the NAS allowed access. Also it was suggested that ssh access had been noted elsewhere. The web page for the NAS provides a check box to enable ssh access with a disclaimer about any changes voiding the warranty. To be explored.
Well, you ran smbclient under the Linux's root account. So, naturally, you're being prompted for root's password when connecting.
So, you are now able to mount both shares via NFS?
On Mon, 8 Mar 2021 at 12:33, Robert McBroom via users < users@lists.fedoraproject.org> wrote:
~]# showmount -e 192.168.1.248 Export list for 192.168.1.248: /mnt/HD/HD_a2/mcstuffy * /mnt/HD/HD_a2/SmartWare * /mnt/HD/HD_a2/Public *
Apparently both smb and nfs access are provided to the shares. As was suggested in another response adding the user and password of the client system to the NAS allowed access. Also it was suggested that ssh access had been noted elsewhere. The web page for the NAS provides a check box to enable ssh access with a disclaimer about any changes voiding the warranty. To be explored.
See: https://community.wd.com/t/mounting-mycloud-ex2-on-a-linux-desktop/98215 was able to mount the NAS using nfsv4.
See the client parts of https://fedoraproject.org/wiki/User:Renich/HowTo/NFS and https://access.redhat.com/solutions/3773891 and leave the server config alone for now. The first thing to check is the NFS version support. On the client run:
# rpcinfo -p <NAS-ip>
You may need id mapping if user and group ID's differ (to check, use "id username").
On 3/8/21 3:36 PM, Ed Greshko wrote:
On 09/03/2021 00:33, Robert McBroom via users wrote:
~]# smbclient -L 192.168.1.248 Enter WORKGROUP\root's password:
Sharename Type Comment --------- ---- ------- Public Disk WDdata SmartWare Disk WDdata TimeMachineBackup Disk mcstuffy Disk Transmission Disk Anti-Virus Essentials Disk rm3 Disk Share_Aggregation Disk Samba MSDFS Server IPC$ IPC IPC Service (2-Bay NAS) SMB1 disabled -- no workgroup available
~]# showmount -e 192.168.1.248 Export list for 192.168.1.248: /mnt/HD/HD_a2/mcstuffy * /mnt/HD/HD_a2/SmartWare * /mnt/HD/HD_a2/Public *
Apparently both smb and nfs access are provided to the shares. As was suggested in another response adding the user and password of the client system to the NAS allowed access. Also it was suggested that ssh access had been noted elsewhere. The web page for the NAS provides a check box to enable ssh access with a disclaimer about any changes voiding the warranty. To be explored.
Well, you ran smbclient under the Linux's root account. So, naturally, you're being prompted for root's password when connecting.
So, you are now able to mount both shares via NFS?
yes, adding the client userid and password as a user on the MyCloud enabled nfs to connect.
On 3/8/21 5:37 PM, George N. White III wrote:
On Mon, 8 Mar 2021 at 12:33, Robert McBroom via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
~]# showmount -e 192.168.1.248 Export list for 192.168.1.248 <http://192.168.1.248>: /mnt/HD/HD_a2/mcstuffy * /mnt/HD/HD_a2/SmartWare * /mnt/HD/HD_a2/Public * Apparently both smb and nfs access are provided to the shares. As was suggested in another response adding the user and password of the client system to the NAS allowed access. Also it was suggested that ssh access had been noted elsewhere. The web page for the NAS provides a check box to enable ssh access with a disclaimer about any changes voiding the warranty. To be explored.See: https://community.wd.com/t/mounting-mycloud-ex2-on-a-linux-desktop/98215 https://community.wd.com/t/mounting-mycloud-ex2-on-a-linux-desktop/98215 was able to mount the NAS using nfsv4.
See the client parts of https://fedoraproject.org/wiki/User:Renich/HowTo/NFS https://fedoraproject.org/wiki/User:Renich/HowTo/NFS and https://access.redhat.com/solutions/3773891 https://access.redhat.com/solutions/3773891 and leave the server config alone for now. The first thing to check is the NFS version support. On the client run:
|# rpcinfo -p <NAS-ip> |
You may need id mapping if user and group ID's differ (to check, use "id username").
~]# rpcinfo -p 192.168.1.248 program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100003 3 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100003 3 udp 2049 nfs 100227 3 udp 2049 nfs_acl 100021 1 udp 34321 nlockmgr 100021 3 udp 34321 nlockmgr 100021 4 udp 34321 nlockmgr 100021 1 tcp 35321 nlockmgr 100021 3 tcp 35321 nlockmgr 100021 4 tcp 35321 nlockmgr 100005 1 udp 37101 mountd 100005 1 tcp 57249 mountd 100005 2 udp 38322 mountd 100005 2 tcp 44879 mountd 100005 3 udp 49287 mountd 100005 3 tcp 59055 mountd 100024 1 udp 47505 status 100024 1 tcp 50765 status
Trying the ssh login gives
~]# ssh -l sshd 192.168.1.248 sshd@192.168.1.248's password:
BusyBox v1.30.1 (2020-09-04 02:41:28 UTC) built-in shell (ash) Enter 'help' for a list of built-in commands.
root@MyCloudEX2Ultra ~ # help Built-in commands: ------------------ . : [ [[ alias bg break cd chdir command continue echo eval exec exit export false fg getopts hash help history jobs kill let local printf pwd read readonly return set shift source test times trap true type ulimit umask unalias unset wait root@MyCloudEX2Ultra ~ #
Seems like BusyBox has been modified to remove all of the really useful commands. Looked at the list of commands for ash and tried a few but they were not there. Not even ls
On 09/03/2021 23:21, Robert McBroom via users wrote:
yes, adding the client userid and password as a user on the MyCloud enabled nfs to connect.
OK. I find that quite odd. But I've not heard much praise of those WD products.
If you did a "df -T" on your system does it show the mount as "nfs" or "nfs4"?
Either way, good to hear it is all working for you now.
On Tue, 9 Mar 2021 at 17:01, Ed Greshko ed.greshko@greshko.com wrote:
On 09/03/2021 23:21, Robert McBroom via users wrote:
yes, adding the client userid and password as a user on the MyCloud
enabled nfs to connect.
OK. I find that quite odd. But I've not heard much praise of those WD products.
Network servers often manage to screw up in ways that are easily fixed if they are hosted on a full-service OS but need "restore from backups" on appliances.
If you did a "df -T" on your system does it show the mount as "nfs" or "nfs4"?
If it shows "nfs", it might be helpful to adjust the mount command to use nfs4 for the build-in file locking.
Either way, good to hear it is all working for you now.
Robert -- hope it continues to work for a few years.
On 10/03/2021 08:56, George N. White III wrote:
If you did a "df -T" on your system does it show the mount as "nfs" or "nfs4"?If it shows "nfs", it might be helpful to adjust the mount command to use nfs4 for the build-in file locking.
If it shows "nfs" I'm not sure adjusting the mount command would have any effect.
AFAIK, if one uses the generic "mount" command the /etc/nfsmount.conf file is used to determine the first version to try during mount negotiation. The default is 4.
So, I think, if df shows "nfs" that would mean the attempt to mount with version 4 has failed.
-
Ed Greshko -
George N. White III -
Robert McBroom