Announcement

Collapse
No announcement yet.

Cant read DVDs all of a sudden

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] Cant read DVDs all of a sudden

    For the last several days up to and including last night, I've been successfully using dd to copy DVDs to ISO before processing them with Handbrake. This morning i get this instead:
    Code:
    [FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]/shared/Incoming/Movies[/B][/COLOR][COLOR=#000000]$ ./ripiso          [/COLOR]
    <13>Aug 26 16:46:26 ripiso: BRUNO 3847540 2048
    <13>Aug 26 16:46:27 ripiso: dd: error reading '/dev/sr0': Input/output error
    <13>Aug 26 16:46:27 ripiso: 1852+0 records in
    <13>Aug 26 16:46:27 ripiso: 1852+0 records out
    <13>Aug 26 16:46:27 ripiso: 3792896 bytes (3.8 MB, 3.6 MiB) copied, 0.178407 s, 21.3 MB/s
    [COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]/shared/Incoming/Movies[/B][/COLOR][COLOR=#000000]$ dmesg |tail -n 6[/COLOR]
    [Wed Aug 26 16:46:26 2020] sr 1:0:0:0: [sr0] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [Wed Aug 26 16:46:26 2020] sr 1:0:0:0: [sr0] tag#19 Sense Key : Illegal Request [current]  
    [Wed Aug 26 16:46:26 2020] sr 1:0:0:0: [sr0] tag#19 Add. Sense: Read of scrambled sector without authentication
    [Wed Aug 26 16:46:26 2020] sr 1:0:0:0: [sr0] tag#19 CDB: Read(10) 28 00 00 00 07 3d 00 00 01 00
    [Wed Aug 26 16:46:26 2020] blk_update_request: I/O error, dev sr0, sector 7412 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [Wed Aug 26 16:46:26 2020] Buffer I/O error on dev sr0, logical block 1853, async page read
    
    [/FONT]
    The "tag#" randomly changes as does the number of bytes read before the error dd fails after a very small number of bytes between 9 and 25MB or so.

    More oddness: the command "eject" will not work using "/dev/sr0" but will with cdrom, then immediately after using "eject cdrom", "eject /dev/sr0" will work again for a few seconds, then return to failing again.

    Also odd behavior; when I open the tray with the button, it will open and then close itself almost immediately, but if I open it a second time it stays open like it should. Almost seems like a kernel/driver issue. The drive is from 2013, so maybe it's just dying. Dang thing hardly ever gets used...

    Code:
    [FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]/shared/Incoming/Movies[/B][/COLOR][COLOR=#000000]$ sudo lshw -C disk[/COLOR]
      *-cdrom                    
           description: DVD-RAM writer
           product: BDDVDRW CH12LS28
           vendor: HL-DT-ST
           physical id: 0
           bus info: scsi@1:0.0.0
           logical name: /dev/cdrom
           logical name: /dev/cdrw
           logical name: /dev/dvd
           logical name: /dev/dvdrw
           logical name: /dev/sr0
           version: 1.02
           capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
           configuration: ansiversion=5 status=ready
         *-medium
              physical id: 0
              logical name: /dev/cdrom[/FONT]
    Last edited by oshunluvr; Aug 26, 2020, 02:54 PM.

    Please Read Me

    #2
    TO be clear: The drive works for normal use - Makemkv, VLC, and Handbrake can all use it. But dd could read it directly yesterday and can't now - UNLESS I start one of those programs first, then start dd.

    This is really odd...

    Please Read Me

    Comment


      #3
      I know it is probably not useful, but do you have libdvdcss2?

      The dmesg output smacks of this, plus the small file size from your script.

      The second answer here may be relevant
      https://unix.stackexchange.com/quest...my-dvd-with-dd

      Comment


        #4
        Yes I do, 1.4.2 the latest IIRC.

        Since it's built on location, I've considered removing it and rebuilding. I may just be a kernel jump since it was installed. It hasn't been updated since mid-2019

        Please Read Me

        Comment


          #5
          And yes, that second paragraph seems precisely on point. Still odd that for several days it worked without issue - until it didn't.

          Maybe the drive was "locked" to libdvdcss2 by some process that the update killed and thus the drive stopped allowing access.

          None of this explains the weird eject behavior though...

          Please Read Me

          Comment


            #6
            Could be differences in the DVDs themselves. THe earlier ones I ripped were older - 90's era, but the last few were late 2000's. That might explain the difference in behavior.

            Please Read Me

            Comment


              #7
              Hi
              I ended up purchasing a new drive to be able to play DVD movies
              jts

              Comment

              Working...
              X