Results 1 to 7 of 7

Thread: NFS cant be that hard

  1. 01-29-2011, 05:56 AM #1
    wilsonal2
    wilsonal2 is offline Junior Member
    Join Date
    Jan 2011
    Posts
    11

    Default NFS cant be that hard

    So what is the deal with getting NFS to work? Some people say NP while others, like me have the {mount.nfs: access denied by server while mounting valkyrie NAS:/mnt/data/public} error when mounting on a Linux box. My Linux box does see the NAS nfs export (showmount -e) And I do have firmware V01R04 installed. And I did follow "BadIntentions" procedure, with the only change is the network ip (mine is 10.25.70.xx and the post show 192.168.1.xx) I bought this unit because of NFS so I can attach it to my linux system as a NAS. SMB does work, but if I wanted to use windoze protocol, I would have just installed Samba and saved myself the $$$. So did Patriot really "lie" when they said this NAS will do NFS or is the Doc's just lacking A LOT of information to get it to work correctly???? Hmmmmm can you say Class Action....
    Reply With Quote Reply With Quote
  2. 01-31-2011, 08:14 PM #2
    BadIntentions
    BadIntentions is offline Super Moderator
    Join Date
    May 2010
    Location
    In the land of make believe.
    Posts
    505

    Default

    Quote Originally Posted by wilsonal2 View Post
    So what is the deal with getting NFS to work? Some people say NP while others, like me have the {mount.nfs: access denied by server while mounting valkyrie NAS:/mnt/data/public} error when mounting on a Linux box. My Linux box does see the NAS nfs export (showmount -e) And I do have firmware V01R04 installed. And I did follow "BadIntentions" procedure, with the only change is the network ip (mine is 10.25.70.xx and the post show 192.168.1.xx) I bought this unit because of NFS so I can attach it to my linux system as a NAS. SMB does work, but if I wanted to use windoze protocol, I would have just installed Samba and saved myself the $$$. So did Patriot really "lie" when they said this NAS will do NFS or is the Doc's just lacking A LOT of information to get it to work correctly???? Hmmmmm can you say Class Action....

    A simple request for help will net you better results. More flies with honey etc etc.

    Your IP range is the issue. The device is not very intelligent, and has only granted access to 192.168.1.xxx (as you put it) by default.

    You can activate telnet, login in, and edit the exports file to allow your IP range. As an NFS/linux user i am sure you are familiar with how to do this.
    I AM NOT A PATRIOT MEMORY EMPLOYEE.

    But they have, on occasion, bribed me with hardware.



    I am happy to help, but don't PM me. Post a thread in the appropriate forum so others may benefit and offer assistance.
    Your lack of planning is not an emergency on my part.
    Reply With Quote Reply With Quote
  3. 02-05-2011, 07:54 PM #3
    wilsonal2
    wilsonal2 is offline Junior Member
    Join Date
    Jan 2011
    Posts
    11

    Default NFS cant be that hard

    Thanks for the reply. I DO tend to forget about the "fly w/honey" stuff. I've tried to edit the {/etc/exports} file. But I only have "read Only" permissions. I'm logged in, via telnet as user "admin" with "root" as the PW. and can not edit this file due to my permissions. my /etc/exports file is as follows:
    /mnt/data/public 10.25.70.*(rw,sync,all_squash,anonuid=501,anongid= 501)

    So I would think that the network is setup correctly. As you stated The device is not very intelligent. Maybe there is something that I am missing that only allows the box to exports NFS shares to the 192.168.1.* (or xx) network.
    Reply With Quote Reply With Quote
  4. 02-06-2011, 05:24 AM #4
    wilsonal2
    wilsonal2 is offline Junior Member
    Join Date
    Jan 2011
    Posts
    11

    Default

    Oh to make sure that I'm clear about the network that my NAS/NFS box is on. My network IP's are Linux Server is 10.25.70.200 and the NAS/NFS Valkyrie is 10.25.70.80 . Both units have a subnet of 255.255.255.0 The command:
    showmount -e 10.25.70.80
    returns:
    Export list for 10.25.70.80:
    /mnt/data/public 10.25.70.*
    Reply With Quote Reply With Quote
  5. 02-06-2011, 05:29 PM #5
    BadIntentions
    BadIntentions is offline Super Moderator
    Join Date
    May 2010
    Location
    In the land of make believe.
    Posts
    505

    Default

    check hosts.allow and see what it says
    I AM NOT A PATRIOT MEMORY EMPLOYEE.

    But they have, on occasion, bribed me with hardware.



    I am happy to help, but don't PM me. Post a thread in the appropriate forum so others may benefit and offer assistance.
    Your lack of planning is not an emergency on my part.
    Reply With Quote Reply With Quote
  6. 03-29-2011, 03:18 AM #6
    Wavebourn
    Wavebourn is offline Junior Member
    Join Date
    Feb 2011
    Posts
    3

    Default

    I still don't understand what to do...

    Thanks for the cgi script, I accessed the box, but as a user with uid=502, and I don't see anything under /etc/ that allows mounting by NFS for 192.168.1.0/24 only.

    No exports file, no hosts.allow. What are you talking about, gentlemen?

    Edit: Oops... Sorry, I did not read what cgi script that enabled root access said... But it does not matter: I can access the box as a root, but still can't figure out how to remove that network-related restrictions. Looks like it is set by the nfs - related cgi script, but can't figure out where...

    Any help?
    Last edited by Wavebourn; 03-29-2011 at 04:21 AM.
    Reply With Quote Reply With Quote
  7. 03-17-2012, 12:33 AM #7
    wilsonal2
    wilsonal2 is offline Junior Member
    Join Date
    Jan 2011
    Posts
    11

    Default

    See http://www.patriotmemory.com/forums/...problem-SOLVED!!!!!
    to mount via NFS
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules