On Sun, 2016-04-17, Bill Cunningham wrote:
>
> "Jorgen Grahn" <
grahn...@snipabacken.se> wrote in message
> news:slrnnh5tf1.5...@frailea.sa.invalid...
>> On Sat, 2016-04-16, Bill Cunningham wrote:
>>> OK well. I don't know what to say. I used this and it worked,
>>>
>>> dd if=/dev/sr1 of=/xpmce1.iso iflag=nocache oflag=direct
>>
>> I suspect that just "dd if=/dev/sr1 of=/xpmce1.iso" would have
>> worked, too.
>>
>>> The copy was made of 650 MB or so. Not so much as a hiccup. Well one of
>>> these CDRs is damaged. I will have to try ddrescue with it. Thanks for
>>> the
>>> help. I hope I haven't bothered anyone too much.
>>
>> You haven't, but you are often hard to follow. (Communication is
>> difficult, so that's not surprising.)
>>
>>> Maybe those flags helped or not.
>>
>> I think not, but yes.
>
> OK no error has stopped copying but this is what I have gathered from one
> created IO.
>
> blk_update... critical medium error sector 1244192
> IO_error sector 1244240
> IO_error logical block 311060 async page read
That does not seem good.
> 1244240 in
> 1244240 out
> 637 MB
>
> Will dd not stop if there's an error and just keep copying?
My guess was that it will not, but I can be wrong.
Looking at the manual, it doesn't say anything explicitly. However
there is a 'noerror' option to "continue after read errors" so I
suppose if you don't enable it, it should stop at the first read
error.
> I think what I did before is plugin my USB DVD/RW and try to use it
> too fast. When I wait for recognition (you know serial, slow,
> especially USB) errors are printed. I use dd and there's no
> problem. Basically before I jumped in too fast and got those errors.
Hm ... you shouldn't get errors just by plugging in the device.
> But copying is not breaking. Should I run ddrescue over these ISO 9660s?
No idea; I haven't used it. Sorry.