![]() ![]() I had to manually type the code above and put up the general gist without going into the numerical output wihtin that range, but can refactor if needed for troubleshooting. The block number range is from 244889344 to 244889351 for the async page read errors Mount: /dev/mapper/luksRecover: can't read superblock FAT-fs (dm-0): unable to read boot sector TestDisk is powerful free data recovery software It was primarily designed to help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software, certain types of viruses or human error (such as accidentally deleting a Partition Table). ![]() blk_update_request: I/O error, dev loop1, sector 4096 ![]() blk_update_request: I/O error, dev loop1, sector 240793344 Buffer I/O error on dev sdb4, logical block 244889344, async page read Step 1: First thing first Launch the TestDisk on your PC, followed by pressing the Enter key once it is launched. Rebooting allowed me to run losetup with no issues. I haven't been able to find documentation on loop devices the way I found documentation on installing archlinux on the wiki.ĮDIT: I found that the reason why losetup wasn't working was because on my working install of archlinux, I had updated the kernel and hadn't rebooted. I've been referencing this thread as well: and it mentions using a loop device but I wasn't able to find documentation that takes me step by step through the process, but then now I'm finding that one of the steps it advises is to use losetup, which I can't use since I get losetup: cannot find an unused loop device. Unfortunately, I don't know where to go from here and would appreciate any help in recovering this data. ![]() So, thankfully (or at least, hopefully), testdisk didn't overwrite my LUKS header and simply did some funky partition shifting. ![]()
0 Comments
Leave a Reply. |