From owner-freebsd-i386@FreeBSD.ORG Thu Mar 27 21:10:02 2008 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2FED106566B for ; Thu, 27 Mar 2008 21:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B3BFC8FC1C for ; Thu, 27 Mar 2008 21:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2RLA20W026918 for ; Thu, 27 Mar 2008 21:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2RLA2oL026917; Thu, 27 Mar 2008 21:10:02 GMT (envelope-from gnats) Date: Thu, 27 Mar 2008 21:10:02 GMT Message-Id: <200803272110.m2RLA2oL026917@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Bruce Cran Cc: Subject: Re: i386/122008: Fdisk fails. Cannot install 7.0 Release on P5VD2-MX with Maxtor PATA X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Cran List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2008 21:10:02 -0000 The following reply was made to PR i386/122008; it has been noted by GNATS. From: Bruce Cran To: Christophe Cap Cc: bug-followup@freebsd.org Subject: Re: i386/122008: Fdisk fails. Cannot install 7.0 Release on P5VD2-MX with Maxtor PATA Date: Thu, 27 Mar 2008 21:02:10 +0000 From looking through the logs it looks like you're using a VIA 8237S ATA controller. Somebody else came across what sounds like the same problem with that chipset just a couple of weeks ago (http://lists.freebsd.org/pipermail/freebsd-questions/2008-March/171027.html) and says they solved it by replacing the cables - even after previously swapping them. This does sound very suspiciously like a cable problem - could you try swapping them again please? -- Bruce