hey guys,

 

I just had a short failure of power and after rebooting unraid didn't add the drives back to my cache (eventhough they were still visible in unmounted devices). So added them back, unfortunately in (most likely) the wrong order. So after that, I shut down the server and exchanged the disk.cfg and super.dat on the usb stick with an backup I had from this night using my windows PC, booted it up, but it's still not working. I'm getting "unmountable: unsupported or no file system". The FS is zfs (encrypted). Any suggestions on how to tackle this further?

The Cache drives are mirrored, so I'm also wondering how I can mount at least one of them manually to not loose any data (nightly backup was done, but there are some changes).

 

[UPDATE1]

running cryptsetup luksOpen /dev/nvme0n1 my_encrypted_volumecryptsetup luksOpen /dev/sdd my_encrypted_volume returns:

Device /dev/nvme0n1 is not a valid LUKS device.

 

 

cryptsetup --debug luksDump /dev/nvme0n1 outputs:

# cryptsetup 2.6.1 processing "cryptsetup --debug luksDump /dev/nvme1n1"
# Verifying parameters for command luksDump.
# Running command luksDump.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device /dev/nvme1n1.
# Trying to open and read device /dev/nvme1n1 with direct-io.
# Initialising device-mapper backend library.
# Trying to load any crypt type from device /dev/nvme1n1.
# Crypto backend (OpenSSL 1.1.1v  1 Aug 2023) initialized in cryptsetup library version 2.6.1.
# Detected kernel Linux 6.1.106-Unraid x86_64.
# Loading LUKS2 header (repair disabled).
# Acquiring read lock for device /dev/nvme1n1.
# Opening lock resource file /run/cryptsetup/L_259:0
# Verifying lock handle for /dev/nvme1n1.
# Device /dev/nvme1n1 READ lock taken.
# Trying to read primary LUKS2 header at offset 0x0.
# Opening locked device /dev/nvme1n1
# Verifying locked device handle (bdev)
# Trying to read secondary LUKS2 header at offset 0x4000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x8000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x10000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x20000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x40000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x80000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x100000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x200000.
# Reusing open ro fd on device /dev/nvme1n1
# Trying to read secondary LUKS2 header at offset 0x400000.
# Reusing open ro fd on device /dev/nvme1n1
# LUKS2 header read failed (-22).
# Device /dev/nvme1n1 READ lock released.
Device /dev/nvme1n1 is not a valid LUKS device.
# Releasing crypt device /dev/nvme1n1 context.
# Releasing device-mapper backend.
# Closing read only fd for /dev/nvme1n1.
Command failed with code -1 (wrong or missing parameters).

 

cryptsetup repair /dev/nvme1n1 outputs:

WARNING!
========
Really try to repair LUKS device header?

Are you sure? (Type 'yes' in capital letters): YES
Device /dev/nvme1n1 is not a valid LUKS device.

 

So it seems like the the luks header has been damaged, so I'm looking for a way to repair it.

 

Thank you in advance

Autchi

Edited November 6, 20241 yr by Autchirion

Unless of have a backup of the LUKS heathers, I don't think it will be possible to recover.

I assumed so, so I tried to regenerate them, following this guide:

https://unix.stackexchange.com/questions/741404/overwritten-luks-with-a-partition-table/741850#741850

 

however, when I run stdbuf -oL strings -n 64 -t d /dev/nvme0n1 | grep '"keyslots":' I get two headers, but I also got two keys, so right now I just tried to go with the two lines where he only gets one. So right now I'm trying to find the correct header and get some input from someone who can help me with luks headers (especially if there are two 🙂 )