On 11/01/2010 01:47 PM, Tobias Powalowski wrote: > Hi guys, > please signoff 2.6.36 series for both arches > and give feedback if > real issues arise. > <snip> > > greetings > tpowa Tobias, As mentioned, I have the same boot failure with 2.6.36-3 (grub Error 24:) However, I have received the first bit of feedback from the dm-devel list. Heinz Mauelshagen had the following suggestions: 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 I will try the libata.ignore_hpa setting and let you know. If you can think of anything else, any other diagnostics, on the Arch side to try, please let me know and I'll be happy to try it. Thanks. -- 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
