Mijzelf  Guru Member

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?

I can think of 3 reasons why files disappear. Filesystem errors, maybe caused by disk problems. Serverside software. Clientside software Filesystem errors are unlikely. It wouldn't limit itself to a single share (unless that share is the only one on an unhealthy volume), nor would it only cause files to disappear. It would…

I am inclined to trust command line tools rather than a gui wrapper. Especially when that gui uses fantasy namings. And it's not hard, you only have to read the documentation carefully. In most cases mdadm will only allow you to do stupid things if you add the —force command line switch. In your case the biggest challenge…

The directories are in /i-data/<some-hex-code>/. But you can use the symlink /i-data/sysvol/

wouldn't then my RAID1 be with status "degraded"? Correct. The headers say the raid array should have 3 members. So when only 2 members are found the array is degraded. Of course this is only cosmetic, the redundancy is exactly the same as a 'genuine' 2 disk raid1 array. I'm afraid the only way to shrink that array to a 2…

I think it's by design. The webinterface just offers the most basic functions, among which no option to degrade an array. In that case the 'manager' pane is only selectable when an implemented manage option could be performed. But there is nothing to do with a 2 disk raid1. (Although you could convert it to a 3 disk raid1,…

Use Samba. "Windows filesharing".

You can create a 3 disk raid5 array. But I don't think the firmware allows you to convert that to a 4 disk raid5 array later. Low level that's no problem, (although lots of data have to be moved), but I don't think it's implemented in the webinterface. But I never tried, and I can be wrong, here.

Your disk 2 is also bad. And yes, it's fairly easy to create a raid5 array. The webinterface just gives you that choice when you create a new volume on your new disk 3. You can also create a raid5 array on 3 disks. In that case the usable space is 4TB.

do I need to replace disc 2 and 3, are you saying that these two are completely damaged? From your screenshot I can see disk 3 has a 'reallocated sector count' of 11920. That is high. A 2TB disk has around 4000000000 sectors, and it's not uncommon that some of them fail, over time. In that case they are 'replaced' by a…

It is supposed to.