From: Heinz Mauelshagen <heinzm@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: kernel update and dmraid causing grub errors
Date: Thu, 04 Nov 2010 13:32:32 +0100 [thread overview]
Message-ID: <1288873952.26244.39.camel@o> (raw)
In-Reply-To: <4CD1E8BC.4060806@suddenlinkmail.com>
On Wed, 2010-11-03 at 17:57 -0500, David C. Rankin wrote:
> On 11/03/2010 07:04 AM, Heinz Mauelshagen wrote:
> > - host protected area changes going together with the kernel changes
> > (eg. the "Error 24: Attempt to access block outside partition");
> > try the libata.ignore_hpa kernel paramaters described
> > in the kernel source Documentation/kernel-parameters.txt
> > to test for this one
>
> Heinz,
>
> I have testing with both libata.ignore_hpa=0 (default) and libata.ignore_hpa=1
> (ignore limits, using full disk), but there is no change. I still get grub Error
> 24: (this is also with a newer 2.6.36-3 kernel). So I'm stumped again. If you
> have any other ideas, please let me know. I'm happy to test on this end.
I overlooked you said it's a grub error, which occurs before any kernel
argument is being processed. Hmm, this could be a grub flaw then
identifying the disk size wrong or getting an offset wrong to load data
from. Did grub change with the kernel installed?
Heinz
>
> I have gone ahead and made the metadata available in case it will help. I have
> also included the fdisk info as well:
>
> http://www.3111skyline.com/dl/bugs/dmraid/dmraid.nvidia/
>
> http://www.3111skyline.com/dl/bugs/dmraid/fdisk-l-info-20100817.txt
>
> Thank you for your help.
>
next prev parent reply other threads:[~2010-11-04 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 22:27 kernel update and dmraid causing grub errors David C. Rankin
2010-11-03 12:04 ` Heinz Mauelshagen
2010-11-03 22:19 ` David C. Rankin
2010-11-03 22:57 ` David C. Rankin
2010-11-04 12:32 ` Heinz Mauelshagen [this message]
2010-11-04 16:17 ` David C. Rankin
2010-11-09 17:55 ` David C. Rankin
2010-11-10 5:49 ` David C. Rankin
2010-11-17 21:59 ` Heinz Mauelshagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1288873952.26244.39.camel@o \
--to=heinzm@redhat.com \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox