trurl

You have to either change the split level or manually create folders on disk6 for new TV share files.

@itimpi didn't realize you had been so busy with the wiki. Great job. I need to link it more often.

But also note that using an earlier version, then upgrading to 6.9.x, while it would still support the old alignment, will require reformatting to take advantage of the new alignment.

Let me know if you want to work on those other things.

Looks good. You might consider moving domains share to cache also but I didn't mention it since you didn't have VMs enabled. Depends on how you configure VMs to use storage.

Why have you allocated 50G to docker.img? 20G should be more than enough unless you have something misconfigured. Also your appdata, domains, system shares have files on the array. This will make dockers/VM keep array disks spinning since these files will be open, and docker/VM performance will be impacted by parity updates. But, that isn't what you were asking about. SMART for all disks looks fine. My guess is connection issues. These are common when mucking about in the case. Check all connections, SATA and power, both ends, including splitters. Maybe consider changing SATA cable.

I usually follow up with a noncorrecting parity check to verify that there isn't some other problem. The only acceptable result is exactly zero.

Unraid doesn't have wifi so it requires an ethernet connection to the network. What do you mean about connecting a monitor by ethernet to the server? By "monitor" do you actually mean a display monitor, or do you mean another PC? You can connect a display monitor directly to your server using whatever video capabilities and cable your server hardware and display monitor support. Ethernet isn't normally used to connect a display monitor to a computer. Maybe something I am not understanding about your question.

I assume that is either writing to cache, or no parity installed. Even so, I thought the scenario you were considering now was going from old server to pc to new server. You could go directly between servers and leave out the PC. Or just do one disk at a time directly on the new server with Unassigned Devices and leave the network out completely. You wouldn't even need the old server running and could just go with your already licensed flash drive on the new server.

Here is the 6.9beta25 thread: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta25-available-r990/ I actually did the multiple pool setup on beta22: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta22-available-r955/ But when the new partitioning for SSDs came out I redid them on beta25. So, I have moved appdata, domains, system shares around quite a bit lately. The multiple pools especially came in handy for the repartitioning, since I just moved them manually with mc between the SSD pools so I could repartition. Much faster than getting Mover and the parity array involved.

@Hoopster was the inspiration for my latest (re)build: https://forums.unraid.net/topic/93149-mitx-motherboard-which-can-support-7-drives-on-board/

You might want to consider using the latest beta since you are doing a new SSD. It has a new partition scheme for SSDs that make them more efficient, as well as multiple fast (cache) pools. I have a fast pool consisting of 1 NVMe for my dockers and VMs, and another with 2 mirrored SSDs for caching.

Instead of odd I would say it was expected.

There are some very nice new features of the latest beta. Multiple fast (cache) pools for SSDs, more efficient partitioning of SSDs. I am running it on my main server and seldom hesitate to run betas because I have a good (enough) backup plan.

If you don't install parity until the transfer is complete. Maybe even then it won't be that fast if you have another computer in the middle.

Builtin Unraid disk encryption doesn't require anything from Nerd Pack. It is possible, though, that something in Nerd Pack replaced some builtin Unraid library. What happens if you boot in SAFE mode?

And you can just connect the old ReiserFS disks to that new server as Unassigned Devices and copy their data that way.

Everything about your configuration is in the config folder on flash. Some things from that configuration that you will not want on the new server is the license .key from that other flash, since each flash must have its own unique key, and the super.dat file, which contains your disk assignments.

The config folder on flash has everything about your configuration

Go to Settings - Docker and disable Docker. Also, delete docker.img from that same page. There are several other changes to make here later. Don't enable Docker again until instructed. Go to Settings - VM Manager and disable VMs. Don't enable VMs again until instructed. Go to each of your User Shares and set them to Use cache: Yes Go to Main - Array Operation and click Move. Wait for it to finish. Then post new Diagnostics.

The simple thing to do would be to just get everything moved from cache, replace cache, then get everything that belongs on cache (appdata, domains, system) moved back to cache. And along the way recreate docker.img at only 20G. As for getting things moved, Mover will move cache-yes user shares from cache to array. And it will move cache-prefer user shares from array to cache. But, mover can't move open files, so to get things moved, you will have to disable Docker and VM services in Settings. Also, mover won't move duplicates, so it is possible there will need to be some manual cleanup along the way. Now that I have explained the basic ideas and the reasons for them, I will give some steps to accomplish parts of this. We will take new diagnostics along the way to see the results and determine what needs to be done. Starting in my next post in this thread.

Unraid does not automatically move files between array disks. Perhaps you mean it is writing new files to the second HDD. This is part of the user share "media" And this is also part of the user share "media". This is the user share "downloads". And this is part of the user share "downloads". The user shares are simply the aggregated top level folders on cache and array disks. For example, any top level folder named "media" on any cache or array disk are in the user share "media". But you say If that is indeed what you have for the host path, I don't know why you would want to do it that way. Post your docker run command for any of these as explained at this very first link in the Docker FAQ:

And you are running with little RAM. But looks like you only have basic NAS functionality configured so that might be OK. Can you add more RAM?

I will not be available until later tomorrow. We can work on it then or maybe someone else will take this up.

Actually, the way you have listed these mappings: is unclear. You don't specify the absolute path /downloads for qbtorrent, instead you have the relative path downloads. I think you must not have it that way really since the docker run command would error out before even getting qbtorrent started. The best way to give us a complete and unambiguous idea of how you have a container configured is to post your docker run command as explained at this very first link in the Docker FAQ: