{"id":2405,"date":"2023-10-19T23:16:44","date_gmt":"2023-10-20T03:16:44","guid":{"rendered":"https:\/\/blog.lufamily.ca\/kang\/?p=2405"},"modified":"2023-10-19T23:16:45","modified_gmt":"2023-10-20T03:16:45","slug":"rescue-usb-using-ventoy","status":"publish","type":"post","link":"https:\/\/blog.lufamily.ca\/kang\/2023\/10\/19\/rescue-usb-using-ventoy\/","title":{"rendered":"Rescue USB using Ventoy"},"content":{"rendered":"\n

In a previous post<\/a>, I described how I created an encrypted USB as a mechanism to pass information to my sons should anything happen to myself or my wife during our vacation last year.<\/p>\n\n\n\n

Well we are about to go on another long trip, and I decided to streamline the process with Ventoy<\/a>.<\/p>\n\n\n\n

Instead of creating a custom Live image whenever a new Ubuntu distribution is released, I have decided to use Ventoy to separate the Linux distribution away from the encrypted data.<\/p>\n\n\n\n

Even though Ventoy supports persistence live distributions, I stayed away from them because I want to be able to replace the current distributions on the USB with new distributions with the least amount of work.<\/p>\n\n\n\n

Below are the instructions that I used to create this Ventoy USB in an Ubuntu desktop environment.<\/p>\n\n\n\n

Download Ventoy from https:\/\/github.com\/ventoy\/Ventoy\/releases<\/a>. Since we are on an Ubuntu operating system, so we want to download the tar.gz<\/code> file. Once the tar.gz<\/code> file is downloaded, extract the file and you should have a ventoy-X.Y.Z<\/code> subdirectory with X.Y.Z<\/code> being the version number of Ventoy.<\/p>\n\n\n\n

Identify the target USB key device using the lsblk<\/code> command (e.g. \/dev\/sdb<\/code>) and goto the ventoy-X.Y.Z<\/code> subdirectory and execute a command like the following:<\/p>\n\n\n\n

sudo .\/Ventoy2Disk.sh -I -r 10000 \/dev\/sdb<\/code><\/pre>\n\n\n\n
The above command will reserve 10000 MB as a tail end partition which we can use for a LUKS (encrypted) partition. We can create this LUKS partition called Succession by using the GNOME Disks app<\/a>. We use a key that is at least 24 characters in length. It can be longer if you like but it becomes quite cumbersome to type.<\/p>\n\n\n\n
Mount the LUKS partition, and then copy the the private data to the LUKS partition which was previously named Succession. My private data resides on the bigbird<\/code> host.<\/p>\n\n\n\n
scp -r bigbird:\/Volumes\/Personal\\\\ Information \/media\/kang\/Succession<\/code><\/pre>\n\n\n\n
After the copying is completed, ensure that the “Personal Information” directory has the proper permission set (e.g. chmod 777 \"Personal Information\"<\/code>).<\/p>\n\n\n\n
Assuming that all the ISO images are in the ISO directory, copy all the ISO images by executing the following command:<\/p>\n\n\n\n
tar cf - ISO | (cd \/media\/kang\/Ventoy; tar xvf - )<\/code><\/pre>\n\n\n\n
I included the following ISO images:<\/p>\n\n\n\n
    \n
  • clonezilla-live-3.1.0-22-amd64.iso<\/li>\n\n\n\n
  • kali-linux-2023.3-live-amd64.iso<\/li>\n\n\n\n
  • kali-linux-2023.3-live-arm64.iso<\/li>\n\n\n\n
  • ubuntu-22.04.3-desktop-amd64.iso<\/li>\n\n\n\n
  • ventoy-1.0.96-livecd.iso<\/li>\n\n\n\n
  • Win10_22H2_English_x64v1.iso<\/li>\n<\/ul>\n\n\n\n
    Note that not all the above ISO images are required, but the live Linux distrbituions are convenient in case you want to access the emergency information in the Succession LUKS partition in a hurry. The other ISO’s are just handy to have.<\/p>\n\n\n\n
    NOTE: When booting into a linux kernel with a PC with a discrete GPU that may not be compatible with a Live Distribution, you may need to use the nomodeset<\/code> boot option.<\/p>\n\n\n\n
    Below is a YouTube video I made that shows how to gain access to the private encrypted data on the USB.<\/p>\n\n\n\n
    \n