Mijzelf  Guru Member

If the volume is not the default one, the path to the file is not predictable, as the mountpoints of the volumes are random names (sysvol is not really a directory, but a symlink to the random name which contains volume 1). Yet it is easy to get a list of the random names: ls /i-data

Do you know how your volume(s) is arranged? (raid0, raid1, jbod)

You should have seen the contents of the file, but instead you see nothing. So either the file is empty, or it isn't there. Is it possible that you installed Transmission on another volume than default?

DM

Is it possible to download Zyxel packages from anywhere on the Internet? Yes, I have a backup here. Using MetaRepository you can bypass the ZyXEL repo, and point it to the backup above. Or maybe it is possible to create a package from the .run file? That is certainly possible. You could exchange the binaries in the stock…

Don't know what you mean by 'regular tape', but unless it's some special metal tape, it should be capable of isolating a 3.3V level. So if you correctly taped the 3th pin, and it didn't work out, there might have been another issue with that disk.

The editor is vi, the file-to-be-edited is '/i-data/sysvol/.PKG/Transmission/config/Transmission/settings.json', so the full command to use the editor to open that file is vi /i-data/sysvol/.PKG/Transmission/config/Transmission/settings.json

'Execute' is the wrong word here. You are executing vi, with as commandline parameter the file you want to edit. The config file for Transmission on a NAS is probably '/i-data/sysvol/.PKG/Transmission/config/Transmission/settings.json' (And forget the other path I gave, it's a mistake).

You can execute it from the command line. For that you need ssh access. Which can be problematic, as you didn't install the ssh server, and meanwhile ZyXEL has shutdown the package server.

The location of the file on a NAS is different from the location on an NSA. At least the configurations of the packages, and the packages itself are separated from each other. I'd expect the package in /i-data/md0/admin/zy-pkgs/Transmission/ but I don't know if the settings file is in …/config or …/etc.

Meanwhile the mirror(s) in the startpost don't work anymore. I have a new one on http://mijzelf.duckdns.org/zyxel/zypkg-repo/, but I'm not sure if it works. No feedback so far.

You only need to change that keys if they are currently 'no'. If not specified, they default to 'yes'. I vaguely remember that you only need to setup the right stuff in ~/.ssh/. But meanwhile it might become a problem to get the client to use the private key, as the algorithms on the NAS are outdated. Further this only…

Did you try to execute the .run file on your NAS? It's a very interesting file. It is an install script, with a tarfile glued to the end, containing binaries for i686 x86_64 armel armhf aarch64 mipsel mipseb ppc6xx and ppc500. That's why it's that huge. The 'armel' version might fit your box, but I'm not able to see if it…

Strange. The NSU runs on the same ethernet as DHCP. Have you tried the other port?