Erik M

Thanks again for walking me through this mess!

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.

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?

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.

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 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 rebooted and now it came up allowing me to start the array.

I had started it in maintence mode and went to Disk 4 Check Filesystem Status and thats where it was in the endless loop. Then I mounted the drive from slot 4 in the unassigned devices area

It will not allow me to start the array though

I was able to mount it as an Unassigned Device

It is not emulating Disk 4 and is in an endless loop Should I put it back into slot 4 and then start the array and check the file syatem again. Phase 1 - find and verify superblock... error reading superblock 4 -- seek to offset 4000786989056 failed couldn't verify primary superblock - attempted to perform I/O beyond EOF !!! attempting to find secondary superblock... .found candidate secondary superblock... error reading superblock 4 -- seek to offset 4000786989056 failed unable to verify superblock, continuing...

Here is the diagnostic after disableing Disk 4 PAH9J6XT is the 4TB but in the unassigned pool 2EJ0H9VX is the new 8TB in the unassigned pool - Future replacement for the bad Drive 4 tower-diagnostics-20260109-1842.zip

Honestly I can't remember but if I did it was very little and I am ok with losing whatever that was. I don't think anyone did write to it though. As soon as I noticed the errors building up on Disk 4, I pulled the array offline.

I'm sorry, yes Serial Number: P4GA8S4C is the original Disk 1. While doing the rebuild, it only got to just under 3% if that makes any difference.

I do not. If I reassign that to it's original Drive 1 slot and remove the new 8tb, do I need to rebuild it? Or can I just go ahead and after reassigning it, replace the drive 4 and then start a rebuild from there? Over the next few months, my objective is to replace the 4TB drives 1 at a time as they are aging out. I think its been 4 to 5 years on a couple of them. By the way, I really appreciate the help. I'm in over my head on this one for sure.