From owner-freebsd-current@FreeBSD.ORG Fri Apr 16 04:34:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB6A416A4CE for ; Fri, 16 Apr 2004 04:34:18 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A193A43D48 for ; Fri, 16 Apr 2004 04:34:17 -0700 (PDT) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i3GBY900003744; Fri, 16 Apr 2004 13:34:14 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <407FC4B1.20806@DeepCore.dk> Date: Fri, 16 Apr 2004 13:34:09 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.5 (X11/20040329) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julien Gabel References: Your message of "Thu, 15 Apr 2004 20:46:01 +0200." <50267.192.168.0.105.1082054761.squirrel@webmail.thilelli.net> <5236.1082057026@critter.freebsd.dk> <49481.192.168.0.105.1082110471.squirrel@webmail.thilelli.net> In-Reply-To: <49481.192.168.0.105.1082110471.squirrel@webmail.thilelli.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org Subject: Re: Can't *write* to a hard disk, problem related to GEOM(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2004 11:34:19 -0000 Julien Gabel wrote: >>>/dev/ad10 was previously part of a hardware miror (ar(4) device with a >>>HighPoint HPT374 (channel 2+3) UDMA133 controller), but since it was >>>broken for an unknown reason, thid drive is no more usable, even alone. >>>For example, I am not be able to create a new slice on it. > > >>Could you try to compile a kernel without the ar(4) driver in it ? >>It may still be latching on to this disk... > > > Since the ar(4) driver is part of ata(4) generic ATA/ATAPI disk controller > driver, I don't think it is possible to do that without shooting myself > on the foot. Any ideas? In -current and 5.something you can disable ATA RAID support by commenting out the "device ataraid" line. -- -Søren