Configuration NAS Mnemosyne: Difference between revisions

From miki
Jump to navigation Jump to search
No edit summary
Line 104: Line 104:
=== NFS ===
=== NFS ===
(See [http://www.linuxtopia.org/online_books/network_administration_guides/NFS_tutorial/index.html HOW-TO page here])
(See [http://www.linuxtopia.org/online_books/network_administration_guides/NFS_tutorial/index.html HOW-TO page here])
<ul>
* Enabled NFS service
<li> Enabled NFS service</li>
* Edited NFS privilege for share '''volume1/backup''', allow '''rw''', for client '''minimoy'''
<li> Edited NFS privilege for share '''volume1/backup''', allow '''rw''', for client '''minimoy'''</li>
⚫
<li> Then from NFS client, tried</li>
<source lang="bash">
⚫
sudo mkdir -p /net/mnemosyne/backup
⚫
sudo mount mnemosyne:/volume1/backup /net/mnemosyne/backup
⚫
# mount.nfs: access denied by server while mounting mnemosyne:/volume1/backup
⚫
</source>
⚫
<li>Looking into NAS file <tt>/var/log/messages</tt> (need to ssh as root on the NAS), there is the line:</li>
<source lang="text">
⚫
... refused mount request from HOST00245402988d.HELL for /volume1/backup (/): no export entry
⚫
</source>
⚫
<li>So it seems that the connection is refused because the DNS name of the NFS client does not match the export line in file <tt>/etc/exports</tt></li>
<source lang="bash">
⚫
/volume1/backup minimoy.HELL(rw,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)
⚫
</source>
⚫
</ul>


⚫
Then from NFS client, tried
<div style="padding-left:2em;"><source lang="bash">
⚫
$ sudo mkdir -p /net/mnemosyne/backup
⚫
$ sudo mount mnemosyne:/volume1/backup /net/mnemosyne/backup
⚫
mount.nfs: access denied by server while mounting mnemosyne:/volume1/backup
⚫
</source></div>
⚫
Looking into NAS file <tt>/var/log/messages</tt> (need to ssh as root on the NAS), there is the line:
⚫
... refused mount request from HOST00245402988d.HELL for /volume1/backup (/): no export entry
⚫
So it seems that the connection is refused because the DNS name of the NFS client does not match the export line in file <tt>/etc/exports</tt>
⚫
/volume1/backup minimoy.HELL(rw,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)
Found a working recipe on [http://forum.synology.com/wiki/index.php/How_to_enable_NFS_on_the_Synology_Server this page]:
Found a working recipe on [http://forum.synology.com/wiki/index.php/How_to_enable_NFS_on_the_Synology_Server this page]:
<ul>
* Content of file <tt>/etc/exports</tt>
<li> Content of file <tt>/etc/exports</tt></li>
⚫
/volume1/backup 172.19.100.102(rw,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)
<source lang="bash">
⚫
* Touched file <tt>/var/lib/nfs/rmtab</tt> (because non-existent), :
⚫
/volume1/backup 172.19.100.102(rw,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)
<div style="padding-left:2em;"><source lang="bash">
</source>
⚫
$ touch /var/lib/nfs/rmtab
⚫
<li> Touched file <tt>/var/lib/nfs/rmtab</tt> (because non-existent) :</li>
⚫
$ cd /
<source lang="bash">
⚫
$ /usr/sbin/exportfs -a # Update list of exported filesystem
⚫
touch /var/lib/nfs/rmtab
⚫
</source></div>
⚫
cd /
⚫
* On NFS client, mount the NFS share with:
⚫
/usr/sbin/exportfs -a # Update list of exported filesystem
<div style="padding-left:2em;"><source lang="bash">
</source>
⚫
$ sudo mount mnemosyne:/volume1/backup /net/mnemosyne/backup

⚫
</source></div>
⚫
<li>On NFS client, mount the NFS share with:</li>
<source lang="bash">
⚫
sudo mount mnemosyne:/volume1/backup /net/mnemosyne/backup
</source>
</ul>



Open issues:
Open issues:
* How to make it work using '''hostname''' instead of IP addess? Additional problem is that at each boot DNS Relay table on the ADSL router is reset to 'HOSTxxxxxxxxxxx' for wired interface on the NFS client, hence making it not recognizable for the NFS server.
* How to make it to work using '''hostname''' instead of IP addess?<br/>Additional problem is that at each boot DNS Relay table on the ADSL router is reset to 'HOSTxxxxxxxxxxx' for wired interface on the NFS client, hence making it not recognizable for the NFS server.
* How to deal with Access Control? I want '''root''' to be mapped to '''nobody''', and write access only allowed for one user (which requires password to login)?
* How to deal with Access Control? I want '''root''' to be mapped to '''nobody''', and write access only allowed for one user (which requires password to login)?<br/>This can be done with the following export line:
<source lang="bash">
: &rarr; This can be done with the following export line:
⚫
/volume1/backup minimoy.HELL(rw,no_wdelay,root_squash,insecure_locks)
<div style="padding-left:2em;">
</source>
⚫
/volume1/backup minimoy.HELL(rw,no_wdelay,root_squash,insecure_locks)
⚫
</div>

Revision as of 18:59, 16 May 2011

Reference Information

  • Device: Synology NAS DS409+
  • Name: Mnemosyne
  • Disk Station Manager: http://mnemosyne:5000
  • Admin account: admin

First install

  • Mounted 4 harddrives Western Digital Caviar Green 2TB WD20EADS
  • Plugged power & Ethernet (on home intranet), then power on.
  • (under Linux) Launched DSAssistant.i386... Server not found
  • (reboot in Windows) Launched Synology Assistant... found!
  • Step-by-step installation (see data below)
  • Disk formatting (system partition / data partition)
  • Logged into Disk Station Manager (see data below)
    • !!! login does not work with Internet Explorer (password not accepted) !!!
  • Set up language
  • Set up e-mail notification
  • Created volume
  • Created users
  • Created shared folders
  • Defined file sharing (windows,NFS)

Configuration

  • System
    • Network
      • Server Name: Mnemosyne
      • Network config: automatic (DHCP)
    • Language
      • Display: English
    • Time
      • Time zone: (UTC+01:00) Brussels, Copenhagen, Madrid, Paris
    • Notification
      • SMTP server: smtp.scarlet.be
      • SMTP port: 25
      • Primary mail: michael.peeters@scarlet.be
      • Secondary mail: michael.peeters@noekeon.be
    • Power
      • Scheduled Power On: Weekdays, 17:30
      • Scheduled Power Off: Daily, 02:00
    • Firmware Update:
      • Version: DSM 2.1-0844 on 2009/04/21 (file synology_ppc853x_409+_0844.pat)
  • Privileges
    • Users:
      • admin (admin user)
      • guest (enabled)
      • archives (Store archives)
      • backup (User to create backup)
      • movies (store movies)
      • musics (store musics)
      • photos (Store photos)
      • videos (Store videos)
    • Shared folder
      • archives (Archives SW, documents...) (group Users: RO - user archives: RW) (NFS RO: gryphon IP / Minimoy IP)
      • backup (For PC backups) (group Users: RO - user backup: RW) (NFS RO: gryphon IP / Minimoy IP)
      • movies (DVD Movies, SVCD...) (group Users: RO - user movies: RW) (NFS RO: gryphon IP / Minimoy IP)
      • musics (Audio CD, mp3, ogg...) (group Users: RO - user musics: RW) (NFS RO: gryphon IP / Minimoy IP)
      • photos (Photos album) (group Users: RO - user photos: RW:) (NFS RO: gryphon IP / Minimoy IP)
      • public (Public folder) (group Users: RW) (NFS RW: gryphon IP / RO: Minimoy IP)
      • videos (Family videos...) (group Users: RO - user videos: RW:) (NFS RO: gryphon IP / Minimoy IP)
  • Storage
    • Volume
      • Volume 1: 4 disk volume, RAID 5, Complete consistency check
  • File Sharing
    • Win/Mac OS
      • Enable Windows file service: enabled
        • Enable Windows file service
        • Workgroup: HELL
        • Optimize CIFS database operations: disabled (see [1])
        • Enable Local Master Broser: disabled
        • Enable CIFS Recycle Bin: disabled
      • Enable AppleTalk: disabled
    • NFS
      • NFS Service: enabled
    • Network Services
      • Terminal: enable SSH service

Statistics

Some statistics related to our NAS

Task Source Size Time Rate
DVD to NAS Unicorn 4,23GB 15m48s avg 4,687kB/s, peak 7,290kB/s
DVD to NAS Unicorn 4,32GB 16m03s avg 4,708kB/s, peak 7,701kB/s
DVD to NAS Unicorn 3,93GB 14m34s avg 4,717kB/s, peak 7,553kB/s
DVD to HDD Unicorn 3,65GB 4m49s avg 13,263kB/s, peak 19,393kB/s
HDD to NAS Unicorn 3,65GB ~7m00s avg 8,900kB/s
DVD to NAS Unicorn 3,65GB 11m23s avg 5,612kB/s, peak 7,848kB/s

How-To

SSH

  • Enable SSH service
  • To have root access, log in as user root, and use same password as admin account.

NFS

(See HOW-TO page here)

  • Enabled NFS service
  • Edited NFS privilege for share volume1/backup, allow rw, for client minimoy
  • Then from NFS client, tried
    • sudo mkdir -p /net/mnemosyne/backup
sudo mount mnemosyne:/volume1/backup /net/mnemosyne/backup
# mount.nfs: access denied by server while mounting mnemosyne:/volume1/backup
  • Looking into NAS file /var/log/messages (need to ssh as root on the NAS), there is the line:
    • ... refused mount request from HOST00245402988d.HELL for /volume1/backup (/): no export entry
  • So it seems that the connection is refused because the DNS name of the NFS client does not match the export line in file /etc/exports
    • /volume1/backup minimoy.HELL(rw,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)


Found a working recipe on this page:

  • Content of file /etc/exports
    • /volume1/backup 172.19.100.102(rw,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)
  • Touched file /var/lib/nfs/rmtab (because non-existent) :
    • touch /var/lib/nfs/rmtab
cd /
/usr/sbin/exportfs -a            # Update list of exported filesystem
  • On NFS client, mount the NFS share with:
    • sudo mount mnemosyne:/volume1/backup /net/mnemosyne/backup


Open issues:

  • How to make it to work using hostname instead of IP addess?
    Additional problem is that at each boot DNS Relay table on the ADSL router is reset to 'HOSTxxxxxxxxxxx' for wired interface on the NFS client, hence making it not recognizable for the NFS server.
  • How to deal with Access Control? I want root to be mapped to nobody, and write access only allowed for one user (which requires password to login)?
    This can be done with the following export line:
/volume1/backup minimoy.HELL(rw,no_wdelay,root_squash,insecure_locks)
Retrieved from "https://miki.immie.org/mediawiki/index.php?title=Configuration_NAS_Mnemosyne&oldid=2918"