From owner-freebsd-current Mon Mar 13 9:14:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5DDB437C060 for ; Mon, 13 Mar 2000 09:14:46 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA59310; Mon, 13 Mar 2000 18:14:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200003131714.SAA59310@freebsd.dk> Subject: Re: Weird problems with my IDE HD In-Reply-To: from Donn Miller at "Mar 13, 2000 11:40:15 am" To: dmmiller@cvzoom.net (Donn Miller) Date: Mon, 13 Mar 2000 18:14:40 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Donn Miller wrote: > I've got two HD's in my machine: one's an older one (WDMA2) and the other > one, my main one, is newer (UDMA33). With recent kernel builds, I've > noticed some strange problems with the older HD. When I try to to > something like fsck -y on the drive, fsck just hangs. Also, if I have > that drive mounted, and I do umount on that drive, umount hangs, and > sometimes umount hangs my whole system. > > I'm trying to determine if it's because my drive is bad, or was there > something that was changed in the ATA driver that may be causing > this? Output of dmesg: There was a window where the ata driver had a problem due to me committing a premature fix to enable the disksort stuff. This is now backed out in 4.0 and the prober fix is in -current. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message