All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: kernel update and dmraid causing grub errors
Date: Wed, 03 Nov 2010 17:19:07 -0500	[thread overview]
Message-ID: <4CD1DFDB.50907@suddenlinkmail.com> (raw)
In-Reply-To: <1288785893.25565.42.camel@o>

On 11/03/2010 07:04 AM, Heinz Mauelshagen wrote:
> Hi David,
> 
> because you're able to access your config fine with some arch LTS
> kernels, it doesn't make sense to analyze your metadata upfront and the
> following reasons may cause the failures:
> 
> - initramfs issue not activating ATARAID mappings properly via dmraid
> 
> - drivers missing to access the mappings
> 
> - 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
> 
> FYI: in general dmraid doesn't rely on a particular controller, just
> metadata signatures it discovers. You could attach the disks to some
> other SATA controller and still access your RAID sets.
> 
> Regards,
> Heinz

Heinz,

	Thank you for your reply. The LTS kernel is just there (long term support)
kernel (2.6.32.25-2). I can boot the SuSE kernels fine, and the immediately
prior Arch kernel just fine as well (2.6.35.7-1).

	I will try the libata.ignore_hpa setting and let you know and I'll pass this
info to the Arch devs to see if they can help as well.

	This has really been a strange issue. It seems like every other kernel (1 out
of every 2 new releases) just won't boot and stops at the very beginning with
either grub Error 24: or Error 5: (Nothing has changed otherwise and simply
booting another kernel works fine). I'll keep plugging away at trying to find an
answer.

	If you can think of any other tests or helpful diagnostics, please let me know.
Since this occurs at the very beginning of boot, there is no logging which makes
this tough to figure out. (not to mention dmraid is just voodoo to me. ;-)

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com

  reply	other threads:[~2010-11-03 22:19 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 [this message]
2010-11-03 22:57   ` David C. Rankin
2010-11-04 12:32     ` Heinz Mauelshagen
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=4CD1DFDB.50907@suddenlinkmail.com \
    --to=drankinatty@suddenlinkmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.