i have a stripe of 2 sata partitions, and i'd like to have that as root. my boot is a single sata partition. this worked before sata has been moved in the kernel, before 2.6.19. now in the boot process i see my sata disks found, the md device built, and the kernel panics with something about not finding a valid ext3 on a device designated by numbers. Reproducible: Always Steps to Reproduce: boot a 2.6.19 with a root=/dev/md0 Actual Results: kernel panic Expected Results: boot i've experienced this on amd64 and x86
Reopen with kernel .config and grub.conf attached.
Created attachment 106398 [details] .config and that same kernel boots from a single sata partition. and when booted it handle's md devices. md is not built as module.
Created attachment 106400 [details] lilo.conf
reopening as requested
# CONFIG_BLK_DEV_IDE_SATA is not set Don't use make oldconfig between different kernel versions...
CONFIG_BLK_DEV_IDE_SATA = Support for SATA (deprecated; conflicts with libata SATA driver) and anyways i don't have that option set but my kernel boots from a SATA disk. how can that be? where is libata? it's not in scsi. where is the new interface? it's not clear to me yet.
*** Bug 164870 has been marked as a duplicate of this bug. ***
*** Bug 165457 has been marked as a duplicate of this bug. ***