I have bought an external DVD driver but, after plugging (or booting with the unit already plugged) I see the unit listed in the resources of the computer but I cannot access it: If I try to access the driver via VLC, I get the error VLC is unable to open the MRL 'cdda:///dev/sr0'. The content of fstab is: $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=341faa1b-4e49-49d7-85a4-e33acecb2212 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=24D6-7429 /boot/efi vfat umask=0077 0 1 /swapfile none swap sw 0 0 What is the right way to plug a DVD in Ubuntu 20.04? Is it a problem with the driver (I need to buy another brand more Linux-prone)? Or do I need to change the permission of the driver with some sudo commands? After I plug the DVD driver I get: $ ls -lt | less | grep sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 cdrom -> sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 cdrw -> sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 dvd -> sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 dvdrw -> sr0 brw-rw----+ 1 root cdrom 11, 0 May 27 21:15 sr0 Thank you

I have a old DVD/HDD recorder (Panasonic DMR-EH58) with RCA inputs & outputs etc. I want to recover all the recordings off its HDD. The HDD is a 2008 ATA/IDE 7200RPM Hitachi deskstar Model no:HDP725025GLAT80 250 GB has a DVD drive. It has been used at a conference center for many years recording camera RCA input. It is in good condition but it is outdated so I am trying to copy the recordings to a computer. I also would like to recover the deleted files if possible as they would not have been overwritten yet. I have borrowed a universal drive adapter and tried to mount it on both Windows 8.1 and ChaletOS Linux (Ubuntu based XFCE type distro). Windows showed it as a grayed F: drive and Linux did not auto mount it either. GParted shows it as "/dev/sdb: unrecognised disk label": Command line attempts follow: joel@joel-laptop:~$ mount dev/sdb mount: dev/sdb: No such file or directory joel@joel-laptop:~$ sudo mount /dev/sdb /mnt/usbdisk [sudo] password for joel: mount: special device /dev/sdb does not exist joel@joel-laptop:~$ mount dev/sdb mount: dev/sdb: No such file or directory joel@joel-laptop:~$ ls -alh /dev/disk/by-path/ total 0 drwxr-xr-x 2 root root 160 Apr 30 22:05 . drwxr-xr-x 6 root root 120 Apr 30 18:41 .. lrwxrwxrwx 1 root root 9 Apr 30 21:31 pci-0000:00:1f.2-ata-1 -> ../../sda lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part6 -> ../../sda6 - Root directory is dev/sda5 - Swap is dev/sda6 - Windows is dev/sda1 - Spare data partition is dev/sda2 Looks like an unsupported file system error...

[This is on Debian 12] To fully access my DVD drive, I need to also know its SCSI generic path (/dev/sgX) in addition to its expected CDROM-/dev/srX path. The specific device is important, though, and I need to access the device even if the system re-shuffles the /dev/srXs and /dev/sgXs.

sudo lsscsi -g
[3:0:0:0]    cd/dvd  HL-DT-ST BD-RE  WH16NS60  1.05  /dev/sr0   /dev/sg3

sudo blkid /dev/sr0
/dev/sr0: UUID="035bbeef20202020" LABEL="WALDEINSAMKEIT" BLOCK_SIZE="2048" TYPE="udf"

sudo blkid /dev/sg3

/dev/sr0 is set with a /dev/disk/by-uuid/035bbeef20202020 but if /dev/sg3 doesn't actually have a UUID (I'm guessing it's not seen as a block device), I could go for the full controller/system path, per this Linus rant I found https://yarchive.net/comp/linux/scsi_ids.html

sudo udevadm info -q path -n /dev/sr0
/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/block/sr0

sudo udevadm info -q path -n /dev/sg3
/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/scsi_generic/sg3

This does not seem like a solution either, as the path includes sr0 or sg3 which will change order. /sys/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0 seems to be a directory the device is referencing but I can't find anything more than the folders block/sr0 and scsi_generic/sg3 which again revert to the original problem of sr0 and sg3 changing if the system cables are reordered or something. How can I get a consistent identifier for /dev/sg3? I have searched hard, but I must be missing a command.

