From owner-freebsd-hardware@FreeBSD.ORG Sat Apr 15 15:42:28 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 912F216A402 for ; Sat, 15 Apr 2006 15:42:28 +0000 (UTC) (envelope-from cfoote@bmyster.com) Received: from loqtis.bmyster.com (ns1.bmyster.com [65.175.135.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2639443D45 for ; Sat, 15 Apr 2006 15:42:27 +0000 (GMT) (envelope-from cfoote@bmyster.com) Received: from ns1.bmyster.com (localhost.bmyster.com [127.0.0.1]) by loqtis.bmyster.com (8.13.3/8.13.3) with ESMTP id k3FFgQjc021137 for ; Sat, 15 Apr 2006 11:42:26 -0400 (EDT) From: "Carl Foote" To: freebsd-hardware@freebsd.org Date: Sat, 15 Apr 2006 11:42:21 -0400 Message-Id: <20060415153418.M52372@bmyster.com> X-Mailer: Open WebMail 2.51 20050228 X-OriginatingIP: 65.175.207.99 (knight) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: IDE tape drive stt3401a 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: Sat, 15 Apr 2006 15:42:28 -0000 I just converted a windows server over to Freebsd 5.4 stable. The stt3401a tape drive that was in server was working fine. The tape drive posts in the BIOS but when freebsd boots up, it will not detect the drive. Documentation for the drive does state it cannot be on the same controller as a hard drive, which I verified. So, on its own controller (secondary) as master, the OS still will not detect the drive when system boots. I have tried all possibilities of appropiate jumper settings to no avail. The best I can get out of the drive is when the OS loads I get a "ata1-slave: FAILURE - ATAPI_IDENTIFY timed out". I get the message three times the os loads and no drive. I know freebsd is doing /dev differently than in the past. It loads /dev dynamically on boot, so it is not loaded with all the device files, just the ones it detects. Is there a way to force the dev file to load. ANY suggestions would be appreciated. Carl Foote, CCNA Bmyster, LLC Computer Networking and Webhosting Vice President, Network Engineer, Webmaster http://www.bmyster.com/ cfoote@bmyster.com 207.490.5992