In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> So I still stick with my statement that the -current bootblocks/loader
>> doesn't have the computrons needed to use the ad device (or any non
>> wd/da/fd device for that matter) for anything usefull :)
>
>The loader is fine; the problem is just
> So I still stick with my statement that the -current bootblocks/loader
> doesn't have the computrons needed to use the ad device (or any non
> wd/da/fd device for that matter) for anything usefull :)
The loader is fine; the problem is just that Poul never finished fixing
the mountroot code. A
It seems Mike Smith wrote:
> > Our boot blocks/loader dont have the needed computrons to use the
> > "ad" device name. However I have some patches to boot2 that allows
> > to boot off an ad root device, provided you dont use the loader, and
> > put the rigth boot string in boot.config.
>
> This s
> It seems Geoff Rehmet wrote:
> > Hmm,
> >
> > My root device still lands up on "wd0" - even though my fstab has
> > the root filesystem on ad0s1a. I haven't looked at getting it to
> > use the ad dev entries for the root file system. (I'm assuming that
> > is still WIP.)
>
> Our boot blocks/
From: Kevin Street [mailto:[EMAIL PROTECTED]]
> Sent: 12 August 1999 03:10
> To: Soren Schmidt
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: ATA - Trouble mounting secondary master
>
>
> Kevin Street <[EMAIL PROTECTED]> writes:
> > S
Kevin Street <[EMAIL PROTECTED]> writes:
> Soren Schmidt <[EMAIL PROTECTED]> writes:
> > Hmm, damn, after the problem went away for Geoff I thought it to be
> > solved since I've never heard of it anywhere else, and I cant reproduce
> > it here no matter what I try.
> > Does it help eany if you o
Soren Schmidt <[EMAIL PROTECTED]> writes:
> It seems Geoff Rehmet wrote:
> > Brian McGroarty writes :
> > > In using the ATA driver, I'm unable to automatically mount a
> > > partition on a master drive on the secondary controller. fsck
> > > complains that device rwd2s1e isn't configured and exi
FWIW, I am running a July 30th kernel. let me see if the problem comes
back with a new CVSup.
> -Original Message-
> From: Brian McGroarty [mailto:[EMAIL PROTECTED]]
> Sent: 11 August 1999 01:41
> To: Soren Schmidt; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject:
I've just tried and coming in via wd and ad produce the same
problem.
Note my previous comment - the access light is a steady on for
this particular drive. It's left that way when devices are
probed during startup.
My configuration FWIW -
(Note that the devclass_alloc_unit messages are new as o
It seems Geoff Rehmet wrote:
> Hmm,
>
> My root device still lands up on "wd0" - even though my fstab has
> the root filesystem on ad0s1a. I haven't looked at getting it to
> use the ad dev entries for the root file system. (I'm assuming that
> is still WIP.)
Our boot blocks/loader dont have t
ren Schmidt [mailto:[EMAIL PROTECTED]]
> Sent: 11 August 1999 08:53
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: ATA - Trouble mounting secondary master
>
>
> It seems Geoff Rehmet wrote:
> > Brian McGroarty
It seems Geoff Rehmet wrote:
> Brian McGroarty writes :
> > In using the ATA driver, I'm unable to automatically mount a
> > partition on a master drive on the secondary controller. fsck
> > complains that device rwd2s1e isn't configured and exists.
> > Immediately mounting by hand works perfectly
Brian McGroarty writes :
> In using the ATA driver, I'm unable to automatically mount a
> partition on a master drive on the secondary controller. fsck
> complains that device rwd2s1e isn't configured and exists.
> Immediately mounting by hand works perfectly.
>
> Compiling the kernel with wd ins
Also of interest -
I have a seperate access light for each of my drives, as they're
in removable bays.
I notice the access light for the secondary master remaining on
after the kernel driver has done its scanning. The light goes
off on this, the failed first access. I believe the light for
the p
Brian McGroarty <[EMAIL PROTECTED]> writes:
> In using the ATA driver, I'm unable to automatically mount a
> partition on a master drive on the secondary controller. fsck
> complains that device rwd2s1e isn't configured and exists.
> Immediately mounting by hand works perfectly.
Nice timing, I w
15 matches
Mail list logo