I've been a Fedora user "since forever" (Red Hat v1.1) but, frustrated by some issues I can't ignore, I am interested in trying both Debian and Ubuntu. Step zero was to download the latest releases. I picked Debian 12.7.0 as my first to try. However, in the past I was using a Windows box to burn DVDs for no good reason but familiarity. ... And thus I'd never had to actually burn the DVD on Linux before. Following the directions from various sources here, I started with: # wodim -v dev='/dev/sg2' -eject debian-12.7.0-amd64-DVD-1.iso Whir-whir-whir went the DVD with lots of progress reported but a cup of coffee or so later I got some errors pertaining to "fixating" the disk, namely: Fixating... Errno: 5 (Input/output error), flush cache scsi sendcmd: no error CDB: 35 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 40 A0 03 21 04 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x21 Qual 0x04 (logical block address out of range) [No matching qualifier] Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 137.712s timeout 120s Trouble flushing the cache wodim: Cannot fixate disk. Fixating time: 137.712s Errno: 5 (Input/output error), prevent/allow medium removal scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 40s Errno: 5 (Input/output error), start/stop unit scsi sendcmd: fatal error CDB: 1B 00 00 00 02 00 cmd finished after 0.000s timeout 40s wodim: Cannot eject media. wodim: fifo had 62911 puts and 62911 gets. wodim: fifo was 0 times empty and 7253 times full, min fill was 34%. Using man I found -fix, and tried it, but it didn't work either, as can be seen here - a VERY different kind of error: # wodim -v dev='/dev/sg2' -fix TOC Type: 1 = CD-ROM scsidev: '/dev/sg2' devname: '/dev/sg2' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.36 Wodim version: 1.1.11 SCSI buffer size: 64512 wodim: Cannot do inquiry for CD/DVD-Recorder. Errno: 5 (Input/output error), test unit ready scsi sendcmd: fatal error CDB: 00 00 00 00 00 00 cmd finished after 0.000s timeout 40s So, I figured I'd try dd since several question/answer entries here strongly implied dd can make a bootable DVD, just watch out for sync issues, so, this: # dd if=debian-12.7.0-amd64-DVD-1.iso of=/dev/sg2 bs=4M && sync But... It doesn't do anything! And from that I did research and found this entry which says dd used to be able to do this and for some unknown but likely (in my view) silly reason, the ability was removed?! However, that is disputed. Hmmm... This system usually makes the cd/dvd drive available on /dev/cdrom and to read I do something like # mount /dev/cdrom /mounts/cd0 and then I have the contents available on /mounts/cd0. But trying /dev/cdrom didn't do anything either: # dd if=debian-12.7.0-amd64-DVD-1.iso of=/dev/cdrom bs=4M && sync No Joy. I've read several other entries on stack exchange sites, such as this one or this one , among others, but didn't find a solution... MAYBE I just had a media error and need to retry the original command? I hate to waste disks but... On suggestion, I tried: # wodim -v dev=/dev/sr0 -eject -sao debian-12.7.0-amd64-DVD-1.iso TOC Type: 1 = CD-ROM scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 SCSI buffer size: 64512 wodim: Cannot do inquiry for CD/DVD-Recorder. Errno: 5 (Input/output error), test unit ready scsi sendcmd: fatal error CDB: 00 00 00 00 00 00 cmd finished after 0.000s timeout 200s Hmmm... There is a /dev/sr0 entry... **I WENT TO A DIFFERENT MACHINE...** Same operating system, same brand drive, etc, and I ran the command from the answer below and it wrote a disk. **IMPORTANTLY** along the way I noted the software - wodim - said: Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. Upon reading that I instantly deduced the drives MAY be the same brand (ASUS) but not the same type, or maybe there's a motherboard difference? I don't know. Since I had copied and pasted the entire output from the original "unfixated" run, I can say it wasn't in there. However, it was in this new SUCCESSFUL run - that boots propertly! - so ... Apparently what I needed to have found was maybe this article. Aren't computers fun?

I am looking for a copy of the RPM source code DVD for CentOS 3.9. The file name is "CentOS-3.9-srcDVD.iso". There are lots of mirrors for the CDs but I have been unable to locate the DVD.

I can install a clonezilla-created Linux image from a USB thumb drive but I'm interested in being able to use Clonezilla Live to install a clonezilla-create image that I have burned onto a DVD. I can't find any references saying it is not possible to install a CloneZilla DVD image (of Linux). Does anyone know if this is possible? I have searched through StackExchange and other community sites, Youtube videos for an answer but what I'm really looking for a definite "no, you cannot install a Clonezilla-create image that is on a DVD". I have tried installing with CloneZilla using the device-image and device-device options.

