Grub2 dual boot with Ubuntu or Mint 18 on encrypted disk - Remix OS for PC

I am trying to add remix OS as a 2nd boot option to a machine that is currently single booting Mint 18 with full disk encryption.
I followed the tutorial for the new marshmallow Remix installed alongside Mint and it worked great on a non-encrypted test box, but I'm having issues doing it on my primary laptop that was installed with full disk encryption option at install time for Mint 18.
How do I need to modify the grub entry for Remix to make it work? For reference here is the grub setup for my Mint installation:
Code:
menuentry 'Linux Mint 18 Cinnamon 64-bit, with Linux 4.4.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-21-generic-advanced-1e6da0b0-6645-4904-a8f7-0c2e7ddbce83' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 ffd7222b-aa1e-44d6-a010-e33cefd386d1
else
search --no-floppy --fs-uuid --set=root ffd7222b-aa1e-44d6-a010-e33cefd386d1
fi
echo 'Loading Linux 4.4.0-21-generic ...'
linux /vmlinuz-4.4.0-21-generic root=/dev/mapper/mint--vg-root ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.4.0-21-generic
}
Here is the default Remix OS entry that I need to modify so that the encrypted volume is mounted first the same way it is for Mint. I have no idea what I need to do to achieve this. Looking above I see the set root options many times... evidently that doesn't do what I thought it did because I've tried every version of setting the root below and getting it badly wrong. My remix lives in /remix just like in the tutorial except that my / is on the encrypted volume.
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/system.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}

---

Bump... pleeze haaalp

---

getut said:
I am trying to add remix OS as a 2nd boot option to a machine that is currently single booting Mint 18 with full disk encryption.
I followed the tutorial for the new marshmallow Remix installed alongside Mint and it worked great on a non-encrypted test box, but I'm having issues doing it on my primary laptop that was installed with full disk encryption option at install time for Mint 18.
How do I need to modify the grub entry for Remix to make it work? For reference here is the grub setup for my Mint installation:
Code:
menuentry 'Linux Mint 18 Cinnamon 64-bit, with Linux 4.4.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-21-generic-advanced-1e6da0b0-6645-4904-a8f7-0c2e7ddbce83' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 ffd7222b-aa1e-44d6-a010-e33cefd386d1
else
search --no-floppy --fs-uuid --set=root ffd7222b-aa1e-44d6-a010-e33cefd386d1
fi
echo 'Loading Linux 4.4.0-21-generic ...'
linux /vmlinuz-4.4.0-21-generic root=/dev/mapper/mint--vg-root ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.4.0-21-generic
}
Here is the default Remix OS entry that I need to modify so that the encrypted volume is mounted first the same way it is for Mint. I have no idea what I need to do to achieve this. Looking above I see the set root options many times... evidently that doesn't do what I thought it did because I've tried every version of setting the root below and getting it badly wrong. My remix lives in /remix just like in the tutorial except that my / is on the encrypted volume.
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/system.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}
Click to expand...
Click to collapse
See whether this helps http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
You'll have to instruct grub to decrypt volume at the boot time.

---

Thisu said:
See whether this helps http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
You'll have to instruct grub to decrypt volume at the boot time.
Click to expand...
Click to collapse
Thanks for the reply. Unless I am missing something, this isn't relevant since I don't have an encrypted boot. I have a normal run of the mill encrypted SSD using stock encryption options when you choose encrypt my whole disk during a Mint or Ubuntu fresh, whole disk installation.
My disk has a NON encrypted boot, then another encrypted partition that everything else lives in.
I just need to know how to kick off the encryption the same way the Mint install does so that the remix os boot can continue. With my poking at the grub cfg I think it has something to do with where I specify the "root" parameters. But until this point I haven't gotten it right... or I may be barking up the wrong tree.

---

getut said:
Thanks for the reply. Unless I am missing something, this isn't relevant since I don't have an encrypted boot. I have a normal run of the mill encrypted SSD using stock encryption options when you choose encrypt my whole disk during a Mint or Ubuntu fresh, whole disk installation.
My disk has a NON encrypted boot, then another encrypted partition that everything else lives in.
I just need to know how to kick off the encryption the same way the Mint install does so that the remix os boot can continue. With my poking at the grub cfg I think it has something to do with where I specify the "root" parameters. But until this point I haven't gotten it right... or I may be barking up the wrong tree.
Click to expand...
Click to collapse
So does that mean all your RemixOs stuff,including kernel,initrd,ramdisk reside within the encrypted partition?
I would suggest you to use something like EFISTUB booting,if you are using UEFI. You'll have to place kernel and initrd in ESP(EFI system partition).