From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N90OP-00066J-Qy for mharc-grub-devel@gnu.org; Fri, 13 Nov 2009 12:57:05 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N90ON-00065X-MH for grub-devel@gnu.org; Fri, 13 Nov 2009 12:57:03 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N90OJ-000642-Vt for grub-devel@gnu.org; Fri, 13 Nov 2009 12:57:03 -0500 Received: from [199.232.76.173] (port=55847 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N90OJ-00063s-Ig for grub-devel@gnu.org; Fri, 13 Nov 2009 12:56:59 -0500 Received: from moutng.kundenserver.de ([212.227.17.9]:52197) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N90OI-0002e1-I9 for grub-devel@gnu.org; Fri, 13 Nov 2009 12:56:59 -0500 Received: from [85.180.5.154] (e180005154.adsl.alicedsl.de [85.180.5.154]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0LoKNd-1MSlgr41FJ-00gqAF; Fri, 13 Nov 2009 18:56:53 +0100 From: Felix Zielcke To: The development of GNU GRUB In-Reply-To: <4AFD9755.90805@gmx.de> References: <4AFD9755.90805@gmx.de> Content-Type: text/plain; charset="UTF-8" Date: Fri, 13 Nov 2009 18:56:51 +0100 Message-ID: <1258135011.2703.63.camel@fz.local> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/k8t+050p0M7YOjvZR0FwmD15ZvJ08N7flmQa rL5vvMFweMn/2XMU/MhKOHU/G2p+eCG1cc54sWN0evRjxTL34t yiRjOp4obpHtgXA9lymIpv+7RJuxVbl X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: Booting TrueCrypt Windows Hard Drive X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2009 17:57:04 -0000 Am Freitag, den 13.11.2009, 18:28 +0100 schrieb Johannes Bauer: > Dear list, > > I've read a whole lot about problems booting Windows through Grub - but > found no solution at all. By playing around with the options, I found a > solution which *almost* works: > > My main (Linux) drive is /dev/sda. / and /boot are on /sda1, i.e. (hd0,1). > My crap (Windows) drive is /dev/sdb. There is only one partition > /dev/sdb1. The whole drive has been encrypted with TrueCrypt. > > I've copied the MBR of /dev/sdb to /boot/truecrypt.mbr. Then I used the > following grub entry: > > menuentry "Sigh" { > insmod drivemap > set root=(hd1,1) > drivemap (hd0) (hd1) > drivemap (hd1) (hd0) > chainloader (hd0,1)/boot/truecrypt.mbr > boot > } > > This gets further than all other tutorials I've read before - it makes > Truecrypt actually ask for my password. After I've entered it > successfully, the Windows logo comes up and it appears to be booting. > However, after about 20 seocnds, it just resets hard. The next time I > boot Windows (7, BTW) that way, I get a message saying that it crashed > during bootup and if I want to use some kind of boot rescue restore > magic. When I say yes, a textmode progressbar comes up. When it reaches > 100%, the computer again resets hard. > > I have a feeling that I'm almost there but am missing something - can > somebody please help me? > > Kind regards, > Johannes On launchpad someone made a bugreport where removing the search and drivemap commands from the generated Win 7 menu entry by os-prober breaks booting it. So I removed drivemap command for Vista and 7. It wouldn't make much sense if the search line would break it. Did you try without drivemap? You could also try to directly chainload MBR with (hd1) Note that there's a difference if you use set root=(hd1,1) chainloader +1 or just chainloader (hd1,1)+1 So you could also play around a bit with them. The root device gets into %dl register and so the bootcode can make use of that one. If you specify the device inside chainloader command only GRUB itself knows that one. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer