Configuration NAS Wolverine: Difference between revisions
Jump to navigation
Jump to search
Line 22: | Line 22: | ||
:* Become root <code>sudo -i</code> |
:* Become root <code>sudo -i</code> |
||
:* Set acccess rights with <code>chmod 700 /volume1/homes/admin /volume1/homes/baddreams /volume1/homes/borg</code> |
:* Set acccess rights with <code>chmod 700 /volume1/homes/admin /volume1/homes/baddreams /volume1/homes/borg</code> |
||
:: {{red|Question}}: Should we instead enable option ''Hide sub-folders and files from users without permissions''? |
|||
* Remove <code>#recycle</code> folder from share <code>/volume1/borg</code>. |
* Remove <code>#recycle</code> folder from share <code>/volume1/borg</code>. |
||
:* Otherwise <code>borg init</code> complains there is already something there. |
:* Otherwise <code>borg init</code> complains there is already something there. |
Revision as of 23:32, 15 September 2018
Specification
- Synology DS118
- Seagate IronWolf 4 TB
- Hard drive 3.5" 4 To 5900 RPM 64 Mo Serial ATA 6 Gb/s for NAS (bulk)
Installation
- Visit http://diskstation:5000/ (or go to http://find.synology.com)
- Issue: Must use chromium (requires java)
- Enable QuickConnect.
- Must visit http://QuickConnect.to/immie-wolverine
- Recommended packages: Moments, Video Station, Media Server, Audio Station, Hyper Backup, Drive, Download Station.
- Don't share device location for find.synology.com.
From now on, we must use http://wolverine:5000 to connect to the NAS.
- Configuration
- File Service
- SMB, change workgroup name from WORKGROUP to
HELL
. - Disable AFP.
- SMB, change workgroup name from WORKGROUP to
- Set user only permission in /homes:
- Login with ssh using
admin
account. - Become root
sudo -i
- Set acccess rights with
chmod 700 /volume1/homes/admin /volume1/homes/baddreams /volume1/homes/borg
- Question: Should we instead enable option Hide sub-folders and files from users without permissions?
- Login with ssh using
- Remove
#recycle
folder from share/volume1/borg
.
- Otherwise
borg init
complains there is already something there.
- Otherwise
Troubleshooting
Login failure and "because the encryption key is invalid..."
Symptoms:
- Login fails.
- Message
Because the encryption key is invalid the password has been transmitted in the clear
Cause:
- The hostname used is wrong (eg. still using old URL http://diskstation:5000).
Solution:
- Use correct hostname (http://wolverine:5000).