From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1DWkF9-0007KX-14 for mharc-grub-devel@gnu.org; Fri, 13 May 2005 20:10:59 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DWkF6-0007Ju-L1 for grub-devel@gnu.org; Fri, 13 May 2005 20:10:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DWkF4-0007J6-Jg for grub-devel@gnu.org; Fri, 13 May 2005 20:10:54 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DWkF3-0007I9-QR for grub-devel@gnu.org; Fri, 13 May 2005 20:10:53 -0400 Received: from [216.57.210.178] (helo=backup.bxwa.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1DWkGi-0003p2-Ff for grub-devel@gnu.org; Fri, 13 May 2005 20:12:36 -0400 Received: from [192.168.0.79] (209-166-92-131.lightstreamdata.com [209.166.92.131] (may be forged)) by backup.bxwa.com (8.12.11/8.12.11) with ESMTP id j4E0EJKL009079 for ; Fri, 13 May 2005 17:14:19 -0700 Message-ID: <428540C3.8090408@bxwa.com> Date: Fri, 13 May 2005 17:05:23 -0700 From: Scott Becker User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: grub-devel@gnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Debugging 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: Sat, 14 May 2005 00:10:57 -0000 On the two servers I've installed RHEL 4 on, I've had trouble with grub. It's the combination of grub and the new I2O_block driver. I suspect the grub patch to support I2O is lacking. I was wondering if Grub 0.95 or 2.0 has a facility to trace the changes being made when grub-install is being ran. After an install or an update I had to run grub-install to get it to boot again. In theory, this shouldn't be neccessary. Since it was, I thought it would be useful to be able to compare the areas of the disk written to during grub-install with what was written there before so that I could trace down the problem. thanks scottb