I'm trying to rip a movie dvd to an ISO image. When I try to copy it, at the beginning it seems like everything is working fine. But when it reaches around 650MB (I guess that's the start of the main movie which is copy protected), it becomes unbelievably slow or the program isn't reacting anymore. I've tried it with dd, ddrescue, mkisofs and K3b. I'm using a LG GP08NU6W as an external dvd drive and I'm running Arch Linux.

I like to watch DVDs on my computer, I am using KDE Plasma 6.1.3. There is no option to play the DVD through VLC Media Player or something of the sorts. I didnt find a way to add this option through regular means, like installing a package, I already got kio-fuse, kio-extras, dolphin-plugins etc. https://develop.kde.org/docs/apps/dolphin/service-menus/ I found this through my searches, adding my own service menu seemed like a fair option. Though I could not find the Mime Type for DVDs; on this list (https://www.digipres.org/formats/mime-types/) I found video/dvd but it doesnt do the trick, the menu doesnt show. I also tried applying it to directories, thinking I might get recognized as directory, but it didnt work. Any idea would I could do? Thanks

I have a udev rule that runs a script when a bluray disc is loaded. I am aware of the time limit on udev scripts and so have the script run a child script with the "at now" command. The child script then does a bunch of ripping and post processing. The strange behavior is that any attempt to read the disc label returns an empty string when run from udev. But, if I run the same script from the command line, it has no problem spinning up the disc and reading the label. in fact, I even have a test script that I tried that only loops and tries to read the label and echo to a text file. It sits and loops outputting an empty string. Whats also weird is that any media check in the udev script says the disc is loaded and ready to go. udev rule:

UBSYSTEM=="block", ENV{ID_CDROM}=="1", ENV{ID_TYPE}=="cd", ACTION=="change", RUN+="/usr/local/bin/autodisk '%E(DEVNAME)'"

udev script autodisk:

#!/bin/bash

{
  if [ "$ID_CDROM_MEDIA_BD" -eq "1" ]; then
    echo /home/nathan/rom_ready $DEVNAME | at now
    exit 1
  fi
}

rom_ready script

#!/bin/bash
counter=0

device=$1

echo $device >  /home/nathan/.var/log/diskrip/.diskripper.log
while true; do

  file -s $device >> /home/nathan/.var/log/diskrip/.diskripper.log
  sleep 1
  echo "loop" >>  /home/nathan/.var/log/diskrip/.diskripper.log
  discname=$(blkid -o value -s LABEL $device)
  echo $discname >>  /home/nathan/.var/log/diskrip/.diskripper.log

  counter=$((counter + 1))
  if [ $counter -ge 20 ]; then break; fi
  
done

the line **file -s $device >> ~/log.text** writes "/dev/sr0: data" to the log file, but that shouldn't happen if the disc isn't ready to read. While rom_ready is looping and failing to output the disc label, if I open a terminal and read the label, i can get the label from the command line, but the rom_ready keeps getting blank data. Also if I run the rom_ready from the terminal instead of from udev, it executes as expected. It's like when I put the disc in and udev is the only thing that initiates an action, the system thinks the disc has been read from, but nothing has actually been read, so all the fields are empty. Whats also weird is that if I include a call to makemkvcon in the udev script, it has no problem loading and ripping the disc as well as naming the file. It just sucks, because I can't automate naming of the directories ahead of time. This doesn't seem to be a problem with regular dvd discs. It reads the label, creates a directory with the name of the movie title, and then rips the disk into that directory.

I had a burnt disc from the 2000s, I tried backing it up, but it had issues. So went out and purchased another copy, a box set in fact. It was released 20 years ago. When I used dvdbackup some of the .VOB files had issues and wouldn't play. I can't use ddrescue because it doesn't understand what is dodgy data and CSS confusion. The dvds seem to play okay with VLC. I can't find away to get around this, I know VLC has a convert feature, but it doesn't work. Surely there is a way to use ddrescue with CSS or pipe out of something which can can open CSS dvds into something which can do error checking, like rsync? This situation that 'you can have a CSS playing programme or a data recovery/backup programme but not both' seems crazy.

