Subject: Re: mirrored root w/ raidframe - howto install bootblock? - msg#00051

List: os.netbsd.ports.sparc

Date: Prev Next Index Thread: Prev Next Index

Martin Husemann <martin@xxxxxxxxxxx> writes:

> On Sun, May 14, 2006 at 10:57:46AM -0400, Greg Troxel wrote:
>> I think what's needed is to augment installboot to understand raid1,
>> or easier to be able to give it two fs arguments, one for the place to
>> put bootxx and the other to look for block #s of /boot.
>
> I think it does (at least it works this way on sparc64): if the partition
> to install the boot into is of type RAID, it will do the necessary magic
> (i.e. offset some stuff -64 blocks).

I can't find any sign of that in src/usr.sbin/installboot.

>From reading sys/arch/sparc/stand/binstall/binstall.sh, it seems
sparc64 boot uses bootblk and ofwboot as stage1 and stage2, and they
both have RAIDframe support. The first stage has FFS code and thus
doesn't require poking block numbers. So installboot doesn't have to
do anything special with the "boot filesystem", just write bootblk to
the beginning of the boot partition, and put ofwboot in the

sparc uses bootxx and boot. Two things needed for nicely dealing with
booting for RAID-1 seem to be missing (i.e., I can't find them):

installboot finding blocks from one filesystem (e.g., raid0a), and
translating those to offsets relative to the entire disk for bootxx,
so that bootxx can load /boot from RAID.

/boot skipping over the raid header so it can load the kernel from RAID

So, does anyone out there have a sparc system that boots from RAID-1?

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

Re: mirrored root w/ raidframe - howto install bootblock?

On Sun, May 14, 2006 at 10:57:46AM -0400, Greg Troxel wrote: > I think what's needed is to augment installboot to understand raid1, > or easier to be able to give it two fs arguments, one for the place to > put bootxx and the other to look for block #s of /boot. I think it does (at least it works this way on sparc64): if the partition to install the boot into is of type RAID, it will do the necessary magic (i.e. offset some stuff -64 blocks). Martin

Next Message by Date: click to view message preview

Small glitch with Ultra 10 and NetBSD/Sparc

Hi, I installed NetBSD/Sparc 3.0 on my Ultra 10 last night (yes, sparc, not sparc64) and there is an amusing glitch. The Sparc MAKEDEV, somewhat sensibly, doesn't create the /dev/*wd* devices. Not too many sparc32s with IDE devices I guess. Of course the Ultra 10 was grumpy without these devices. Maybe MAKEDEV could make them? Thanks! cheers bruce -- edoneel@xxxxxxxxxxxxxxxx SDF Public Access UNIX System - http://sdf.lonestar.org

Previous Message by Thread: click to view message preview

Next Message by Thread: click to view message preview

Re: mirrored root w/ raidframe - howto install bootblock?

At Mon, 15 May 2006 07:50:25 -0400, Greg Troxel wrote: > > sparc uses bootxx and boot. Two things needed for nicely dealing with > booting for RAID-1 seem to be missing (i.e., I can't find them): > > installboot finding blocks from one filesystem (e.g., raid0a), and > translating those to offsets relative to the entire disk for bootxx, > so that bootxx can load /boot from RAID. > > /boot skipping over the raid header so it can load the kernel from RAID > > So, does anyone out there have a sparc system that boots from RAID-1? > From my code reading, it looks like it can't work. No, it cannot work. NetBSD/sparc still doesn't support booting from RAIDframe RAID-1 partitions. The ideal fix might actually be be to use ofwboot on sparc, but that code assumes features unique to newer versions of OFW. I tried hacking on it long ago but didn't have the time then (or now) to learn enough about the various versions of OFW to make it portable. Someone who is sufficiently familiar with OFW might get it working in no time at all. (The fact that all the sparc64 boot stuff lives under sys/arch/sparc, including even the likes of ofwboot.c which cannot now work on sparc, confused the heck out of me for a major amount of time a couple of years ago when I was first trying to figure all this stuff out.) -- Greg A. Woods H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack <woods@xxxxxxxxxxx> Planix, Inc. <woods@xxxxxxxxxx> Secrets of the Weird <woods@xxxxxxxxx> pgpGmPKlEMUwz.pgp Description: PGP signature

Loading Comments...