Well... I just reinstalled Debian Sid with devfs support (rolled my own kernel) from scratch (before I was trying to place system files over on the raid, but apparently some how it was missing something, still a mystery) and it is booting with grub, but I have to append via grub "/boot/vmlinuz-2.4.8-5devfs root=/dev/ataraid/disc0/part2" And this is working now, with devfs. So I'm not sure why, if the kernel only recognizes d0p2, why does it seem to be working now? I am no longer getting my kernel panic. I don't know why I needed to reinstall from scratch, but that seemed to do the trick oddly enough. Any thoughts? I really wish I knew why my copying over files to the raid array did not do the trick the first time, as all required files with their permissions seemed to be in place. -----Original Message----- From: ataraid-list-admin@xxxxxxxxxx [mailto:ataraid-list-admin@xxxxxxxxxx]On Behalf Of Arjan van de Ven Sent: Tuesday, August 28, 2001 3:36 AM To: ataraid-list@xxxxxxxxxx Subject: Re: Hacked LILO file corrupted?! On Mon, Aug 27, 2001 at 11:42:48PM -0400, George D. Plymale wrote: > Who here has experience setting up grub to boot a root device from > /dev/ataraid? I have it setup to use this configuration: > root = (hd0,3) > kernel=/vmlinuz-2.4.8-5devfs root=/dev/ataraid/disc0/part2 this is wrong; root=/dev/ataraid/d0p2 is what is should be. (it's the official name and the only one the kernel will understand) _______________________________________________ Ataraid-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/ataraid-list
