MNM-Node_1 was brought offline for upgrades
Timeline
MNM-Node_2 storage corrupted
ATDevs Team Coordination Server stopped working
ATDevs Team Council was formed
Current status and notes
Quite a bit of time has passed since everything failed or died. We're working on getting services back up using our new server, but this will take a while. Here is what we're actively working on, what is planned for the future, and what is done:
Loading status details…
This is the thing people can help with
If you know how to make a LUKS partition open, even though the partition table was accidentally wiped, please email [email protected]. Here's the details of it:
An uncaught typo while trying to wipe the GPT partition table of a drive caused the wrong block device to get wiped. This 1TB block device contained the following partitions:
- 200-300MB LUKS partition/free space (this partition is not cared about, as it had no contents)
- Remainder of the space was another LUKS partition
The LUKS header of partition 2 was confirmed intact. Attempts were made to force-open the partition with the device in read-only mode, but all only errored because cryptsetup seems to not know what to do with a LUKS partition outside of a partition.
The LUKS partition contains a ZFS partition that also has encryption enabled. We only need to be able to access this partition and read all of its data. We'll handle the rest from there.
Something created a new partition table, but doesn't seem to have done anything to the LUKS partition.
If you can help, we'll provide more details about different things with it, including the raw image of the LUKS header.