trurl

I'm not sure split level matters in this scenario. My experience with rsync, for example, is that it also created all the subfolders in advance. At that point nothing to split. Here is the way I handled this when I noticed it happening. When it began to actually copy files, it went in alphabetical order of the folders. I just started at the other end of the alphabet and moved folders it hadn't copied yet to other disks.

Did you try this?

Did you reboot?

Can you get to the command line with telnet/ssh?

You aren't in SAFE mode anymore. Try it in SAFE mode without dockers/VMs.

Since the array is not started can't really see which user shares actually exist, but you have a .cfg file in config/shares anonymized as c---e.cfg That suggests you have created (perhaps accidentally) a user share named "cache", and the screenshot seems to be complaining about creating a pool named the same as a user share.

If you tried to copy them all in one batch, then probably Krusader created the empty folders in advance. Those empty folders all went to one disk because they didn't take much space. Then it copied the files into those already created empty folders.

Since user shares appear to be working normally and the disk is emulated, it seems like Unraid is working correctly. But you didn't answer my questions, most especially this part

Free trial. Great forum. Unraid is already a NAS, of course, that hosts VMs and dockers. Some of the things you want to do may not even require a VM, there are currently 879 dockers and plugins listed on the Unraid Apps page.

There isn't really enough to go on in your description to determine that the problem is related to Unraid, or even to determine if there is a problem. Download speed also depends on the source, for example.

You only want to run NewPerms on specific User Shares to avoid breaking dockers which might have other permission settings for their appdata. There is also the Docker Safe New Permissions if you want to do it all at once, which will skip appdata.

All New Config does is reset your disk assignments. Nothing else is changed.

Sounds like you have nothing to worry about. Building parity will simply calculate parity by reading all other disks and write the result to the parity disk. Since parity is calculated last in your scenario, it will be in sync with all other disks. Clearing disks is only about keeping existing parity when you add a disk to a new slot. A clear disk is all zeros and so doesn't change the parity calculation.

You will always get a parity check if it can't record a clean shutdown. Let it complete just in case.

My guess is a coding error overwrote the OS folders. Hopefully it didn't get to /boot or /mnt yet. Reboot and make sure you don't run that script again.

Any disk assigned as parity will get overwritten with parity, simple as that.

So memtest failed?

Why? You might be able to delete old logs (syslog.1, syslog.2, ...) in /var/log. Doubt you can delete the current syslog.

Tools - New Config

I have split the posts you made about this same problem in other threads all into this thread. Please don't post about the same problem in multiple places. It makes it impossible to coordinate responses. Crossposting has been considered a bad thing on message boards since before the World Wide Web.

Probably anything entered at the command line would be reset on reboot since the OS is in RAM.

Rebuild of disk1 already completed when diagnostics were taken Sep 10 09:13:36 ur1-meppel kernel: md: recovery thread: recon D1 ... ... Sep 10 14:04:45 ur1-meppel kernel: md: sync done. time=17469sec Sep 10 14:04:45 ur1-meppel kernel: md: recovery thread: exit status: 0 And you are having connection issues on cache Sep 10 09:09:17 ur1-meppel kernel: ata1.00: ATA-10: KINGSTON SA400S37120G, 50026B77834CF063, SBFKB1E2, max UDMA/133 ... Sep 10 09:25:12 ur1-meppel kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Sep 10 09:25:12 ur1-meppel kernel: ata1.00: failed command: FLUSH CACHE Sep 10 09:25:12 ur1-meppel kernel: ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 30 Sep 10 09:25:12 ur1-meppel kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Sep 10 09:25:12 ur1-meppel kernel: ata1.00: status: { DRDY } Sep 10 09:25:12 ur1-meppel kernel: ata1: hard resetting link Don't know anything about Proxmox. Are you referring here to Unraid User Shares? User Share names are anonymized in Diagnostics (take a look for yourself to see what I mean). You have a number of shares all beginning with p and ending with s, and there are share .cfg files 2 shares that don't exist, one beginning in p and ending in s, and another beginning in c and ending in r. Looks like most of your disks are empty or nearly so. Did you format any of them recently, perhaps because they were unmountable?

Try renaming config/network.cfg on flash then reboot to get back to default network settings

That is the painless part. Previous Apps on the Apps page will reinstall all your dockers exactly as they were. If you do nuke docker.img, you will have to recreate any custom docker network you had. If you were following Spaceinvader video to setup letsencrypt then you did.