Re: BD-R formatting help
Thomas Schmitt [EMAIL PROTECTED] wrote: Hi, me: So with a BD-R +POW with first ISO-session written with 32 sector offset and LBA-0-patching one would get a Table Of Content as follows: Joerg Schilling: As I mentioned before, 2 sectors is not enough. I assume you meant 32, not 2. of course Ok. But what data other than the first 32 sectors of a ISO 9660 image could be needed to direct a mount program to an arbitrary root directory location on media ? The data needed to identify a specific UDF session does not fit into 32 sectors. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, Joerg Schilling wrote: The data needed to identify a specific UDF session does not fit into 32 sectors. For now the trick is explicitely restricted to ISO 9660 images (i.e. with Volume Descriptors as of ECMA-119). If libisofs ever supports UDF and especially the Bridge Format which is very similar to ISO 9660 multi-session, then i will have to take this into account in libisoburn. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, SRM+POW recordings are *not*. SRM+POW recordings are multi-track, but not multi-session. Meaning that even multi-session aware OS will look for volume descriptor at LBA#16 for SRM+POW recording. [...] I leave session open in SRM+POW [...] appropriate to refer to recording as increment, not session, in SRM+POW So it is very similar to our layouts on overwriteable media. Except that the NWA is prescribed by the new track and not at the discretion of the burn program. (MMC advises to use the track provided NWA in 4.5.3.6.9 The Expanding Orphanage.) I have to split the meaning of Session for clarity. There are no MMC-sessions on overwriteables and on BD-R+POW (as written by growisofs). But there are ISO-sessions or Volumes which get generated as if they were to be appended to MMC-multi-session media. (This stems from ISO 9660 on CD-R, after all.) We simply seem to assign different meanings to mountable in the context. To me mountable is mere validity/sanity of volume descriptor and to you is access to first recording. Let's call it muted instead, in which case answer is yes, 1st recording will become muted. Sanity is restored. I would rather say beheaded than muted. :) Pity is treason, Robespierre. I plead for keeping the ISO-sessions distinguishable in order to allow to mount the older states of the (pseudo-)multi-session media. There is only one thing missing in the current doings of growisofs: the persistent copy of the Volume Descriptors of the initial ISO-session. All other ISO-sessions stay reachable because their descriptors do not get overwritten later. One only has to find them. This allows to present the user with a uniform view on multi-session ISO burning quite regardless of the media type. growisofs already provides much of that uniformity. But with session history the media classes differ visibly and sometimes painfully. (Imagine you know there is the old unspoiled file content on media but you cannot access it because a new ISO-session was added and overwrote it by the spoiled content.) So on BD-R +POW and the first session i would propose to write 32 dummy sectors, then the ISO image which was prepared by -C 0,32, and then to overwrite the dummies by a patch copy from LBA 32++. (Or write the patched 32 sectors already before the image gets written. You'd spare one cluster of orphans that way. The dummy method should be more like the current procedure, though.) --- For reference, according to READ TRACK INFORMATION end of any given track coincides with start of next one. Now this is a riddle. From where did POW take the clusters which replaced the old LBA 0 clusters ? The specs say the Logical Overwrite of a Cluster is redirected to the NWA of some open Logical Track. A SRM disc with POW shall be initialized by the formatting process as a single session disc with a single Logical Track. The latter statement seems to forbid your track structure. Duh ? Anyway. If there is only one open track then the cluster had to be taken from its NWA. If you start the next track and inquire its NWA then i'd expect it skips the orphaned cluster address. If it would use the orphan LBA for the start of a sequential write, then an avalanche of orphans would hit the Defect List. Maybe the firmware programmers have decided to forget about the MMC prescription and to feed POW by spares and not by orphans ?i It seem so much more natural. Just not as usable for bulk overwrites. --- export MKISOFS=xorrisofs to lift the ban on options like -outdev, Cool. I have to consider it... Another help for xorriso would be if you added option -o - to the mkisofs run. Other than mkisofs there are legal states without output drive in xorriso. So whenever the user escapes the mkisofs emulation in a growisofs run, the first duty is to set -outdev -. If you gave -o - in the mkisofs part then this would not be needed. The possibility to leave the mkisofs emulation depends on growisofs current habit to write its own mkisofs options only at the start of the argument list. If you ever change this, then this trick will fail. I would have to ask you for a xorriso mode in growisofs then: mkisofs -M $indev -C $msc1,$msc2 -o $outdev is equivalent to xorriso -indev stdio:$indev \ -load sbsector $msc1 -grow_blindly $msc2 \ -outdev stdio:$outdev Currently your use of the mkisofs CLI seems to be suitable enough. As always: Thanks for your guidance ! Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt [EMAIL PROTECTED] wrote: So you leave the track open ? I assumed you fork a new track, write the session, use POW to patch LBA 0 to 31 and then close the track. (I did not examine growisofs.c for that, i have to confess.) With overwriteables i write the first session to LBA 32 Cool. You can do this easily with mkisofs too: -C 0,32 (but no -M) Just start writing at LBA 32 and do the LBA 0 patching when the session is done. More is not needed. Well, maybe a dvd+rw-toc command. This is a bad advise as it will not work with UDF enabled. BTW: The reason why I call the multi-session method used by growisofs a dirty trick is because it destroys the first session in case you append another session. BTW: what advantage do you expect from using your xorrisofs instead of mkisofs? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
It's just that last- and first-session mounts will be equivalent. Apparently we have to rewind the discussion a bit, because there is one thing I said/implied that was *wrong*. Sorry. Rewind backwards to the question about if BD-R is like DVD+R. I said yes, with POW twist and then discussion went on to multi-sessioning and I erroneously implied that all BD-R recordings performed by growisofs are multi-session. Only SRM and SRM-POW recordings are, SRM+POW recordings are *not*. SRM+POW recordings are multi-track, but not multi-session. Meaning that even multi-session aware OS will look for volume descriptor at LBA#16 for SRM+POW recording. What I implied was that multi-session aware OS would look for volume descriptor in the last recorded increment, while none multi-session aware one - at LBA#16, which is wrong. SRM+POW recordings *performed by growisofs* appear single-session to all OSes. There was a number of factors affecting this decision and I reckoned this is the most reliable/sensible way to make whole data accessible in widest range of OSes [modulo possible bugs]. There are other possible working options, but the SRM+POW method implemented by growisofs appeared, once again, *most sensible*. Yes. And thus the real first session will not be mountable because its volume descriptors are overwritten. We simply seem to assign different meanings to mountable in the context. To me mountable is mere validity/sanity of volume descriptor and to you is access to first recording. Let's call it muted instead, in which case answer is yes, 1st recording will become muted. Sanity is restored. First session effectively grows and it has nothing to do with drive recognizing multi-session. So you leave the track open ? No. But I leave session open in SRM+POW (as implied in the beginning). I assumed you fork a new track, write the session, use POW to patch LBA 0 to 31 and then close the track. Right. Except that considering rant in the beginning it might be more appropriate to refer to recording as increment, not session, in SRM+POW context. With overwriteables i write the first session to LBA 32 Cool. You can do this easily with mkisofs too: -C 0,32 (but no -M) Just start writing at LBA 32 and do the LBA 0 patching when the session is done. More is not needed. Cool. Well, maybe a dvd+rw-toc command. xorriso would do that for growisofs too. It has an alias name especially for that: export MKISOFS=xorrisofs growisofs -Z /dev/dvd /some/files growisofs -M /dev/dvd /more/files Emulation of -C goes up to the -C 16,x bug. :)) Even incremental backups are possible: growisofs -Z /dev/dvd -- outdev - -update_r /my/files /files growisofs -M /dev/dvd -- outdev - -update_r /my/files /files (Btw: would it be possible to lift the ban on options like -outdev, -overwrite, -options_from_file, ... ? They all are mistaken for -o.) Cool. I have to consider it... other sessions would have to be identified by looking at track start addresses instead of volume size round ups. I assume there is a regular pattern of gaps between two sessions. For reference, according to READ TRACK INFORMATION end of any given track coincides with start of next one. Though it (end of track) does not necessarily coincides with the end of recording. I don't seem to have data on sessions... I should have, I'll look... And even if not: one can scan for ISO 9660 heads quite effectively. Rounding up to BD cluster size would also be appropriate. A remark about http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/ Your text can make the reader believe that POW consumes Spares. But it messes up the logical address space instead. (If you write to an orphan then you create a new orphan. Cough.) MMC-5 4.5.3.5.4.1: When a SRM disc has the POW capability, the Logical Overwrite of a Cluster is redirected to the NWA of some open Logical Track Only information about the redirections is stored in the Defect List. Busted on spot! To my defense I can only say that it does say in the beginning that it's somewhat less organized notes:-) But to be serious the page was never meant to be a 100% accurate technical description and I deliberately avoided going into very deep details. It admittedly can create such impression, but it does not actually say it, does it? It says that Spare Area is required for SRM+POW and is used to support POW. And it *is* used, because at least the defect list resides in the Spare Area, i.e. consumes it. But either way, yes, your remark is perfectly correct and I do appreciate it. I just hope more people do:-) Cheers. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, This is a bad advise as it will not work with UDF enabled. Good point. growisofs should watch out for that mkisofs option before deciding to do the 32 sector life saver offset. BTW: The reason why I call the multi-session method used by growisofs a dirty trick is because it destroys the first session in case you append another session. xorriso demonstrates that the 32 block offset of the first ISO-session is a fine remedy. It can show the ISO-sessions via option -toc on all media to which it can write multiple ISO-sessions. If you write a first DVD+RW ISO-session by xorriso then you can add further ISO-sessions by growisofs without spoiling that feature. BTW: what advantage do you expect from using your xorrisofs instead of mkisofs? From man xorriso, Overview of features: i deem the following not present in mkisofs but well usable under control of growisofs: Renames or deletes file objects in the ISO image. Changes file properties in the ISO image. Updates ISO subtrees incrementally to match given disk subtrees. Also i believe it has a more comprehensive default mapping of input paths to ISO image paths. It does a better job with copying directory attributes when creating the ISO directories of a given path. It can cut out pieces from oversized disk files and map them to ISO files without needing buffer space. It addresses Andy's concerns about files larger than 4 GB and the questionable quality of reader software when it comes to multi-extent files: xorriso option -split_size maps a regular file on disk to a directory in the ISO image and places the pieces with descriptive file names into that directory. Finally it offers an alternative to existing reader software by being able to restore to disk what it wrote to ISO image. If you hit a kernel bug with ISO level 3, then xorriso will retrieve your file anyway. If you got a directory full of split files, xorriso will re-unite them on disk. To avoid confusion: xorriso is mainly intended to integrate ISO 9660 Rock Ridge multi-session with CD/DVD/BD burning. There are good reasons for a closer coupling. But it is also ready to serve as ISO formatter for any other burn program. (And as burn program for any other formatter.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
SRM+POW recordings are *not*. SRM+POW recordings are multi-track, but not multi-session. Meaning that even multi-session aware OS will look for volume descriptor at LBA#16 for SRM+POW recording. [...] I leave session open in SRM+POW [...] appropriate to refer to recording as increment, not session, in SRM+POW So it is very similar to our layouts on overwriteable media. Except that the NWA is prescribed by the new track and not at the discretion of the burn program. (MMC advises to use the track provided NWA in 4.5.3.6.9 The Expanding Orphanage.) Yes. I have to split the meaning of Session for clarity. There are no MMC-sessions on overwriteables and on BD-R+POW (as written by growisofs). But there are ISO-sessions or Volumes which get generated as if they were to be appended to MMC-multi-session media. (This stems from ISO 9660 on CD-R, after all.) Right. I plead for keeping the ISO-sessions distinguishable in order to allow to mount the older states of the (pseudo-)multi-session media. ... I'll definitely consider all the suggestions. --- For reference, according to READ TRACK INFORMATION end of any given track coincides with start of next one. Now this is a riddle. From where did POW take the clusters which replaced the old LBA 0 clusters ? Presumably from past the end of user data. The specs say the Logical Overwrite of a Cluster is redirected to the NWA of some open Logical Track. A SRM disc with POW shall be initialized by the formatting process as a single session disc with a single Logical Track. The latter statement seems to forbid your track structure. Duh ? No. It only says how it should be *initially* formatted, but says nothing about that it shall stay that way for eternity. Anyway. If there is only one open track then the cluster had to be taken from its NWA. After transfer of iso-formatted volume NWA is at its end, right? When LBA 0 is overwritten, space is borrowed from NWA, which increments[!] NWA. *Then* current track is closed. So next track's NWA starts at cluster past borrowed space and no avalanche takes place. But [as mentioned earlier] end of track does not necessarily coincides with end of recording, iso-formatted volume in this case. If you start the next track and inquire its NWA then i'd expect it skips the orphaned cluster address. It does. If it would use the orphan LBA for the start of a sequential write, then an avalanche of orphans would hit the Defect List. POW-aware recording program is expected to check on NWA after every write and handle its changes accordingly. In growisofs case single check in the beginning of recording suffices. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, me: A SRM disc with POW shall be initialized by the formatting process as a single session disc with a single Logical Track. Andy Polyakov: It only says how it should be *initially* formatted, but says nothing about that it shall stay that way for eternity. Ahum. Sounds reasonable. But [as mentioned earlier] end of track does not necessarily coincides with end of recording, iso-formatted volume in this case. So with a BD-R +POW with first ISO-session written with 32 sector offset and LBA-0-patching one would get a Table Of Content as follows: - First ISO-session begins at LBA 32. I.e. PVD at 48. It is valid if another PVD is found at LBA 16 which indicates at least the size of the PVD at LBA 48. - Further ISO-sessions begin at the start LBA of further tracks as reported by READ TRACK INFORMATION. So other than with overwriteable media, no chained hopping from ISO-session to ISO-session is needed. Nevertheless it could probably be implemented by skillfully guessing the start LBAs of the track from the size of the previous ISO-session. Just in case there are brain damaged drives. (Tricky is that orphan LBAs will exactly bear what i look for: System Area and Volume Descriptors. But of the previous ISO-session, not of the next one.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
I'm trying not to throw away *too* many of these darn expensive discs. Hey. Your boss could afford a BD burner two years ago ! It must have cost a little fortune. ;) That may be, but it is still painful to me to be tossing these babies in the rubbish bin! :'( Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt [EMAIL PROTECTED] wrote: Hi, When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. Interesting. How did it know in advance where the bad sectors are before trying to write to them ? But how did you manage to engage Defect Management ? Did i miss the solution of the formatting riddle ? The way I understand the problem, you will not get benefits from setting up spare areas for a BD-R that is written in a single shot. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
maybe you missed the _point_ of the riddle Indeed. I was not aware of that. Did you post the READ FORMAT CAPACITIES: of a dvd+rw-mediainfo run on such a media ? I remember to have seen some which report unformatted as state and offer some formatting descriptors. (None with 4 GB, though.) No, but BD-R[E] format capacity descriptors are more like guidelines. Specification permits you to specify any value between minimum and maximum (which you find among descriptors returned by the unit) with granularity of 256 clusters. Indeed, here is output for media formatted with -ssa=4G: INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM+POW Media ID: PHILIP/R02 BD SPARE AREA INFORMATION: Spare Area:999424/1998848=50.0% free POW RESOURCES INFORMATION: Remaining Replacements:16843040 Remaining Map Entries: 0 Remaining Updates: 0 READ DISC INFORMATION: Disc status: appendable Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 10220544*2KB Track Size:10220544*2KB FABRICATED TOC: Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED] READ CAPACITY: 10220544*2048=20931674112 Compare to descriptors offered for blank media: READ FORMAT CAPACITIES: unformatted: 12219392*2048=25025314816 00h(3000): 11826176*2048=24220008448 32h(0):11826176*2048=24220008448 32h(0):5796864*2048=11871977472 32h(0):12088320*2048=24756879360 Note READ CAPACITY return value being off by ~4GB from unformatted. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. Interesting. How did it know in advance where the bad sectors are before trying to write to them ? But how did you manage to engage Defect Management ? Did i miss the solution of the formatting riddle ? The way I understand the problem, you will not get benefits from setting up spare areas for a BD-R that is written in a single shot. This is wrong understanding. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Releases turned to be feature driven lately and as no new features were required (e.g. HD-DVD was dismissed) I had no immediate plans so far. But as option to specify TDMA allocation is of apparent interest, it might be appropriate to consider release in foreseeable future, i.e. from week to month. Ok, I'll try to keep my eyes open for it. Do you do an announce on this list? Yes. [Don't kill the messenger...] Yes. The real problem is that we don't know how TDMA is used exactly and therefore it's hard to judge if it's excessive or not. It surely varies from application to application and it might be that for your purposes (I assume you pretty much fill the media up at once) it's absolutely excessive. Best is to ask vendor for recommendation. I can't say for anyone else, but in my case, I would say that half is excessive. Which is why I said that option to specify TDMA reservation size is of *apparent* interest ;-) A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt [EMAIL PROTECTED] wrote: Hi, maybe you missed the _point_ of the riddle Indeed. I was not aware of that. Did you post the READ FORMAT CAPACITIES: He used a very old cdrecord to read the data and for this reason, the mail did not include all information. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, Andy Polyakov wrote: BD-R[E] format capacity descriptors are more like guidelines. Specification permits you to specify any value between minimum and maximum ... Indeed, here is output for media formatted with -ssa=4G: Thanks for the info. It will be very interesting to explore BD-R as soon as i get my hands on a drive and a few media. Is my impression right that their sequential personality is much like DVD+R ? Joerg Schilling wrote: The way I understand the problem, you will not get benefits from setting up spare areas for a BD-R that is written in a single shot. Andy Polyakov wrote: This is wrong understanding. My understanding from specs is that it is Defect Management. I.e. the drive will write a portion of its buffer to media. Then it will checkread as long as the data is still in the buffer. If a read error occurs, then it will take relocation measures and write the content again from buffer to Spare Area. The checkread usually cuts write speed by half. This (my) understanding of MMC-5 makes me wonder why Matt's burner worked around the scratch rather than running into it and to replace the casualties by spare sectors. Did it examine the blank media for damages ? Matt: Did you scratch before or after formatting ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: maybe you missed the _point_ of the riddle Indeed. I was not aware of that. Did you post the READ FORMAT CAPACITIES: He used a very old cdrecord to read the data and for this reason, the mail did not include all information That may be, but it also did not include that information because it was not sent prior to today. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: Indeed. I was not aware of that. Did you post the READ FORMAT CAPACITIES: of a dvd+rw-mediainfo run on such a media ? NO, but if you'd like to see it, here it is. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM+POW Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/12088319 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/12088319 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s BD SPARE AREA INFORMATION: Spare Area:60736/131072=46.3% free POW RESOURCES INFORMATION: Remaining Replacements:16843296 Remaining Map Entries: 0 Remaining Updates: 0 READ DISC INFORMATION: Disc status: appendable Number of Sessions:1 State of Last Session: incomplete Next Track: 1 Number of Tracks: 2 READ TRACK INFORMATION[#1]: Track State: partial incremental Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:12058848*2KB READ TRACK INFORMATION[#2]: Track State: complete incremental Track Start Address: 12058848*2KB Free Blocks: 0*2KB Track Size:29472*2KB FABRICATED TOC: Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED] READ CAPACITY: 12088320*2048=24756879360
Re: BD-R formatting help
Joerg Schilling wrote: He used a very old cdrecord to read the data and for this reason, the mail did not include all information My cdrecord reports that it is build 2.01.01a33. Exactly what version do you think I should be using? Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: The way I understand the problem, you will not get benefits from setting up spare areas for a BD-R that is written in a single shot. Jörg That would be the wrong way to look at the problem. If you burn in the mode that is Live Verify it will absolutely make a difference! Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: My understanding from specs is that it is Defect Management. I.e. the drive will write a portion of its buffer to media. Then it will checkread as long as the data is still in the buffer. If a read error occurs, then it will take relocation measures and write the content again from buffer to Spare Area. The checkread usually cuts write speed by half. Exactly. It does cut the speed in half (because it is reading and writing all of the data) but when your data is important or when the media is expensive, you don't want to throw away the disc on a bad burn like you would with a DVD that didn't verify after the burn. This (my) understanding of MMC-5 makes me wonder why Matt's burner worked around the scratch rather than running into it and to replace the casualties by spare sectors. Did it examine the blank media for damages ? Matt: Did you scratch before or after formatting ? Ok, I suppose your words are a better explanation of what happened. It burned all the way up to the scratch and must have relocated the data to the spare and continued to the burn. I don't mean to say that it located the bad spot before hand. It found it when it tried to read back the scratched area and failed. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Customer Service [EMAIL PROTECTED] wrote: Joerg Schilling wrote: He used a very old cdrecord to read the data and for this reason, the mail did not include all information My cdrecord reports that it is build 2.01.01a33. The latest version is a53. a33 is from August 2007 Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy: I sent you a couple of messages off the list, did you get them? Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, Matt Schulte wrote: I don't mean to say that it located the bad spot before hand. I understood your report of yesterday that there is a visible difference on the surface of the recorded media caused by the scratch. (Like a ring of different reflectivity or so.) This would have indicated that not the same kind of writing happened to the affected area. And that would have implied foresight. It is not impossible that the media knows about the scratch if it was encountered already during formatting. Date: Mon, 24 Nov 2008 16:43:30 -0600 When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. It is really a nice visual. Problem is 1mm is kind of hard to image and I was looking to make a bigger scratch. So how did you learn about the triggering of the defect handler ? Except by this from your dvd+rw-mediainfo run: BD SPARE AREA INFORMATION: Spare Area:60736/131072=46.3% free I assume it was 50 % before. About 9 to 10 MB would be consumed then. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Is my impression right that their sequential personality is much like DVD+R ? Yes, but with optional +POW twist (see my Blu-ray page). My understanding from specs is that it is Defect Management. I.e. the drive will write a portion of its buffer to media. Then it will checkread as long as the data is still in the buffer. If a read error occurs, then it will take relocation measures and write the content again from buffer to Spare Area. The checkread usually cuts write speed by half. Correct. Did it examine the blank media for damages ? No, BD-R can't do that. Prior verification or how they call it full certification can be applied to BD-RE only [naturally]. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, Yes, but with optional +POW twist (see my Blu-ray page). Plus the code of your tools :)) But doesn't the POW gesture make session 1 unmountable as soon as a further session is recorded ? Even on a drive which would recognize and handle multi-session ? Accessing older sessions is helpful with incremental backups. With overwriteables i write the first session to LBA 32 and do the patching of LBA 0 to 31 already with that first session. An interested reader can mount -o sbsector=32 and thus access session 1 even if LBA 0 to 31 gets overwritten later. All other sessions can easily be found by our NWA rounding (you 16, me 32). They form a nice chain. I could imagine that this would work with BD-R POW too. Hopping over the orphans will make scanning for sessions more cumbersome. This would apply to drives which would need your POW patching. For a multi session drive one would just have to know that the real session 1 starts at LBA 32 and that the Volume Descriptors at LBA 0 point to the newest session. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, It is as if it burned up to the scratch, hopped over it, and started burning again. Eww. Do we know how Logical Block Addresses map to real dye spots geometrically ? That's not in MMC. Unless one could assume that the Physical Adresses really form a simple chain of media imprints. But i doubt that. Andy Polyakov's BD-R wrote: BD SPARE AREA INFORMATION: Spare Area:999424/1998848=50.0% free Matt Schulte's BD-R wrote: BD SPARE AREA INFORMATION: Spare Area:60736/131072=46.3% free I wrote: I assume it was 50 % before. About 9 to 10 MB would be consumed then Matt Schulte wrote: I don't think I understand this question. I scratched the media, then burned my data. We seem to get in sync now (slowly): There is a visible difference in the dye and the report of your dvd+rw-mediainfo run indicates that probably 10 MB of spare have been used to protect you from data loss. (Whatever this other 50 % reservation is good for.) So if one can dare to make a linear extrapolation you should be able to compensate 10 millimeters of scratch before the spare area gets near to be exhausted. Unfortunately it has been about two years since I created this disc. Did you test whether your burner is still able to format a BD-R to default spare size ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
But doesn't the POW gesture make session 1 unmountable as soon as a further session is recorded ? ??? Why should it? It's just that last- and first-session mounts will be equivalent. Even on a drive which would recognize and handle multi-session ? First session effectively grows and it has nothing to do with drive recognizing multi-session. As you hinted yourself, -o sbsector=16 works even when drive handles multi-session. Accessing older sessions is helpful with incremental backups. Then you want to format for SRM-POW (SRM minus POW, i.e. *without* POW), in which case it will behave exactly as multi-session write-once. As mentioned on the page SRM+POW is chosen as default to maintain broadest accessibility by making all the data available even in non-multi-session aware OSes. With overwriteables i write the first session to LBA 32 and do the patching of LBA 0 to 31 already with that first session. An interested reader can mount -o sbsector=32 and thus access session 1 even if LBA 0 to 31 gets overwritten later. Cool. All other sessions can easily be found by our NWA rounding (you 16, me 32). They form a nice chain. I could imagine that this would work with BD-R POW too. Yes it would. Except that other sessions would have to be identified by looking at track start addresses instead of volume size round ups. Hopping over the orphans will make scanning for sessions more cumbersome. This would apply to drives which would need your POW patching. Drives don't need it! Some OSes would. Or I misunderstood the question, in which case please rephrase. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: Customer Service [EMAIL PROTECTED] wrote: Joerg Schilling wrote: He used a very old cdrecord to read the data and for this reason, the mail did not include all information My cdrecord reports that it is build 2.01.01a33. The latest version is a53. a33 is from August 2007 Ok, I've got your new build, what exactly do you want to see? I've sent quite a few info files at this point and I'd rather not redo all of them. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, It's just that last- and first-session mounts will be equivalent. Yes. And thus the real first session will not be mountable because its volume descriptors are overwritten. First session effectively grows and it has nothing to do with drive recognizing multi-session. So you leave the track open ? I assumed you fork a new track, write the session, use POW to patch LBA 0 to 31 and then close the track. (I did not examine growisofs.c for that, i have to confess.) With overwriteables i write the first session to LBA 32 Cool. You can do this easily with mkisofs too: -C 0,32 (but no -M) Just start writing at LBA 32 and do the LBA 0 patching when the session is done. More is not needed. Well, maybe a dvd+rw-toc command. xorriso would do that for growisofs too. It has an alias name especially for that: export MKISOFS=xorrisofs growisofs -Z /dev/dvd /some/files growisofs -M /dev/dvd /more/files Emulation of -C goes up to the -C 16,x bug. :)) Even incremental backups are possible: growisofs -Z /dev/dvd -- outdev - -update_r /my/files /files growisofs -M /dev/dvd -- outdev - -update_r /my/files /files (Btw: would it be possible to lift the ban on options like -outdev, -overwrite, -options_from_file, ... ? They all are mistaken for -o.) other sessions would have to be identified by looking at track start addresses instead of volume size round ups. I assume there is a regular pattern of gaps between two sessions. And even if not: one can scan for ISO 9660 heads quite effectively. I got a brain damaged DVD-ROM drive which cannot recognize multi-session DVD-R or DVD+R. But with a generous gap estimation of 16 MB i can collect a Table Of Content anyway. Drives don't need it! Some OSes would. Aha. I extrapolated the brain damaged DVD drives to brain damaged BD-ROM drives. My fault. Whatever, to save the mount entry of session 1 seems worthwhile if it is possible. Sessions 2 can then be found after the end of session 1 since the PVD of session 1 is at LBA 48 and tells how long session 1 was. Then we hop over the orphan gap, round up to the next 32 blocks and should find the next System Area and Volume Descriptors. (Naively spoken, i confess. It is about replaying NWA generation.) A remark about http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/ Your text can make the reader believe that POW consumes Spares. But it messes up the logical address space instead. (If you write to an orphan then you create a new orphan. Cough.) MMC-5 4.5.3.5.4.1: When a SRM disc has the POW capability, the Logical Overwrite of a Cluster is redirected to the NWA of some open Logical Track Only information about the redirections is stored in the Defect List. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: Unfortunately it has been about two years since I created this disc. Did you test whether your burner is still able to format a BD-R to default spare size ? No, I haven't done it again, I'm trying not to throw away *too* many of these darn expensive discs. It would appear that dvd+rw-format has never been able to format a BD-R, as currently if you put ssa=anything with a BD-R disc, it will fail. That would mean that when I did it the last time, I used growisofs which itself performs a format (I am not sure whether it is as it goes or whether it is just done at the beginning of the burn). Probably something like: -use-the-force-luke=spare:min,wrvfy Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, It would appear that dvd+rw-format has never been able to format a BD-R That would mean that when I did it the last time, I used growisofs which itself performs a format Still questionable whether there is enough difference between both FORMAT commands to explain the difference in success on both BD-R discs. I'm trying not to throw away *too* many of these darn expensive discs. Hey. Your boss could afford a BD burner two years ago ! It must have cost a little fortune. ;) You could combine a test of growisofs auto-format with the 10 mm scratch test. If it formats then the scratch will become illustrative. If it does not format, then you will test how bad a 10 mm scratch is with a BD-R that has no Defect Management. So give it a double dozen GB of data to eat. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
I am trying to make the spare area of a BD-R be something larger than the default. I was hoping to run something like: ./dvd+rw-format -ssa=4G /dev/dvd But when I execute this command, it says that it is invalid for the detected media. This is not intentional. In other words it's a bug and it will be looked into. Suggested code modification might be appropriate, but I'd rather not say it without double-checking. In a course of few days. The source code change mentioned in originating post is correct and will be included [though in modified form] to next dvd+rw-tools update. After making the above change, it then gets past this portion of the code and gets down to where the actual formatting is going to take place. I get this message: sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 Deferred sr00:00: sense key Medium Error Additional sense indicates Format command failed This I can't reproduce. In other words I managed to format BD-R disc with -ssa=4G, i.e. unit succeeded to format it with ~4GB spare area. Have you managed to record BD-R in this particular unit at all? Same question about BD-RE? What I'm trying to say is that the unit might simply be broken... Another option is a kernel bug, maybe in SATA support (as you mentioned it's SATA connected). Have you managed to record a DVD? Side note about spare area capacity. There is something they call TDMA, Temporary Disc Management Area, residing in Lead-In. As you allocate spare area, part of it will be reserved for *additional* TDMA regions. Relevant question is what part of it? MMC specification says that default value is up to vendor and in Panasonic case it seem to be 1/2 of spare area capacity. This means that if you ask your unit for spare area utilization data right after format, you'll see that 1/2 of it is already used. Well, it's not actually used, but reserved for TDMAs. Whether it's excessive or not, time will show. Meanwhile I'm considering adding extra option to dvd+rw-format, which would allow you to specify which portion of spare area will be reserved for TDMA. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: I assume you have disabled all automounters and similar programs which could access the drive. So this could come from the device driver trying to learn about the present media. In the embedded 2.4.32 install, there is no automounter. Nothing happens unless I explicitly run it. In the stock Ubuntu install, I haven't disabled anything. Does this kernel log protesting start as soon as you insert the media into the drive or does it start only when you run dvd+rw-format ? No it only starts complaining after I run dvd+rw-format. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: OK, thank you. BZW: it seems that the spare size if your other disk was not changed Yes, that is kind of the problem. dvd+rw-format doesn't seem to be doing anything at all. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy Polyakov wrote: The source code change mentioned in originating post is correct and will be included [though in modified form] to next dvd+rw-tools update. Great, any idea when you are planning your next release? This I can't reproduce. In other words I managed to format BD-R disc with -ssa=4G, i.e. unit succeeded to format it with ~4GB spare area. Have you managed to record BD-R in this particular unit at all? Same question about BD-RE? What I'm trying to say is that the unit might simply be broken... Another option is a kernel bug, maybe in SATA support (as you mentioned it's SATA connected). Have you managed to record a DVD? I have been able to record on this drive before. As long as I don't try to pre-format a BD-R. And I have never had any problems with the BD-RE's. I have also been able to record DVD's with this unit. I am going to move to a SATA unit soon, but right now I'm still tinkering with the same kind of drive that you have. Here's what I'm actually trying to do: I want to demonstrate to the customer how wonderful Blu-Ray is for data integrity. I want to say something like see it can even detect a defect in the media on the fly and still successfully complete a burn. I want to be able to make a small scratch on the disc and then watch it burn around the scratch and keep going (I have actually done this). Problem is that a small scratch is hard to see and a large scratch is a really big chunk of disc capacity (hence my -ssa=4G). Side note about spare area capacity. There is something they call TDMA, Temporary Disc Management Area, residing in Lead-In. As you allocate spare area, part of it will be reserved for *additional* TDMA regions. Relevant question is what part of it? MMC specification says that default value is up to vendor and in Panasonic case it seem to be 1/2 of spare area capacity. This means that if you ask your unit for spare area utilization data right after format, you'll see that 1/2 of it is already used. Well, it's not actually used, but reserved for TDMAs. Whether it's excessive or not, time will show. Meanwhile I'm considering adding extra option to dvd+rw-format, which would allow you to specify which portion of spare area will be reserved for TDMA. A. Wait, are you saying that if you used -ssa=4G you are actually going to get 2G of spare and 2G of TDMA? Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
The source code change mentioned in originating post is correct and will be included [though in modified form] to next dvd+rw-tools update. Great, any idea when you are planning your next release? Releases turned to be feature driven lately and as no new features were required (e.g. HD-DVD was dismissed) I had no immediate plans so far. But as option to specify TDMA allocation is of apparent interest, it might be appropriate to consider release in foreseeable future, i.e. from week to month. This I can't reproduce. In other words I managed to format BD-R disc with -ssa=4G, i.e. unit succeeded to format it with ~4GB spare area. Have you managed to record BD-R in this particular unit at all? Same question about BD-RE? What I'm trying to say is that the unit might simply be broken... Another option is a kernel bug, maybe in SATA support (as you mentioned it's SATA connected). Have you managed to record a DVD? I have been able to record on this drive before. As long as I don't try to pre-format a BD-R. And I have never had any problems with the BD-RE's. I have also been able to record DVD's with this unit. I am going to move to a SATA unit soon, but right now I'm still tinkering with the same kind of drive that you have. I.e. you suffered from this problem with non-SATA unit? To reiterate. You run dvd+rw-format and kernel starts logging test unit ready: meduim error. As you start dvd+rw-format in text console (i.e. without starting windowing system), the kernel log appears as dvd+rw-format output. Error messages are emitted till you press ctrl-c. Is it correctly understood? Do you see any output from dvd+rw-format? Like process indicator? What does dvd+rw-format print exactly? Basically I'm running low on ideas, primarily because I couldn't reproduce this... Side note about spare area capacity. There is something they call TDMA, Temporary Disc Management Area, residing in Lead-In. As you allocate spare area, part of it will be reserved for *additional* TDMA regions. Relevant question is what part of it? MMC specification says that default value is up to vendor and in Panasonic case it seem to be 1/2 of spare area capacity. This means that if you ask your unit for spare area utilization data right after format, you'll see that 1/2 of it is already used. Well, it's not actually used, but reserved for TDMAs. Whether it's excessive or not, time will show. Meanwhile I'm considering adding extra option to dvd+rw-format, which would allow you to specify which portion of spare area will be reserved for TDMA. A. Wait, are you saying that if you used -ssa=4G you are actually going to get 2G of spare and 2G of TDMA? [Don't kill the messenger...] Yes. The real problem is that we don't know how TDMA is used exactly and therefore it's hard to judge if it's excessive or not. It surely varies from application to application and it might be that for your purposes (I assume you pretty much fill the media up at once) it's absolutely excessive. Best is to ask vendor for recommendation. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, Andy Polyakov wrote: The real problem is that we don't know how TDMA is used exactly To be heretic: Did anybody see Defect Management work with any type of media (MRW, DVD-RAM, BD-RE, BD-R) in a way that is not worse than a plain bad block ? My experience is with DVD-RAM and there the answer is no. If defects are frequent then you have to fear that some show up later after the burn. All in all you cannot trust such a media anyway. On the level of an ISO 9660 filesystem i believe that a software solution could in many cases be the better one: - write session quick and dirty - compare files on disk and in session - in case of errors write an add-on session which replaces the damaged files. -- As for Matt's idea with the scratch demo: I have DVDs which look like an ice stadium and they work perfectly. Others have no scratch and they failed to verify after one or two burns. One can hardly drill holes without endangering the drive. But how about a few dots with a black felt tip marker ? Tell me how it worked out ... when it finally works. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy Polyakov wrote: Releases turned to be feature driven lately and as no new features were required (e.g. HD-DVD was dismissed) I had no immediate plans so far. But as option to specify TDMA allocation is of apparent interest, it might be appropriate to consider release in foreseeable future, i.e. from week to month. Ok, I'll try to keep my eyes open for it. Do you do an announce on this list? I.e. you suffered from this problem with non-SATA unit? To reiterate. You run dvd+rw-format and kernel starts logging test unit ready: meduim error. As you start dvd+rw-format in text console (i.e. without starting windowing system), the kernel log appears as dvd+rw-format output. Error messages are emitted till you press ctrl-c. Is it correctly understood? Do you see any output from dvd+rw-format? Like process indicator? What does dvd+rw-format print exactly? Basically I'm running low on ideas, primarily because I couldn't reproduce this... Your description sounds about right. Andy: would you like an ssh session to see it for yourself? [Don't kill the messenger...] Yes. The real problem is that we don't know how TDMA is used exactly and therefore it's hard to judge if it's excessive or not. It surely varies from application to application and it might be that for your purposes (I assume you pretty much fill the media up at once) it's absolutely excessive. Best is to ask vendor for recommendation. A. I can't say for anyone else, but in my case, I would say that half is excessive. I kind of suspect that this would be how most users are going to use blu-ray anyways. I know there are several other very interesting uses for this type of media, but I think the most common will be the most boring. Just plain old burning something big. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: As for Matt's idea with the scratch demo: I have DVDs which look like an ice stadium and they work perfectly. Others have no scratch and they failed to verify after one or two burns. One can hardly drill holes without endangering the drive. But how about a few dots with a black felt tip marker ? Tell me how it worked out ... when it finally works. It isn't an idea, it works. I placed a small scratch on the disc (maybe 1mm) and burned several GB of data (enough to fill well past the scratch). When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. It is really a nice visual. Problem is 1mm is kind of hard to image and I was looking to make a bigger scratch. How do you figure that drilling a hole in a disc will endanger the drive? Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: Hi, When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. Interesting. How did it know in advance where the bad sectors are before trying to write to them ? But how did you manage to engage Defect Management ? Did i miss the solution of the formatting riddle ? You didn't miss the solution, but maybe you missed the _point_ of the riddle ;-) It is not that I cannot turn on defect management. It is that I cannot turn on defect management with an arbitrary spare size. For my experiment, the size of the scratch was small enough that the default size of the spare was enough to take care of it. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. Interesting. How did it know in advance where the bad sectors are before trying to write to them ? But how did you manage to engage Defect Management ? Did i miss the solution of the formatting riddle ? How do you figure that drilling a hole in a disc will endanger the drive? There should arise some imbalance. Given the usual noises of a DVD drive when reading at full speed this could become a problem. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, maybe you missed the _point_ of the riddle Indeed. I was not aware of that. Did you post the READ FORMAT CAPACITIES: of a dvd+rw-mediainfo run on such a media ? I remember to have seen some which report unformatted as state and offer some formatting descriptors. (None with 4 GB, though.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi,
That particular error message was being printed by a very pared down 2.4.32
That should be young enough to run the drive
anyway. But my 2.4 kernels never reported
errors directly to the user space terminal.
The errors reported are probably due to the
uninitialized status of the BD-R.
Nov 21 16:22:29 ubuntu kernel: [27434.649982] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
It would be nice if it would tell which sector
and what ASC and ASCQ numbers came with sense 0x03.
[27887.746641] hdc: error code: 0x70 sense_key: 0x03 asc: 0x57 ascq: 0x00
That's a bit more informative:
3 57 00 UNABLE TO RECOVER TABLE-OF-CONTENTS
Question to myself, MMC specs and all others:
Shoult it have a TOC at that time ?
[27887.744680] ide: failed opcode was: unknown
Grmpf. Why does it know the error and not the
command which caused it ? (This question goes
towards heaven.)
The terminal screen begins scrolling this text until I CTL-C:
hdc: error code: 0x70 sense_key: 0x03 asc: 0x57 ascq:0x00
This mass output does not look like typical
dvd+rw-tools behavior.
I assume you have disabled all automounters and
similar programs which could access the drive.
So this could come from the device driver trying
to learn about the present media.
Does this kernel log protesting start as soon
as you insert the media into the drive or does
it start only when you run dvd+rw-format ?
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Customer Service [EMAIL PROTECTED] wrote: Joerg Schilling wrote: OK, so this medium holds 200704 spare sectors. I am not sure whether this is the default or whether this is a result of a format call. BTW: Is this a Philips Medium? Jörg Attached is the output of cdrecord -v -minfo on a fresh-from-the-cellophane BD-R. Yes, these are both Philips branded discs. OK, thank you. BZW: it seems that the spare size if your other disk was not changed. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy Polyakov [EMAIL PROTECTED] wrote: This is bullshit. If you write to the media as it was at that moment, it If you like to be taken for serious, it would be apropriate to use a less offensive language. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Customer Service [EMAIL PROTECTED] wrote: Joerg Schilling wrote: Thomas Schmitt [EMAIL PROTECTED] wrote: Can it be that the BD-R was already treated with a format command previously ? MMC-5 4.5.3.5 BD-R Recording Models says Once the recording mode has been established, it is not changeable. This is why I asked him to run cdrecord -minfo From the output of cdrecord that I just sent, it looks (to me) like the disc is still blank. As if the command failed before it even made it far enough to touch the disc. Sorry, please add a -v this should give you the formatted capacity list in addition. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: Customer Service [EMAIL PROTECTED] wrote: Joerg Schilling wrote: Thomas Schmitt [EMAIL PROTECTED] wrote Can it be that the BD-R was already treated with a format command previously ? MMC-5 4.5.3.5 BD-R Recording Models says Once the recording mode has been established, it is not changeable. This is why I asked him to run cdrecord -minf From the output of cdrecord that I just sent, it looks (to me) like the disc is still blank. As if the command failed before it even made it far enough to touch the disc. Sorry, please add a -v this should give you the formatted capacity list in addition. Jörg As you wish... I am not sure whether you guys like attachments or whether you want things inline, so I just attached it. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com Cdrecord-ProDVD-ProBD-Clone 2.01.01a33 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.9'. atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'BD-MLT SW-5582 ' Revision : 'BZE6' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-R sequential recording Profile: BD-R sequential recording (current) Profile: BD-R random recording Profile: BD-RE Profile: BD-ROM Profile: DVD-RAM Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-RW restricted overwrite Profile: DVD-RW sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-R/DL sequential recording Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO Drive buf size : 6684672 = 6528 KB Current Secsize: 2048 Disk type: 'BDR' (BD-R) Disk class: 01 Manufacturer: 'PHILIP' Media type: 'R02' Disk: is not in cartridge Media cartrige: write protect is off Free Spare Blocks: 0 Alloc Spare Blocks: 0 rzone size: 40 rzone number: 1 border number: 1 ljrs: 0 track mode: 4 copy: 0 damage: 0 reserved track: 0 blank: 1 incremental: 1 fp: 0 data mode: 1 lra valid: 0 nwa valid: 1 rzone start:0 next wr addr: 0 free blocks:12219392 blocking factor:32 rzone size: 12219392 last recorded addr: 0 read compat lba:0 Capacity Blklen/Sparesz. Type 12219392 200704 Unformated or Blank Media 1182617612288 Reserved (0) 118261760 Reserved (0) 57968640 Reserved (0) 120883200 Reserved (0) Mounted media class: BD Mounted media type: BD-R sequential recording Disk Is not erasable data type:standard disk status: empty session status: empty BG format status: none first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 1 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Blank 0 12219391 12219392 -1 Next writable address: 0 Remaining writable size:12219392
Re: BD-R formatting help
Customer Service [EMAIL PROTECTED] wrote: Sorry, please add a -v this should give you the formatted capacity list in addition. Jörg As you wish... I am not sure whether you guys like attachments or whether you want things inline, so I just attached it. OK, so this medium holds 200704 spare sectors. I am not sure whether this is the default or whether this is a result of a format call. BTW: Is this a Philips Medium? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: OK, so this medium holds 200704 spare sectors. I am not sure whether this is the default or whether this is a result of a format call. BTW: Is this a Philips Medium? Jörg Attached is the output of cdrecord -v -minfo on a fresh-from-the-cellophane BD-R. Yes, these are both Philips branded discs. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com Cdrecord-ProDVD-ProBD-Clone 2.01.01a33 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.9'. atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'BD-MLT SW-5582 ' Revision : 'BZE6' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-R sequential recording Profile: BD-R sequential recording (current) Profile: BD-R random recording Profile: BD-RE Profile: BD-ROM Profile: DVD-RAM Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-RW restricted overwrite Profile: DVD-RW sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-R/DL sequential recording Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO Drive buf size : 6684672 = 6528 KB Current Secsize: 2048 Disk type: 'BDR' (BD-R) Disk class: 01 Manufacturer: 'PHILIP' Media type: 'R02' Disk: is not in cartridge Media cartrige: write protect is off Free Spare Blocks: 0 Alloc Spare Blocks: 0 rzone size: 40 rzone number: 1 border number: 1 ljrs: 0 track mode: 4 copy: 0 damage: 0 reserved track: 0 blank: 1 incremental: 1 fp: 0 data mode: 1 lra valid: 0 nwa valid: 1 rzone start:0 next wr addr: 0 free blocks:12219392 blocking factor:32 rzone size: 12219392 last recorded addr: 0 read compat lba:0 Capacity Blklen/Sparesz. Type 12219392 200704 Unformated or Blank Media 1182617612288 Reserved (0) 118261760 Reserved (0) 57968640 Reserved (0) 120883200 Reserved (0) Mounted media class: BD Mounted media type: BD-R sequential recording Disk Is not erasable data type:standard disk status: empty session status: empty BG format status: none first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 1 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Blank 0 12219391 12219392 -1 Next writable address: 0 Remaining writable size:12219392
Re: BD-R formatting help
Thomas Schmitt wrote: ./dvd+rw-format -ssa=4G /dev/dvd But when I execute this command, it says that it is invalid for the detected media. || (mmc_profile != 0x12 mmc_profile != 0x43 mmc_profile != 0x41 ssa) ) After making the above change, it then gets past this portion If i get the code of dvd+rw-format.cpp 0.7.1 right then you are not supposed to use option -ssa together with profile 0x41. You are supposed to use option -force. At other spots in the code i find traces that ssa is well expected, though. Your code change should have had a chance for success. You will notice that the code has: force=ssa=1; so if you choose ssa, you are automatically setting force too. sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 Deferred sr00:00: sense key Medium Error Additional sense indicates Format command failed This does not look as if it was from dvd+tools but rather from the kernel. Do you see that in a log file or does it appear with the format run on terminal ? This actually shows up in the log as well as on the terminal. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 Deferred sr00:00: sense key Medium Error This does not look as if it was from dvd+tools but rather from the kernel. Do you see that in a log file This actually shows up in the log as well as on the terminal. I can by no means find a potential origin of that message in dvd+rw-tools. Nor would my local Linux kernel print me these messages Did you already tell what operating system and version you use ? (I assume sr0 is Linux) READ FORMAT CAPACITIES: unformatted: 12219392*2048=25025314816 00h(3000): 11826176*2048=24220008448 32h(0):11826176*2048=24220008448 32h(0):5796864*2048=11871977472 32h(0):12088320*2048=24756879360 It offers these three 32h formattings with about 0.8 GB and 0.25 GB of spare. The middle one seems to be 12.5 GB for spare area and for data. Obviously it believes to be ready for formatting but the FORMAT command fails. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Sorry, please add a -v this should give you the formatted capacity list in addition. As you wish... I am not sure whether you guys like attachments or whether you want things inline, so I just attached it. OK, so this medium holds 200704 spare sectors. This is bullshit. If you write to the media as it was at that moment, it would end-up *without* spare sectors at all and consequently with defect management permanently disabled for that particular disc. Secondly 200704 is maximum number of spare BD *clusters* *allowed* to be configured, not currently configured. I am not sure whether this is the default or whether this is a result of a format call. The media remained unformatted and is as good as virgin. In other words format call had no effect. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote:
I can by no means find a potential origin of
that message in dvd+rw-tools. Nor would my
local Linux kernel print me these messages
Did you already tell what operating system and
version you use ? (I assume sr0 is Linux
That particular error message was being printed by a very pared down
2.4.32 kernel that was running on an embedded slackware 10 install.
In order to do the current testing, I've thrown the unit into a default
x86 install of Ubuntu Gutsy.
I have downloaded and compiled the dvd+rw-tools V7.1 as Ubuntu seems to
be behind on their builds.
To be complete, attached messages.txt is what gets printed to
/var/log/messages when I try the same command.
The terminal screen begins scrolling this text until I CTL-C:
hdc: error code: 0x70 sense_key: 0x03 asc: 0x57 ascq:0x00
And I find the attachment dmesg.txt.
Matt Schulte
Commtech, Inc.
Voice: 316-636-1131
Fax: 316-636-1163
http://www.commtech-fastcom.com
Nov 21 16:22:23 ubuntu kernel: [27428.609016] cdrom: This disc doesn't have any
tracks I recognize!
Nov 21 16:22:29 ubuntu kernel: [27434.616377] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.616387] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.616391] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.617816] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.618802] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.618808] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.618811] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.620260] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.626333] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.626342] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.626346] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.627793] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.628785] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.628791] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.628794] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.630246] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.631259] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.631264] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.631267] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.632715] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.633690] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.633695] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.633698] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.635255] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.637129] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.637134] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.637138] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.638354] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.639327] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.639332] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.639335] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.640993] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.641962] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.641968] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.641971] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.643674] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.644808] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.644814] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.644817] ide:
Re: BD-R formatting help
Thomas Schmitt [EMAIL PROTECTED] wrote: Can it be that the BD-R was already treated with a format command previously ? MMC-5 4.5.3.5 BD-R Recording Models says Once the recording mode has been established, it is not changeable. This is why I asked him to run cdrecord -minfo Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: What does cdrecord -minfo show for this medium? Hello, I'm at a different email address, but it's still me. So here is the cdrecord -minfo output: Cdrecord-ProDVD-ProBD-Clone 2.01.01a33 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'BD-MLT SW-5582 ' Revision : 'BDB2' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO Mounted media class: BD Mounted media type: BD-R sequential recording Disk Is not erasable data type:standard disk status: empty session status: empty BG format status: none first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 1 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Blank 0 12219391 12219392 Next writable address: 0 Remaining writable size:12219392 Matt Schulte -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: Thomas Schmitt [EMAIL PROTECTED] wrote: Can it be that the BD-R was already treated with a format command previously ? MMC-5 4.5.3.5 BD-R Recording Models says Once the recording mode has been established, it is not changeable. This is why I asked him to run cdrecord -minfo From the output of cdrecord that I just sent, it looks (to me) like the disc is still blank. As if the command failed before it even made it far enough to touch the disc. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Hi, Matt! I'm monkeying around with the blu-ray drives again (though now it is a SATA interface) and I've come upon something that I don't quite understand. I am trying to make the spare area of a BD-R be something larger than the default. I was hoping to run something like: ./dvd+rw-format -ssa=4G /dev/dvd But when I execute this command, it says that it is invalid for the detected media. This is not intentional. In other words it's a bug and it will be looked into. Suggested code modification might be appropriate, but I'd rather not say it without double-checking. In a course of few days. Meanwhile please submit dvd+rw-mediainfo output (even garbled one you mentioned you obtain if you don't reload media). cdrecord does not show format descriptors. After making the above change, it then gets past this portion of the code and gets down to where the actual formatting is going to take place. I get this message: sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 Deferred sr00:00: sense key Medium Error Additional sense indicates Format command failed You indicated it's BDB2 firmware? Is it latest? We both know that there is BZE6 available for SW-5582. Do you know how they number their releases? For example is BZxx later than BDxx? What I'm implying firmware upgrade might be due to make it work with arbitrary ... Cheers. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
You indicated it's BDB2 firmware? Is it latest? We both know that there is BZE6 available for SW-5582. Do you know how they number their releases? For example is BZxx later than BDxx? What I'm implying firmware upgrade might be due to make it work with arbitrary ... Cheers. A. I completely forgot that we updated the firmware on this bad boy. Let me give that a shot first. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy Polyakov wrote: This is not intentional. In other words it's a bug and it will be looked into. Suggested code modification might be appropriate, but I'd rather not say it without double-checking. In a course of few days. Meanwhile please submit dvd+rw-mediainfo output (even garbled one you mentioned you obtain if you don't reload media). cdrecord does not show format descriptors. Updating the firmware didn't do it. I'm attaching three different mediainfo outputs. mediainfo1 is a blank disc before attempting to do anything to it. mediainfo2 is the same disc after running: ./dvd+rw-format -ssa=4G /dev/dvd(and before I ejected the disc) mediainfo3 is the same disc after ejecting and injecting. You will notice that 1 and 3 are the same. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ FORMAT CAPACITIES: unformatted: 12219392*2048=25025314816 00h(3000): 11826176*2048=24220008448 32h(0):11826176*2048=24220008448 32h(0):5796864*2048=11871977472 32h(0):12088320*2048=24756879360 READ TRACK INFORMATION[#1]: Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 12219392*2KB Track Size:12219392*2KB READ CAPACITY: 0*2048=0 INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/10220543 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/10220543 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DISC INFORMATION: Disc status: appendable Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ FORMAT CAPACITIES: INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ FORMAT CAPACITIES: unformatted: 12219392*2048=25025314816 00h(3000): 11826176*2048=24220008448 32h(0):11826176*2048=24220008448 32h(0):5796864*2048=11871977472 32h(0):12088320*2048=24756879360 READ TRACK INFORMATION[#1]: Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 12219392*2KB Track Size:12219392*2KB READ CAPACITY: 0*2048=0
Re: BD-R formatting help
Hi, ./dvd+rw-format -ssa=4G /dev/dvd But when I execute this command, it says that it is invalid for the detected media. || (mmc_profile != 0x12 mmc_profile != 0x43 mmc_profile != 0x41 ssa) ) After making the above change, it then gets past this portion If i get the code of dvd+rw-format.cpp 0.7.1 right then you are not supposed to use option -ssa together with profile 0x41. You are supposed to use option -force. At other spots in the code i find traces that ssa is well expected, though. Your code change should have had a chance for success. sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 Deferred sr00:00: sense key Medium Error Additional sense indicates Format command failed This does not look as if it was from dvd+tools but rather from the kernel. Do you see that in a log file or does it appear with the format run on terminal ? Such an occasion would occur if the FORMAT command was sent with IMMED bit for asynchronous work. A TEST UNIT READY command which is used to watch progress then delivers the error message of the asynchronous FORMAT. As far as i can see the format descriptor gets the right format type 0x32 for BD-R. Can it be that the BD-R was already treated with a format command previously ? MMC-5 4.5.3.5 BD-R Recording Models says Once the recording mode has been established, it is not changeable. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
BD-R formatting help
I'm monkeying around with the blu-ray drives again (though now it is a
SATA interface) and I've come upon something that I don't quite
understand.
I am trying to make the spare area of a BD-R be something larger than
the default. I was hoping to run something like:
./dvd+rw-format -ssa=4G /dev/dvd
But when I execute this command, it says that it is invalid for the
detected media. Looking at the code is appears as if this should be a
valid option, I also tried to use:
./dvd+rw-format -force -ssa=4G /dev/dvd
also to no avail.
I took a wild swing at this one. And thought that maybe this would
fix the problem.
if (((mmc_profile == 0x1A || mmc_profile == 0x2A) blank)
|| (mmc_profile != 0x1A compat)
|| (mmc_profile != 0x12 mmc_profile != 0x43 mmc_profile !=
0x41 ssa) )
{ fprintf (stderr,- illegal command-line option for this media.\n);
goto offer_options;
}
After making the above change, it then gets past this portion of the
code and gets down to where the actual formatting is going to take
place.
I get this message:
sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00
Deferred sr00:00: sense key Medium Error
Additional sense indicates Format command failed
And if I eject the disc and re-insert it, then run mediainfo on it, it
shows up as blank. If I run mediainfo on it before I eject it, I get
a bunch of garbage.
Any thoughts?
Thank you,
Matt Schulte
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
