From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1TqVEs-0002S8-3n for mharc-grub-devel@gnu.org; Wed, 02 Jan 2013 15:48:38 -0500 Received: from eggs.gnu.org ([208.118.235.92]:38917) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TqVEo-0002RU-IE for grub-devel@gnu.org; Wed, 02 Jan 2013 15:48:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TqVEm-0002O5-0m for grub-devel@gnu.org; Wed, 02 Jan 2013 15:48:34 -0500 Received: from apteryx.fr ([178.33.44.46]:51918) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TqVEl-0002Np-Qv for grub-devel@gnu.org; Wed, 02 Jan 2013 15:48:31 -0500 Received: from [192.168.0.18] (gif [82.242.4.230]) by apteryx.fr (Postfix) with ESMTPSA id 640F32940F56 for ; Wed, 2 Jan 2013 21:48:30 +0100 (CET) Message-ID: <50E49D1D.4020100@guillemet.org> Date: Wed, 02 Jan 2013 21:48:29 +0100 From: =?UTF-8?B?SGVydsOpIEd1aWxsZW1ldA==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: grub-devel@gnu.org Subject: Re: Boot windows on external disk : "not a valid root device" References: <50E371C2.7000909@guillemet.org> <20130102001448.GC5547@riva.dynamic.greenend.org.uk> <50E38046.7010202@gmail.com> <50E387E5.8040309@guillemet.org> <50E38AC9.4050102@gmail.com> In-Reply-To: <50E38AC9.4050102@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 178.33.44.46 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 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: Wed, 02 Jan 2013 20:48:37 -0000 Le 02/01/2013 02:18, Vladimir '=CF=86-coder/phcoder' Serbinenko a =C3=A9c= rit : > On 02.01.2013 02:05, Herv=C3=A9 Guillemet wrote: >=20 >> Le 02/01/2013 01:33, Vladimir '=CF=86-coder/phcoder' Serbinenko a =C3=A9= crit : >>> On 02.01.2013 01:14, Colin Watson wrote: >>> >>>> On Wed, Jan 02, 2013 at 12:31:14AM +0100, Herv=C3=A9 Guillemet wrote= : >>>>> I have a new Asus N56VZ laptop and replaced the Windows hard drive = by a >>>>> SSD with Linux installed. EFI Grub2 successfully launchs Linux. >>>>> Now I'd like to boot Windows from the original hard drive mounted b= y USB. >>>>> >>>>> No matter what I try, either using grub.cfg or command line, Grub's >>>>> chainloader fails : >>>>> >>>>>> set root=3D(usb0,gpt1) >>>>>> chainloader ($root)/EFI/Microsoft/Boot/bootmgfw.efi >>>>> Error: not a valid root device. >>>>> >>>>> The content of the drive may be seen using "ls". >>>>> >>>>> What's the exact meaning of "not a valid root device" ? >>>> >>>> It indicates that either no UEFI device handle corresponding to that >>>> device was found, or that no UEFI protocol interface is available fo= r >>>> that device handle. In other words, "can't work out how to talk to = that >>>> device using UEFI". >>>> >>>> I think your device naming is dubious: as far as I can see, GRUB's >>>> efidisk module does not fully support calling a disk "usb0". The "l= s" >>>> command should show you the list of available disks and partitions, = or >>>> you can type "set root=3D(" and then use tab-completion. If the dis= k is >>>> truly only accessible as "usb0", then perhaps efidisk needs some wor= k to >>>> support that. >>>> >>> >>> Other than loopback, all devices follow the naming scheme insluding t= ype >>> prefix as detailed in manual. "usbN" means that the device is accesse= d >>> using GRUB own modules. To use chainloader on EFI you have to avoid >>> loading any USB modules and use hdX names. >> >> Ok, I tried, but then the external disk is not visible and ls only sho= ws >> me hd0. Can you see a possible solution ? >> >=20 > It probably means that EFI doesn't see you USB disk. Be sure that it's > connected on poweron and be sure to use recent GRUB. If still doesn't > help look if it's seen through EFI shell. > For using chainloader you need disk to be visible through EFI, otherwis= e > bootmgfw.ef won't be able to find rest of the files. > If the EFI doesn't see the USB disk in shell and/or in boot device > selection you should contact your manufacturer. >=20 EFI shell did not see it. However, after turning on some "Legacy USB support" option in the BIOS/UEFI setting, it does, as well as Grub using (hd0,gptX) ! Windows has not appreciated to be relocated at the end of a USB cable though, but it's another story. Thanks to you 3 for yours answers and help, --=20 Herv=C3=A9