Configuration NAS Wolverine: Difference between revisions

From miki
Jump to navigation Jump to search
m (Mip moved page Configuration Synology DS118 to Configuration NAS Wolverine: Use machine's name)
No edit summary
Line 1: Line 1:
== Specification ==
== Reference information ==
* Synology DS118
* Device: '''Synology NAS DS118''' (one bay).
* Name: '''Wolverine'''.
* Seagate IronWolf 4 TB
* Web interface: '''http://wolverine:5000''', then log in with admin account '''admin'''.
: Hard drive 3.5" 4 To 5900 RPM 64 Mo Serial ATA 6 Gb/s for NAS (bulk)
* SSH: <code>ssh admin@wolverine</code>, then <code>sudo -i</code> to get root access.
:Or use any other member of the ''administrator'' group.
* 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 ==
== Installation ==
Line 12: Line 18:
* '''Don't''' share device location for find.synology.com.
* '''Don't''' share device location for find.synology.com.


From now on, we must use '''http://wolverine:5000''' to connect to the NAS.
From now on, we must use to connect to the NAS.


;Configuration
;Configuration

Revision as of 11:09, 16 September 2018

Reference information

  • Device: Synology NAS DS118 (one bay).
  • Name: Wolverine.
  • Web interface: http://wolverine:5000, then log in with admin account admin.
  • SSH: ssh admin@wolverine, then sudo -i to get root access.
Or use any other member of the administrator group.
  • 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

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 to connect to the NAS.

Configuration
  • File Service
  • SMB, change workgroup name from WORKGROUP to HELL.
  • Disable AFP.
  • 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?
  • Remove #recycle folder from share /volume1/borg.
  • Otherwise borg init complains there is already something there.

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:

Solution: