From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1RnUn2-0000en-KY for mharc-grub-devel@gnu.org; Wed, 18 Jan 2012 07:38:56 -0500 Received: from eggs.gnu.org ([140.186.70.92]:58304) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RnUmt-0000a2-R5 for grub-devel@gnu.org; Wed, 18 Jan 2012 07:38:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RnUmo-0001XP-3x for grub-devel@gnu.org; Wed, 18 Jan 2012 07:38:47 -0500 Received: from mail-wi0-f169.google.com ([209.85.212.169]:36721) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RnUmn-0001UP-U4 for grub-devel@gnu.org; Wed, 18 Jan 2012 07:38:42 -0500 Received: by wicr5 with SMTP id r5so4900816wic.0 for ; Wed, 18 Jan 2012 04:38:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Vdu/FDeStEe7gp3bx1gEEiJACyuK1aMw9B0dUZX9NrE=; b=HsCZfSEASy2/4Wp9SSs03IO7iqoO9N39EMKmu+osbJ6YmRb1tlmdEHSLekZZ1dH6e9 9Gi6QA+LzFEFdlr8ozQJssLGDF146LHIOH7RFwtr/9IFLoXgyar1AWzAzOyaNhY7viEi eiEIfa6EFxvtUffK2S1lWGXvwZ3B/g41hZYjc= Received: by 10.180.97.166 with SMTP id eb6mr6358405wib.5.1326890320682; Wed, 18 Jan 2012 04:38:40 -0800 (PST) Received: from fedora.x201.phnet (118-75.203-62.cust.bluewin.ch. [62.203.75.118]) by mx.google.com with ESMTPS id em13sm22208166wid.7.2012.01.18.04.38.38 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 Jan 2012 04:38:39 -0800 (PST) Message-ID: <4F16BD4C.1050402@gmail.com> Date: Wed, 18 Jan 2012 13:38:36 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: The development of GNU GRUB Subject: Re: "not a valid root device" error in UEFI chainloader command References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.212.169 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, 18 Jan 2012 12:38:53 -0000 On 18.01.2012 03:54, Keshav P R wrote: > Hi, > I tried to manually chainload UEFI shell from grub2 terminal in > x86_64 firmware. I get > >> insmod part_gpt >> insmod fat >> chainloader (hd0,gpt1)/shellx64.efi > error: not a valid root device Setting "root" isn't just for convenience inside GRUB, with some loader (multiboot, chainloader, bsd) it's actually passed to the payload as its root. If you forget to set it, it obviously won't work > If I use > >> set pager=1 >> set debug=all >> chainloader (hd0,gpt1)/shellx64.efi > [long rows of text - but no visible error] >> boot > [shell launched] > > However a menuentry like > > menuentry "UEFI Shell" { > search --fs-uuid --no-floppy --set=root ${_uefi_sys_fs_uuid} > chainloader (${root})/shellx64.efi > } > > works. I can reproduce this error everytime I try to manually > chainload from grub2 terminal, but does not occur even once when > loaded via menuentry. Thanks in advance. > > Regards. > > Keshav > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel > -- Regards Vladimir 'φ-coder/phcoder' Serbinenko