[Cin] Not all blu-ray disk are the same ...
Andrew Randrianasulu
randrianasulu at gmail.com
Thu Dec 29 03:20:08 CET 2022
чт, 29 дек. 2022 г., 01:53 Terje J. Hanssen <terjejhanssen at gmail.com>:
>
>
> Den 27.12.2022 02:17, skrev Andrew Randrianasulu:
>
>
>
> вт, 27 дек. 2022 г., 03:57 Terje J. Hanssen <terjejhanssen at gmail.com>:
>
>>
>>
>> Den 26.12.2022 23:01, skrev Andrew Randrianasulu:
>>
>>
>> https://superuser.com/questions/879216/how-to-determine-whether-blu-ray-disc-is-htl-or-lth
>>
>> lists two methods one with cdrecord + internet, another one using imgburn
>>
>> ===
>>
>> Here's the best way I've found:
>>
>> 1.
>>
>> Determine the manufacturer code and media type of the media. On
>> Linux, I used cdrecord
>> <http://cdrtools.sourceforge.net/private/cdrecord.html> dev=XXX -atip
>> | grep -i 'manufacturer\|media type', where XXX is the code for the
>> Blu-ray burner as listed by cdrecord -scanbus.
>>
>>
>> This give me an opportunity to discuss certain reported issues with
>> access privilegies from K3b/Cdrecord.
>>
>> I have also reported this as a possible K3b build bug to openSUSE
>> bugzilla a couple of weeks ago
>> https://bugzilla.opensuse.org/show_bug.cgi?id=1206384
>>
>> Suggestions are welcome how to troubleshoot and get rid of them, as they
>> can be part of or main cause to my burning/disc problem. !?
>>
>>
>> cdrecord -scanbus
>> Cdrecord-ProDVD-ProBD-Clone 3.02a09 (x86_64-unknown-linux-gnu) Copyright
>> (C) 1995-2016 Joerg Schilling
>> 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.
>> cdrecord: No access. Cannot open '/dev/sg0'. Cannot open or use SCSI
>> driver.
>> cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are
>> root.
>> cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
>>
>> cdrecord dev=/dev/sr0 -atip | grep -i 'manufacturer\|media type'
>> 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.
>> scsidev: '/dev/sr0'
>> devname: '/dev/sr0'
>> scsibus: -2 target: -2 lun: -2
>> Warning: Open by 'devname' is unintentional and not supported.
>> Linux sg driver version: 3.5.27
>> Manufacturer: 'VERBAT'
>> Media type: 'IM1'
>>
>> https://github.com/netblue30/firejail/issues/2989
>
> I read somewhere in cdrtools documentation cdrecord may use linux
> capabilities ...
>
> this issues suggest using
>
> sudo getcap /usr/bin/cdrecord
>
> So, I guess there should be setcap too?
>
>
> I admit I have never heard about or used getcap and setcap before, but
> found them in the Leap package 'libcap-progs'.
> I ran setcap as you suggested in your additional post 'cdrecord as user'.
> The "Insufficient 'xxxx' privileges disappeared, but sorry not the failed
> burning.
>
> Five years ago I burned several labeled "LongLife" Verbatim BD-R DL/50 Gb
> discs with the same LG burner and previous K3b/Cdrecord. When these discs
> became EOL, I tried corresponding 'Mediarange' discs. These failed to burn
> and Cdrecord returned an unknown error (code 254). This error 254 is
> posted on some forums with different solutions.
> Some said burning could be broken by some unfrienly programs. Regarding
> Mediarange, Joerg Schilling suggested to upgrade the burner's firmware, but
> still no burning success with those Mediarange discs anymore.
>
I think xorriso is only disk burning program left with maintainer ...
try it, and also try contact suggested at its homepage
===
Contact for issues of this web page or the described program: Thomas
Schmitt, scdbackup at gmx.net
====
> My current Verbatim BD-R/RE DL/50 Gb discs are labeled "Hard Coat" - and
> respectively "M+A+B+L" resistant (layer for archival life), and "SERL" for
> up to 1000 times rewriteable. But LG/K3b don't like them and fails with
> error code 254. What is rather confusing, I have happend to successful burn
> a couple of these BD-RE discs, while most have failed after several trial.
>
well, may drive tries to defect manage them and got confused? (I myself
write initially about background format here but then saw it named defect
management)
https://forums.linuxmint.com/viewtopic.php?t=246015
> - Typical output in the burning window is:
> - SAO writing at 2x speed (default SAO and 3x selected)
> - Cdrecord returned an unknown error (code 254)
> - Sometimes TAO writing solves this issue (I have not tried that)
> - (Another error "Cannot fixate disk" has also appeared)
>
>
> I have currently had some more success to complete burn some unbranded
> BD-RE/DL discs from Slowmoose, with less failing. The remarkable is that
> the disc burn is so unstable and inconsistently, as it may fail on the
> first two attemps before it succeed on the third. Some burns may fail
> immediately, other not so fun after 1 or 1.5 hour(s), or ca. 1/3-1/2 of
> total burning time for 40 Gb)
>
> I maybe read somewhere that som other burning programs could "leave disc
> without "closing session" (or similar?), and Cdrecord next could run into
> issue to rewrite those discs afterwards. I know I have tried also 'dd' on
> some discs.
>
> Two of more or less related links
> https://wiki.archlinux.org/title/Optical_disc_drive
> https://bbs.archlinux.org/viewtopic.php?id=58884
>
>
>
>
>
>> Just now K3b/Cdrecord seems to not even write to more BD-RE DL discs :(
>>
>> The above messages are also part of the current debugging output from K3b
>> included here (sorry for the length):
>>
>> Devices
>> -----------------------
>> HL-DT-ST BD-RE BH10LS30 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM,
>> DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL)
>> [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, BD-ROM, BD-R Sequential
>> (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R,
>> RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random
>> Recording, Sequential Recording, Sequential Recording + POW] [%7]
>>
>> System
>> -----------------------
>> K3b Version: 21.12.3
>> KDE Version: 5.90.0
>> Qt Version: 5.15.2
>> Kernel: 5.14.21-150400.24.38-default
>>
>> Used versions
>> -----------------------
>> cdrecord: 3.2a09
>>
>> cdrecord
>> -----------------------
>> 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.
>> scsidev: '/dev/sr0'
>> devname: '/dev/sr0'
>> scsibus: -2 target: -2 lun: -2
>> Warning: Open by 'devname' is unintentional and not supported.
>> Linux sg driver version: 3.5.27
>> SCSI buffer size: 64512
>> Cdrecord-ProDVD-ProBD-Clone 3.02a09 (x86_64-unknown-linux-gnu) Copyright
>> (C) 1995-2016 Joerg Schilling
>> TOC Type: 1 = CD-ROM
>> Using libscg version 'schily-0.9'.
>> Driveropts: 'burnfree'
>> atapi: 1
>> Device type : Removable CD-ROM
>> Version : 5
>> Response Format: 2
>> Capabilities :
>> Vendor_info : 'HL-DT-ST'
>> Identifikation : 'BD-RE BH10LS30 '
>> Revision : '1.02'
>> Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
>> Current: BD-RE
>> Profile: BD-ROM
>> Profile: BD-R sequential recording
>> Profile: BD-R random recording
>> Profile: BD-RE (current)
>> Profile: DVD-RAM
>> Profile: DVD-R sequential recording
>> Profile: DVD-R/DL sequential recording
>> Profile: DVD-R/DL layer jump recording
>> Profile: DVD-RW sequential recording
>> Profile: DVD-RW restricted overwrite
>> Profile: DVD+RW
>> Profile: DVD+R
>> Profile: DVD+R/DL
>> Profile: DVD-ROM
>> Profile: CD-R
>> Profile: CD-RW
>> Profile: CD-ROM
>> Profile: Removable Disk (current)
>> Using generic SCSI-3/mmc-3 BD-RE driver (mmc_bdre).
>> Driver flags : NO-CD BD MMC-3 BURNFREE
>> Supported modes: PACKET SAO LAYER_JUMP
>> Drive buf size : 2031616 = 1984 KB
>> Drive pbuf size: 3850240 = 3760 KB
>> Drive DMA Speed: 17771 kB/s 100x CD 12x DVD 3x BD
>> FIFO size : 4194304 = 4096 KB
>> Track 01: data 39383 MB
>> Total size: 39383 MB = 20164288 sectors
>> Current Secsize: 0
>> Capacity Blklen/Sparesz. Format-type Type
>> 24438784 36864 0x00 Unformated or Blank Media
>> 23652352 24576 0x00 Reserved (0)
>> 23259136 2048 0x01 Reserved (0)
>> 23652352 24576 0x30 Reserved (0)
>> 23259136 36864 0x30 Reserved (0)
>> 24307712 4096 0x30 Reserved (0)
>> 24438784 2048 0x31 Reserved (0)
>> Format was needed.
>> Starting to write CD/DVD/BD at speed 2 in real FORMAT mode for single
>> session.
>> Last chance to quit, starting real write in 3 seconds.
>> 2 seconds.
>> 1 seconds.
>> 0 seconds. Operation starts.
>> Formatting media
>> operation 0% done
>> === last message repeated 29 times. ===
>> Formatting time: 61.464s (00:01:01.464)
>> Condition not caught: capacity_not_set.
>>
>> cdrecord command:
>> -----------------------
>> /usr/bin/cdrecord -v gracetime=2 dev=/dev/sr0 speed=2 -sao
>> driveropts=burnfree -data -tsize=20164288s -
>>
>>
>>
>>
>> 1.
>>
>> Look up the manufacturer and media type codes at
>> http://www.blu-raydisc.info/licensee-list/discmanuid-licenseelist.php .
>> The table on that site identifies "recording type" (i.e. HTL or LTH) and
>> also write speed from these codes.
>>
>> === quote end====
>>
>> site worked when I clicked on link.
>>
>> Apparently LTH should be marked due to their bad compatibility with
>> earlier drives, but .... reality is less stellar :(
>>
>>
>> A quick look in the tables it seemed for me that all 50GB BD-R/RE DL
>> discs use "HTL" recording type.
>>
>>
>>
>> and in imgburn
>>
>> ====
>>
>> With image burning software. ImgBurn <http://www.imgburn.com/> for
>> instance.
>>
>> In Imgburn main menu just click on anything writing related. For example,
>> "Write image file to disc"
>>
>> Now a new window pops up
>>
>> Please check that you have the correct burner selected in the left hand
>> side, if you have more than one disc burner.
>>
>> Scroll down on the right pane, and you find the info under "Recorded Mark
>> Polarity"
>> ====
>>
>>
>> HTL is apparently more durable....
>>
>> Terje posted link to Canadian site and I did little search on my own
>>
>>
>> https://www.pcworld.com/article/423607/hard-core-data-preservation-the-best-media-and-methods-for-archiving-your-data.html
>> (from 2016)
>>
>> to be honest I newer heard about HTL vs LTH when it comes to BDs....
>>
>> I found some ASUS drive in my city, so *may be* I'll have some means to
>> test real disks in new year.
>>
>>
>>
>> Many articles recommend to keep three types of media for archiving stored
>> on at least two locations to spread the risk.
>> For camcorded video this envolves for me
>>
>> 1. keep the source media (tape cassettes)
>> 2. a digitized version on portable expansion USB3 discs
>> 3. and on optical Blu-ray data discs and playable BD-video discs.
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20221229/e9cc30ff/attachment-0001.htm>
More information about the Cin
mailing list