Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #203210 > unrolled thread
| Started by | md <mickydean@protonmail.com> |
|---|---|
| First post | 2018-12-10 07:00 +0100 |
| Last post | 2018-12-10 20:50 +0100 |
| Articles | 11 — 5 participants |
Back to article view | Back to linux.debian.user
dd: error reading '/dev/sr0': Input/output error md <mickydean@protonmail.com> - 2018-12-10 07:00 +0100
Re: dd: error reading '/dev/sr0': Input/output error Gene Heskett <gheskett@shentel.net> - 2018-12-10 07:50 +0100
Re: dd: error reading '/dev/sr0': Input/output error "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-10 08:50 +0100
Re: dd: error reading '/dev/sr0': Input/output error Gene Heskett <gheskett@shentel.net> - 2018-12-10 09:30 +0100
Re: dd: error reading '/dev/sr0': Input/output error "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-10 09:50 +0100
Re: dd: error reading '/dev/sr0': Input/output error Gene Heskett <gheskett@shentel.net> - 2018-12-10 14:00 +0100
Re: dd: error reading '/dev/sr0': Input/output error Jude DaShiell <jdashiel@panix.com> - 2018-12-10 10:20 +0100
Re: dd: error reading '/dev/sr0': Input/output error "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-10 10:40 +0100
Re: dd: error reading '/dev/sr0': Input/output error Gene Heskett <gheskett@shentel.net> - 2018-12-10 14:30 +0100
Re: dd: error reading '/dev/sr0': Input/output error Gene Heskett <gheskett@shentel.net> - 2018-12-10 14:10 +0100
Re: dd: error reading '/dev/sr0': Input/output error Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-12-10 20:50 +0100
| From | md <mickydean@protonmail.com> |
|---|---|
| Date | 2018-12-10 07:00 +0100 |
| Subject | dd: error reading '/dev/sr0': Input/output error |
| Message-ID | <x3mLM-7mW-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
When copying a dvd to file on the harddrive, I'm getting the message dd: error reading '/dev/sr0': Input/output error If I first run dvdbackup, then Ctrl-C out of it. I can then reissue the dd command and it will finish fine. If I eject the dvd then insert another dvd, the same situation occurs. My system: MD> lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.6 (stretch) Release: 9.6 Codename: stretch example terminal session:: MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s dd: error reading '/dev/sr0': Input/output error 67688+0 records in 67688+0 records out 34656256 bytes (35 MB, 33 MiB) copied, 7.55342 s, 4.6 MB/s MD> dvdbackup -M libdvdread: Attempting to retrieve all CSS keys libdvdread: This can take a _long_ time, please be patient libdvdread: Get key for /VIDEO_TS/VIDEO_TS.VOB at 0x00000142 libdvdread: Elapsed time 0 <snip> libdvdread: Elapsed time 0 ^C MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso status=progress 7996654080 bytes (8.0 GB, 7.4 GiB) copied, 1831 s, 4.4 MB/s 15621264+0 records in 15621264+0 records out 7998087168 bytes (8.0 GB, 7.4 GiB) copied, 1831.44 s, 4.4 MB/s
[toc] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-12-10 07:50 +0100 |
| Message-ID | <x3ny9-7Sr-1@gated-at.bofh.it> |
| In reply to | #203210 |
On Monday 10 December 2018 00:34:58 md wrote: > When copying a dvd to file on the harddrive, I'm getting the message > dd: error reading '/dev/sr0': Input/output error > If I first run dvdbackup, then Ctrl-C out of it. I can then reissue > the dd command and it will finish fine. If I eject the dvd then insert > another dvd, the same situation occurs. > Classic slow spinup. You can get a better dvd drive that /might/ be faster. > My system: > > MD> lsb_release -a > No LSB modules are available. > Distributor ID: Debian > Description: Debian GNU/Linux 9.6 (stretch) > Release: 9.6 > Codename: stretch > > example terminal session:: > > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s > dd: error reading '/dev/sr0': Input/output error > 67688+0 records in > 67688+0 records out > 34656256 bytes (35 MB, 33 MiB) copied, 7.55342 s, 4.6 MB/s > > MD> dvdbackup -M > libdvdread: Attempting to retrieve all CSS keys > libdvdread: This can take a _long_ time, please be patient > libdvdread: Get key for /VIDEO_TS/VIDEO_TS.VOB at 0x00000142 > libdvdread: Elapsed time 0 > <snip> > libdvdread: Elapsed time 0 > ^C > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso status=progress > 7996654080 bytes (8.0 GB, 7.4 GiB) copied, 1831 s, 4.4 MB/s > 15621264+0 records in > 15621264+0 records out > 7998087168 bytes (8.0 GB, 7.4 GiB) copied, 1831.44 s, 4.4 MB/s -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2018-12-10 08:50 +0100 |
| Message-ID | <x3oud-8rB-1@gated-at.bofh.it> |
| In reply to | #203210 |
Hi,
md wrote:
> When copying a dvd to file on the harddrive, I'm getting [...]
> MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso
> 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s
> dd: error reading '/dev/sr0': Input/output error
Do you see fresh messages in the output of dmesg ?
Like
Dec 2 13:56:33 ... kernel: [...] Sense Key : Medium Error [current]
Dec 2 13:56:33 ... kernel: [...] Info fld=0x69c0
Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0]
Dec 2 13:56:33 ... kernel: [...] Add. Sense: Unrecovered read error
Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0] CDB:
Dec 2 13:56:33 ... kernel: [...] Read(10): 28 00 00 00 69 b8 00 00 40 00
What do you get from
xorriso -outdev /dev/sr0 \
-check_media use=outdev \
data_to=/sdb1/movie.udf \
--
(It will at least show error messages directly.)
Gene Heskett wrote:
> Classic slow spinup.
After 33 MiB of reading ?
(We have a bug in the kernel since 2008 which prevents waiting for the
drive to become ready after automatic tray loading. But this causes
0 bytes of read result and lets dd end immediately.)
> You can get a better dvd drive
Read failures of decaying drives often show surprising success-or-error
patterns. Depending on how idvdbackup accesses the drive, its doings
might be beneficial.
But reading in
http://manpages.ubuntu.com/manpages/bionic/man1/dvdbackup.1.html
"-M, --mirror
backup the whole DVD"
i'd expect it to read sequentiall, like dd does.
So more questions to md:
- Does a second or third dd run yield success if no dvdbackup was run
inbetween ?
- Does dvdbackup yield a complete set of files if you let it work
until it ends on its own ?
Have a nice day :)
Thomas
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-12-10 09:30 +0100 |
| Message-ID | <x3p6V-to-1@gated-at.bofh.it> |
| In reply to | #203213 |
On Monday 10 December 2018 02:45:43 Thomas Schmitt wrote: > Hi, > > md wrote: > > When copying a dvd to file on the harddrive, I'm getting [...] > > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso > > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s > > dd: error reading '/dev/sr0': Input/output error > > Do you see fresh messages in the output of dmesg ? > Like > > Dec 2 13:56:33 ... kernel: [...] Sense Key : Medium Error [current] > Dec 2 13:56:33 ... kernel: [...] Info fld=0x69c0 > Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0] > Dec 2 13:56:33 ... kernel: [...] Add. Sense: Unrecovered read error > Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0] CDB: > Dec 2 13:56:33 ... kernel: [...] Read(10): 28 00 00 00 69 b8 00 00 > 40 00 > > What do you get from > > xorriso -outdev /dev/sr0 \ > -check_media use=outdev \ > data_to=/sdb1/movie.udf \ > -- > > (It will at least show error messages directly.) > > Gene Heskett wrote: > > Classic slow spinup. > > After 33 MiB of reading ? That much would would also invalidate the dry sliders theory > > (We have a bug in the kernel since 2008 which prevents waiting for the > drive to become ready after automatic tray loading. But this causes > 0 bytes of read result and lets dd end immediately.) > I've noted that too. > > You can get a better dvd drive > > Read failures of decaying drives often show surprising > success-or-error patterns. Depending on how idvdbackup accesses the > drive, its doings might be beneficial. > But reading in > > http://manpages.ubuntu.com/manpages/bionic/man1/dvdbackup.1.html > "-M, --mirror > backup the whole DVD" > > i'd expect it to read sequentiall, like dd does. > > So more questions to md: > > - Does a second or third dd run yield success if no dvdbackup was run > inbetween ? > > - Does dvdbackup yield a complete set of files if you let it work > until it ends on its own ? > > > Have a nice day :) > > Thomas -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> +
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2018-12-10 09:50 +0100 |
| Message-ID | <x3pqh-A2-3@gated-at.bofh.it> |
| In reply to | #203216 |
Hi, Gene Heskett wrote: > > > Classic slow spinup. I wrote: > > After 33 MiB of reading ? > That much would would also invalidate the dry sliders theory There might well be mechanical or optical problems involved. As said, the failure patterns of drives are variform. Thus my question whether dd can replace dvdbackup as trailblazer. ------------------------------------------------------------------------ Off topic: > > (We have a bug in the kernel since 2008 which prevents waiting for the > > drive to become ready after automatic tray loading. > I've noted that too. I identified the two commits involved (210ba1d1724f5c4ed87a2ab1a21ca861a915f734 and 96bcc722c47d07b6fd05c9d0cb3ab8ea5574c5b1) and have a proposal for a fix. What i don't have is real iron for kernel development or contact to a kernel developer who would be interested in the sr driver and its bugs. The old timeout limit was 20 seconds. My lamest drive needs 18 seconds to become ready (not by spin-up delay but rather by long reading time when assessing the medium state). So i'd propose 30 seconds of patience. ------------------------------------------------------------------------ Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-12-10 14:00 +0100 |
| Message-ID | <x3tkd-2VA-1@gated-at.bofh.it> |
| In reply to | #203217 |
On Monday 10 December 2018 03:44:20 Thomas Schmitt wrote: > Hi, > > Gene Heskett wrote: > > > > Classic slow spinup. > > I wrote: > > > After 33 MiB of reading ? > > > > That much would would also invalidate the dry sliders theory > > There might well be mechanical or optical problems involved. As said, > the failure patterns of drives are variform. Thus my question whether > dd can replace dvdbackup as trailblazer. > > ---------------------------------------------------------------------- >-- > > Off topic: > > > (We have a bug in the kernel since 2008 which prevents waiting for > > > the drive to become ready after automatic tray loading. > > > > I've noted that too. > > I identified the two commits involved > (210ba1d1724f5c4ed87a2ab1a21ca861a915f734 and > 96bcc722c47d07b6fd05c9d0cb3ab8ea5574c5b1) and have a proposal for a > fix. What i don't have is real iron for kernel development or contact > to a kernel developer who would be interested in the sr driver and its > bugs. > > The old timeout limit was 20 seconds. My lamest drive needs 18 seconds > to become ready (not by spin-up delay but rather by long reading time > when assessing the medium state). So i'd propose 30 seconds of > patience. > I personally think thats a heck of a good idea. Someone with commit rights should make it so. The best cd/dvd writer we have, k3b, cannot be told to verify its written image because it times out way too fast at re-recognizing the ejected and reloaded disk. This has needed fixing since years ago. > ---------------------------------------------------------------------- >-- > > Have a nice day :) > > Thomas -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Jude DaShiell <jdashiel@panix.com> |
|---|---|
| Date | 2018-12-10 10:20 +0100 |
| Message-ID | <x3pTj-ZF-1@gated-at.bofh.it> |
| In reply to | #203213 |
On Mon, 10 Dec 2018, Thomas Schmitt wrote: > Date: Mon, 10 Dec 2018 02:45:43 > From: Thomas Schmitt <scdbackup@gmx.net> > To: debian-user@lists.debian.org > Cc: mickydean@protonmail.com > Subject: Re: dd: error reading '/dev/sr0': Input/output error > Resent-Date: Mon, 10 Dec 2018 07:46:23 +0000 (UTC) > Resent-From: debian-user@lists.debian.org > > Hi, > > md wrote: > > When copying a dvd to file on the harddrive, I'm getting [...] > > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso > > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s > > dd: error reading '/dev/sr0': Input/output error > > Do you see fresh messages in the output of dmesg ? > Like > > Dec 2 13:56:33 ... kernel: [...] Sense Key : Medium Error [current] > Dec 2 13:56:33 ... kernel: [...] Info fld=0x69c0 > Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0] > Dec 2 13:56:33 ... kernel: [...] Add. Sense: Unrecovered read error > Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0] CDB: > Dec 2 13:56:33 ... kernel: [...] Read(10): 28 00 00 00 69 b8 00 00 40 00 > > What do you get from > > xorriso -outdev /dev/sr0 \ > -check_media use=outdev \ > data_to=/sdb1/movie.udf \ > -- > > (It will at least show error messages directly.) > > > Gene Heskett wrote: > > Classic slow spinup. > > After 33 MiB of reading ? > > (We have a bug in the kernel since 2008 which prevents waiting for the > drive to become ready after automatic tray loading. But this causes > 0 bytes of read result and lets dd end immediately.) > > > > You can get a better dvd drive > > Read failures of decaying drives often show surprising success-or-error > patterns. Depending on how idvdbackup accesses the drive, its doings > might be beneficial. > But reading in > > http://manpages.ubuntu.com/manpages/bionic/man1/dvdbackup.1.html > "-M, --mirror > backup the whole DVD" > > i'd expect it to read sequentiall, like dd does. > > So more questions to md: > > - Does a second or third dd run yield success if no dvdbackup was run > inbetween ? > > - Does dvdbackup yield a complete set of files if you let it work > until it ends on its own ? > > > Have a nice day :) > > Thomas > Why not prefix that dd command with a sudo udevadm settle command and only allow the dd command to run on success case? > --
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2018-12-10 10:40 +0100 |
| Message-ID | <x3qcF-16d-1@gated-at.bofh.it> |
| In reply to | #203218 |
Hi,
Jude DaShiell wrote:
> Why not prefix that dd command with a sudo udevadm settle command and
> only allow the dd command to run on success case?
man udevadm says:
udevadm settle [options]
Watches the udev event queue, and exits if all current events are
handled.
We have no indication yet that the udev event queue is involved.
(I'd also say that udev traditionally makes additional trouble rather than
preventing some.)
---------------------------------------------------------------------------
Off topic again:
(If dd can read 33 MiB, then it is not a start-up problem.)
The known impatience of Linux with automatic tray loading can be worked
around by pulling in the tray with a burn program (eject -t falls victim
to the kernel impatience).
I use:
xorriso -outdev /dev/sr0
before trying to read the medium by POSIX i/o like dd(1) or read(2).
Have a nice day :)
Thomas
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-12-10 14:30 +0100 |
| Message-ID | <x3tNg-3lf-11@gated-at.bofh.it> |
| In reply to | #203219 |
On Monday 10 December 2018 04:37:10 Thomas Schmitt wrote: > Hi, > > Jude DaShiell wrote: > > Why not prefix that dd command with a sudo udevadm settle command > > and only allow the dd command to run on success case? > > man udevadm says: > > udevadm settle [options] > Watches the udev event queue, and exits if all current events > are handled. > > We have no indication yet that the udev event queue is involved. > (I'd also say that udev traditionally makes additional trouble rather > than preventing some.) > > ---------------------------------------------------------------------- >----- Off topic again: > (If dd can read 33 MiB, then it is not a start-up problem.) > > The known impatience of Linux with automatic tray loading can be > worked around by pulling in the tray with a burn program (eject -t > falls victim to the kernel impatience). > I use: > > xorriso -outdev /dev/sr0 > > before trying to read the medium by POSIX i/o like dd(1) or read(2). > This is also something that has not been installed till now, and has more buttons than grandma's button jar. But could it be configured into k3b for automatic usage? $64k question... Thanks Thomas > > Have a nice day :) > > Thomas -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-12-10 14:10 +0100 |
| Message-ID | <x3ttU-3ew-13@gated-at.bofh.it> |
| In reply to | #203218 |
On Monday 10 December 2018 04:11:28 Jude DaShiell wrote:
> On Mon, 10 Dec 2018, Thomas Schmitt wrote:
> > Date: Mon, 10 Dec 2018 02:45:43
> > From: Thomas Schmitt <scdbackup@gmx.net>
> > To: debian-user@lists.debian.org
> > Cc: mickydean@protonmail.com
> > Subject: Re: dd: error reading '/dev/sr0': Input/output error
> > Resent-Date: Mon, 10 Dec 2018 07:46:23 +0000 (UTC)
> > Resent-From: debian-user@lists.debian.org
> >
> > Hi,
> >
> > md wrote:
> > > When copying a dvd to file on the harddrive, I'm getting [...]
> > > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso
> > > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s
> > > dd: error reading '/dev/sr0': Input/output error
> >
> > Do you see fresh messages in the output of dmesg ?
> > Like
> >
> > Dec 2 13:56:33 ... kernel: [...] Sense Key : Medium Error
> > [current] Dec 2 13:56:33 ... kernel: [...] Info fld=0x69c0
> > Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0]
> > Dec 2 13:56:33 ... kernel: [...] Add. Sense: Unrecovered read
> > error Dec 2 13:56:33 ... kernel: [...] sr 2:0:0:0: [sr0] CDB:
> > Dec 2 13:56:33 ... kernel: [...] Read(10): 28 00 00 00 69 b8 00
> > 00 40 00
> >
> > What do you get from
> >
> > xorriso -outdev /dev/sr0 \
> > -check_media use=outdev \
> > data_to=/sdb1/movie.udf \
> > --
> >
> > (It will at least show error messages directly.)
> >
> > Gene Heskett wrote:
> > > Classic slow spinup.
> >
> > After 33 MiB of reading ?
> >
> > (We have a bug in the kernel since 2008 which prevents waiting for
> > the drive to become ready after automatic tray loading. But this
> > causes 0 bytes of read result and lets dd end immediately.)
> >
> > > You can get a better dvd drive
> >
> > Read failures of decaying drives often show surprising
> > success-or-error patterns. Depending on how idvdbackup accesses the
> > drive, its doings might be beneficial.
> > But reading in
> >
> > http://manpages.ubuntu.com/manpages/bionic/man1/dvdbackup.1.html
> > "-M, --mirror
> > backup the whole DVD"
> >
> > i'd expect it to read sequentiall, like dd does.
> >
> > So more questions to md:
> >
> > - Does a second or third dd run yield success if no dvdbackup was
> > run inbetween ?
> >
> > - Does dvdbackup yield a complete set of files if you let it work
> > until it ends on its own ?
> >
> >
> > Have a nice day :)
> >
> > Thomas
>
> Why not prefix that dd command with a sudo udevadm settle command and
> only allow the dd command to run on success case?
I was not aware of that utility, from the man page:
udevadm settle [options]
Watches the udev event queue, and exits if all current events are
handled.
--timeout=seconds
Maximum number of seconds to wait for the event queue to become
empty. The default value is 120 seconds. A value of 0 will check
if the queue is empty and always return immediately.
Perhaps there is a place to configure that into k3b, and make a write
verify work?
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2018-12-10 20:50 +0100 |
| Message-ID | <x3zJ0-6V7-7@gated-at.bofh.it> |
| In reply to | #203210 |
Le 10/12/2018 à 06:34, md a écrit : > > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s > dd: error reading '/dev/sr0': Input/output error (...) > MD> dvdbackup -M > libdvdread: Attempting to retrieve all CSS keys > libdvdread: This can take a _long_ time, please be patient > libdvdread: Get key for /VIDEO_TS/VIDEO_TS.VOB at 0x00000142 Didn't these messages about CSS keys ring a bell in anybody's mind ? Looks like it is a video DVD protected with CSS. The DVD drive must be unlocked first or will issue read errors on some protected sectors. Check the kernel logs with dmesg.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web