[Bug 484102] Re: Grub2 doesn't chainload truecrypt loader correctly
Attila Lendvai
attila.lendvai at gmail.com
Mon Jan 14 09:33:24 UTC 2013
FYI, grub2tc has been fixed to work with newer ruby versions, but when i
try to boot the generated multiboot kernel i get this error:
"No physical memory is available at the location required for the
windows boot manager. The system cannot continue."
the iso booting method in my previous comment works fine though. you can
use 'sudo blkid' to find the UUID of your root partition.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/484102
Title:
Grub2 doesn't chainload truecrypt loader correctly
Status in “grub2” package in Ubuntu:
Invalid
Bug description:
Binary package hint: grub2
I am working on a dual-boot system with one hard disk.
sda1 = /boot
sda2 = Windows Vista Ultima encrypted with TrueCrypt System Encryption
sda3 = Ubuntu 9.10 encrypted lvm
The grub2 entry for windows is created by the file 50_windows in the
"/etc/grub.d" directory:
#! /bin/sh -e
echo "Adding Windows Vista entry" >&2
cat << EOF
menuentry "Windows Vista" {
set root=(hd0,2)
parttool (hd0,2) boot+
chainloader (hd0,1)/truecrypt.mbr
}
EOF
Choosing this entry in the grub2 menu the Truecrypt loader only shows the following message:
"TrueCrypt Boot Loader
Load damaged! Use Rescue Disk: Repair > Options > Restore Truecrypt Boot Loader"
But this would install the Bootloader into the MBR, where grub2 shall be. The TrueCrypt Loader is in /boot/truecrypt.mbr
Booting Ubuntu works without problems.
With grub-legacy the chainloading worked.
The menu.lst:
title Windows Vista
rootnoverify (hd0,1)
savedefault
makeactive
chainloader (hd0,0)/truecrypt.mbr
My Grub2 version: 1.97~beta4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/484102/+subscriptions
More information about the foundations-bugs
mailing list