westptx

Thanks for the clarification. It would be awesome if that was mentioned somewhere in a log or a "reasons why this disk was disabled" just to clear any confusion. I went ahead and started the parity rebuild, so we're back to normal operations.

As an addendum, I created a flash drive from a recent flash backup and that seems to locate everything just fine. However, I already switched USB drives once and unRaid is preventing me from using my backup. That being said, if the backup flash drive can read the drives perfectly fine...then why can't the original flash drive? Is this some sort of bug?

So I've been trying to move around some drives (physically) in my machine. When I went to turn the server back on, 2 of the disks in my array are detected, but they've been kicked out of the array into the unassigned pool: I know that Disk 3 was ...MFQ8 and I also know that Disk 4 was ....MQ5N. What I don't understand is have they been discarded by unraid? I thought drives were registered to the array by their serial numbers and not their mount points. In case that it's helpful, i've attached my diagnostic logs as well. I'm quite confused and I really don't want to have to rebuild those two drives all over again. Also, it is worth noting that the array has not been started at all since I started dealing with this issue. atlas-diagnostics-20190729-0227.zip

Oh yeah, i definitely get the difference. Once I actually looked at my script, clearly, I realized the errors of my ways. While I'm not the most well-versed in linux-based OSes, I know enough to be dangerous....and dumb!

I believe that I read that user0 is the data disk only while user has that + cache. For the time being, I have cache turned off during the import. I'll turn it back on once I get back to a steady-state operation.

Alright, someone hand me the newb hat. My rsync command was forcing the files to /mnt/disk1. Jesus...that was dumb.

Well hmmm...so, no matter what I do..if I manually create a folder that doesn't already exist in the share, it is still pegged to disk 1, no matter what. Even when I try to run unBalance, it makes it seem like there are no other drives available: The planning stage found that no folders/files can be transferred. This might be due to one of the following reasons: - The source share(s)/folder(s) you selected are either empty or do not exist in the source disk - There isn't available space in any of the target disks, to transfer the share(s)/folder(s) you selected Check more disks in the TO column or go to the Settings page, to review the share(s)/folder(s) selected for moving/copying or to change the amount of reserved space.

Ah, so I think this is it. I'm importing 1 disk at a time since they're all being replaced and there are many cases where the folder is created but some other disk has the data. I think this hit the nail on the head. I was going crazy trying to figure out what on earth was going on. Thanks for the clarification.

I'm quite new to Unraid...but I like what I see. I'm in the process of importing my data into a brand new array however, only one hard drive is actively being written to. I actually just got a free space warning for the disk in question. From what I understand of the high-water allocation (the setting used for all of my shares), I would've expected data being written to Disk 1 until 4 GB left, then Disk 2, 3, 4, etc. However, that doesn't seem to be the case. I went ahead and grabbed logs if that helps. As far as I know, everything was set to the default settings from what I initially created the array. If anyone has any pointers, that would be awesome!