Re: SCSI CD mount problems

On Mon, Jun 23, 2003 at 09:50:39 -0400, Guy Middleton wrote:
> On Sun, Jun 22, 2003 at 10:24:44PM -0600, Kenneth D. Merry wrote:
> > On Tue, Jun 17, 2003 at 22:01:02 -0400, Guy Middleton wrote:
> > > I have a Yamaha CRW4416S CD drive as /dev/cd0.  When I try to mount a disk,
> > > it says "cd9660: /dev/cd0: Invalid argument", and this in the log file:
> > > 
> > > (cd0:ahc0:0:3:0): READ(10). CDB: 28 0 0 0 0 10 0 0 1 0 
> > > (cd0:ahc0:0:3:0): CAM Status: SCSI Status Error
> > > (cd0:ahc0:0:3:0): SCSI Status: Check Condition
> > > (cd0:ahc0:0:3:0): ILLEGAL REQUEST asc:21,0
> > > (cd0:ahc0:0:3:0): Logical block address out of range
> > > (cd0:ahc0:0:3:0): Unretryable error
> > > (cd0:ahc0:0:3:0): cddone: got error 0x16 back
> > > 
> > > 
> > > I know the drive works, I can write good disks with it.  What's happening
> > > here?  This is on 5.1-RELEASE.
> > 
> > It's complaining that we're trying to access a logical block address that
> > isn't on the CD.
> > 
> > Since it is trying to read block 16 (0x10) from the CD, my guess is that it
> > is a blank CD.
> > 
> > Does it do that for every CD, or just that one?
> 
> This was actually a FreeBSD ISO distribution disk.  It does this for every
> disk; the only time I could successfully mount a disk was with one I had just
> written on that drive.  If I then opened and closed the drive, I could not
> mount the disk.

I assume you can put the disks in other drives and they work fine?

> > What does dmesg say about the CD capacity if you boot?  You can also get
> > that CD's capacity like this:
> > 
> > camcontrol cmd cd0 -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4"
> > 
> > The first number is the last LBA on the CD, the second one is the
> > blocksize.
> 
> 
> dmesg says this at boot:
> 
> cd0 at ahc0 bus 0 target 3 lun 0
> cd0: <YAMAHA CRW4416S 1.0f> Removable CD-ROM SCSI-2 device 
> cd0: 8.333MB/s transfers (8.333MHz, offset 31)
> cd0: cd present [0 x 2048 byte records]
> 
> 
> Camcontrol says this:
> 
> # camcontrol cmd cd0 -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4"
> -1 2048 

All I can say is that it appears that something is wrong with the drive.

We're just reporting what it reports back as far as capacity, and the fact
that it complains about a block being out of range just confirms that it
has bogus capacity information internally.

Ken
-- 
Kenneth Merry
ken_at_kdm.org