43 minutes ago, trurl said:

Post new diagnostics

7 minutes ago, Einar Eliassen said:

looks like its gonna take many hours

Are you doing check filesystem? Shouldn't take hours.

3 hours ago, Einar Eliassen said:

After just starting the array again the first time it all looks good ? All disks are green.

That's expected after New Config. But you didn't follow instructions.

3 hours ago, JorgeB said:

Unassign disk13 and disk15

-Start array (in normal mode now), and post new diagnostics

3 hours ago, Einar Eliassen said:

I try to have them switch places.

You can't change disk positions or you will invalidate parity2.

10 hours ago, Einar Eliassen said:

I have started a check on the drive....looks like its gonna take many hours.

Running through the night it just finished and found filesystem corruption. Pressed Fix....is this going to run for the same amount of hours ?

Do you have another copy of anything important and irreplaceable?

I kinda improvised as the disks didnt show up as faulty. Just the single one.

Pretty sure there wasnt anything precious on that drive, just annoying to have it replaced.

But if this works I hope the system will be stable again.

I am hoping the root of all this evil was the cable splitters. Because of all the molex connection needed. There simply wasnt enough of them provided by the PSU.

One of the cables was power to SATA + adapter for SATA-to-Molex-splitter. So yeah...that might have been a bit of a hack to get it all powered.

Now I have 2 cables with 4 molex-power connectors each from the PSU manufacturer.

The filesystem check may fix the issues, is it still running?

19 minutes ago, JorgeB said:

The filesystem check may fix the issues, is it still running?

Yes, it was running all night, then this morning I had the option to click FIX. It has been working since then on "fixing". Taking way longer than I thought, so maybe not sure it will work.

But I can take the loss of the drive if needed, its a price I am willing to pay to get this up and running again.

3 minutes ago, Einar Eliassen said:

Yes, it was running all night, then this morning I had the option to click FIX. It has been working since then on "fixing". Taking way longer than I thought, so maybe not sure it will work.

But I can take the loss of the drive if needed, its a price I am willing to pay to get this up and running again.

What format was the drive? With XFS for instance fixing normally only takes a few minutes unless the drive is corrupted beyond repair. The same applies to the file system check which you earlier mentioned as running all night.

48 minutes ago, itimpi said:

What format was the drive? With XFS for instance fixing normally only takes a few minutes unless the drive is corrupted beyond repair.

Encrypted XFS

Just now, Einar Eliassen said:

Encrypted XFS

Since that is an XFS variant then I believe that normally one would expect a file system check to be reasonably fast (do not use encrypted file systems myself so could be wrong). The only reason that the initial check normally takes a long time with XFS is if the superblock at the start of the file system cannot be found and a scan of the entire disk has to be made to look for a backup version but then you get a message saying this is happening.

The repair should still be fast unless the file system is really badly corrupted and in such cases it is rarely worth doing the repair as most of the files/folders end up in the lost+found folder which can take significant manual effort to resolve so it is normally easier to restore from backups.

So it stopped trying to fix it now I guess. The status window kinda bugged out, so I couldnt see the final message. But I can now press FIX again if I want to fix it.

But that will just result in nothing again I think. So I guess my next step is just to format the sucker....

So I just formatted the drive, and it all seems to be stable, for now at least. Hoping the random drive faults wont happen again now that I hopefully have the best possible powercable that is available to me.