Two things are jumping out at me here (in addition to Declan's excellent suggestion to try mounting a known-good CD): 1) What's the deal with the wacky chained symlinks? Symlinks are a truly horrible idea when it comes to block devices, because most people have no clue what they're trying to do with them (the infamous /dev/cdrom thing on RedHat boxes comes immediately to mind). Try mounting the actual block device, rather than a symlink two levels up. Additionally, the dmesg output you presented indicates that Linux thinks the drive is /dev/sr0, yet /dev/sr0 is a symlink. Linux should be recognizing the actual block devce, not a symlink. 2) The fact that you're seeing bread errors even when nothing is in the drive really makes me think hardware failure (specifically the laser going bad). It sounds like the drive can't even tell what (if anything) is in it. Its not surprising that you were able to burn a CD OK. The drive isn't trying to read anything during a burn, so even if the laser never even comes on, it doesn't know the difference, and merily goes on its way.
Anyway, i'd say try Declan's suggestion first, if that fails, remove the multitude of spaghetti symlinks, and if that continues to fail, you might want to consider that you have a bad drive. --- Chris Kassopulo <[EMAIL PROTECTED]> wrote: > 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? ===== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
