I applied the patch to 2.1.132 (it needed some help, but it seems to be
ok).
I wanted to boot from my raid0-device (created with raidtools 0.42pre3).
This used to work fine till 2.1.123.
Till then I get a oops ( which I mentioned on this list a couple of
times). So now I applied the patch to see
And lo, Eyal Lebedinsky saith unto me:
>
> Jon Lewis wrote:
> >
> > On Sat, 26 Dec 1998, Eyal Lebedinsky wrote:
> >
> > > I think the FAST-5 was negotiated as the best the drive will do. Here is
> > > how another disk comes up:
In your kernel configuration, be sure that you've specified someth
Eyal Lebedinsky <[EMAIL PROTECTED]> wrote:
> I really think the disks are just stubborn.
Yes. Moreover they might handle disconnection unefficiently, which will
kill your RAID0 performance completely.
Jon Lewis wrote:
>
> On Sat, 26 Dec 1998, Eyal Lebedinsky wrote:
>
> > I think the FAST-5 was negotiated as the best the drive will do. Here is
> > how another disk comes up:
>
> Are the old disks SCSI-1 or SCSI-2? If you don't have important data on
> them, you might try forcing 10MB/s and se
Sorry if this is a repeat, been having problems with our isp.
What magic incantation is required at the LILO prompt to use the 'noautodetect'
option?
> Subject: RELEASE: RAID-0,1,4,5 patch 1998.12.14, 2.0.36/2.1.131-ac9
. . .
> - 'noautodetect'
>
> there is a new 'noautodetect' kernel boot op
