Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Jun 1999 11:11:46 -0600 (MDT)
From:      Jonathon Doran <doranj@Colorado.EDU>
To:        seanw@xtdl.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Toshiba CDROM
Message-ID:  <199906101711.LAA08472@ucsu.Colorado.EDU>
In-Reply-To: <00b401beb170$eb6bb2f0$129e92d0@wizard.xtdl.com> from "Sean Glazier" at Jun 8, 99 01:36:55 am

next in thread | previous in thread | raw e-mail | index | archive | help

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: <TOSHIBA CD-ROM XM-6201TA 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: <IBM DDRS-39130D DC1B> 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: <IBM DDRS-39130D DC1B> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906101711.LAA08472>