New to Linux Blu-Ray Burning

[m8sw8]

So, I've been getting into physical media as of late and have been trying to get into Blu-Rays (particularly BDXLs), as I'd like to back up any movies or GOG games that I have. On Linux, I understand that Brasero is usually pretty shit with BDXLs, and I've been using K3B. The drive that I'm using is a 60$ HP-BU2ON internal laptop writer, and 50GB Blu-Ray discs. As of now I'm waiting on an external enclosure for it, and my failures could very well just come from the fact that I've been running the burning software off of a live session Linux mint installation on an oooolllld laptop (The HDD is fried on it.) I just had to use it because it's the only thing that had the port necessary to use the internal writer. I just wanted to make sure I had a good lineup of software+writer first in order to not keep wasting discs lol.

[october262]

Burning Blu-ray discs on Linux is fully supported using reliable open-source tools like K3b or command-line utilities like xorriso. A standard 25GB or dual-layer 50GB data disc can be prepared by installing the required backend burning packages and setting a slow write speed to ensure data integrity.


Recommended Software -
K3b (KDE Burn Baby): The most feature-rich graphical interface for optical media burning on Linux. It handles UDF file systems required for large Blu-ray files smoothly.

Xfburn: A lightweight alternative that works well for basic data track burning if K3b's dependency tree is too heavy for your desktop environment

xorriso / cdrtools: Robust command-line backends that handle low-level UDF/ISO formatting for Blu-ray media.

[october262]

for BDXL - Burning BDXL (high-capacity triple/quad-layer 100GB or 128GB Blu-ray) discs on Linux requires a BDXL-ready hardware drive (like external models from Buffalo or LG) paired with reliable low-level command-line backends such as growisofs, as graphical user interfaces can sometimes lack seamless multi-layer tracking

Hardware & Software Requirements - BDXL Drive: Use a verified USB 3.0/3.2 writer (e.g., B&H Photo-Video-Audio listing for the Buffalo MediaStation 16x) connected via a powered USB port or active hub to prevent power drops during long burns.

Software Tools: Most users on Reddit agree that k3b (with advanced GUI options enabled to force the growisofs backend) or direct CLI usage of growisofs provides the most stable results for high-capacity media

Recommended Burning Steps via K3b

Install k3b and dvd+rw-tools via your distribution's package manager

Open K3b settings, go to the Advanced tab, and check "Show advanced GUI elements".

Create a new Data Project, and drag your files/folders into the workspace. Ensure the total size stays under 100GB (triple-layer) or 128GB (quad-layer)

[m8sw8]

Okay, so funnily enough, I got the recommended drive, I used K3b, did the advanced GUI options, and was trying to add 45.5 GB of data to a 50GB Blu-ray and it said that growisofs crashed. Which leads me to believe that either the discs are faulty, or there is something wrong with the backend stuff.

[october262]

Okay, so funnily enough, I got the recommended drive, I used K3b, did the advanced GUI options, and was trying to add 45.5 GB of data to a 50GB Blu-ray and it said that growisofs crashed. Which leads me to believe that either the discs are faulty, or there is something wrong with the backend stuff.

Burning Blu-ray discs with growisofs (often via K3b) typically fails due to permission issues, file size limits, defect management overhead, or hardware incompatibility.

1. Fix Permissions If K3b reports mkisofs crashed before burning, it is often a permissions error for the backend tools. Set the SUID bit on the necessary binaries:

sudo chmod 4711 /usr/bin/wodim
sudo chmod 4711 /usr/bin/cdrdao
sudo chmod 4711 /usr/bin/growisofs

2. Respect File Size Limits K3b may allow adding more data than the disc can hold. For a standard 25GB BD-R, do not exceed 23,609 MB. Exceeding this limit causes mkisofs to crash during the image creation phase.

3. Handle Defect Management (Spare Area) growisofs may fail near the end of the disc (e.g., CLOSE SESSION failed or WRITE@LBA=...) because the drive automatically reserves ~256MB for defect management, leaving insufficient space for the ISO.

Solution: Disable pre-formatting by adding the parameter -use-the-force-luke=spare:none to your command.
Alternative: Pre-format the disc manually using dvd+rw-format /dev/sr0 before burning.
4. Optimize Burning Settings

Use Compatible Tools: In K3b settings, ensure the Writing app is set to Growisofs rather than default options that might switch to incompatible tools.
Lower Speed: Dual-layer (50GB) discs are sensitive to write speed. Use -speed=2 or -speed=4 to prevent buffer underruns or write errors.
Compatibility Flags: Add -dvd-compat to permanently close the session, which helps with player compatibility and can prevent some session closure errors.
5. Hardware Verification If errors persist (e.g., INPUT/OUTPUT ERROR or POWER CALIBRATION AREA ERROR), the issue may be hardware-related.

USB Ports: Use a USB 2.0 port instead of 3.0, as USB 3.0 controllers can sometimes cause SCSI command timeouts during long burns.
Drive Quality: Slim USB drives are known to be unreliable for Blu-ray writing. Consider using an internal drive or a reputable external model (e.g., ASUS TurboDrive).
Firmware: Ensure your burner's firmware is up to date, as new firmware versions often improve media compatibility.