... I have a Cendyne cd-rw drive and had issues with the firmware. It worked fine with 
some media but not with others. Are you burning onto a new flavor of cdrom... like 
Memorex etc. It might pay to seek firmware updates and flash your dive. That fixed me 
right up... or so it seems.   

On Mon, Jul 23, 2001 at 11:13:05AM -0700, Rob Hudson wrote:
> The short:  After I burn a cd, I can't read it.
> 
> The long...
> 
> I've got a relatively old (1-2 yrs?) CDRW.  It's a Creative 4224 (4x
> write, 2x rewrite, 24x read) cd burner.  I compiled my kernel to do
> SCSI-emulation.
> 
> Here's my dmesg, snipped up:
> 
> hdd: CREATIVE CD-RW RW4224E, ATAPI CDROM drive
> [snip]
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> scsi : 1 host.
>   Vendor: CREATIVE  Model: CD-RW RW4224E     Rev: 1.36
>   Type:   CD-ROM                             ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
> scsi : detected 1 SCSI generic 1 SCSI cdrom total.
> sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.11
> 
> I created an image via mkhybrid.  I mounted it as a loop device and it
> looked good (meaning I have the necessary modules to read Joliet and
> ISO9660 compiled in the kernel, and mkhybrid worked).
> 
> I burned the image via cdrecord:
>  cdrecord -v speed=2 dev=0,0,0 archive.iso
> 
> cdrecord did it's work, spouting no errors.  It fixed (fixated?) the
> CD.  When it was done, I tried to mount it and got errors:
> 
> mount: wrong fs type, bad option, bad superblock on /dev/scd0,
>        or too many mounted file systems
> 
> I can see the impression on the underside of the CD where the data is.
> If I put the CD in the cd-reader in windows, it appears empty.
> 
> Here is what kern.log says of my mount attempt:
> 
>   VFS: Disk change detected on device sr(11,0)
>   attempt to access beyond end of device
>   0b:00: rw=0, want=33, limit=2
>   dev 0b:00 blksize=1024 blocknr=32 sector=64 size=1024 count=1
>   isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=32
> 
> Any clue to what could be wrong?  
> 
> Thanks,
> Rob
> 

-- 
- Debian GNU/Linux ->
http://www.debian.org

Reply via email to