Can't burn BD-R media, DVD+R - OK.

Discussion in 'Installation/Configuration' started by kaza, Apr 3, 2010.

  1. kaza

    kaza New Member

    Hello,

    I attempted to backup some directories tree onto a BD-R disk
    and it seems not to be recognized while doing the same to
    the DVD+R disk worked OK (with a smaller tree, of corse ) .
    I'm running FC11, kernel: 2.6.29.4-167.hpfs.fc11.x86_64
    with a GNOME desktop. I attempted the burn with "CD/DVD Creator",
    "B rasero Disk Burner" and "K3b". With all 3 it seems like the BD-R media
    isn't recognized as valid, although, at least in "K3b" case the "Media info"
    shows what looks like a correct data:

    Medium
    |-Type: B D-R Sequential (S R M)
    |-Capacity: 2715:25:17 m in 23.3 GB
    |-Rewritable: no
    |-Appendable: no
    |-Empty: yes
    |-Sessions: 0
    -Supported writing speeds: 18x (3324 KB/s)

    When I proceed to the "burn" stage, instead of a detected media type I get:
    "Please insert an empty or appendable DVD+/-R(W) medium..."
    or, if the size of the data was above 4.4GB:
    "Please insert an empty or appendable double layer DVD+/-R(W) medium..."

    How can it be that the media info is detected correctly but when I attempt to
    burn on it, the system behaves as if it doesn't recognize the media?

    The devices listed:

    <.../kaza>\ls -l /dev | grep cd
    lrwxrwxrwx. 1 root root 3 2010-04-03 16:46 cdrom -> sr0
    lrwxrwxrwx. 1 root root 3 2010-04-03 16:46 cdrw -> sr0
    lrwxrwxrwx. 1 root root 3 2010-04-03 16:46 scd0 -> sr0
    crw-rw----+ 1 root cdrom 21, 0 2010-04-03 16:46 sg0
    brw-rw----+ 1 root cdrom 11, 0 2010-04-03 16:46 sr0

    When I start "k3b" (and ejecting and re-inserting the disk
    in the middle) I get the following dumped into the terminal:

    <.../kaza>k3b&
    [1] 5423
    <.../kaza>kbuildsycoca running...
    (K3bDevice::HalConnection) initializing HAL >= 0.5
    Mapping udi /org/freedesktop/Hal/devices/storage_model_BD_RE__GGW_H20L to device /dev/sr0
    /dev/sr0 resolved to /dev/sr0
    /dev/sr0 is block device (0)
    /dev/sr0 seems to be cdrom
    bus: 0, id: 0, lun: 0
    (K3bDevice::Device) /dev/sr0: init()
    (K3bDevice::Device) /dev/sr0 feature: CD Mastering
    (K3bDevice::Device) /dev/sr0 feature: CD Track At Once
    (K3bDevice::Device) /dev/sr0 feature: CD-RW Media Write Support
    (K3bDevice::Device) /dev/sr0 feature: DVD Read (MMC5)
    (K3bDevice::Device) /dev/sr0 feature: DVD+R
    (K3bDevice::Device) /dev/sr0 feature: DVD+RW
    (K3bDevice::Device) /dev/sr0 feature: DVD+R Double Layer
    (K3bDevice::Device) /dev/sr0 feature: BD Read
    (K3bDevice::Device) /dev/sr0 feature: BD Write
    (K3bDevice::Device) /dev/sr0 feature: DVD-R/-RW Write
    (K3bDevice::Device) /dev/sr0 feature: Rigid Restricted Overwrite
    (K3bDevice::Device) /dev/sr0 feature: Layer Jump Recording
    (K3bDevice::Device) /dev/sr0 feature: HD-DVD Read
    (K3bDevice::Device) /dev/sr0 unknown profile: 2
    (K3bDevice::Device) /dev/sr0: dataLen: 60
    (K3bDevice::Device) /dev/sr0: checking for TAO
    (K3bDevice::Device) /dev/sr0: checking for SAO
    (K3bDevice::Device) /dev/sr0: checking for SAO_R96P
    (K3bDevice::Device) /dev/sr0: checking for SAO_R96R
    (K3bDevice::Device) /dev/sr0: checking for RAW_R16
    (K3bDevice::Device) /dev/sr0: checking for RAW_R96P
    (K3bDevice::Device) /dev/sr0: checking for RAW_R96R
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    (K3bDevice::Device) /dev/sr0: GET PERFORMANCE dataLen = 56
    (K3bDevice::Device) /dev/sr0: GET PERFORMANCE successful with reported length: 52
    (K3bDevice::Device) /dev/sr0: Number of supported write speeds via GET PERFORMANCE: 3
    (K3bDevice::Device) /dev/sr0 : 26973 KB/s
    (K3bDevice::Device) /dev/sr0 : 17982 KB/s
    (K3bDevice::Device) /dev/sr0 : 8991 KB/s
    (K3bDevice::DeviceManager) setting current write speed of device /dev/sr0 to 3324
    /dev/sr0 resolved to /dev/sr0
    (K3bDevice::DeviceManager) dev /dev/sr0 already found
    (K3bDevice::DeviceManager) found config entry for devicetype: HL-DT-ST BD-RE GGW-H20L
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    Devices:
    ------------------------------
    Blockdevice: /dev/sr0
    Generic device:
    Vendor: HL-DT-ST
    Description: BD-RE GGW-H20L
    Version: YL03
    Write speed: 3324
    Profiles: DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, HD DVD-ROM, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE
    Read Cap: DVD-ROM, DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+RW Dual Layer, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, HD DVD-ROM, HD DVD-R, BD-ROM, BD-R, BD-RE
    Write Cap: DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-R, CD-RW, BD-R, BD-RE
    Writing modes: SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW
    Reader aliases: /dev/sr0
    ------------------------------
    DiskInfo:
    Mediatype: BD-R Sequential (SRM)
    Current Profile: BD-R Sequential (SRM)
    Disk state: empty
    Empty: 1
    Rewritable: 0
    Appendable: 0
    Sessions: 0
    Tracks: 0
    Layers: 1
    Capacity: 00:00:00 (LBA 0) (0 Bytes)
    Remaining size: 00:00:00 (LBA 0) (0 Bytes)
    Used Size: 00:00:00 (LBA 0) (0 Bytes)
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    (K3bDevice::Device) /dev/sr0: GET PERFORMANCE dataLen = 56
    (K3bDevice::Device) /dev/sr0: GET PERFORMANCE successful with reported length: 52
    (K3bDevice::Device) /dev/sr0: Number of supported write speeds via GET PERFORMANCE: 3
    (K3bDevice::Device) /dev/sr0 : 26973 KB/s
    (K3bDevice::Device) /dev/sr0 : 17982 KB/s
    (K3bDevice::Device) /dev/sr0 : 8991 KB/s
    (K3bDevice::DeviceManager) request for empty device!
    (K3bDevice::DeviceManager) request for empty device!
    removing udi /org/freedesktop/Hal/devices/volume_empty_bd_r
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    DiskInfo:
    Mediatype: BD-R Sequential (SRM)
    Current Profile: BD-R Sequential (SRM)
    Disk state: empty
    Empty: 1
    Rewritable: 0
    Appendable: 0
    Sessions: 0
    Tracks: 0
    Layers: 1
    Capacity: 2715:25:17 (LBA 12219392) (25025314816 Bytes)
    Remaining size: 2715:25:17 (LBA 12219392) (25025314816 Bytes)
    Used Size: 00:00:00 (LBA 0) (0 Bytes)
    adding udi /org/freedesktop/Hal/devices/volume_empty_bd_r
    (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
    (K3bDevice::Device) /dev/sr0: GET PERFORMANCE dataLen = 56
    (K3bDevice::Device) /dev/sr0: GET PERFORMANCE successful with reported length: 52
    (K3bDevice::Device) /dev/sr0: Number of supported write speeds via GET PERFORMANCE: 3
    (K3bDevice::Device) /dev/sr0 : 26973 KB/s
    (K3bDevice::Device) /dev/sr0 : 17982 KB/s
    (K3bDevice::Device) /dev/sr0 : 8991 KB/s
    (K3bDevice::DeviceManager) request for empty device!

    [1] Done k3b
    <.../kaza>ICE default IO error handler doing an exit(), pid = 5653, errno = 11

    What doesn the message "GET CONFIGURATION length det failed."
    means?

    Any ideas as to what as to what am I doing wrong?
    I also attempted to start "k3b" as a root with the same\results.

    Thanks in advance for any help,
    kaza.
     
  2. kaza

    kaza New Member

    Some more info about BluRay drive as k3b sees it

    Hello again,

    Here's some more info I noticed:

    In "k3b", when I select Settings -> Configure -> Devices
    There is the following info displayed under "Writer Drives":

    HL-DT-ST BD-RE GGW-H20L

    System device name: /dev/sr0 (0,0,0)
    Interface type: Generic SCSI <- Strange, the drive is on SATA link.
    Vendor: HL-DT-ST
    Description: BD-RE GGW-H20L
    Firmware: YL03
    Wrires CD-R: yes
    Writes CD-RW: yes
    Reads DVD: yes
    Writes DVD-R(W): yes
    Writes DVD-R Dual Layer: yes
    Writes DVD+R(W): yes
    Writes DVD+R Dual Layer: yes
    Buffer size: 2.0 MB
    Cdrdao driver: auto
    CD-Text capable: auto
    Supports burnfree: yes
    Write modes: SAO, TAO, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P,
    RAW/R96R, Restricted Overwrite, Layer Jump,
    Random Recording, Sequential Recording,
    Sequential Recording +POW


    When I dragged directories to burn, I noticed that when the data size was
    X < 4.4GB, the status line at the bottom showed: "X out of 4.4GB".
    When X became 4.4GB<X<8GB, the status line changed to:
    "X out of 8GB" and when X became greater than 8GB,a red
    part appeared at the right side of the status line saying: "Y GB above capacity"
    when Y = X - 8 GB, totally ignoring the fact that the same k3b detected
    the media (as in "Media info") as blank BD-R with a capacity of 25 GB.
    From the list of supported types of reads and writes it seems k3b selects
    the smallest applicable media for the data size from the group of CD, DVD
    and Dual layer DVD and its apparent inability to write BD-R is the reason
    it instructs me to insert a blank DVD or a blank DVD dual layer while
    I have a blank BD-R inserted.

    So the question can be narrowed down to: what controls the possible
    write formats of k3b (and probably other burning apps), regardless of
    the media type discovered?

    I attempted to boot a slightly newer kernel 2.6.30.10-105.2.23.fc11.x86_64 -
    same results. The dvd+rw-tools version:

    dvd+rw-tools-7.1-3.fc11.x86_64

    In the Settings -> Configure -> Programs of "k3b" there is a list
    of programs, some of them are marked as "not found" (see attached
    png of the captured window), can it be the reason some write formats
    are unavaliable?

    Thanks in advance for any help,
    kaza.
     

    Attached Files:

Share This Page