Subject: Re: dvd+rw-tools 7.1, Blu-Ray, and INVALID FIELD
IN CDB on session close - msg#00013

Previous Message by Date:

Get in touch

I am Turner QC an attorney at law. I am pleased to get across to you for a very urgent business proposal,contact me regarding this via: mturnerqc@xxxx -- To UNSUBSCRIBE, email to cdwrite-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Next Message by Date:

Can't blank BD-RE disc?

Does the following make any sense at all? $ dvd+rw-format -blank /dev/sr1 * BD/DVD±RW/-RAM format utility by <appro@xxxxxxxxxxxxxx>, version 7.1. * 24.8GB BD media detected. * blanking .:-[ FORMAT UNIT failed with SK=5h/INVALID FIELD IN PARAMETER LIST]: Input/output error $ dvd+rw-format /dev/sr1 * BD/DVD±RW/-RAM format utility by <appro@xxxxxxxxxxxxxx>, version 7.1. * 24.8GB BD media detected. - media is not blank - you have the option to re-run dvd+rw-format with: -format=full to perform (lengthy) Full Certification; -ssa[=none|default|max|XXX[GM]] to eliminate or adjust Spare Area. $ dmesg|tail [655497.264832] scsi32 : SCSI emulation for USB Mass Storage devices [655497.265100] usb-storage: device found at 48 [655497.265105] usb-storage: waiting for device to settle before scanning [655502.260459] usb-storage: device scan complete [655502.262074] scsi 32:0:0:0: CD-ROM PIONEER BD-RW BDR-205 1.03 PQ: 0 ANSI: 0 [655502.331684] sr1: scsi3-mmc drive: 125x/125x writer dvd-ram cd/rw xa/form2 cdda tray [655502.332054] sr 32:0:0:0: Attached scsi CD-ROM sr1 [655502.332314] sr 32:0:0:0: Attached scsi generic sg2 type 5 [655505.545597] ISO 9660 Extensions: Microsoft Joliet Level 3 [655505.548489] ISO 9660 Extensions: RRIP_1991A $ dvd+rw-format -format /dev/sr1 * BD/DVD±RW/-RAM format utility by <appro@xxxxxxxxxxxxxx>, version 7.1. * 24.8GB BD media detected. * formatting .:-[ FORMAT UNIT failed with SK=5h/INVALID FIELD IN PARAMETER LIST]: Input/output error $ dvd+rw-format -format=full /dev/sr1 * BD/DVD±RW/-RAM format utility by <appro@xxxxxxxxxxxxxx>, version 7.1. * 24.8GB BD media detected. * formatting .:-[ FORMAT UNIT failed with SK=5h/INVALID FIELD IN PARAMETER LIST]: Input/output error $ dvd+rw-mediainfo /dev/sr1 INQUIRY: [PIONEER ][BD-RW BDR-205 ][1.03] GET [CURRENT] CONFIGURATION: Mounted Media: 43h, BD-RE Media ID: PHILIP/W02 Current Write Speed: 2.0x4495=8990KB/s Write Speed #0: 12.0x4495=53940KB/s Write Speed #1: 2.0x4495=8990KB/s Speed Descriptor#0: 00/12088319 R@xxxxxxxx=8990KB/s W@xxxxxxxx=8990KB/s READ DISC INFORMATION: Disc status: complete Number of Sessions: 1 State of Last Session: complete Number of Tracks: 1 READ FORMAT CAPACITIES: formatted: 12088320*2048=24756879360 00h(3000): 11826176*2048=24220008448 30h(3000): 11826176*2048=24220008448 30h(5000): 11564032*2048=23683137536 30h(1000): 12088320*2048=24756879360 31h(800): 12219392*2048=25025314816 READ TRACK INFORMATION[#1]: Track State: complete Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size: 12088320*2KB FABRICATED TOC: Track#1 : 14@0 Track#AA : 14@12088320 Multi-session Info: #1@0 READ CAPACITY: 12088320*2048=24756879360 -- Ryan C. Underwood, <nemesis@xxxxxxxxxxxx> -- To UNSUBSCRIBE, email to cdwrite-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Previous Message by Thread:

