From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 17 15:57:55 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15B251065670 for ; Wed, 17 Mar 2010 15:57:55 +0000 (UTC) (envelope-from mayo@oyam.ca) Received: from mail-yx0-f185.google.com (mail-yx0-f185.google.com [209.85.210.185]) by mx1.freebsd.org (Postfix) with ESMTP id D61398FC13 for ; Wed, 17 Mar 2010 15:57:54 +0000 (UTC) Received: by yxe15 with SMTP id 15so558500yxe.7 for ; Wed, 17 Mar 2010 08:57:54 -0700 (PDT) MIME-Version: 1.0 Sender: mayo@oyam.ca Received: by 10.101.184.29 with SMTP id l29mr1447374anp.55.1268841473917; Wed, 17 Mar 2010 08:57:53 -0700 (PDT) Date: Wed, 17 Mar 2010 08:57:53 -0700 X-Google-Sender-Auth: ccbec50df3dee2d3 Message-ID: <2dd037201003170857u621dec6fka8b8e2d7df145c4f@mail.gmail.com> From: Mayo Jordanov To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Problems with drive X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2010 15:57:55 -0000 Hello, I'm hitting some problems with a Toshiba drive (MK3263GSX). When I boot from a cd during installation, it installs on it fine, and there are no issues or errors on the consoles. When it comes to booting from the drive, it's geometry is detected as 0 sectors, 0 heads, 0 cylynders, 0 mb and of course failts to boot. (Geometry during install is correct). If I then boot off a cd or usb and mount the drive, it works just fine, and everything from the installation is on it, similarly copy to/from the drive is fine as well. I've had other OS installed on the drive (same system) no problem, and it seems it's only having issues on FreeBSD during boot. Any ideas, pointers? I don't know if it makes any difference, but the CD I install from is a USB cdrom. I've also tried playing with ata timeouts, but it didn't seem to help. There is no raid involved. I have two machines like this, and both behave identically. The errors from dmesg during boot are: ad0: 0MB at ata0-master SATA150 ad0: FAILURE - READ_DMA48 status=51 error=10 LBA=18446744073709551613 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551613 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551599 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551612 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551615 ad0: FAILURE - READ_DMA48 status=51 error=10 LBA=18446744073709551553 Thank you, Mayo Jordanov