Does anybody have a slower DVD read rate than this?

English Hardware
1

I’m reading from a CD-R, using a Liteon DVD rewriter, 20x capability. The CD was written on a Liteon DVD writer on a Windows computer. The CD-R contains about 780 MB of data as a sets of WAV files.

Dolphin tells me (at first) that it will take approx. 1000 days to copy the data to my hard disk

Can I claim to have the slowest ever reading from a DVD device? Now it only has another 7 to 12 hours left, copying at a data rate between 25 and 33 KB/sec.

Seriously, what’s the likely explanation for this unique performance?

2

XEyedBear adjusted his/her AFDB on Thursday 16 Jul 2009 21:36 to write:

>
> I’m reading from a CD-R, using a Liteon DVD rewriter, 20x capability.
> The CD was written on a Liteon DVD writer on a Windows computer. The
> CD-R contains about 780 MB of data as a sets of WAV files.
>
> Dolphin tells me (at first) that it will take approx. 1000 days to copy
> the data to my hard disk
>
> Can I claim to have the slowest ever reading from a DVD device? Now it
> only has another 7 to 12 hours left, copying at a data rate between 25
> and 33 KB/sec.
>
> Seriously, what’s the likely explanation for this unique performance?
>
>

You are not converting on the fly are you to mps, ogg or some other format?

Probably having difficulties reading the disk, are there any messges in you
/var/log/messages log about read errors?

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

3

Not too sure either if this is related to another thread you have about audio cd’s.
This is a data cd? Correct?
otherwise you would be ripping the cd?

I would be interested to know if k3b is letting you burn cd’s at differing speeds. How it performs ripping cd’s.

4

No I’m not doing any conversion on the fly (on the other hand I have no control over what Linux might be doing without telling me). I’m doing a plain file copy in Dolphin, I believe.

There is no messages.log file - only a messages file which I do not know how to open (a simple text editor won’t open it).

5

Yes, there is a connection to another thread about Dolphin not being able to find this CD.

