At a guess, (GUESS) your system doesn't know what protocol the cdr is
written, is trying to automount it and going through a few modules before
giving up the ghost
The usual failure mode for a cdr/cdrw is failure to read. I am always amazed
how many red faces this advice produces, but clean the $�"! disk - make sure
you can see no pawprint on it. Do not discount dodgy media as an option.
Start with a known iso9660 disk, and try to dd from it
[root@genius /root]# dd if=/dev/hdc of=smallfile bs=100 count=1
1+0 records in
1+0 records out
That's what I get. Smallfile, btw is 'unlessable' crap.
--
Regards,
Declan Moriarty
Applied Researches - Ireland's Foremost Electronic Hardware Genius
A Slightly Serious(TM) Company
Experience is like a comb,
that Life gives you - AFTER all your hair has fallen out!
Recently, somebody somewhere said:
> Greetings,
>
> I bought an HP9100 cdrw a while back cause my cdrom died. Installed it,
> burned a cd in windows and linux - no problems. I've only used it since
> as a reader. I can read the cd I burnt when I installed. I burn a cd
> today, the right things happen (lights and gcombust feedback) but when
> I try to mount it:
>
> /home/ckasso# mount /dev/sr0
> mount: wrong fs type, bad option, bad superblock on /dev/scd0,
> or too many mounted file systems
>
> I can burn and read in windows and can read in linux. I've looked at
> fstab, modules.conf and grub's menu.lst. All seems ok. The only
> interesting thing is dmesg. I get this when the tray is empty, holding
> a good cd, a bad one or a cocoanut donut.
>
> dmesg output (duplicate lines edited out):
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: HP Model: CD-Writer+ 9100c Rev: H2,1
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
> sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.12
> VFS: Disk change detected on device ide1(22,0)
> isofs_read_super: bread failed, dev=16:00, iso_blknum=16, block=32
> VFS: Disk change detected on device sr(11,0)
> attempt to access beyond end of device
> 0b:00: rw=0, want=33, limit=2
> isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=32
> I/O error: dev 0b:00, sector 2
> I/O error: dev 0b:00, sector 0
> FAT bread failed
> read_super_block: unable to read superblock on dev 0b:00
> read_old_super_block: try to find super block in old location
> read_old_super_block: unable to read superblock on dev 0b:00
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISO 9660 Extensions: RRIP_1991A
>
> ~$ ls -l /dev
> lrwxrwxrwx 1 root root 8 Aug 27 04:20 cdrom -> /dev/sr0
> lrwxrwxrwx 1 root root 4 Aug 27 04:20 sr0 -> scd0
> brw-rw---- 1 root cdrom 11, 0 May 16 2001 scd0
> brw-rw-r-- 1 root disk 22, 0 May 16 2001 hdc
>
> Hardware or not writing properly? Any opinions or insights?
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
