I’ve been racking my brain for a little while as, no matter what I do, when I try to burn DVD images using any internal drive via K3B, Brasero, or Xfburn- it claims that it succeeds, but the disc is unreadable.
While attempting to burn the image using the internal blu-ray writer, no matter what slower speed I set the drive to (4x/8x), it shows something crazy like 36-52x
When I look at a healthy, readable disc that had the same image burned, the amount of “used” space on its underside is as expected and in-line with the amount of space used. When I look at one of the discs that supposedly were successful, but is unreadable, the amount of “used” space appears FAR smaller than what one would expect
Attempts to burn a data disc are just fine, both on the external and internal writer
The issue doesn’t seem to be isolated to a bad burner/bad hardware, as I bought another internal blu-ray writer from ASUS (the one I was using was an LG WH14NS40) and the same problem occurs
Both external drives I can set burn speed to manually, and they abide
I have only updated this tumbleweed install via ‘sudo zypper dup’. No manual yast update tomfoolery
Multiple attempts were made, with permissions as-is for K3B, and later with adjustments made (e.g. sudo chmod 4711 /usr/bin/cdrdao, sudo chmod 4711 /bin/cdrdao, sudo chmod 4711 /bin/cdrecord, sudo chmod 4711 /usr/bin/cdrecord) but the same problem occurred regardless of the permissions/settings
I’m not aware of any firmware issues with either burner and tried performing my own research, but, I’ve found nothing of consequence that speaks to this particular problem
I’m at a bit of a loss so I figured posting on here might help, even if it’s a rtfm getting chucked at me.
K3B informs the user since ages when the permissions are not correct. And the TO already mentioned that he checked the permissions. Without correct permissions, burning is not possible at all.
@commonoddity You mentioned that with the external drives, everything is fine but not with internal ones? This would exclude (partly) a software/driver issue. You also mentioned that another internal drive (new) does show the same errors. This could still be an hardware defect, as the internal drive is connected via another method to the motherboard as the external one: external drive via USB? and internal via SATA?. There can be an issue either with the SATA cable, the motherboard connector or the motherboard itself.
Apologies for the late reply. Work has been brutal. TW architecturally has shifted from Apparmor to SELinux, that is correct- but that’s on new installs. I’ve been rolling updates with ‘sudo zypper dup’ on this install for quite some time and I’m still using Apparmor.
@hui This is a brand spanking new rig. While it is possible that there could be a hardware defect, I suspect this isn’t the case. I have many devices in this machine, and the cable is brand new. I’ve tested other cables and the issue persists. Other sata devices are working as expected/without any issues. Swapping between ports, the issue continues to persist.
The other half of it is that it’s consistently reproducible behavior that results in the drive burning at speeds it shouldn’t be able to burn at in the first place, and the underside of the disc once burnt shows that it -does- burn, just that it takes up a smaller area of the surface for the same amount of bits. Normally when there are hardware failures there would be some kind of errors to match what is happening, and if it’s a faulty chipset/cable/etc it is rare that it would be a consistently reproducible issue (I’ve run into faulty hardware issues before on multiple occasions).
The most damning thing is that K3B reports a success each time AND ignores the manually set write speed. This is what makes all of this so awkward and I am concerned there is some kind of other issue happening here that isn’t being caught, but I am not sure how to pull deeper logs/debug payloads so I can open up a ticket with the K3b folks (which I somehow suspect will be met with a “actually go open a ticket with instead”).
I’ll try loading up Leap via Live ISO and see if the same behavior occurs there.
Some additional testing, as the idea came to my head that maybe the medium I bought was garbage/etc (again, doubt it).
Burned one of the images to a blu-ray disc (Memorex, 25gb single layer) and the burn finished successfully, but was also unreadable. The average write speed sat at about 4x (although during burn it was being estimated around 5.1~5.4x).
I performed a ‘sudo zypper dup’ and have observed that the permissions had reverted, when k3b updated, to what they were before (0755 across all the binaries)
While the disc cannot be read, while the disc is in the drive and K3b attempts to read it, it lists it as an “Appendable Data BD-R”, despite having the image burned using the “Burn image” method
ALL of the logs I have provided show the following:
cdrecord: Insufficient 'file read' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'file write' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'device' privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
cdrecord: Insufficient 'network' privileges. You will not be able to do remote SCSI.
This includes the logs where I adjusted the permissions for the binaries (e.g. cdrecord, etc) to 4711 like K3b suggests.
I’m at a loss. Not sure where to go with this aside for testing a LiveISO of Leap as has been suggested.
I ran ‘startx’ as root, because I couldn’t otherwise load a DE. This includes after having installed mesa and nouveau packages (I use a 4070 super, so I imagine this was the hurdle- or otherwise something else, which is not relevant here really). This should no longer pose a permissions issue.
Burn speeds were insanely high, similar to what I was observing on Tumbleweed
The disc ended up being completely unreadable
Am I really the only one this is happening to? Is there any additional logging I could do to help post a bug report? Appreciate any help, folks.
I appreciate you posting this, Svyatko, but I’ve read all of these already. The issue persists regardless of any fixes/etc that exist in these threads.
Edit: Actually… I should point out the bullet points I’ve outlined earlier do say that:
Write attempts appear successful, and the disc does finish writing
The write speeds appear to be wrong/off
The completed disc is unreadable
This ONLY applies to burning images, unless I use a USB writer (be it DVD or Blu-ray)
Writing regular data discs works just fine
I wouldn’t be making a post like this unless it was a serious issue that scouring the internet wouldn’t help fix.