

Goal now is to try mounting at an the offset suggested, and do some additional reading on the subject (and mount command). * Which I can access and see that it's grubĬryptsetup luksUUID /dev/sdc2 showed 4396dbd3-d71c-4d9b-a477-3a8c882a1631 I/O size (minimum/optimal): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id Type Sector size (logical/physical): 512 bytes / 512 bytes The first will be a small boot partition and the other will be the LVM.Looks to be the case per blkid: You likely then will only have 2 partition in the MBR. Although /boot as ext2 partition may need fsck.
#Kali linux ntfs undelete how to
How to Resize a LUKS Encrypted File System.Īnd then if you can mount you may need fsck on the LVM ext4 partition(s), not the physical partitions.
#Kali linux ntfs undelete install
Sudo apt-get update & sudo apt-get install lvm2 cryptsetup How to: Mount & Resize an Encrypted Partition (LUKS) also mount for repairs While primarily about resizing, the first part is about mounting the LVM & encrypted partition. If flash drive is gpt partitioned and has ESP - efi system partition, I would expect it was UEFI.īut did flash drive boot on its own or only when plugged into original system and was using ESP or MBR from internal drive?ĭo you have /EFI/Boot/boot圆4.efi in the ESP on flash drive? That is the only way flash drives directly boot, if not booting from internal drive. If you booted Centos in BIOS mode then it would not show in /sys/firmware.

Last edited by james_wood2 June 6th, 2017 at 12:18 AM. Also, I believe the LUKS partition was sitting inside an LVM partition according to fdisk -l, and my own memory. Optimally I would like to restore the partition table so the drive is again bootable w/o sign of damage, however, if that's not possible, I would like to uncover a way to recover the damaged LUKS partition (or is it 'drive' given I had opted to encrypt the drive at installation?). Now, I am still trying to work through the Linux+ certification, so I am not afraid to say this mistake is beyond my training and experience to date. I understand from reading there may be a way to mount the disk at an offset, then try and open the drive.


Afterwards, I used dd to 'clone' the original damaged disk so that I ensure I now have a 'practice' disk to try and recover from.ĭata not handy, however I had once tried recovering the partitions, but could not unlock the LUKS partition afterwards. In the process, I lost the partition table to the original disk and now can no longer boot from it (the backup also failed to clone with this Clonezilla method). A week back something went wrong when I was using Clonezilla to clone a USB disk to another of the same model. Thought I'd try this forum first, seeing how another thread I read earlier today seemed beneficial.
