On Fri, Apr 18, 2008 at 06:10:48PM -0400, Josh Grosse wrote: > I've been using root on raid for some years, and am using a -current system > from March 22. > > I've been unable to boot recently built kernels unless I use boot -a and > select device raid0a manually. My older kernel works fine. > > With new kernels, booting -s I get: > > # mount > root_device on / type ffs (local, readonly) > # mount -a > mount_ffs /dev/raid0a on /: Invalid argument > > The root directory is mountable, just ... not as the root directory. > > # mount /dev/raid0a / > mount_ffs /dev/raid0a on /: Invalid argument > # mount /dev/raidoa /mnt > # > > My kernel uses swapgeneric, since the config file contains only these three > lines: > > include "arch/i386/conf/GENERIC" > pseudo-device raid 4 > option RAID_AUTOCONFIG > > I know there were a few changes to rf_openbsdkintf.c and subr_disk.c at > the end of March, but I'm not a bright enough bulb to debug this myself. > > Any pointers? >
This is currently broken (deliberately) as changes are made to the logic concerning mounting the root disk. There are some more changes that need to be made before a fix to raidframe can be committed. .... Ken
