24 minutes ago, J Morris said:

I do believe the data for disk2 is still being emulated correctly

Not sure I follow what you did, and it doesn't look like a standard procedure, but If the emulated disk is mounting then the rebuilt disk should as well.

25 minutes ago, J Morris said:

as I see a /mnt/user0 folder in the filesystem

That hasn't anything to do with disk2 or emulated disks, post current diags.

Alright, here are the logs.

hoth-diagnostics-20251209-1130.zip

Stop the array, click on disk2 and change the fs to auto, start the array, and post new diags and the output from

wipefs /dev/md2p1

Array must be started, and despite the name, that command as is won't wipe anything.

Done. Here is the output (there was none):
root@Hoth:~# wipefs /dev/md2p1

root@Hoth:~#

Thank you again for your assistance @JorgeB.

hoth-diagnostics-20251209-1252.zip

41 minutes ago, J Morris said:

(there was none):

That means there's no filesystem signature present, suggesting parity isn't valid and isn't emulating the disk correctly. Do you still have old disk 2 intact?

Just now, JorgeB said:

That means there's no filesystem signature present, suggesting parity isn't valid and isn't emulating the disk correctly. Do you still have old disk 2 intact?

Yes I do. Took it out so it stayed intact.

Recommend installing that disk, making sure it mounts, resyncing parity, then doing the replacement.

Alright. Will I need to reset config again since its smaller than the disk that's currently disk2?

Just now, J Morris said:

Will I need to reset config again since its smaller than the disk that's currently disk2?

Yes, you'll need to do a new config

Alright, disk2 has appeared again in file manager (wasn't there before so you were right about it not emulating correctly). The parity sync is in progress and I'll add the new disk once its done. Thanks again for your help @JorgeB !