I saw a similar post here : Vero doesn't recognize USB DVD drive
I’m using a USB DVD drive to play DVDs through my Raspberry pi 2. I have the codec for MPEG2, and most DVDs work just fine, but I have also had DVDs show up as HDDs, either with 1.00 GB size or 6.67 GB size, with what appears to be the SD card contents.
The particular DVD we’re having trouble with now is Downton Abbey, season 4, borrowed from the Library. Could it be that it’s formatted under VC-1? I’ve tried booting with the DVD drive unconnected, tried booting without the dvd in the drive, neither appears to work. Sorry, no log, but this doesn’t seem like something the log would pick up. I am using the default skin. Have seen other similar posts as well, maybe a hardware issue?
The pop up message saying that an external hard drive was detected when you insert a DVD is just a quirk of the way our automounter system integrates with Kodi - you’ll probably notice this with disks that play fine too.
On the disk that fails, I assume the play disc option fails to appear but you can see some of the files from the disk in video->files ?
I’m doing some work on the automounter system at the moment (in fact we’re investigating replacing udisks completely with udevil) and in my testing the usual reason for this is read errors on the disk preventing Kodi from detecting it as a DVD Video (as opposed to DVD data) disk.
DVD Video disk detection is handled entirely within Kodi using direct block device access, and not performed by the system automounter. (Udisks at the moment)
Can you try switching on debug mode in Kodi, reboot, insert and attempt to play the troublesome disk then use the log uploader to upload the system journal and Kodi log ?
Btw I have also observed an issue on some DVD drives where the first disk inserted plays fine but after playing a DVD, switching to another DVD without rebooting causes spurious read errors which can among other things prevent proper DVD detection.
Although I have a general idea of what is causing this, investigation into the precise cause and solution is ongoing.
Edit: re-read your comment about DVDs appearing but the contents appearing to be that of the SD card - I have also come across this issue and am pretty sure it is also a result of read errors on a disk as I have only seen it on an older slightly flaky DVD drive - the same disk used in a new drive mounts correctly.
Just got done uploading my log file, using the the uploader, it went to the URL, with /ihozetoduf at the end. Hopefully I did it right…
As to the DVD drive, It is old, but has always been rock solid. The DVD did come from the library, but appears in decent shape, considering. I’ve also tried the other discs in the series, but they seem to have the same issue.
To give maybe a little more context : When I boot up, I plug in the USB drive without the disc in there. Once it seems like it’s figured out what’s going on, I insert the disc. I get no notice as to an external drive or a disc has been mounted, which I usually do with a good disc in the drive. I go to Videos/Files, and there’s a new HDD showing up, with the contents of the SD card.
Anyway, thanks for the quick response, I really appreciate it. Let me know if there’s anything else I can do to help. I’m new to Raspberry Pi/OSMC/Linux, but having a great time learning!
MOD EDIT: http://paste.osmc.io/ihozetoduf
Please provide the ENTIRE log URL so as to make assisting you as easy as possible for those who volunteer their time and knowledge to do so.
1 Like
You’ll find that behaviour even if you do get the popup message
Derek
Here is an extract from your log file:
Sep 24 02:28:11 osmc kernel: scsi 0:0:0:0: CD-ROM HP DVD Writer 1040r MH21 PQ: 0 ANSI: 0
Sep 24 02:28:11 osmc kernel: sr 0:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Sep 24 02:28:11 osmc kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Sep 24 02:28:11 osmc kernel: sr 0:0:0:0: Attached scsi CD-ROM sr0
Sep 24 02:28:11 osmc kernel: sr 0:0:0:0: Attached scsi generic sg0 type 5
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] Sense Key : 0x5 [current]
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] ASC=0x6f ASCQ=0x3
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00
Sep 24 02:28:43 osmc kernel: blk_update_request: I/O error, dev sr0, sector 4096
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] Sense Key : 0x5 [current]
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] ASC=0x6f ASCQ=0x3
Sep 24 02:28:43 osmc kernel: sr 0:0:0:0: [sr0] CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00
Sep 24 02:28:43 osmc kernel: blk_update_request: I/O error, dev sr0, sector 4096
Sep 24 02:28:43 osmc kernel: Buffer I/O error on dev sr0, logical block 512, async page read
Sep 24 02:28:43 osmc udisks-glue[317]: Device file /dev/sr0 inserted
Sep 24 02:28:43 osmc udisks-glue[317]: Device /dev/sr0 did not match any rules.
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] Sense Key : 0x5 [current]
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] ASC=0x6f ASCQ=0x3
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00
Sep 24 02:28:44 osmc kernel: blk_update_request: I/O error, dev sr0, sector 4096
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] Sense Key : 0x5 [current]
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] ASC=0x6f ASCQ=0x3
Sep 24 02:28:44 osmc kernel: sr 0:0:0:0: [sr0] CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00
Sep 24 02:28:44 osmc kernel: blk_update_request: I/O error, dev sr0, sector 4096
Sep 24 02:28:44 osmc kernel: Buffer I/O error on dev sr0, logical block 512, async page read
Sep 24 02:28:44 osmc udisks-glue[317]: Disk /dev/sr0: 6.7 GiB, 7220461568 bytes, 3525616 sectors
Sep 24 02:28:44 osmc udisks-glue[317]: Units: sectors of 1 * 2048 = 2048 bytes
Sep 24 02:28:44 osmc udisks-glue[317]: Sector size (logical/physical): 2048 bytes / 2048 bytes
Sep 24 02:28:44 osmc udisks-glue[317]: I/O size (minimum/optimal): 2048 bytes / 2048 bytes
“blk_update_request: I/O error, dev sr0, sector 4096” is a read error - for whatever reason the drive was unable to read that sector on the disk so gave up and returned an error to the operating system.
“udisks-glue[317]: Device /dev/sr0 did not match any rules.” - this is udisks-glue complaining that it was unable to identify the file system on the disk, thus it doesn’t know how to mount the disk. Almost certainly a result of the read error.
So unfortunately whatever the cause of this particular disk not reading is, it’s a hardware issue not a software issue. It could be as simple as a scratch on the disk, as not all drives are equally good at reading partially damaged disks, and the older the drive gets the more difficulty it will have with a non-pristine disk.
EG, you might find that same disk will play in a different drive, yet a different disk may play OK in this drive. That’s the kind of things that can happen with DVD drives. I have an older DVD drive in the office here and it is notorious for having intermittent problems reading a few particular disks but reads most other disks fine.
Ok, glad it’s not something I’m doing anyway, and good to know what this means in the future.
Thanks so much for your time!