J Morris

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 !

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

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

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

Alright, here are the logs. hoth-diagnostics-20251209-1130.zip

Yes I believe that is because I restarted the server a few times. After looking through many forum posts I made a new config and assigned the old 14tb parity to disk2 slot. I then started the array to do a parity check on the new 18tb drive with write corrections unchecked. After some time it succeeded finding 0 errors. At this point I stopped the array, switched the 14tb to an 18tb to trigger a data-rebuild and it succeeded this morning. However, the disk2 format was still reporting as luks file system and Unmountable: wrong or no file system. The disk should be xfs - encrypted. If I stop the array and change it to that format then start it again it reports Unmountable: disk not encrypted or something to that affect. The system is still trying to format the disk. Shouldn't the rebuild have set the disk to the correct file system? At this point I'll stop clicking things and wait for advice. Thank you! Edit: I do believe the data for disk2 is still being emulated correctly as I see a /mnt/user0 folder in the filesystem. Also the original disk is out of the server at the moment with its contents intact. It had reallocated sectors but still seems to work fine.

Sorry to resurrect an old thread. I just attempted a parity swap and after about 26 hours, it was at 99% for a bit and then instead of saying complete or something to that effect, the copy button came back like it wants to do the parity sync again. My situation is this, I have a failing 14TB data HD. My current parity is 14TB. The plan was to do the parity swap to a new 18TB drive and add another new 18TB data drive as well. Instead of waiting for the copy for another 26 hours with the server down, can I add a new 18TB drive as the parity 2, let the data rebuild complete, then move the old 14TB parity 1 into the array for data? I see the commands from @JorgeB but I clicked copy again after the page refreshed to see if it was actually going to go through it all again (it was). At this point I'm not sure if the original parity copy is complete or not. It doesn't seem to think so as setting it to the parity disk does not allow the array to start. I also considered just swapping the 14TB parity to the 18TB parity, but it seems risky with a failing drive. Thanks for your help! Edit: Preemptively adding diags. hoth-diagnostics-20251205-1623.zip

Hi all, I'm having issues with the Enshrouded Docker container not updating but I found a quick solution. The error in the logs is: Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Error! App '2278520' state is 0x6 after update job. This has happened with the two previous updates and both times I just deleted the container, copied over the saves, and went from there. However, this time I figured out you can just rename/delete the two app manifest .../appdata/enshrouded/steamapps/ and then restart the container and it will update just fine. I was thinking its a permissions issue, but I renamed the old appmanifest files rather than deleting them and they've got the same permissions as the new files it created.