Sorry for the response delay. My computer had died and the motherboard needed to be replaced (and the first replacement motherboard was also bad). I’m just now starting to catch up.
One cannot mount a blank DVD or CD. I’m thinking perhaps that pop-up item might be a more indirect clue than taking it at face value. For example, if the DVD drive wants to mount at a particular location, and something is already there, then this would be an issue regardless of whether it is a DVD (blank or otherwise) or anything else which could be mounted. However, there is still the question of whether it is just a bad message since a blank DVD cannot be mounted…I’m thinking that your mount rule needs to be examined. This part of the problem may not actually be a problem (so far as burning DVDs goes).
When you see this message, what do you see from:
lsblk -f
It’s useful to note that ISO9660 filesystems on a drive must have special schemes set up if they are to be grown on the DVD itself. Working with this demands that the original burn to DVD has special options with software capable of working with those options. There is less of a restriction on this to use growisofs
on a file intended to burn which is originally purely ISO9660 (possibly with Rock Ridge or Joliet extensions which are just for long name formats and are not actually part of the ISO9660 itself…Joliet would be involved with the Unicode option “utf
”, but can be ignored).
In the log_growisofs.txt
I see an I/O error. I don’t have enough experience with this to say if it is a hardware issue or a configuration issue. If you use an ordinary data DVD or CD, can you read from this drive? If so, then likely the I/O error is software (perhaps as simple as a configuration).
The log_verbose_lsusb.txt
seems normal and without error. This tends to indicate the hardware and basics of the driver are functioning correctly. I think this drive is capable of functioning correctly, at least so far as basics go.
I’ve not used Brasero, but the logs seem useful. Incidentally, almost every CD/DVD program is just a front end to combinations of other software. In the logs I see all is valid up to and including reading of an ISO file, “/home/nvidia/Desktop/waku.iso
”. Then there is the beginning of write. Not all burners and drivers support exactly the same set of commands (e.g., some might understand DVDs and CDs, others might understand only CDs), and although I am not certain, it may not be a problem that at the start of write there is one feature failure (not sure):
BraseroLibburn called brasero_job_get_action
BraseroLibburn unsupported operation
BraseroLibburn deactivating
(I wouldn’t look too hard at this “generic” and undetailed error, at least not yet, since it has no useful details of what operation is not supported)
It tries to “init
” the device, gets a return value of “1
”, and this might be good. I don’t know what is inside the code there to say if “1
” is success or not, but probably it is success (if it were “-1
”, then I’d say it is almost certainly an error). The program continues on, so it seems highly likely the burner is working up to this point.
Here is the point which really matters (the problem is a SCSI command, which is basically part of the SATA I/O):
BraseroLibburn SCSI command 2Ah yielded host problem: 0x7 SG_ERR_DID_ERROR (Internal error detected in the host adapter)
At this point it becomes even more important to find out if the drive can read a data type CD or DVD. Does the drive work for reading?
I don’t know enough about these dmesg
errors to say exactly what is going on, but it is possible that write itself fails for any number of reasons. Examples might be an ISO image too large, or software trying to use commands the driver does not understand, or actual hardware write issues:
[ 121.689529] capability: warning: `growisofs' uses 32-bit capabilities (legacy support in use)
[ 127.000033] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 146.967577] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 208.405848] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 208.440591] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 208.440605] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x1b 1b 01 00 00 01 00 00 00 00 00 00 00
[ 215.061633] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 215.096359] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 215.096400] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x1b 1b 01 00 00 01 00 00 00 00 00 00 00
[ 224.021288] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 229.397338] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 229.431774] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 229.431787] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x1b 1b 00 00 00 02 00 00 00 00 00 00 00
[ 344.312541] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
[ 352.326211] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
[ 388.534566] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
[ 452.382546] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
[ 478.226270] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 528.145436] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 533.777504] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 533.812135] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 533.812150] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x1b 1b 00 00 00 02 00 00 00 00 00 00 00
[ 618.513535] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 624.145518] usb 1-2.4.2: reset full-speed USB device number 4 using tegra-xusb
[ 624.180062] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 624.180078] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x1b 1b 00 00 00 02 00 00 00 00 00 00 00
Also, how well does this drive write on another Ubuntu system?