When I was using DOS and Windows I've seen quite a selection of tools to check optical disks for readability and benchmark an optical drive itself. Most of them were even visualising the results in form of a pretty chart. Are there any such for GNU/Linux OSes? I'd prefer to have a full-featured visual GUI tool, but for the particular case I've got now, I just need to check if my CD drive can read every byte of a particular heavily-scratched CD-RW disk.

Title says it all. But I plugged in an external DVD drive into my Raspberry Pi running Raspbian. It says its Linux compatible However when I actually plug it into the device. Everything goes wrong in incomprehensible ways. SSH says "kex_exchange_identification: read: Connection reset by peer. Connection reset by 192.168.50.2 port 22" Or when I do "ls" it says "-bash: /usr/bin/ls: Input/output error" Or when I do "sudo" it says "-bash: sudo: command not found" Nothing really works with it plugged in. However when I reboot the RaspberryPi all is well... up until I plug in the DVD drive. What is going on? How can I troubleshoot or fix it given so many commands are down? What might've happened? **Investigation updates** $PATH Before /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games After - Same BUT this is odd to me. This is a newly configured version of the OS. Why is it pointing to games and all of these other things? Odd? DVD drive "hyripe external cd/dvd drive" Another thing that seems potentially relevant. Device is booting and using an external SSD plugged in via a USB port as memory. dmesg output [ 19.657310] Initializing XFRM netlink socket [ 87.772696] usb 2-2: USB disconnect, device number 2 [ 87.775097] device offline error, dev sda, sector 135274584 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775132] Buffer I/O error on dev sda2, logical block 16777227, lost async page write [ 87.775164] device offline error, dev sda, sector 177217664 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775179] Buffer I/O error on dev sda2, logical block 22020112, lost async page write [ 87.775195] device offline error, dev sda, sector 177221200 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775208] Buffer I/O error on dev sda2, logical block 22020554, lost async page write [ 87.775223] device offline error, dev sda, sector 177221456 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775236] Buffer I/O error on dev sda2, logical block 22020586, lost async page write [ 87.775250] device offline error, dev sda, sector 177225992 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775262] Buffer I/O error on dev sda2, logical block 22021153, lost async page write [ 87.775276] device offline error, dev sda, sector 177309888 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775288] Buffer I/O error on dev sda2, logical block 22031640, lost async page write [ 87.775302] device offline error, dev sda, sector 1056768 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775314] Buffer I/O error on dev sda2, logical block 0, lost async page write [ 87.775328] device offline error, dev sda, sector 1056840 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775340] Buffer I/O error on dev sda2, logical block 9, lost async page write [ 87.775354] device offline error, dev sda, sector 1056856 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2 [ 87.775366] Buffer I/O error on dev sda2, logical block 11, lost async page write [ 87.776903] device offline error, dev sda, sector 123307176 op 0x1:(WRITE) flags 0x9800 phys_seg 3 prio class 2 [ 87.776946] Aborting journal on device sda2-8. [ 87.777003] Buffer I/O error on dev sda2, logical block 15237120, lost sync page write [ 87.777038] JBD2: I/O error when updating journal superblock for sda2-8. [ 87.778325] EXT4-fs error (device sda2): ext4_journal_check_start:84: comm systemd-journal: Detected aborted journal [ 87.778377] EXT4-fs (sda2): previous I/O error to superblock detected [ 87.780733] EXT4-fs (sda2): I/O error while writing superblock [ 87.780759] EXT4-fs (sda2): Remounting filesystem read-only [ 87.932676] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 87.946770] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 87.960681] EXT4-fs warning (device sda2): dx_probe:822: inode #11752: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 87.960788] EXT4-fs warning (device sda2): dx_probe:822: inode #11752: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 87.996669] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block [ 87.996739] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block [ 87.997338] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block [ 88.036652] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK [ 88.036752] scsi 0:0:0:0: rejecting I/O to dead device [ 88.036853] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block [ 88.036936] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block [ 88.036961] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block [ 88.036980] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block [ 89.272857] usb usb2-port1: over-current change #1 [ 89.347052] usb 1-1-port1: over-current change #1 [ 89.488839] usb usb2-port2: over-current change #1 [ 89.567467] usb 1-1-port2: over-current change #1 [ 89.704835] usb usb2-port3: over-current change #1 [ 89.785661] usb 1-1-port3: over-current change #1 [ 89.920848] usb usb2-port4: over-current change #1 [ 90.005647] usb 1-1-port4: over-current change #1 [ 91.216972] usb usb2-port1: over-current change #2 [ 91.432929] usb usb2-port2: over-current change #2 [ 91.648944] usb usb2-port3: over-current change #2 [ 91.864930] usb usb2-port4: over-current change #2 [ 92.353317] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd [ 92.381049] usb 2-2: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01 [ 92.381060] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 92.381064] usb 2-2: Product: RTL9210 [ 92.381068] usb 2-2: Manufacturer: Realtek [ 92.381071] usb 2-2: SerialNumber: 012345678904 [ 92.386529] usb 2-2: Enable of device-initiated U1 failed. [ 92.387180] usb 2-2: Enable of device-initiated U2 failed. [ 92.396633] usb 2-2: Enable of device-initiated U1 failed. [ 92.397227] usb 2-2: Enable of device-initiated U2 failed. [ 92.400265] scsi host1: uas [ 92.403800] scsi 1:0:0:0: Direct-Access Realtek RTL9210 NVME 1.00 PQ: 0 ANSI: 6 [ 92.434380] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 92.439587] sd 1:0:0:0: [sdb] 250069680 512-byte logical blocks: (128 GB/119 GiB) [ 92.441039] sd 1:0:0:0: [sdb] Write Protect is off [ 92.441052] sd 1:0:0:0: [sdb] Mode Sense: 37 00 00 08 [ 92.444215] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 92.445600] sd 1:0:0:0: [sdb] Preferred minimum I/O size 512 bytes [ 92.445610] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes [ 92.456256] sdb: sdb1 sdb2 [ 92.456687] sd 1:0:0:0: [sdb] Attached SCSI disk [ 93.009059] EXT4-fs warning: 152 callbacks suppressed [ 93.009080] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gmain: error -5 reading directory block [ 93.946572] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 93.946708] EXT4-fs warning (device sda2): dx_probe:822: inode #11752: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 93.946748] EXT4-fs warning (device sda2): dx_probe:822: inode #11752: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 93.996856] usb 1-1.4: new high-speed USB device number 3 using xhci_hcd [ 94.097995] usb 1-1.4: New USB device found, idVendor=13fd, idProduct=1040, bcdDevice= 1.06 [ 94.098020] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 94.098032] usb 1-1.4: Product: UJDA755 DVD/CDRW [ 94.098042] usb 1-1.4: Manufacturer: Initio [ 94.098050] usb 1-1.4: SerialNumber: 0000000000000000W [ 94.102518] usb-storage 1-1.4:1.0: USB Mass Storage device detected [ 94.104036] scsi host2: usb-storage 1-1.4:1.0 [ 94.947221] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 94.947358] EXT4-fs warning (device sda2): dx_probe:822: inode #11752: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 94.947400] EXT4-fs warning (device sda2): dx_probe:822: inode #11752: lblock 0: comm wf-panel-pi: error -5 reading directory block [ 95.009150] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm gmain: error -5 reading directory block [ 95.197299] scsi 2:0:0:0: CD-ROM MATSHITA UJDA755 DVD/CDRW 1.00 PQ: 0 ANSI: 0 [ 95.198097] scsi 2:0:0:0: Attached scsi generic sg1 type 5 [ 95.198889] EXT4-fs warning (device sda2): htree_dirblock_to_tree:1082: inode #4195975: lblock 0: comm systemd-udevd: error -5 reading directory block [ 95.199149] EXT4-fs warning (device sda2): htree_dirblock_to_tree:1082: inode #11102: lblock 0: comm systemd-udevd: error -5 reading directory block [ 96.695423] usb usb2-port1: over-current change #3 [ 96.909249] usb usb2-port2: over-current change #3 [ 97.126132] usb 2-2: USB disconnect, device number 3 [ 97.156984] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 97.384973] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK [ 97.685449] usb 2-2: new SuperSpeed USB device number 4 using xhci_hcd [ 97.713108] usb 2-2: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01 [ 97.713134] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 97.713147] usb 2-2: Product: RTL9210 [ 97.713157] usb 2-2: Manufacturer: Realtek [ 97.713166] usb 2-2: SerialNumber: 012345678904 [ 97.716723] usb 2-2: Enable of device-initiated U1 failed. [ 97.717440] usb 2-2: Enable of device-initiated U2 failed. [ 98.256005] usb 2-2: Enable of device-initiated U1 failed. [ 98.256581] usb 2-2: Enable of device-initiated U2 failed. [ 98.262045] EXT4-fs warning: 73 callbacks suppressed [ 98.262062] EXT4-fs warning (device sda2): htree_dirblock_to_tree:1082: inode #4195975: lblock 0: comm systemd-udevd: error -5 reading directory block [ 98.262332] EXT4-fs warning (device sda2): htree_dirblock_to_tree:1082: inode #11102: lblock 0: comm systemd-udevd: error -5 reading directory block [ 98.262441] EXT4-fs warning (device sda2): dx_probe:822: inode #4194305: lblock 0: comm systemd-udevd: error -5 reading directory block [ 98.262888] scsi host1: uas

