From owner-freebsd-questions@FreeBSD.ORG Mon May 10 10:46:11 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 7C6DB16A4CF for ; Mon, 10 May 2004 10:46:11 -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 C939B43D4C for ; Mon, 10 May 2004 10:46:10 -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 478A769A7E; Mon, 10 May 2004 13:46:08 -0400 (EDT) Message-ID: <409FBFDC.5020504@potentialtech.com> Date: Mon, 10 May 2004 13:46:04 -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: Kent Stewart References: <409FBA92.2030401@potentialtech.com> <200405101029.25080.kstewart@owt.com> In-Reply-To: <200405101029.25080.kstewart@owt.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-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 17:46:11 -0000 Kent Stewart wrote: > On Monday 10 May 2004 10: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) >> >>Moved the drives into an older 466mhz system ... same effect ... boot >>locks up at the probe message just before it would normally detect >>ad0. In this new system, we even tried removing the existing drives >>altogether and starting from scratch on these drives ... the boot >>from the CD hangs just like everything else. >> >>So ... I brought one back to the office to put in a test machine so I >>could gather lots of good data, file a PR and get the problem fixed. >>Threw it into an old lab machine (266 mhz SOYO board) and the sucker >>WORKS PERFECT! (so much for gathering data for a bug report) >> >>So ... I'm at a complete loss as to what I should do ... and a bigger >>loss on what I should recommend to the client. > > I don't think it is the drive unless size is considered. There are bios > problems when the size goes above 120GB or so. You may be bumping into > this problem.If that is the case, a bios upgrade may let you use the > HD. That's pretty odd, as the only mobo that the drive works with is has a bios that's completely unable to understand the drive (the bios screen says it's 8G). Both of the other machines we tried in detected the drive size correctly in the bios. Are you saying that an older bios that incorrectly detects the drive is more likely to work than a newer one that _does_ detect it correctly? Scratch that ... _I'm_ the one that's saying it, since that's what I'm seeing. -- Bill Moran Potential Technologies http://www.potentialtech.com