Comments
-
The problem is clear. The firmware tar is not able to unpack the package.tgz file. A solution could be to repack the spk file on a more mature Linux system. (Didn't test that, I'm don't use Plex myself.) But I can't provide a repacked file because I'm not allowed to redistribute Plex.
-
Can you access the webinterface? If not, can you when you remove the designated disk?
-
How do you set the IP address without access to the NAS? Are you assigning an address in the right subnet?
-
typing <ipofnas> into explorer opens a web-browser window… That should be \\<ipofnas\. Without the double backslash Explorer has to guess which protocol to use. And I think it defaults to http. Don't know why that yields an empty page though.
-
Don't know. I pinged the administrator of that website, but he hasn't answered yet.
-
The 16 TiB limit is per volume. So yes, you can create 2 16TB volumes on 4 16TB disks. (How? 2xraid1? 2xraid5 would leave 4*5TB unused.)
-
There is some feedback window which tells which process is using all that CPU time. What does it show?
-
That can certainly be done, using the command line. You can enable the ssh server (somewhere in network settings) and login over ssh. Then you have to find the mountpoints of the disks. These are in /e-data, so the command ls /e-data/ will give you the mountpoints. Then enter the empty disk: cd /e-data/<some-hex-code>/ and…
-
Is you client in the same network as the NAS? And are you accessing it on it's local IP? Samba is not designed to be used across the internet, and many ISP's block it. A firewall can be a problem. When I remember well, when you connect a Windows PC to a new network it gives you the choice between 3 levels of firewall…
-
There are basically 3 possibilities: 1) The NAS doesn't ask for an IP address. 2) The Fritzbox doesn't assign one 3) Somehow the assigned address isn't picked up by the NAS. Your description of the problem is rather short, but I think I can read that the Fritzbox has a list of detected MAC addresses. Does it also have a…
-
Do you know what the problem is? No directly. You are aware you should exchange <ip-of-nas> by the actual ip address of the NAS?
-
Yes, that is possible, but way beyond the goal. Samba is already running on the NAS. Actually it's the main function of the NAS. You only have to configure your client to access it. If you are on a Windows PC, all you have to do is typing \\<ip-of-nas>\ in the address bar of explorer. On Linux (and maybe also on a Mac) you…
-
As a Win32 worm cannot run on a Linux/Armv7 box, I guess an infected Windows client keeps putting the file on that NAS.
-
The 'reset' button on the front is not a reset button, but a power button. A short press signals the OS to shutdown gracefully. A longer press 'just cuts the power'. The reset button on the back should be used to reset your admin password.
-
I'm not aware of that problem. Are you sure it's the NAS, and not your router? remotely from the Web ? Have you checked if you can still access the NAS locally?