Storj on QNAP NAS how to?

Node Operators getting started
,
1

i try install qnap 1.1.4 on QNAP Service unvailable
manual settings not workin from putty, any qnow?

2
  1. Enable Container Station and ssh
  2. Generate your identity on PC/Mac, sign it with an authorization token and transfer the identity folder to your QNAP; or generate and sign it on your QNAP with app (it just can take a week rather a few hours on PC/Mac).
  3. Check your identity: Confirm the identity (if you already transferred an identity, you need to update path to the identity location in the check command).
  4. Login via ssh to QNAP
  5. Figure out what is your paths to the identity and data in the command line. If you used an qnap app, then you can execute this command to get paths:
docker inspect storjlabsSnContainer -f '{{.Mounts}}'
  1. Remove the QNAP app
  2. Run the setup step: Storage Node - Setup once, replacing "<identity-dir>" and "<storage-dir>" to their actual values (the < and > should be removed as well). Never run this command in the future for the same identity.
  3. Run a regular container: Storage Node - Run the node
  4. Check your logs: How do I check my logs? - Storj Node Operator Docs

See also an alternative way: Qnap Storagenode - #3 by sean

3

not working,

  1. identity generateg and copying to /homes/admin/identity
  2. node Folder: /homes/admin/storjnode
    docker still not starting

command from putty not working

4

i have problem witch path does no exist… what i made wrong?

5

Did you manage to enable a Container Station? Does your QNAP supports docker at all?
Please provide a command and response for “not working” situation.
By default, if you select a text in the PuTTY window, it will be copied to the clipboard, so, please paste it here between two new lines with three backticks, like this:

```
copied text here
```

perhaps it doesn’t exist? I do not know your filesystem structure, but I’m not sure that paths like /homes/ are exists on QNAP. Please check your actual paths.

Usually all user’s data is in /share/ as far as I know,

You may try to use a command

df -h

to identify mounted paths.
or at least

ls -l /share/
6

Filesystem Size Used Available Use% Mounted on
none 400.0M 280.0M 120.0M 70% /
devtmpfs 3.9G 8.0K 3.9G 0% /dev
tmpfs 64.0M 784.0K 63.2M 1% /tmp
tmpfs 3.9G 136.0K 3.9G 0% /dev/shm
tmpfs 16.0M 0 16.0M 0% /share
/dev/sdi5 7.7M 47.0K 7.3M 1% /mnt/boot_config
tmpfs 16.0M 0 16.0M 0% /mnt/snapshot/export
/dev/md9 493.5M 142.1M 351.3M 29% /mnt/HDA_ROOT
cgroup_root 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/mapper/cachedev1
50.5T 17.3G 50.5T 0% /share/CACHEDEV1_DATA
/dev/md13 417.0M 388.7M 28.3M 93% /mnt/ext
tmpfs 48.0M 60.0K 47.9M 0% /share/CACHEDEV1_DATA/.samba/lock/msg.lock
tmpfs 16.0M 0 16.0M 0% /mnt/ext/opt/samba/private/msg.sock
/dev/mapper/cachedev1
50.5T 17.3G 50.5T 0% /lib/modules/4.14.24-qnap/container-station
tmpfs 100.0K 0 100.0K 0% /share/CACHEDEV1_DATA/Container/container-station-data/lib/lxd/shmoun ts
tmpfs 100.0K 0 100.0K 0% /share/CACHEDEV1_DATA/Container/container-station-data/lib/lxd/devlxd

7

I guess this is your disk for data. So, you need to create a storagenode folder here, place the identity folder here and use the storagenode folder to store storagenode’s data.