Forums > Cd drve won't mount

uLoVeMikeRoch

Nov 5 2005, 05:34 PM

Ok, I have been having problems with my cd drives and it's pissing me off. I've researched all over, and no solutions are found. Any ideas? I get the whole, error bad superblock dmesg l or tail thing too.

This is my /etc/fstab and Im pretty sure my drive is hdc and cdrom0.

<!-- begin code provided by createblog.com --><br /># /etc/fstab: static file system information.<br />#<br /># <file system> <mount point>   <type>  <options>       <dump>  <pass><br />proc            /proc           proc    defaults        0       0<br />/dev/hda1       /               ext3    defaults,errors=remount-ro 0       1<br />/dev/hda5       none            swap    sw              0       0<br />/dev/hdc        /media/cdrom0   udf,iso9660 ro,user,noauto  0       0<br /><br /><!-- end code provided by createblog.com -->

mipadi

Nov 5 2005, 06:08 PM

Does the directory /media/cdrom0 exist?

uLoVeMikeRoch

Nov 8 2005, 09:30 PM

QUOTE(mipadi @ Nov 5 2005, 6:08 PM)

Does the directory /media/cdrom0 exist?

It exists, but the folder is empty.

This is my Dmesg l tail thing.

<!-- begin code provided by createblog.com --><br />end_request: I/O error, dev hdc, sector 64<br />isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16<br />hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }<br />hdc: packet command error: error=0x40<br />ide: failed opcode was 100<br />ATAPI device hdc:<br />  Error: Hardware error -- (Sense key=0x04)<br />  (reserved error code) -- (asc=0x09, ascq=0x04)<br />  The failed "Read Cd/Dvd Capacity" packet command was:<br />  "25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "<br /><br /><!-- end code provided by createblog.com -->

kryogenix

Nov 9 2005, 03:27 PM

What model drive?

mipadi

Nov 9 2005, 04:29 PM

It seems like a hardware error. First, there is an issue in some versions of Ubuntu/Kubuntu with optical drives. You might try updating the kernel. What version of the kernel do you have? (This can be obtained by running cat /proc/version or uname -a in the terminal.)

It could also be a hardware failure. Check your cables, make sure the drive is hooked up properly, etc.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.