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

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?

Edited July 29, 20196 yr by westptx

Disks 3 and 4 have been disabled, disks are only disabled if there's a write error, you'll need to rebuild them (or if they are fine use a new config and re-sync parity).

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.

3 minutes ago, westptx said:

It would be awesome if that was mentioned somewhere in a log

Read/write errors are logged, but syslog doesn't survive a reboot, you should have system notifications enable, you'll get a warning when something like that happens.