You're right? But it was in the log file? Edit: I normally include an inxi -F with support requests. I don't know why I forgot this time. My bad. I did say that I was trying to recover from the Manjaro machine in the first post, but didn't make it clear that was the same machine that I had accidentally deleted the partition on.CHS only plays a role in legacy operating systems. You did not name the operating systems you used.
I am using Manjaro UEFI/GTP x3 (1 desktop, 1 workstation and 1 laptop) another system is Debian 11/Windows 10 efi/gtp dual boot, and my laptop is QubesOS/Debian 11 dual boot on 2 separate SSDs also efi/gtp. I was attempting to repair a separate Windows 11/Dell machine for a family member. Was down to either the motherboard being faulty or the SSD, so I installed the SSD into my Manjaro desktop, and attempted to install Windows on it. I had tried to use the DELL recovery tool, then install Manarjo, Debian and Ubuntu onto the Dell machine all without success earlier. All of the gnu-linux based installations had selected the NVME drive first to partition and install an OS on by default. They also didn't want to make changes to the partitions by default and all had confirmation screens for actually writing the partition table explaining with BOLD CAPS that I was making destructive changes to the disk. Windows does not have this "feature". I quickly skipped through setup skimming all the EULA BOLD CAPS Vogon Poetry lines, and it chose by default to install on my SLOW 'storage' SATA drive which has many system backups on it, raw video footage for a project I'm scrubbing/editing and colour grading on instead of the very fast PCIE 4.0 4x NVME 1TB drive. It did not ask for confirmation after choosing to delete the partition. Windows also as a "feature" wrote the changes without confirmation as well and showed me a blank 10TB SATA disk next to a badly corrupted (but working as it turns out) 1TB NVME. That's when I facepalmed and started this journey. (*as for the DELL story, we got a replacement motherboard through warranty and the NVME (and rest of the components for that matter) seems to have survived the mobo death.
I did the repairs mostly on the Manjaro Desktop system that I deleted the 10TB partition on. I also moved the SATA drive and did some of the recovery on the Manjaro workstation, so I could work on some of the film with some missing footage until I got the newer data back like I did last night finally. I had a slightly older and smaller backup that was about 2 months behind (I referred to it earlier in this thread being too small for the recovery attempt), but was missing some irreplaceable footage shot this summer, which only emphasizes the importance of REGULAR backups.
I will re-scan the copy I have now working after the copy is complete to give you a log file with the disk outside of the enclosure.Please provide the logfile requested above with the drive being in the enclosure it came with. I am interested in finding out why the log line referring to LUKS was incomplete.
The most recent logfile contained in this thread is already one from inside the enclosure using efi/gtp mode viewtopic.php?p=36505#p36505
The first one was in Intel mode not in this thread and deleted. I didn't bother with it anymore after you asked me to re-scan using the beta branch instead of the stable one. I can rescan it with the breadboard (the plastic case is broken) USB 3.0 interface in efi/gtp mode in the beta version after I have my data back if you like. It will probably take 2 days or so given the transfer rates and then scanning again.