I’m not sure what constitutes an audio CD. The CD I am trying to read was created by me under windows as an audio cd (using a shareware CD burner) from a set of WAV files created by capturing radio broadcasts in Audacity under Windows. Now that I know how to find the CD using Dolphin I can see that it contains a number of other directories which I didn’t consciously write to the CD (files such as CDA, FLAC, ‘Full CD’, Information, ‘Ogg Vorbis’

I am only copying the files of type wav from the CD in Dolphin. Should I be ripping it instead? If so, what tool should I be using?

6

XEyedBear adjusted his/her AFDB on Friday 17 Jul 2009 17:06 to write:

>> /var/log/messages log about read errors?
>>
>
>
> No I’m not doing any conversion on the fly (on the other hand I have no
> control over what Linux might be doing without telling me). I’m doing a
> plain file copy in Dolphin, I believe.
>
> There is no messages.log file - only a messages file which I do not
> know how to open (a simple text editor won’t open it).
>
>

I don`t think I put a “.” in there :slight_smile:

The messages file is the one and it should open as user in a normal text
editor, or you can just use as:

dmesg

in a console for the last few lines of the system messages, you can also use
Yast>Misc>system log view to view your logs.

However I will say that at the moment I am trying to copy a 7gig ISO file
from an internal drive to an external USB 2.5" 80gig drive and it is taking
forever and the desktop is like molasses, even though there is hardly any
CPU action on any of the three cores here.

HTH

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

7

I think you should be ripping the cd in k3b. Then you will have no problem. Just try it:)

8

Yes (No ?) you are quite right - you didn’t put a ‘.’ in there. With my bad eyesight, coupled with a high resolution monitor (= tiny pixel pitch. not big screen!), I just decided there was one there and I couldn’t see it…

I’ll look at it again, but I suspect the problem is because I’m copying and not ripping. What a yarn, eh?

I’ll try k3b (he says, in blissful ignorance, assuming it will work without any problems…)

9

[QUOTE=baskitcaise;2013839]
… you can also use
Yast>Misc>system log view to view your logs.

/QUOTE]

AH, now this is nice and easy for me - but the results are bit of a frightener, aren’t they? (see last line of long boring post):

end_request: I/O error, dev sr0, sector 64
Buffer I/O error on device sr0, logical block 16
Buffer I/O error on device sr0, logical block 17

and so on for along time

end_request: I/O error, dev sr0, sector 0
end_request: I/O error, dev sr0, sector 4
end_request: I/O error, dev sr0, sector 0
__ratelimit: 56 callbacks suppressed
Buffer I/O error on device sr0, logical block 0
Buffer I/O error on device sr0, logical block 1
Buffer I/O error on device sr0, logical block 2
Buffer I/O error on device sr0, logical block 3
Buffer I/O error on device sr0, logical block 4
Buffer I/O error on device sr0, logical block 5
Buffer I/O error on device sr0, logical block 6
Buffer I/O error on device sr0, logical block 7
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
end_request: I/O error, dev sr0, sector 4
Buffer I/O error on device sr0, logical block 1

sr0: CDROM not ready. Make sure there is a disc in the drive.
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
Buffer I/O error on device sr0, logical block 1
Buffer I/O error on device sr0, logical block 2
Buffer I/O error on device sr0, logical block 3
Buffer I/O error on device sr0, logical block 4
Buffer I/O error on device sr0, logical block 5
Buffer I/O error on device sr0, logical block 6
Buffer I/O error on device sr0, logical block 7
Buffer I/O error on device sr0, logical block 8
Buffer I/O error on device sr0, logical block 9
end_request: I/O error, dev sr0, sector 0
end_request: I/O error, dev sr0, sector 4

These are taken from the time when I was (finally) being able to play a commercially produced audio CD.

I hope they are all explained by media errors and are not an indication of hardware malfunction (I purchased the drive only 2 days ago!)

At the time I was experiencing very slow copy speed, there were many instances like this:

Jul 16 14:07:00 LINEAR-1 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jul 16 14:07:00 LINEAR-1 kernel: klogd 1.4.1, ---------- state change ----------
Jul 16 14:07:00 LINEAR-1 kernel: ISO 9660 Extensions: RRIP_1991A
Jul 16 14:07:00 LINEAR-1 hald: mounted /dev/sr0 on behalf of uid 1000
Jul 16 14:08:36 LINEAR-1 su: (to root) tony on /dev/pts/0
Jul 16 14:11:11 LINEAR-1 hald: unmounted /dev/sr0 from ‘/media/SU1110.001-1’ on behalf of uid 1000
Jul 16 14:11:15 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:11:16 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.

Jul 16 14:11:35 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:11:37 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 0
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 0
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 1
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 2
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 3
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 4
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 5
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 6
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 7
Jul 16 14:11:37 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 0
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 0
Jul 16 14:11:37 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 1
Jul 16 14:31:38 LINEAR-1 – MARK –
Jul 16 14:36:40 LINEAR-1 smartd[3858]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 88 to 89
Jul 16 14:36:40 LINEAR-1 smartd[3858]: Device: /dev/sdb [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 24 to 9
Jul 16 14:41:09 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.

Jul 16 14:41:17 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:41:18 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:41:19 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:21 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:23 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:25 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:27 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:29 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:31 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:33 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:35 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:41:39 LINEAR-1 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jul 16 14:41:39 LINEAR-1 hald: mounted /dev/sr0 on behalf of uid 1000
Jul 16 14:41:39 LINEAR-1 kernel: ISO 9660 Extensions: RRIP_1991A
Jul 16 14:42:47 LINEAR-1 hald: unmounted /dev/sr0 from ‘/media/SU1110.001-1’ on behalf of uid 1000
Jul 16 14:42:50 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:42:51 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:42:52 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:42:53 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:42:54 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:42:55 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:42:57 LINEAR-1 kernel: sr0: CDROM not ready yet.

Jul 16 14:43:09 LINEAR-1 kernel: sr0: disc change detected.
Jul 16 14:43:11 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 0
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 0
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 1
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 2
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 3
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 4
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 5
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 6
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 7
Jul 16 14:43:11 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 0
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 0
Jul 16 14:43:11 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 1
Jul 16 14:43:16 LINEAR-1 kernel: end_request: I/O error, dev fd0, sector 0
Jul 16 14:43:16 LINEAR-1 kernel: end_request: I/O error, dev fd0, sector 0
Jul 16 14:45:02 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:03 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:04 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:05 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:06 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:07 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.

Jul 16 14:45:15 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:16 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.

Jul 16 14:45:39 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:40 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:41 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:42 LINEAR-1 kernel: sr0: CDROM not ready. Make sure there is a disc in the drive.
Jul 16 14:45:43 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:45:45 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:45:47 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:45:49 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:45:51 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:45:53 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:45:55 LINEAR-1 kernel: sr0: CDROM not ready yet.
Jul 16 14:46:05 LINEAR-1 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jul 16 14:46:05 LINEAR-1 kernel: ISO 9660 Extensions: RRIP_1991A
Jul 16 14:46:05 LINEAR-1 hald: mounted /dev/sr0 on behalf of uid 1000
Jul 16 14:47:01 LINEAR-1 hald: unmounted /dev/sr0 from ‘/media/Data disc (13 Jul 09)’ on behalf of uid 1000
Jul 16 14:47:24 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 0
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 0
Jul 16 14:47:24 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 4
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 1
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 2
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 3
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 4
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 5
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 6
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 7
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 8
Jul 16 14:47:24 LINEAR-1 kernel: Buffer I/O error on device sr0, logical block 9
Jul 16 14:47:24 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 0
Jul 16 14:47:24 LINEAR-1 kernel: end_request: I/O error, dev sr0, sector 4

But here’s the one that really has me worried:

Jul 16 21:03:55 LINEAR-1 smartd[3965]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 152 to 220

How come my whole PC hasn’t gone up in smoke and flames!?

10

Just a passing thought, is the drive in question a SATA drive ? if so,check the cable isn’t bent/twisted/kinked in any way. If it is get a new one. Any bends/twists/kinks in a SATA cable will cause disk errors/slow downs/problems

Andy

11

Excellent advice. You always get advice and experience just after you need it.

Isn’t design a wonderful 2-edged sword? Here’s this lovely red SATA signal cable - so much easier to bend and twist than the traditional 80 core ribbon.Not only that, but once you bend it, it stays bent - even 180 degrees. Great, now I can bend it around these other objects to improve air flow,… aaarrrggghhhh!

But now I know.

12

I did. Magic! What a great little application. It read the disk in just a few minutes. Problem solved, knowledge gained. And it’s still only 11:30 in the morning.

Thanks chaps. Have a nice day.

13

Good news. We are here to help.:wink: