On Thu, May 24, 2012 at 03:48:02AM -0500, Justin Haynes wrote:
> Thanks, that does work. I was then able to create a SCSI mirror with
> two drives using softraid, refer to that new volume by DUID in
> /etc/fstab, and see the machine automatically mount the volume on
> boot.
>
> Is there a way to pass a root device to bsd during the boot process?
> I don't find one in the man pages for boot (which is actually the i386
> man page). I suppose I can have openfirmware boot bsd -a and I can
> type the device whenever it reboots. I'm eager to hear any other
> ideas you may have.
I don't know how to pass wd1a from ofwboot to the kernel. I don't
think there is a way. You can only specify the single arguments
-acds. Other people might know better than me.
My other ideas where to run a custom kernel:
1. Copy of GENERIC that use:
config bsd root on wd1a swap on wd1b dump on wd1b
instead of the line:
config bsd swap generic
or
2. Copy of GENERIC that hard-code wd0 and wd1 to the original drives.
That have special line added (like the old FAQ about RAIDFRAME had):
#original dmesg
#wdc0 at macobio0 offset 0x1f000 irq 19: DMA
#wd0 at wdc0 channel 0 drive 0: <IBM-IC35L060AVER07-0>
#wd1 at wdc0 channel 0 drive 1: <ST380021A>
wdc0 at macobio0 offset 0x1f000 irq 19
wd0 at wdc0 channel 0 drive 0 flags 0x0000
wd1 at wdc0 channel 0 drive 1 flags 0x0000
Of course both are totally untested by me. You should use an alternate
name for the kernel (like /bsdtest) and change your OpenFirmware
command instead of destroying the working kernel.
The 2nd model is quite untested and might need changes to work.
(Like the line wdc0 at macobio0 might not be needed.) The first one
might need a new kernel compile every time you add a drive.
I booted my eMac (it had been more than 2 years and it runs 4.6)
and I can't test anything for you. The hard drive is going bad in
the section that has OpenBSD on it. I don't look forward to changing
it.
> At any rate, this will do for now, and I can continue to use this as a
> NAS and migrate files to the new volume. It probably later makes
> sense for me to use an i386 based NAS rather than using this machine.
> In addition to this limitation in booting, I've found there are quite
> a few SATA expansion cards that will not work and that not all the
> SATA ports are recognized on the cards that do work. Ideally I'd like
> to have 10-20 sata ports I can continue to add drives to.
>
> Thanks.
Can't help you there.
>
>
> On Wed, May 23, 2012 at 11:53 PM, Hugo Villeneuve
> <harpa...@jwales.eintr.net> wrote:
> > On Wed, May 23, 2012 at 10:24:17PM -0500, Justin Haynes wrote:
> >>
> >> Is the kernel assuming root should be on the same disk it was booted
> >> from, and inferring where root should be based on the bootpath?:
> >>
> >> scsibus2 at softraid0: 256 targets
> >> bootpath: /pci@f20000000/mac-io@17/ata-4@1F000/disk@0:/bsd
> >> root on wd0a swap on wd0b dump on wd0b
> >> panic: root filesystem has size 0
> >
> > It's been a while since I started my eMac, but I would have expected
> > that the full bootpath, as provided by OpenFirmware, to be mapped
> > to the right device.
> >
> > Strange.
> >
> > Anyhow, I would try from the OpenFirware to add the -a flag to the
> > boot command (replace the device name with the apropriate name):
> >
> > boot ultra0:,ofwboot /bsd -a
> >
> > If that works (no idea if it will), you should get an extra prompt
> > that ask for a root device, type "wd1a".
> >
> > You might be lucky and it might work. If it does, I got more ideas.