This question is inspired by [_this answer on SuperUser_](https://superuser.com/a/1828714/11116) by Proger_Cbsk. The RID is the Recorder IDentification. It uniquely identifies the drive that wrote the CD/DVD. What software if anything can read the RID written by a CD-RW, or DVD-RW? According to the linked answer, > Oddly, the INCITS standard has a command to read the RID in a DVDR, but not for a CDR ! I would like to read the RID of a CD and DVD, * DVDR: I would like to know how to issue the standardized command to read the RID * CDR: I would like to do the same for CDRs. If this is drive-vendor specific, that is fine. I will purchase that drive.

I want to be able to just insert a DVD movie and be sure I'll have full access to all its features. - Can this be done without VLC in Linux? **VLC** is maybe the best video player out-there and as far as I can tell the best DVD player for Linux, but it may happen that it fails from time to time (I sometimes lose video, audio, or synchronization between those) - so that it may be useful to know if there is a way to have full access to all features of a DVD movie with a different application. Example (tested in Manjaro and Mint KDE): - once the DVD disk inside the computer drive, VLC can show the menu like so: and each menu entry may lead to other sub-menu entries: This example is in **VLC**. Can other player do as well as this? Or better: I remember that in Windows I used players that at any moment during playback were able to show the first level of the menus by selecting a specific option. I cannot seem to find that in VLC neither - clicking the 'DVD Menus' added to the interface, it will just restart from the beginning. What happens when trying the same DVD with a different player? Well, **many video players don't even have an "Open DVD" option**. **SMPlayer** has that option, shows the first level of the menus but does nothing then (it seems to see the menus just as a video stream or something). **Gnome MPlayer** also has it, but cannot find the dvd as it looks for it by default in /dev/dvd and it doesn't have a way to change that. When starting the DVD in this player anyway, it treats menus as video stream. Even without an "Open DVD" option I was able to test with other players. Many do not see the menus as such but play them as a video stream, and so the menus are not usable. (I tested **mpv, Gnome MPV, bomi, Gnome MPlayer, Baka Mplayer, KPlayer, KMPlayer, Dragon Player**) **Totem** player was able to display the first level of menus just like VLC but clicking any of them was just starting the first entry.

I have a WH16NS40 DVD drive that I want to use on my Debian 12 virtual machine. The drive is inside a Vantec NexStar DX2 USB 3.0 external enclosure, which connects to the DVD drive via a standard SATA cable. I had it working and was able to read and write ISOs to discs from my Debian 12 workstation, but when I plugged it into my hypervisor (Proxmox) and passed the USB device through to the VM, it does not show up as sr0 in lsblk and is not in /dev for sr0. The USB part does show up though, as shown below. lsusb

Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s

lshw

*-usb
                      description: Mass storage device
                      product: USB to ATA/ATAPI Bridge
                      vendor: JMicron
                      physical id: 1
                      bus info: usb@2:1
                      version: 4.15
                      serial: 0123456789ABCDEF
                      capabilities: usb-2.10 scsi
                      configuration: driver=usb-storage maxpower=30mA speed=480Mbit/s

dmesg output:

[    1.418561] usb 2-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= 4.15
[    1.418564] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.418565] usb 2-1: Product: USB to ATA/ATAPI Bridge
[    1.418566] usb 2-1: Manufacturer: JMicron
[    1.418566] usb 2-1: SerialNumber: 0123456789ABCDEF
[    1.422595] usb-storage 2-1:1.0: USB Mass Storage device detected
[    1.422697] usb-storage 2-1:1.0: Quirks match for vid 152d pid 0578: 1000000
[    1.422734] scsi host3: usb-storage 2-1:1.0
[    1.422797] usbcore: registered new interface driver usb-storage
[    1.423715] usbcore: registered new interface driver uas

