Am Montag 01 November 2010 schrieb David C. Rankin:
> On 10/31/2010 04:32 PM, Thomas Bächler wrote:
> > Am 31.10.2010 22:00, schrieb David C. Rankin:
> >> > Updated an x86_64 box to 2.6.35.8-1 and the boot hangs at the very
> >> > start with
> >> >
> >> > the following error:
> >> >
> >> > Booting 'Arch Linux on Archangel'
> >> >
> >> > root (hd1,5)
> >> >
> >> > Filesystem type is ext2fs, Partition type 0x83
> >> >
> >> > Kernel /vmlinuz26 root=/dev/mapper/nvidia_baacca_jap5 ro vga=794
> >> >
> >> > Error 24: Attempt to access block outside partition
> >> >
> >> > Press any key to continue...
> >
> > That's a grub error and has no relation to any kernel update.
>
> I know that, but it has something to do with the kernel and/or dmraid
> because LTS boot just fine with the same menu.lst and kernel
> kernel26-2.6.35.7-1 boot just fine with the same menu.lst, but upgrading
> to 2.6.35.8-1 kills the box. While:
>
> pacman -U kernel26-2.6.35.7-1-x86_64.pkg.tar.xz
> kernel26-headers-2.6.35.7-1-x86_64.pkg.tar.xz
>
> fixes it.
>
> I know it looks like grub, but all kernels except 2.6.35.8-1 work??
Well i'm not sure what error 24 is, but dmraid can be really complicated.
I would recommend you write the dmraid authors from fedora, i'm sure it's a
grub vs. dmraid issue which we cannot solve.

greetings
tpowa

--
Tobias Powalowski
Archlinux Developer & Package Maintainer (tpowa)
http://www.archlinux.org
tpowa@archlinux.org

On 11/01/2010 01:39 PM, Tobias Powalowski wrote:
> Well i'm not sure what error 24 is, but dmraid can be really complicated.
> I would recommend you write the dmraid authors from fedora, i'm sure it's a
> grub vs. dmraid issue which we cannot solve.
>
> greetings
> tpowa

Will do and I'll report back. If you look back over the bug report, you will see
that this seems to pop up every other kernel or so. In the past, it has always
been solved by "try the newer kernel in testing." which has worked most of the time.

We'll see what the dmraid devs have to say. This seems to only effect my jmicron
controller based box. The other boxes seem OK. So maybe it's a firware dmraid
error that gets tripped depending the way the kernel loads the dmraid module??
Who knows...

--
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