From owner-freebsd-scsi Sat Mar 13 23:50:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 7152F14D7E for ; Sat, 13 Mar 1999 23:50:38 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA25235 for freebsd-scsi@FreeBSD.org; Sun, 14 Mar 1999 08:50:19 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id IAA58166; Sun, 14 Mar 1999 08:48:51 +0100 (MET) (envelope-from j) Message-ID: <19990314084849.47902@uriah.heep.sax.de> Date: Sun, 14 Mar 1999 08:48:49 +0100 From: J Wunsch To: FreeBSD SCSI list Subject: SONY SMO-C501-09 not recognized under CAM Reply-To: Joerg Wunsch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, as i wrote in the other message, i'm now (finally) also with CAM at home. Basically, everything's working fine so far. (Unlike what Ken wrote, i can't confirm the problems with the IBM DCAS with tagged queuing, but i'll try to collect bonnie and iozone data first.) Well, the subject says what's not working yet: my old SONY MO drive. Upon booting, i get (after a rather long timeout, i. e. while the system is already proceeding with the boot): (da2:ncr1:0:3:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ncr1:0:3:0): NOT READY asc:4,0 (da2:ncr1:0:3:0): Logical unit not ready, cause not reportable (da2:ncr1:0:3:0): fatal error, failed to attach to device (da2:ncr1:0:3:0): lost device (da2:ncr1:0:3:0): removing device entry Hmm, yes, the drive ain't spinning by that time (i keep it down when not used), but i was under the impression the probe routine would spin it up anyway? At least the old od(4) driver did so (and in my hacked version, automatically brought the drive down when not openened by anyone.) I can then spin it up manually using the associated pass device, but a `camcontrol rescan' doesn't get it back as a `da2' as i would have expected. Here's all i could get so far: uriah # camcontrol inquiry -n pass -u 4 Removable Direct Access SCSI-CCS device Serial Number 0.0MB/s transfers uriah # camcontrol start -n pass -u 4 Unit started successfully uriah # camcontrol tur -n pass -u 4 Unit is ready uriah # camcontrol rescan 1 Re-scan of bus 1 was successful uriah # camcontrol rescan 0 Re-scan of bus 0 was successful uriah # camcontrol devlist < > at scbus-1 target -1 lun -1 (xpt0) at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 2 lun 0 (pass1,cd0) at scbus0 target 4 lun 0 (pass2,sa0) < > at scbus0 target -1 lun -1 () at scbus1 target 1 lun 0 (pass3,da1) at scbus1 target 3 lun 0 (pass4) < > at scbus1 target -1 lun -1 () Does anybody have a hint, maybe an idea for the quirk entry that's required in order to get the drive working? (Yes, it's SCSI-CCS only, and it actually ain't even a SCSI drive, but rather an ESDI-to-SCSI bridge. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message