I am running the check file system now and will let it run until it stops on it's own but what I'm seeinf is the same as I posted before with an endless loop.

If I check the Disk 4 in the unassigned devices, I can see the contents are there. I plugged in an external drive that is empty thinking I could copy the contents over to it but unbalance does not see the unassigned drives and I can't find out how to navigate there in krusader either. If we do build an array with a different drive, I can use that one. There's approx 2TB of data to move.

Ok, I may be doing it wrong. If I run the file system check on the empty slot, it's an endless loop.

If I go down to the little checkmark in the Unassigned Devices area (it only works when it is unmounted), it completes quickly and this is the result:

FS: xfs

Executing file system check/sbin/xfs_repair -n '/dev/sdc1' 2>&1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

No file system corruption detected!

If I mount the drive, the check file system is grey and can't run. Clicking on the Disk Log Information on the mounted drive, the screenshots are the result.

While we wait for any additional instructions, I am going to shutdown the server and go through all of the drive connections and reseat the memory just incase it is a bad connection causing the errors.

I did run into that when I had the drives in a cage outside of the case. That was before I got a Node 804 that can house all of my drives.

I did redo all of the cables on the drives and they are secure.

I managed to figure out krusader and am copying the files from the bad Drive 4 to a new WD Red 4TB drive.

There were only 2 shares on it and the smaller one copied over easily. The other share is 1.4TB of media. That may take a little time so I will let it run in the background and grab a little sleep.

If Unassigned was mounting no reason to think it needed checking.

Are you copying from the failed Unassigned to a new disk also Unassigned?

1 hour ago, Erik M said:

krusader

There is a built-in File Manager in Unraid V7, simpler (and safer) to use that but if krusader is working let it.

I just glanced over the thread, but it looks like it's resolved? Please let me know if my help is still needed.

Everything copied over with krusader.

Should my next step be to put an empty drive into Drive 4 slot and have the array rebuild?

Or, should I move the drive I just copied the files to into that slot and do a new config preserving all?

2 hours ago, Erik M said:

move the drive I just copied the files to into that slot and do a new config preserving all?

Preserve All, but since it is not the drive that was assigned to that slot, you will still have to assign it. And you must let it rebuild parity.

Thank you again! I have set it about rebuilding the parity. It should finish Sunday afternoon then I'll see what happens.

After all of this is settled, I'll look at moving the SSD in the array a pool like you mentioned before. The only thing I use that drive for is holding files for Tdarr to transcode. When they are finished transcoding, I move them to the array.

I believe after reading Cache Pools that a single ssd pool will be enough for my requirements.

I'm also toying with the idea of making the new 8TB drive I have into a 2nd Parity drive instead of a data drive. I have 8TB of space free on the array. That will take me a while to fill. No real need for a larger data pool other than I see low free space. My idiot brain starts thinking anything under 50% free space is unacceptable even though I know that as far down as 30% free if just fine.

43 minutes ago, Erik M said:

I believe after reading Cache Pools that a single ssd pool will be enough for my requirements.

According to your earlier diagnostics, you already had 500G SSD as cache. You could add that other 500G SSD to that same pool and get a mirror. In addition to caching, that pool already has your Docker/VM related shares on it, as they should be.

If you remove that drive from the array you will have to New Config and rebuild parity again, of course.

47 minutes ago, Erik M said:

making the new 8TB drive I have into a 2nd Parity drive instead of a data drive.

Debatable whether or not you have enough drives to justify dual parity, but if you don't need it for capacity I guess you might as well. You can always go back to single parity if you need another data disk.

Thanks again for walking me through this mess!