itimpi

You should never assume that Limetech staff will see any particular forum post, so it might be worth contact support to see what they have to say.

That will be the Mac trying to be 'helpful' and automatically opening the downloaded ZIP file to show its contents. Find the zip file on your Mac and post that.

You probably rebooted so that the read/write counts got reset (or used the Reset Statistics button) so you no longer see the earlier writes to disk1 in the counts.

Looking at you share settings what you are seeing is expected behaviour. With you largest data drive being 10TB and using high-water allocation method then the points for switch drives occur at the 5GB, 2.5GB, 1.25GB etc points. You are currently in the 2.5GB zone, and since disk1 is down to 1.25GB free Unraid has switched to disk2.

At least it seems to be a reproducible error that follows a particular stick. I wonder if it worth cleaning the contacts on the suspect stick just in case?

How data gets distributed across your drives depends on your User Share settings. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread so we can see how you have things set up.

That suggests to me that there might be something else going on. Hopefully the suggested screenshot + diagnostics might show something.

The USB Creator tool always seems to be a bit fussy about the systems it runs on. The Manual install method is far more reliable in my experience.

There should be a checkbox against the Start button that will allow you to start the array. The missing disk will then be emulated using the combination of the other drives plus parity (assuming you have valid parity) so the array will function as though the drive was still present. Whether you move files off the 'emulated' drive or simply wait for the replacement to arrive so you can rebuild its contents to the replacement is up to you. Are you sure the drive has really failed rather than simply been disabled because a write to it failed? Cabling and power issues are far more common than real drive failures. We should be able to get a good idea from your diagnostics if one of these apply.

If you are having problems with how long some of the array level operations take then you might want to consider installing the Parity Check Tuning plugin to at least offload the times those operations are running to be run in increments outside prime time. This give you better prime time performance at the cost of the total duration being longer.

Make sure you are not overclocking the RAM (a XMP profile IS an overclock). You can also try with less RAM sticks installed as sometimes it is the memory controller that cannot handle the number of installed RAM sticks without issues. Sometimes the CPU has a max RAM speed it can handle as well so check the manual for that.

With stock Unraid it will forget where it was and you have to start again from the beginning. If you install the Parity Check Tuning plugin and set the restart option in the plugin settings, then as long as the reboot gets a clean shutdown it will continue from where it had already reached.

Stop array unassign parity1 ready to make Unraid forget current assignment start array to commit change stop array assign parity1 start array to sync both parity drives

Corruption of BTRFS file systems seems to be a common symptom of potential RAM problems. Note that if you boot in UEFI mode then you need get a more recent version from memtest86.com that can boot in UEFI mode. It would not do any harm to use that version anyway even if you do boot Unraid in legacy mode.

If you try to copy the files off the cache then since the file system is BTRFS which automatically checksums files the ones that are corrupt will refuse to copy without error.

Each pool can be configured independently both in terms if the number of drives in it, the type of file system and any raid levels.

You can have many pools individually set up with their own configuration. Each User Share can specify which pool (if any) will be used for caching purposes for that particular share. Is that what you wanted know?

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

There is no built-in capability to schedule spin ups.

Have you tried running Tools->New Permissions on the share in question in case something went wrong with permissions that is stopping them being visible over the network. The other thing to try is to run a check filesystem on all the array drives (by clicking on them in the Main tab to get to that option) to check there is no corruption at that level causing a problem.

The biggest problem is that the driver for the main array does not (currently at least) support trim.

No. It looks like the parity drive must have dropped offline. It is worth checking the power and SATA cabling to the drive. You may have to power cycle the server to get the drive back online.

Well it works for me! The important thing is that the DNS Server and gateway on your local LAN is used so you can get back out to the internet which is why the local LAN needs to be on a different subnet to the remote client.

You can write a script that does that but bear in mind: the flash drive cannot be labelled ‘UNRAID’ as otherwise the boot process would get confused the licence would not be valid for the backup as it is tied to a specific flash drive GUID. Perhaps the real question is why do you want to do this? You could use the Unraid Connect plugin to achieve automated backups to the cloud without having to write a script or tie up a flash drive.

Does not the “Remote Access to LAN” option give you what you want? The one caveat is that your Unraid server must be on a different subnet to your remote users if you want the DNS to work correctly. Typically this means at least avoiding the 192.168.0.x and 192.168.1.x subnets for your local LAN as these are common defaults for many routers.