From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mpjbb-0007mv-Lw for mharc-grub-devel@gnu.org; Mon, 21 Sep 2009 10:11:03 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MpjbW-0007mH-94 for grub-devel@gnu.org; Mon, 21 Sep 2009 10:10:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MpjbQ-0007lG-U6 for grub-devel@gnu.org; Mon, 21 Sep 2009 10:10:57 -0400 Received: from [199.232.76.173] (port=55969 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MpjbO-0007ku-Ho for grub-devel@gnu.org; Mon, 21 Sep 2009 10:10:50 -0400 Received: from mail-pz0-f182.google.com ([209.85.222.182]:43223) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MpjbO-0005qj-3r for grub-devel@gnu.org; Mon, 21 Sep 2009 10:10:50 -0400 Received: by pzk12 with SMTP id 12so2267358pzk.10 for ; Mon, 21 Sep 2009 07:10:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=zipiLa73w/8EpXO1NBtIK6a16J5vRFJtlKJ/Kw6iRZ0=; b=YA2VsJB1HNGrmetyIwdby/Dyo51SvjkV4C5Au2gsizfN4kN7pA93JQAUXZDgrp7Xcz KFV5tgznHSTL+uCebC51jRxJ6/zMoIjLQyqIqrb5KndVdDGbhrl4KEWU4O8i7oKPHAuF XuZWuCr2PdsS8lOZ0hTAbmz2O84qC+ro4cL60= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=fby8x6V6chmKl7hMdaU3w15tuyNRXXX6xWoFNp9NSHAdrySS/QXEYGHceYyzEItzn4 zE9GW4Y1HYtXxx4vd6SNxSBuGyP7MyVPlbooCgExa66ztUdOyYqPNKiI4M8nC0tpeqN2 AtwZUcFd8crC6SSdhBYUrDfGHLsBD+OnQMKlk= Received: by 10.114.237.18 with SMTP id k18mr8547633wah.63.1253542249001; Mon, 21 Sep 2009 07:10:49 -0700 (PDT) Received: from ?192.168.1.101? (or-71-53-64-80.dhcp.embarqhsd.net [71.53.64.80]) by mx.google.com with ESMTPS id 21sm47511pzk.3.2009.09.21.07.10.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 21 Sep 2009 07:10:47 -0700 (PDT) Message-ID: <4AB78965.8000606@gmail.com> Date: Mon, 21 Sep 2009 07:10:45 -0700 From: Dean Loros User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090920 Shredder/3.0pre MIME-Version: 1.0 To: grub-devel@gnu.org References: <4ab726d8.9d53f10a.2065.414bSMTPIN_ADDED@mx.google.com> In-Reply-To: <4ab726d8.9d53f10a.2065.414bSMTPIN_ADDED@mx.google.com> X-Enigmail-Version: 0.96a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: Current Grub2 & problem with /boot on different drive X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2009 14:10:58 -0000 Today's Topics: > 7. Re: Current Grub2 & problem with /boot on different drive > (Vladimir 'phcoder' Serbinenko) > > > ---------------------------------------------------------------------- > Message: 7 Date: Sun, 20 Sep 2009 22:00:13 +0200 From: Vladimir 'phcoder' Serbinenko Subject: Re: Current Grub2 & problem with /boot on different drive To: The development of GRUB 2 Message-ID: <4AB689CD.4060501@gmail.com> Content-Type: text/plain; charset=UTF-8 Dean Loros wrote: > > Greetings-- > > > > Ubuntu has been testing Grub2 for a number of months now & a > > "interesting" problem has surfaced. If your /boot is on a different > > drive than the MBR, you will have several minutes of drive use before > > you get to the Grub2 menu. My current timing is 3min 50sec to menu--this > > is with a i7-920 system with four internal drives--all SATA-II. My first > > bug report on Launchpad was dated 8-28-2009 & this had started a few > > days earlier. Before that date, Grub2 would take only 3~5 seconds to get > > to menu. Updates after this have not cured this issue. The current > > "work-around" in the bug report is to re-set MBR & /boot to the first > > drive. This problem only shows up in multi-boot/multi-drive systems. > > > > > We have theoretically discussed this problem with Robert but weren't sure if instances of it exist. The problem is that (UUID=..) syntax rescans all drives on every access. We devised a solution to split search.mod into search_uuid.mod, search_file.mod and so on but we agreed that it will be done after 1.97 due to amount of changes it requires. I'm ok to implement it, it's not much work but I can't make any promises about my current disponibility. As a workaround for time being you can use one or more of the following: 1) Increase cache size. Can this be done in 1.97? Change include/grub/disk.h and replace #define GRUB_DISK_CACHE_NUM 1021 with a bigger number 2) Modify scripts to hardcode boot device and not use UUID. If you change disk order it will result in boot failure but it may be a local workaround 3) add search -s -u as first command of your grub.cfg Hi Vladimir-- I have tried option #3 & have a question about syntax--should it be just search -s -u UUID number or should the number be in <> ? I tried without the <> & grub took the same ammount of time as before--I have edited grub.cfg with the <>, but have not rebooted with it in that form until I hear from you on this. Thanks!!!! Dean Loros -- Dean Loros autocrosser at ubuntuforums.org Performance by Design Ltd.