From owner-freebsd-questions Thu Jun 10 12:33:10 1999 Delivered-To: freebsd-questions@freebsd.org Received: from user.xtdl.com (user.xtdl.com [206.25.228.20]) by hub.freebsd.org (Postfix) with ESMTP id 13F7814D71 for ; Thu, 10 Jun 1999 12:33:00 -0700 (PDT) (envelope-from seanw@xtdl.com) Received: from wizard ([208.146.158.18]) by user.xtdl.com (8.8.8/8.6.9) with SMTP id PAA00529; Thu, 10 Jun 1999 15:52:37 -0400 (EDT) Reply-To: From: "Sean Glazier" To: "Jonathon Doran" Cc: Subject: RE: Toshiba CDROM Date: Tue, 8 Jun 1999 15:34:16 -0400 Message-ID: <00e801beb1e5$e5028f90$129e92d0@wizard.xtdl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: <199906101711.LAA08472@ucsu.Colorado.EDU> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sure will, I am going to pull apart the box shortly. I'll let ya know. I didn't notice that in the messages. I was always looking at the bottom of the file. I let you know how it goes. I see a failure trying to read that device at the bottom of the messages file. Sean > -----Original Message----- > From: Jonathon Doran [mailto:doranj@Colorado.EDU] > Sent: Thursday, June 10, 1999 1:12 PM > To: seanw@xtdl.com > Cc: freebsd-questions@freebsd.org > Subject: Re: Toshiba CDROM > > > Before worrying about device special files etc, we should address a > more fundamental problem. Sean's cdrom isn't being probed by the scsi > driver (thus no mounts). > > Sean has two scsi controllers (I assume on board), ach0 and ahc1. > > In May, the cdrom showed up: > > May 11 03:10:56 user2 /kernel: cd0 at ahc1 bus 0 target 4 lun 0 > May 11 03:10:56 user2 /kernel: cd0: 1037> Removable CD > -ROM SCSI-2 device > May 11 03:10:56 user2 /kernel: cd0: 5.813MB/s transfers > (5.813MHz, offset 15) > May 11 03:10:56 user2 /kernel: cd0: Attempt to query device size > failed: NOT REA > DY, Medium not present > > But, in June it is gone: > > Jun 10 00:50:15 user2 /kernel: da1 at ahc1 bus 0 target 1 lun 0 > Jun 10 00:50:15 user2 /kernel: da1: Fixed > Direct Access S > CSI-2 device > Jun 10 00:50:15 user2 /kernel: da1: 11.626MB/s transfers > (5.813MHz, offset 8, 16 > bit), Tagged Queueing Enabled > Jun 10 00:50:15 user2 /kernel: da1: 8715MB (17850000 512 byte > sectors: 255H 63S/ > T 1111C) > Jun 10 00:50:15 user2 /kernel: da0 at ahc1 bus 0 target 0 lun 0 > Jun 10 00:50:15 user2 /kernel: da0: Fixed > Direct Access S > CSI-2 device > Jun 10 00:50:15 user2 /kernel: da0: 11.626MB/s transfers > (5.813MHz, offset 8, 16 > bit), Tagged Queueing Enabled > Jun 10 00:50:15 user2 /kernel: da0: 8715MB (17850000 > > Sean says that the scsi BIOS sees the drive, and doesn't think there is a > cabling problem. I'm scratching my head a bit here. Certainly the first > priority is fixing whatever happened between May 11 and June 10 -- get the > drive to be probed. > > I'm thinking improper termination at this point. This isn't always a deal > breaker (in fact, I accidently ran my cdrom with bad termination for a few > months without realizing it). Sean: could you please let us > know the order > the devices are on the chain. Also, please doublecheck the termination of > all devices. I'm sure you've been over this a couple of times by now, but > the problem is most certainly HW (IMHO of course). > > Jon Doran > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message