Am 01.11.2010 21:35, schrieb David C. Rankin: > On 11/01/2010 03:22 PM, David C. Rankin wrote: >> 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... > > Just FYI, > > After upgrading to device-mapper-2.02.75-1 and reinstalling > kernel26-2.6.35.8-1, the error has completely changed to: > > Error 5: Partition table invalid or corrupt > > Rebooting to LTS boots just fine :-( We will see what the dmraid guys say. These error are semi-random, they probably depend on where the kernel and initramfs files are physically located in the file system. It seems that about every second kernel works for you. Grub (and all other bootloaders for that matter) use BIOS calls to access files on the hard drive - they rely on the BIOS (and in your case, the jmicron dmraid BIOS) for file access. This access seems to fail for certain areas on your file system.
Attachment:
signature.asc
Description: OpenPGP digital signature