Even before I put a disc in the drive, it was present in my workstation as /dev/sr0. But not here. My workstation is running KDE desktop, are there packages that come with KDE that make detecting these USB enclosures more accurate? How can I force the OS to consider this USB device a CDROM device and assign it as sr0? Thanks in advance!

I downloaded some os iso to be burned on a DVD and let's say that my connection was not safe enough and/or my burner application had a malware, tl;dr I downloaded and burned the iso to DVD in a NOT safe environment. Following this guide https://unix.stackexchange.com/questions/373123/how-to-checksum-a-cd-dvd-to-verify-integrity-of-my-debian-installation I checked the DVD burned on a different safe machine and the CRC check is identical to the one provided from the distribution website. Is the DVD burned considered to be safe ? Can other hidden sectors or metadata not being part in the crc process be used to dispatch malware or can I be 100% sure that the DVD content is safe for setup a new machine ?

I recently discovered some old double-sided mini dvd-rw disks (2.8GB) which were used for recording video with a Sony DCR-DVD201E handycam. Both sides already had content but they were unfinalized so I could not mount them on my Ubuntu 22.04 box. I proceeded with finalizing them through the camera. One side worked fine. But the other one didn't: The disk now appears as almost full of data (~1.3GB out of 1.4GB) but something seems to be wrong with the filesystem, which appears completely empty of files or folders both on my computer AND the camera. Note that the disk does *not* contain any bad blocks and it does not cause any read errors. So we're not talking about medium failures or hardware-related issue. Judging from other disks created and finalized by the same camera (including the other side of this disk), the filesystem should contain something like this:

