Date: Sat, 30 Apr 2005 10:38:54 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: jondoor@udor.net Cc: freebsd-current@freebsd.org Subject: Re: ATA RAID -- Promise SATA150 vanished /dev/ar0 Message-ID: <4273441E.5000609@DeepCore.dk> In-Reply-To: <4272AFC6.2040907@udor.net> References: <4272AFC6.2040907@udor.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jon Door wrote: > I have a Promise Fastrak SATA RAID controller (PDC20371). Running a >=20 > stripe between two 120GB drives. Running under a generic RELENG_5 the=20 > controller, its drives, and the stripe where all detect without problem= =2E=20 > /dev/ar0 was generated without any special changes. Today I upgraded to= =20 > 6.0-CURRENT. Now the Promise controller and its drives are recognized=20 > but no /dev/ar0, and no evidence of the stripe. Booting back to a=20 > RELENG_5 system show the stripe data to still be intact. I've beem read= ing > through all the ATA mkIII posts and haven't seen this specific issue, a= m=20 > I missing a step here or is this possibly an issue between the new ATA = > code and my RAID card? Are there more up to date patches for the ATA=20 > code that > I might have missed? > Thank You. >=20 > I do have the following devices in my kernel config and have tried both= =20 > a custom config and a totally generic kernel: > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.428 2005/03/31 20:21:42 scott= l=20 > Exp $ > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives How did you define the array originally ? using the BIOS or atacontrol ? Does the Fasttrak BIOS see the array ? Please provide the dmesg from a verbose booted system as that will tell=20 what metadata it looks for and eventually finds. --=20 -S=F8ren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4273441E.5000609>