cdrom reads only 88MB

BroX · 04-17-2005, 05:24 AM

Hey all,

as the subject states, when I want to read a cd with large files, only the first 88MB are read. I'm sure there should be more because before I could simply play the movie files (and the discs are not rewritable). Now it only plays the beginning. 'ls -l -/mnt/cdrom' also tells me that the files are only 88MB.

Anyone an idea what could be wrong here? I never had this problem before.

Cheers, Leon.

marsques · 04-17-2005, 06:51 AM

have you got one cdrom drive or two (ie 1) DVD and a 2) CDRW or vise versa) so you could check if this problem occurs in the other drive as well...

does this happen with a different version of the kernel...

did this start happening since you installed a new program or anything of that sort...

BroX · 04-18-2005, 04:31 AM

I have only one cdrom drive, read only. With other kernel versions (Slack 2.4.29 & 2.6.11, Gentoo 2.4.28) I get exactly the same. I do not recall installing anything new lately that could affect this. Thing is that I haven't played avi files from CD for a while so I don't know when it started. Smaller files <88MB are being read just fine.

marsques · 04-18-2005, 01:01 PM

is it the same under windows?

marsques · 04-18-2005, 01:07 PM

when i typed "ls -l /home" it says "total 120" however it is a 10GB partition with only 3.5GB of data in it..

mlangdn · 04-18-2005, 02:00 PM

You may have data written to the /mnt/cdrom directory (or whatever the mount point is named). That directory needs to be empty. I had a similar problem when I accidently copied data to a mount point using drag and drop.

I use the terminal now - hehe!

marsques · 04-18-2005, 02:21 PM

actually no... the directory does not need to be empty... when you mount it on a directory it just takes over the directory...

i just mounted the cdrom on a different directory that already had files in it... after mounting the cdrom in that directory the files that were there were no longer accessible but the one's on the cdrom were... however after unmounting the cdrom original files in the directory were accessible again...

etrumbo · 04-18-2005, 03:36 PM

This seems unlikely but it's worth asking anyway. Is it possibly a multisession recorded CD in a non-multisession compatible CD-ROM drive? I've run into this even with late model PC's not wanting to see anything past the first session I recorded.

BroX · 04-19-2005, 02:38 AM

Thanks for all the input!

* /mnt/cdrom/ is empty (when nothing is mounted)
* In windows all is fine
* it's not a multisession problem because the same occurs with cd's with only one large file on it [EDIT] NOT TRUE! See down.

When I mount the drive I don't see anything in dmesg or /var/log/messages. However, when I try to copy the file to the harddisk, I get an Input/output error. And in /var/log/messages I see the following

Code:

Apr 19 10:19:24 leon-fyg kernel: isofs_read_level3_size: More than 100 file sections ?!?, aborting...

In /var/log/syslog this shows up after trying to copy the file (I shortened it, it is actually a repetition of similar messages):

Code:

Apr 19 10:19:39 leon-fyg kernel: isofs_read_level3_size: inode=45302 ino=61042
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54
end_request: I/O error, dev 16:00 (hdc), sector 5796
hdc: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
hdc: media error (bad sector): error=0x34
end_request: I/O error, dev 16:00 (hdc), sector 5800

I googled all around but can't find anything. Could it be a hardware issue?

If anyone has an idea how to diagnose this problem I'd be delighted to hear about this.

Cheers, Leon.

BroX · 04-20-2005, 09:13 AM

I remember that a while ago I removed some packages which I assumed were only for burning.

Could it be that tat causes the cdrtools (contain mkisofs) stuff I pasted above? I reinstalled mkisofs but that doesn't help.

Other suggestions?

Cheers, Leon.

killerbob · 04-20-2005, 10:25 AM

How was the CDROM burned? Is it possible you were using something like DirectCD to burn the disc, and may not have full support in Linux?

BroX · 04-20-2005, 11:05 AM

Quote:

Originally posted by killerbob
How was the CDROM burned? Is it possible you were using something like DirectCD to burn the disc, and may not have full support in Linux?

Yep, I just figured out that at least one of the CDs that it occurred with IS indeed a InCD multisession.

How can I enable support for this?

I already modprobe'd udf, but that didn't do it. I tried closing the multisession but can't find a pc here with InCD installed...

Cheers, Leon.

killerbob · 04-20-2005, 11:23 AM

I'm afraid I don't know. Ever since I noticed that DirectCD doesn't even work in Windows without 3rd party software installed, I haven't used the software or anything like it. That was probably 7 or 8 years ago. I'd rather go through a few extra steps and create an ISO 9660 disc that can be read by anything.

The only bit of useful suggestion I can make is that if the disc reads fine in Windows, copy it to your hard drive and burn the disc again using a different format, maybe? Or mount the Windows directory under Linux and copy the files from there? Blank discs cost maybe a quarter each, and it could save you a lot of headache....

BroX · 04-21-2005, 01:49 AM

Quote:

Originally posted by killerbob
The only bit of useful suggestion I can make is that if the disc reads fine in Windows, copy it to your hard drive and burn the disc again using a different format, maybe? Or mount the Windows directory under Linux and copy the files from there? Blank discs cost maybe a quarter each, and it could save you a lot of headache....

Thanks, that's exactly what I'm gonna do. Apparently the last time I read the disks without a problem was longer ago than I thought (i.e. in my dual-boot period). Apologies for the confusement my train of thought might have caused

Cheers, Leon.