From owner-freebsd-questions@FreeBSD.ORG Mon May 10 12:36:58 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A9FD16A4CE for ; Mon, 10 May 2004 12:36:58 -0700 (PDT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F3443D1D for ; Mon, 10 May 2004 12:36:56 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (pa-plum1c-102.pit.adelphia.net [24.53.179.102]) by internet.potentialtech.com (Postfix) with ESMTP id 7808D69A71; Mon, 10 May 2004 15:36:52 -0400 (EDT) Message-ID: <409FD9D0.1000702@potentialtech.com> Date: Mon, 10 May 2004 15:36:48 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040506 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Chad Leigh -- Shire.Net LLC" References: <409FBA92.2030401@potentialtech.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: questions@freebsd.org Subject: Re: Anyone else having trouble with Samsung 160G drives? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 19:36:58 -0000 Chad Leigh -- Shire.Net LLC wrote: > > On May 10, 2004, at 11:23 AM, Bill Moran wrote: > >> This is the weirdest problem I'm seen in a while. >> >> Client bought a pair of 160G Samsung SP1604N ATA drives. I'm supposed >> to install >> them in an existing FreeBSD 4.9 system for additional storage space. >> >> As soon as the drives are installed, kernel won't boot. It freezes up >> right before >> the "ad0: ..." messages appear and won't respond to anything except >> the reset button. >> Tried primary slave, secondary slave ... threw in a Highpoint ATA card >> and tried >> every possible configuration ... no dice. This was on a relatively >> new AOpen mobo >> with a 2G processor (don't have the model # handy, but I'll get it if >> it's important) > > When you moved the drives, did you move the cables? Can the problem be > diagnosed by switching out the cables? Didn't keep _real_ close track of it, but we had 4 different cables that were moving around, and I believe we tried a few different combinations of them. Additionally, we've tried the drive in 3 different computers in our lab, and each one has successfully booted so far. (2 older machines and a fairly recent 2G ASUS board) I'm tending to lean toward BIOS weirdness. -- Bill Moran Potential Technologies http://www.potentialtech.com