On Fri, Apr 18, 2008 at 06:51:10PM -0400, Kenneth R Westerback wrote:
> 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.
Thanks, Ken!
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.
On Fri, Apr 18, 2008 at 06:10:48PM -0400, I made a typo:
># mount /dev/raidoa /mnt
D'oh! Typin' stuff by hand, rather than pasting directly.
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 / ty
On 2008-03-02, Almir Karic <[EMAIL PROTECTED]> wrote:
> # newfs /dev/rraid0a
correct, raw device i.e. /dev/rraid0a for newfs.
> # mount /dev/rraid0a /mnt/
> mount_ffs: /dev/rraid0a on /mnt: Block device required
you need the block device, i.e. /dev/raid0a, not the raw device.
i did all the things reccommanded by the summary section of raidctl(8)
(i even tried changing the 'a' partition to 'e', to be the same as in
the man page, no luck), i also tried following
http://unixsadm.blogspot.com/2007/10/openbsd-raidframe-mirror-software-raid.html
no change either.
my GENERIC.
6 matches
Mail list logo
