Linux problem: can't read superblock
 

I have two drives, a dvd+rw and a cd-rom, and neither will mount a cd. If I try to just open the icon on the desktop for either device when a cd is in either one, I get the following:

/dev/hdd: Input/output error
mount: /dev/hdd: can't read superblock

(and hdc for the other)

This also happens when I try to mount either in the command line. I've tried rebooting a few times and it's still doing this. I'm running Mandrake 10.1.

Thanks in advance.

**edit** here's what I got from a dmesg|tail:

hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev hdd, sector 68
Buffer I/O error on device hdd, logical block 17
cdrom: hdd: mmc-3 profile capable, current profile: 8h
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev hdd, sector 0
FAT: unable to read boot sector

And to make it even stranger, it'll play in KsCD and find the names of the songs, the band name, and the CD.

Red Book (audio) CD's don't have a filesystem. One can be simulated with something like CDfs which will then mount, but otherwise they're just a bunch of playable tracks.

If it mounts like a data disc then it's some type of hybrid disc, usually for art, media players, copy protection, or other things.

Okay, I wasn't sure about that. The problem that I'm concerned with is that grip keeps saying, "no disc" whenever I try to rip a CD.

Thanks for the help cyrnel.

Same thing with other audio CDs?

Just a guess but does it work for root? Playing just involves sending play commands while ripping needs raw access to the tracks.

Yes, and with both drives. I just tried running grip as root about a minute before you posted this and it still couldn't find the disc.

What's cdparanoia say? Can it find tracks further into the disc? Maybe:

cdparanoia -v 2

I'm way stale. I was hoping one of the local ripping monsters would wander through.

Here's what I'm seeing when I try that:

cdparanoia III release 9.8 (March 23, 2001)
(C) 2001 Monty <monty@xiph.org> and Xiphophorus

Report bugs to paranoia@xiph.org
http://www.xiph.org/paranoia/

Checking /dev/cdrom for cdrom...
Testing /dev/cdrom for cooked ioctl() interface
CDROM sensed: ATAPI compatible Hewlett-Packard DVD Writer 300


004: Unable to read table of contents header

Unable to open disc. Is there an audio CD in the drive?

How about -vsQ? Kick it in the head.

[joe@localhost joe]$ cdparanoia -vsQ
cdparanoia III release 9.8 (March 23, 2001)
(C) 2001 Monty <monty@xiph.org> and Xiphophorus

Report bugs to paranoia@xiph.org
http://www.xiph.org/paranoia/

Checking /dev/cdrom for cdrom...
Testing /dev/cdrom for cooked ioctl() interface
CDROM sensed: ATAPI compatible Hewlett-Packard DVD Writer 300

004: Unable to read table of contents header

Unable to open disc. Is there an audio CD in the drive?


And thank you again for the help. :)

This is interesting, I just tried "cdparanoia -Q -d /dev/hdd" and here is the result:

cdparanoia III release 9.8 (March 23, 2001)
(C) 2001 Monty <monty@xiph.org> and Xiphophorus

Report bugs to paranoia@xiph.org
http://www.xiph.org/paranoia/


Table of contents (audio tracks only):
track length begin copy pre ch
===========================================================
1. 21883 [04:51.58] 0 [00:00.00] no no 2
2. 9192 [02:02.42] 21883 [04:51.58] no no 2
3. 7538 [01:40.38] 31075 [06:54.25] no no 2
4. 12785 [02:50.35] 38613 [08:34.63] no no 2
5. 13062 [02:54.12] 51398 [11:25.23] no no 2
6. 10725 [02:23.00] 64460 [14:19.35] no no 2
7. 9865 [02:11.40] 75185 [16:42.35] no no 2
8. 10728 [02:23.03] 85050 [18:54.00] no no 2
9. 15560 [03:27.35] 95778 [21:17.03] no no 2
10. 19275 [04:17.00] 111338 [24:44.38] no no 2
11. 11270 [02:30.20] 130613 [29:01.38] no no 2
12. 14840 [03:17.65] 141883 [31:31.58] no no 2
TOTAL 156723 [34:49.48] (audio only)

After screwing with it for a while and manually changing to config in it to just go right to /dev/hdd, it works now, but it just didn't like the way it used to be set up. That's kind of weird considering it's been that way for months and was never a problem before.

Thank you very much cyrnel for all of your help. It definitely pointed me in the right direction. :)