Re: dvd+rw-tools 7.1, Blu-Ray, and INVALID FIELD IN CDB on session close

I tried this same burn with xorriso: xorriso : UPDATE : 55 files added in 1 seconds xorriso : FAILURE : Image size 12075443s exceeds free space on media 11826176s Is it possible that the problem is that not enough space is left on the disc to close the session ? Yes, in fact: ISO image produced: 11716947 sectors Written to media : 11717104 sectors at LBA 0 Writing to '/dev/sr1' completed sucessfully. If that is the case, I am a bit alarmed that growisofs is not warning me about having overburned the media! I was under the impression that growisofs would not permit overburning unless it was specifically allowed with the -overburn flag. But of course that is because I was burning on-the-fly rather than from an ISO image file, so there was no way for growisofs to know that too much data for the disc was incoming. xorriso is better because it can burn on-the-fly itself, so it knows beforehand what the size of the generated data should be. Perhaps growisofs should be changed to warn the user at the end if he attempted to overburn a disc, and that it might be the source of any problems that occurred during the session? In any case, the CLOSE SESSION problem is still around even with the smaller amount of data that burned correctly with xorriso: 11717109 extents written (22884 MB) builtin_dd: 11717120*2KB out @ average 1.3x4390KBps /dev/sr1: flushing cache /dev/sr1: closing track /dev/sr1: closing session :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error So, capacity issues aside, libburn seems to be doing something right that growisofs is doing wrong. Still fascinating that growisofs happily (and dumbly) overburned and closed the session with the BD-RE but not with any BD-R I've tried. Anyone have a clue what's going on here? Ryan On Mon, Feb 08, 2010 at 11:32:51AM -0600, Ryan C. Underwood wrote: > > Hello, > > Please see the issue I posted here with my new Pioneer BDR-205 fw 1.03: > http://club.myce.com/f143/cant-close-session-bdr-205-external-macally-cm-s525u-308505/ > > I then found the following posts on this ML explaining quite similar > problems: > http://www.mail-archive.com/cdwrite@xxxxxxxxxxxxxxxx/msg13071.html > http://www.mail-archive.com/cdwrite@xxxxxxxxxxxxxxxx/msg13093.html > > I followed the advice in the last post to try cdrskin instead, and this > is what happened (0.7.6.pl00-2): > > $ mkisofs -rJ . | cdrskin -v dev=/dev/sr1 blank=format_if_needed [tried > with speed=4 also] - > > cdrskin 0.7.6 : limited cdrecord compatibility wrapper for libburn > cdrskin: verbosity level : 1 > cdrskin: NOTE : greying out all drives besides given dev='/dev/sr1' > cdrskin: scanning for devices ... > I: -input-charset not specified, using utf-8 (detected in locale settings) > [...] > cdrskin: status 1 burn_disc_blank "The drive holds a blank disc" > Current: BD-R sequential recording > Track 01: data unknown length > Total size: 0 MB (00:00.00) = 0 sectors > Lout start: 0 MB (00:02/00) = 0 sectors > Starting to write CD/DVD at speed MAX in real TAO mode for single session. > Last chance to quit, starting real write in 0 seconds. Operation starts. > Waiting for reader process to fill input buffer ... input buffer ready. > Starting new track at sector: 0 > Track 01: 5 MB written (fifo 98%) [buf 25%] 4.0x. 0.04% done, > estimate finish Mon Feb 8 11:09:41 2010 > Track 01: 7 MB written (fifo 99%) [buf 40%] 1.3x.cdrskin: FATAL : > SCSI error on write(3632,16): [5 21 02] Invalid address > > cdrskin: thank you for being patient for 20 seconds > Track 01: Total bytes read/written: 7471104/7438336 (3632 sectors). > Writing time: 19.746s > Cdrskin: fifo had 5727 puts and 3679 gets. > Cdrskin: fifo was 0 times empty and 1160 times full, min fill was 97%. > Min drive buffer fill was 0% > cdrskin: burning failed > cdrskin: FATAL : burning failed. > > No errors in dmesg (aside from those related to inserting the blank > disc). > > Then I tried the same command again: > > [...] > cdrskin: ... scanning for devices done > cdrskin: status 3 BURN_DISC_APPENDABLE "There is an incomplete disc in the > drive" > Current: BD-R sequential recording > cdrskin: beginning to burn disc > cdrskin: status 3 BURN_DISC_APPENDABLE "There is an incomplete disc in the > drive" > Current: BD-R sequential recording > Track 01: data unknown length > Total size: 0 MB (00:00.00) = 0 sectors > Lout start: 0 MB (00:02/00) = 0 sectors > Starting to write CD/DVD at speed MAX in real TAO mode for single session. > Last chance to quit, starting real write in 0 seconds. Operation starts. > Waiting for reader process to fill input buffer ... input buffer ready. > Starting new track at sector: 3616 > cdrskin: thank you for being patient for 3 seconds > cdrskin: FATAL : SCSI error on write(0,16): [5 21 02] Invalid address > > Track 01: Total bytes read/written: 32768/0 (0 sectors). > Writing time: 3.825s > Cdrskin: fifo had 2095 puts and 47 gets. > Cdrskin: fifo was 0 times empty and 0 times full, min fill was 100%. > Min drive buffer fill was 50% > cdrskin: burning failed > cdrskin: FATAL : burning failed. > > So I'm baffled how to simply write an ISO filesystem to a Blu-Ray disc > without errors... > > -- > Ryan C. Underwood, <nemesis@xxxxxxxxxxxx> -- Ryan C. Underwood, <nemesis@xxxxxxxxxxxx> -- To UNSUBSCRIBE, email to cdwrite-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Next Message by Thread:

Re: vd+rw-tools 7.1, Blu-Ray, and INVALID FIELD IN CDB on session close

Hi, > But what does it mean for the close session > command to have aborted? Andy Polyakov states in http://lists.debian.org/cdwrite/2008/07/msg00092.html that it is a harmless bug. It was under suspicion in another case, but that might have been mere coincidence. After all the CLOSE SESSION error happens unconditionally together with any other problem. > Are there any mastering frontends that use > xorriso on the backend? None that i know of. xfburn uses the same libburn as xorriso. But i do not know whether it already had encounters with BD media. Afaik, Brasero uses libburn for CD but growisofs for DVD. Be aware that multi-session BD-R might be more easy to use after being burned by growisofs rather than by libburn. This is not an issue if you only record a single session per media. By pseudo-overwriting (POW) the first blocks of the media, growisofs points even very outdated operating systems to the newest session. Without POW one might have to tell the OS where the desired session starts. dvd+rw-mediainfo or xorriso -toc can find out. If the OS is even too dumb for making use of that info, then you need xorriso to copy the newer files to disk. On a smart OS, i deem the libburn method better because growisofs makes inaccessible the directory tree of the first session when adding the second session (with new complete tree). I plan to combine the advantages of both methods. (If only BD-R media weren't so expensive.) ------------------------------------------------ BTW: It seems our mail providers will never become friends. Mine insists in not accepting empty sender address '<>' and yours insists in not playing with such one: <nemesis@xxxxxxxxxxxx>: 65.38.17.158_does_not_like_recipient./Remote_host_said:_554_5.7.1_Service_un available;_Helo_command_[mail.gmx.net]_blocked_using_dsn.rfc-ignorant.org;_N ot_supporting_null_originator_(DSN)/Giving_up_on_65.38.17.158./ At least a million germans use GMX. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx