From owner-freebsd-scsi Mon Jan 15 11:23:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA01844 for freebsd-scsi-outgoing; Mon, 15 Jan 1996 11:23:31 -0800 (PST) Received: from argus.flash.net (root@[206.149.24.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA01837 for ; Mon, 15 Jan 1996 11:23:27 -0800 (PST) Received: (from lists@localhost) by argus.flash.net (8.6.12/8.6.12) id NAA03367 for freebsd-scsi@freebsd.org; Mon, 15 Jan 1996 13:22:31 -0600 From: mailing list account Message-Id: <199601151922.NAA03367@argus.flash.net> Subject: IBM MTA-3230 m-o drive To: freebsd-scsi@freebsd.org Date: Mon, 15 Jan 1996 13:22:30 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk okay, now that i'm back on the net.... I have managed to get my IBM MTA-3230 3.5" m-o drive working by playing with the dipswitches on the drive [type 0 as opposed to type 7], but have a problem now that only happens under freebsd [2.0,5, and 2.1.0]. when I reboot, my aha-1542cf or the drive doesn't seem to reset properly. The scsi bios will see a drive there, but will not be able to get any info from the drive [name, type, etc], freebsd will boot and say it is a type 0, fixed, unknown name, but come up with the proper geometry. mounting is possible in this state, but it may be indicative of a bigger problem. The only known fix for this is to power down both the system and the drive, bring up the drive, then the system, in that order. just powering down the system will not fix the problem. I do not seem to remember this happening with the AHA-2940W controller under 2.0.5. Any ideas? Jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@argus.flash.net - FlashNet Communications - Ft. Worth, Texas