VIDEO_TS/
VIDEO_TS/
VIDEO_TS/VIDEO_TS.BUP
VIDEO_TS/VIDEO_TS.IFO
VIDEO_TS/VIDEO_TS.VOB
VIDEO_TS/VTS_01_0.BUP
VIDEO_TS/VTS_01_0.IFO
VIDEO_TS/VTS_01_1.VOB
:
:

The output of dvd+rw-mediainfo is the following:

$ dvd+rw-mediainfo /dev/sr0
INQUIRY:                [HL-DT-ST][DVDRAM GP57EB40 ][RF01]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         13h, DVD-RW Restricted Overwrite
 Media ID:              TDK502sakuM3
 Current Write Speed:   2.0x1385=2770KB/s
 Write Speed #0:        2.0x1385=2770KB/s
 Speed Descriptor#0:    00/716191 R@6.0x1385=8310KB/s W@2.0x1385=2770KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    716800*2KB=1468006400
READ DVD STRUCTURE[#0h]:
 Media Book Type:       32h, DVD-RW book [revision 2]
 Last border-out at:    2045*2KB=4188160
READ DISC INFORMATION:
 Disc status:           complete
 Number of Sessions:    1
 State of Last Session: complete
 Number of Tracks:      1
READ FORMAT CAPACITIES:
 formatted:		690544*2048=1414234112
 00h(800):		716192*2048=1466761216
 10h(10):		716192*2048=1466761216
 13h(10):		25648*2048=52527104
 15h(10):		716192*2048=1466761216
READ TRACK INFORMATION[#1]:
 Track State:           complete incremental
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Fixed Packet Size:     16*2KB
 Track Size:            690544*2KB
FABRICATED TOC:
 Track#1  :             14@0
 Track#AA :             14@690544
 Multi-session Info:    #1@0
READ CAPACITY:          690544*2048=1414234112

K3b reports the following: However if you mount the disk, ls, du, etc. show 0 data/files/folders. I ripped the contents using dd:

dd bs=2048 skip=0 count=690544 if=/dev/sr0 of=./out.iso

The output file is recognized via file command as:

out.iso: UDF filesystem data (version 1.5) '2009_06_27_05H54M_PM'

Then I tried udfinfo:

filename=out.iso
label=2009_06_27_05H54M_PM
uuid=00a8784b20202020
lvid=2009_06_27_05H54M_PM
vid=SONY_MOBILE
vsid=        SONY_MOBILE_VOLUME_SET
fsid=SONY_MOBILE_FILE_SET
fullvsid=00A8784B        SONY_MOBILE_VOLUME_SET
owner=
organization=
contact=
appid=
impid=*SONY_MOBILE
winserialnum=0x709b0f01
blocksize=2048
blocks=690544
usedblocks=690268
freeblocks=0
behindblocks=0
numfiles=0
numdirs=1
udfrev=1.02
udfwriterev=1.02
integrity=closed
accesstype=readonly
softwriteprotect=yes
hardwriteprotect=yes
start=16, blocks=5, type=VRS
start=32, blocks=16, type=MVDS
start=48, blocks=16, type=RVDS
start=64, blocks=1, type=LVID
start=256, blocks=1, type=ANCHOR
start=260, blocks=690268, type=PSPACE
start=690543, blocks=1, type=ANCHOR

I mounted it and tried photorec but it produces multiple small mpeg files, many of which are unplayable and which are probably part of a bigger VOB file that doesn't show up. Since I know that the disc contains VOB files, I tried ffmpeg just in case it could somehow skip the "garbage" and transcode it into something useful, however if failed:

out.iso: Invalid data found when processing input

Handbrake also failed to recognize any data when I tried to use the file as a source, although it does work properly with the directory structure of other disks possessing the VIDEO_TS folder I showed earlier. Then I tried opening the out.iso file with VLC. That one actually DID work, i.e. it started streaming video content, however with some issues: - You cannot navigate in the video as timestamps/index is broken - Converting it to mp4 creates a video with stuttering, broken timestamps, etc.. - It is obvious that it doesn't contain the whole video. Most probably the camera broke the content into multiple VOB files, so at some point it stops reading I tried to recode one of the mp4 files that I produced using VLC, even with shorter length than expected, in order to be able to see proper length (in seconds) and navigate using a player, but ffmpeg produced the following errors in the output without fixing them in the final output file:

ffmpeg -fflags +igndts -i vlc-converted.mp4 -vcodec libx264 -acodec aac fixed.mp4
:
[aac @ 0x555e72b0a6c0] Queue input is backward in time
[mp4 @ 0x555e72afe980] Non-monotonous DTS in output stream 0:1; previous: 143927607, current: 143927095; changing to 143927608. This may result in incorrect timestamps in the output file.
[aac @ 0x555e72b0a6c0] Queue input is backward in time
[mp4 @ 0x555e72afe980] Non-monotonous DTS in output stream 0:1; previous: 143933751, current: 143933239; changing to 143933752. This may result in incorrect timestamps in the output file.
:

So the questions are these: - Are you aware of any (linux) tool that can discover files in a UDF filesystem which contains the data but obviously doesn't have proper filesystem entries for them? - If no UDF tool exists, are you aware of any tool that can specifically recognize VOB files from a raw filesystem and "restore" them as ddrescue would do? - If none of the above is possible, do you know any ffmpeg trick or alternative tool that could at least fix the timestamp indexes of the portion of the video stream that VLC managed to convert?

I am starting to make backups of my movie DVDs at home. I am using DD to make ISO images of my DVD as follows: dd if=/dev/dvd of=~/dvd/abc.iso However, even though the content of the DVD is only, for example, 5.4GB (I check this with du -sh), the resulting image is still 7GB, so it seems as if it is making an ISO image of the entire disc, even the unused portion. Is there a way to make an ISO backup of the DVD using dd that is only as large as the used portion of data on the disc?

I just installed Debian Live and movie or video DVDs do not play. Totem gives me this error: > Could not read from resource. Opening the disk in VLC has no response. How can I play DVDs?

I have a (children's) DVD that consists of several short films. Here is a screenshot of the DVD's own menu where you can select the short film you want to see: You can either watch from that menu, in which case you return to that menu after the film has finished, or you can watch all in a row (using another button, not seen in the screenshot). Both are not desirable because we want to mimick the old TV show this DVD is a compilation of. In that show, there was always the intro (number 1), then one episode (any of number 2 to 10), then the outro (number 11). **So I basically want to make a playlist saying: play number 1, then play (e.g.) number 5, then play number 11. Is that possible without transforming the data of the DVD into something else? If yes, what do I need to do? I am okay with installing software and using the terminal.** --- Here is what I tried so far: I opened the DVD with VLC media player and expected to find a list of tracks/movies just like for music CDs, but there weren't any (ok, one): When I open the DVD in a file explorer, it has the usual structure of an AUDIO_TS and a VIDEO_TS folder.