Click FIX, and it it asks to zero the log also click that, then restart the array and post new diags.

Alright I did that:

jankserver-diagnostics-20260827-1503.zip

Edited Thursday at 12:04 PM3 days by peterpeter

Array started in normal mode, please, or we cannot see if the disks are mounting.

Whoops, sorry!

jankserver-diagnostics-20260827-1633.zip

Emulated disk2 is mounted now, and repair didn't create any lost+found, so that's a good sign.

Disk3 isn't mounting as before, I'm not sure what @JorgeB had in mind for that

22 hours ago, JorgeB said:

disk3 is also not mounting due to a different problem, but let's ignore that for now

I notice disk1 has very little data, mostly just appdata and system shares. Is that expected?

1 minute ago, trurl said:

I notice disk1 has very little data, mostly just appdata and system shares. Is that expected?

Yes that is expected.

Disk3 appears to have a smaller partition than it should; we can try to fix that in the end, but first I would recommend rebuilding disk2 to a new disk, assuming the contents of the emulated disk looks OK, don't recommend using the 1.5TB you were trying to use before, as that disk is failing SMART.

21 minutes ago, JorgeB said:

don't recommend using the 1.5TB you were trying to use before, as that disk is failing SMART.

That means it might take another few days until I get a replacement drive. I'll update you guys again when I rebuild disk2 to another disk.

I rebuilt disk2 to another disk, here's the diagnostics:

jankserver-diagnostics-20260829-0015.zip

Ok, now for disk3, which xfs is expecting a partition larger than the current one, possibly larger than the actual disk, and if it's the latter, it would require rebuilding to a larger disk, but first, with the array stopped, post the output from

fdisk -l /dev/sdc

I just looked at the screenshot again - it seems like the disk is 232.89GB and the partition is 232.9? If I have to rebuild into another disk, I'm ready with a replacement drive (it's an SSD and I know that's not perfect but im working with what I have)

The partition size is correct, but XFS is expecting a partition for a 1.5TB disk, not sure how that happened, but it's likely something you did before.

I see two main options

• Rebuild the disk to a new 1.5TB or larger disk, it should then mount

• use a file recovery app like UFS Explorer; it should be able to recover the data, then reformat the disk.

2 hours ago, JorgeB said:

The partition size is correct, but XFS is expecting a partition for a 1.5TB disk, not sure how that happened, but it's likely something you did before.

I can absolutely see how it happened - I interrupted the rebuild to the larger 1.5TB disk and that probably left xfs in a confused state. I'll use UFS Explorer to transfer the data to another disk and reformat the 250GB one.