Date: Fri, 16 Apr 2004 13:54:43 +0200 (CEST) From: "Julien Gabel" <jpeg@thilelli.net> To: freebsd-current@freebsd.org Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> Subject: Re: Can't *write* to a hard disk, problem related to GEOM(4)? Message-ID: <50219.192.168.0.105.1082116483.squirrel@webmail.thilelli.net> In-Reply-To: <407FC4B1.20806@DeepCore.dk> References: Your message of "Thu, 15 Apr 2004 20:46:01 %2B0200." <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> <407FC4B1.20806@DeepCore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>/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. Ok. So I will disable the ataraid support in the kernel, reboot without no mirror (and no support for it) and... what am I suppose to try in this particular situation? I am not sur what you want me to test in this case. Will just re-enable the ataraid support and reboot be sufficient to release the latch? Thanks, -- -jpeg.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50219.192.168.0.105.1082116483.squirrel>