![installing grub on usb ext2 installing grub on usb ext2](https://forum.manjaro.org/uploads/default/original/2X/c/c8d2293c24b2bdcd82f7fa0a52d847d1b2991354.png)
Or you can use file container encryption, e.g., Veracrypt, which is what I use for all my systems. You can encrypt the home folder, but that entails a significant performance hit. First, be aware the installer doesn't support system encryption for USB installs. Please go back to the first post in the thread, hit edit (the little pencil icon) and add "Solved" to the thread title.Īs regards the USB project, I'll mention two additional thoughts. If not using, adjust partition scheme accordingly. I wouldn't bother with a swap partition on a flash drive unless is was at least 64 GB, but that's your choice.
![installing grub on usb ext2 installing grub on usb ext2](https://blog.modest-destiny.com/images/2017/04/demo-bios.jpg)
Mainly useful if you want to be able to hibernate. LM19 does not (by default, uses a swap file instead), though swap partition is still supported optionally. Note: When fabien85 and I wrote our posts, the prevailing version was Mint 18.x, which requires a swap partition.
![installing grub on usb ext2 installing grub on usb ext2](https://i.stack.imgur.com/65dgI.png)
I've done Option 1 in LM19, so that still works, and can't think of any reason Option 2 wouldn't.
INSTALLING GRUB ON USB EXT2 INSTALL
I'd like to emphasize there's no point doing full install to a 2.0 flash drive (you probably have a 3.0, but I want to make sure). Since then, I've written up Option 2 myself here. See here for links, plus a discussion of pros and cons of each. I know two methods which get around the bug. If I can't spot the solution, hopefully someone else can.Īs for the USB drive, you're going to have to do that over. I've never had to do it, but senior user Pjotr has a detailed guide on his Linux tips website. And I do agree full install is preferable to persistence in most cases.Īnyhoo, I'm pretty sure all you need to do to fix the laptop is reinstall Grub. BTW, in gold_finger's defense, UEFI was still relatively new four years ago, the installer bug had only just been discovered and wasn't widely known.