While in Spain recently, I tried playing some Sunday Times DVDs on a RPi1B using a small portable DVD reader/writer (unpowered) connected via a USB hub (powered).
Just one of them offered a problem which I’ve not found with any others - OSMC failed to recognise the DVD, and I got an item something like ‘3.95 GB’ in the files list.
Out of curiosity, I attempted the same DVD, but using a late issue of RaspBMC (after the update to Kodi) - which succeeded, and played the DVD.
On return, I tried the same DVD with a similar DVD reader/writer - same results.
I also tried it with RPi2B and OSMC - no recognition of DVD as holding video - and then Win7 - played video content after recognising the DVD.
What next? I cannot think what would be helpful here.
Derek
Further testing shows the same results using vero and the latest OSMC.
The 3.75GB entry in the Video file list
a) if explored looks like a linux system structure, which isn’t that on the DVD, having bin, sbin …
b) if 'play is attempted on the entry with contect menu, it locks mediacenter and I have to stop and re-start mediacenter via SSH to get things running again.
Derek
Please enable debug mode in Kodi, reboot, insert the disk, then upload full debug logs. If you only see the SD card file system it means OSMC was unable to mount the disk - this should show up in the debug logs.
Thanks - logs from vero are
http://paste.osmc.io/kusanoyovi
and from RPi2 are http://paste.osmc.io/ezaxedasos
Derek
Unfortunately it seems to be an IO read error on the disk that is causing it to fail to mount:
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] Sense Key : 0x5 [current]
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] ASC=0x6f ASCQ=0x3
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00 00 00
Nov 13 09:41:51 osmcUD kernel: blk_update_request: I/O error, dev sr0, sector 4096
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD kernel: sr 0:0:0:0: [sr0] unaligned transfer
Nov 13 09:41:51 osmcUD udisks-glue[310]: Device file /dev/sr0 inserted
Nov 13 09:41:51 osmcUD udisks-glue[310]: Device /dev/sr0 did not match any rules.
Nov 13 09:41:51 osmcUD udisks-glue[310]: brw-rw---- 1 root cdrom 11, 0 Nov 13 09:41 /dev/sr0
I can’t see how that can be anything but hardware - if the sector on the disk is unreadable, software can’t do anything about that.
Most likely either the disk itself or the drive, or maybe a combination of the two.
Thanks for the analysis. It confirms what I thought might be happening.
The waters were somewhat muddied by the facts that other combinations of OS, DVD and drive worked. I’ll be doing a further test, when I get around to it, using a different type of drive.
The fact that RaspBMC could cope, but OSMC couldn’t suggests something to be watched for in the future, I think.
Derek