Re: solaris cdrecord BH08LS20 drive BD-R problems
> > > > > > Could you try again with BD-RE media? > > > > > > > > > > Formatting error - please advise > > > > > I am going to write the missing format code soon > > > > > Would you be willing to test it with your unformatted blank? > > > > could you please test the preliminary 2.01.01a79 > > > > > > > Using my unformatted blank BD-RE disc, it works (but still slow) > > > Nice to see that the format code works! > > > > > Yes, Very Nice! > You seem to have a general USB speed problem I had been testing on my old Ultra 60 with only 768 MB memory Here are the results of testing on my SunFire V800 server (much better speed) using the previously formatted BD-RE disc # cdrecord -v dev=3,0,0 speed=1 driveropts=burnfree image.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a79 (sparc-sun-solaris2.10) TOC Type: 1 = CD-ROM scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-RE Profile: BD-ROM Profile: BD-R sequential recording Profile: BD-R random recording Profile: BD-RE (current) Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R Profile: CD-RW Profile: CD-ROM Profile: Removable Disk (current) Using generic SCSI-3/mmc-3 BD-RE driver (mmc_bdre). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 2097152 = 2048 KB Drive pbuf size: 3932160 = 3840 KB Drive DMA Speed: 10752 kB/s 61x CD 7x DVD 2x BD FIFO size : 4194304 = 4096 KB Track 01: data 6614 MB Total size: 6614 MB = 3386473 sectors Current Secsize: 2048 Trying to clear drive status. WARNING: Drive returns zero media size, correcting. Blocks total: 11826176 Blocks current: 11826176 Blocks remaining: 8439703 Reducing transfer size from 64512 to 32768 bytes. Starting to write CD/DVD/BD at speed 2 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Starting new track at sector: 0 Track 02: 6614 of 6614 MB written (fifo 100%) [buf 50%] 0.8x. Track 02: Total bytes read/written: 6935496704/6935496704 (3386473 sectors). Writing time: 1433.357s Average write speed 1.1x. Min drive buffer fill was 50% Fixating... Fixating time:4.035s cdrecord: fifo had 211655 puts and 211655 gets. cdrecord: fifo was 0 times empty and 34766 times full, min fill was 92%.
Re: solaris cdrecord BH08LS20 drive BD-R problems
> Could you please run cdrecord -atip bash-3.00# cdrecord dev=3,0,0 -atip Cdrecord-ProDVD-ProBD-Clone 2.01.01a77 (sparc-sun-solaris2.10) scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 BD-RE driver (mmc_bdre). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Disk type: 'BDW' (BD-RE) Disk class: 02 Manufacturer: 'RITEK' Media type: 'BW1' Disk: is not in cartridge Media cartrige: write protect is off Capacity Blklen/Sparesz. Format-type Type 1221939220480 0x00 Unformated or Blank Media 1182617612288 0x00 Reserved (0) 11564032 2048 0x01 Reserved (0) 1182617612288 0x30 Reserved (0) 1156403220480 0x30 Reserved (0) 12088320 4096 0x30 Reserved (0) 12219392 2048 0x31 Reserved (0)
Re: solaris cdrecord BH08LS20 drive BD-R problems
> Could you try again with BD-RE media? Formatting error - please advise bash-3.00# cdrecord -v dev=3,0,0 speed=1 driveropts=burnfree image.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a77 (sparc-sun-solaris2.10) Copyright (C) 1995-2010 J�g Schilling TOC Type: 1 = CD-ROM scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-RE Profile: BD-ROM Profile: BD-R sequential recording Profile: BD-R random recording Profile: BD-RE (current) Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R Profile: CD-RW Profile: CD-ROM Profile: Removable Disk (current) Using generic SCSI-3/mmc-3 BD-RE driver (mmc_bdre). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 2097152 = 2048 KB Drive pbuf size: 3932160 = 3840 KB Drive DMA Speed: 6562 kB/s 37x CD 4x DVD 1x BD FIFO size : 4194304 = 4096 KB Track 01: data 6614 MB Total size: 6614 MB = 3386473 sectors Current Secsize: 2048 Capacity Blklen/Sparesz. Format-type Type 1221939220480 0x00 Unformated or Blank Media 1182617612288 0x00 Reserved (0) 11564032 2048 0x01 Reserved (0) 1182617612288 0x30 Reserved (0) 1156403220480 0x30 Reserved (0) 12088320 4096 0x30 Reserved (0) 12219392 2048 0x31 Reserved (0) Format was needed. Starting to write CD/DVD/BD at speed 1 in real FORMAT mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. cdrecord: DVD+RW Full format capacity not found. cdrecord: Cannot format medium.
Re: solaris cdrecord BH08LS20 drive BD-R problems
> > Previously I was using the JMicron JM20336 USB-SATA bridge. > > Now I have the JM20329, apparently a simpler (and slower) chip. > > The BH08LS20 drive connected via USB 2.0, using blank BD-R disc > Cdrecord will be changed to work-around the firmware bug Tested last night with cdrtools a77 version on sun ultra 60 with solaris 10 The work-around allowed me to burn a 7 GB image to blu-ray disc but it took over 2 hours, seemingly as slow as growisofs on that machine How do I get cdrecord to burn at 2x speed? # cdrecord -v dev=4,0,0 speed=2 driveropts=burnfree image.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a77 (sparc-sun-solaris2.10) TOC Type: 1 = CD-ROM scsidev: '4,0,0' scsibus: 4 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-R sequential recording Profile: BD-ROM Profile: BD-R sequential recording (current) Profile: BD-R random recording Profile: BD-RE Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R Profile: CD-RW Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 2097152 = 2048 KB Drive pbuf size: 3932160 = 3840 KB Drive DMA Speed: 1575 kB/s 8x CD 1x DVD 0x BD FIFO size : 4194304 = 4096 KB Track 01: data 6614 MB Total size: 6614 MB = 3386473 sectors Current Secsize: 2048 WARNING: Drive returns zero media size, correcting. Blocks total: 12219392 Blocks current: 12219392 Blocks remaining: 8832919 Reducing transfer size from 64512 to 32768 bytes. Starting to write CD/DVD/BD at speed 8 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Starting new track at sector: 0 Track 01: 6614 of 6614 MB written (fifo 100%) [buf 31%] 0.2x. Track 01: Total bytes read/written: 6935496704/6935496704 (3386473 sectors). Writing time: 7189.700s Average write speed 0.2x. Min drive buffer fill was 12% Fixating... Fixating time: 19.265s cdrecord: fifo had 211655 puts and 211655 gets. cdrecord: fifo was 0 times empty and 181399 times full, min fill was 87%.
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, > > > JM20329 versus JM20336 > > Did it have positive effect on Solaris machine? > Yes, only windows has a good driver for JM20336 Stunning. One would expect that USB is standardized enough to plug any compliant device into any compliant computer. I could accept the need for a special driver if it was about a computer side controller. But i understand you exchanged the one on the drive side of the cable. Somehow that first USB-SATA bridge did not really implement the USB usage model. > So cdrecord will work after Jörg prepares his > workaround for the LG drive firmware bug. :-D Did you already try cdrecord with the new bridge ? Maybe the drive firmware is ok but had no chance to prove this to cdrecord yet. Although ... this here looks really a bit strange > $ growisofs -Z /dev/scd0=image.iso -use-the-force-luke=spare:none > /dev/scd0: "Current Write Speed" is 8.2x4390KBps. > ... > builtin_dd: 4270960*2KB out @ average 1.9x4390KBps Obviously the drive announces much more speed than 2x. Scrolling back to 9 Oct 2009, dvd+rw-mdiainfo output: > GET [CURRENT] CONFIGURATION: > Mounted Media:41h, BD-R SRM > Current Write Speed: 8.0x4495=35964KB/s > Write Speed #0: 8.0x4495=35964KB/s > Write Speed #1: 6.0x4495=26973KB/s > Write Speed #2: 4.0x4495=17982KB/s > Write Speed #3: 2.0x4495=8991KB/s "8.2x4390KBps" would rather be "KiB" than "KB" so it is indeed the same as "8.0x4495=35964KB/s". cdrecord -minfo told on 15 Oct: > Manufacturer: 'RITEK' > Media type: 'BR2' Google finds me http://www.videohelp.com/dvdmedia/memorex-bd-r-4/4749 http://club.myce.com/f172/ritek-bd-r-sl-273812/ It looks that the media are nominally 4x. Right ? Hard to say whether -use-the-force-luke=spare:none did not have the desired effect or the USB bridge did not deliver enough bandwidth resp. too much latency so that the drive decided to slow down to 2x. Clarifying experiments would be: growisofs without -use-the-force-luke=spare:none or cdrskin (Linux only) which will surely not format BD-R automatically. E.g.: cdrskin -v dev=5,0,0 image.iso (derived from your cdrecord command as reported 14 Oct 2009) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
> > I believe it was the JMicron USB-SATA bridge > > JM20329 versus JM20336 > Did it have positive effect on Solaris machine? Yes, only windows has a good driver for JM20336 So cdrecord will work after Jörg prepares his workaround for the LG drive firmware bug. :-D > > To use SRM with no spares on the CentOS box > > would I try a command line similar to this? > > # growisofs -Z /dev/scd0=image.iso \ > > -use-the-force-luke=spare:none -speed=2 > I would omit the -speed option and let growisofs > negotiate that with the drive. Afaik -speed is > rather intended to slow down poor media Okay, I tried it and it worked with JM20329 chip. And growisofs did negotiate 2x speed properly. It only took 17 minutes to burn 8.7 GB. See results below: $ growisofs -Z /dev/scd0=image.iso -use-the-force-luke=spare:none Executing 'builtin_dd if=coxdj_20091030.iso of=/dev/scd0 obs=32k seek=0' /dev/scd0: "Current Write Speed" is 8.2x4390KBps. 0/8746919936 ( 0.0%) @0x, rem ??:?? RBU 100.0% UBU 0.0% 0/8746919936 ( 0.0%) @0x, rem ??:?? RBU 100.0% UBU 0.0% 4030464/8746919936 ( 0.0%) @0.3x, rem 469:59 RBU 99.8% UBU 1.6% 19136512/8746919936 ( 0.2%) @1.0x, rem 121:37 RBU 100.0% UBU 35.9% 19464192/8746919936 ( 0.2%) @0.0x, rem 149:27 RBU 100.0% UBU 100.0% 41680896/8746919936 ( 0.5%) @1.5x, rem 80:03 RBU 100.0% UBU 35.9% 49512448/8746919936 ( 0.6%) @0.5x, rem 76:07 RBU 100.0% UBU 35.9% 66322432/8746919936 ( 0.8%) @1.1x, rem 65:26 RBU 100.0% UBU 35.9% 70746112/8746919936 ( 0.8%) @0.3x, rem 67:27 RBU 100.0% UBU 92.2% 100433920/8746919936 ( 1.1%) @2.0x, rem 51:39 RBU 100.0% UBU 92.2% 130514944/8746919936 ( 1.5%) @2.0x, rem 44:00 RBU 100.0% UBU 92.2% 160563200/8746919936 ( 1.8%) @2.0x, rem 38:19 RBU 100.0% UBU 89.1% ... ... ... 8553627648/8746919936 (97.8%) @2.0x, rem 0:22 RBU 99.8% UBU 92.2% 8583643136/8746919936 (98.1%) @2.0x, rem 0:18 RBU 99.8% UBU 92.2% 8613658624/8746919936 (98.5%) @2.0x, rem 0:15 RBU 100.0% UBU 92.2% 8643674112/8746919936 (98.8%) @2.0x, rem 0:11 RBU 100.0% UBU 92.2% 8671428608/8746919936 (99.1%) @1.9x, rem 0:08 RBU 100.0% UBU 92.2% 8701444096/8746919936 (99.5%) @2.0x, rem 0:05 RBU 100.0% UBU 92.2% 8731459584/8746919936 (99.8%) @2.0x, rem 0:01 RBU 92.2% UBU 92.2% builtin_dd: 4270960*2KB out @ average 1.9x4390KBps /dev/scd0: flushing cache /dev/scd0: closing track /dev/scd0: closing session
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Rob W: > I believe it was the JMicron USB-SATA bridge chip. > JM20329 versus JM20336 Did it have a positive effect on the Solaris machine ? > On solaris I used this command for burning > # growisofs -Z /dev/rdsk/c3t0d0s0=image.iso According to Andy's text i assume that the media was formatted automatically and thus would at most be written at half its nominal speed. 4.5 MiB/second. But the reported performance was less than one third of that half. Still very mysterious. > To use SRM with no spares on the CentOS box > would I try a command line similar to this? > # growisofs -Z /dev/scd0=image.iso \ > -use-the-force-luke=spare:none -speed=2 That's what i read from the text. (I have my own burn programs to test. Thus i use them at any occasion i have with BD media. One year of BD burning strengthened my opinion that at least my drive and my media work well with full nominal 2x speed.) I would omit the -speed option and let growisofs negotiate that with the drive. Afaik -speed is rather intended to slow down poor media. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > Just wanted to follow up with more experimentation ... > > > Previously I was using the JMicron JM20336 USB-SATA bridge. > > Now I have the JM20329, apparently a simpler (and slower) chip. > > The BH08LS20 drive connected via USB 2.0, using blank BD-R disc. > > Using this drive connected to my CentOS machine with JM20329, > I tried NeroLinux again, and this time was successful. > At 2x, it only took 18 minutes to burn a 9 GB iso image. > > Perhaps I should try growisofs on the CentOS machine. Cdrecord will be changed to workaound the firmware bug. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, > I tried NeroLinux again, and this time was successful. What changed in comparison to the failed attempt ? Anything else but replugging cables ? > At 2x, it only took 18 minutes to burn a 9 GB iso image. If the nominal speed was 2x then this was obviously with an unformatted BD-R or with Streaming Bit on. > Perhaps I should try growisofs on the CentOS machine. To prevent growisofs from formatting and then writing at half speed, see: http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/ "growisofs allows for SRM recordings without spare area through "undocumented" -use-the-force-luke=spare:none option, but it's not recommended;" Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Just wanted to follow up with more experimentation ... > Previously I was using the JMicron JM20336 USB-SATA bridge. > Now I have the JM20329, apparently a simpler (and slower) chip. > The BH08LS20 drive connected via USB 2.0, using blank BD-R disc. Using this drive connected to my CentOS machine with JM20329, I tried NeroLinux again, and this time was successful. At 2x, it only took 18 minutes to burn a 9 GB iso image. Perhaps I should try growisofs on the CentOS machine.
Re: solaris cdrecord BH08LS20 drive BD-R problems
> ... there is DMA. > >> Even though above is about SPARC Solaris 8 I found no evidence that DMA >> default settings for ATA would be different on SPARC Solaris 10 and even >> OpenSolaris for SPARC. > > The variable atapi-cd-dma-enabled was introduced for Solaris 10. > Before _all_ CDs always had no DMA. Given placement of the remark any sane person would assume that it refers SPARC Solaris 10, wouldn't [s]he? Well, the boot variable was introduced in Solaris 10 x86[!] and the variable is Solaris x86 specific! It has no meaning on SPARC Solaris [not to mention that it's impossible to set any custom boot variable with eeprom(sparc)]! >> In the course of discussion it was also implied that cdrecord's "Solaris >> DMA related READMEs" are up-to-date with accuracy of 12 months and apply >> to *all* Solaris releases. To summarize, the READMEs discuss binary >> patching of ata binary driver on Solaris 9 x86 as the only way to engage >> DMA for optical ATAPI units. > > They are as correct as they can be with the feedback from users... Quoting Jörg: "Unless this changed during the past 12 month, my information is of course correct and up to date." This remark was also made as reply to my "SPARC Solaris [8] *is* capable of DMA." Any sane person would interpret it as "Jörg has looked over the information about a year ago and verified that there is nothing to add and patching ata binary driver is still the only way to engage DMA for optical ATAPI unit on Solaris versions >=9, both x86 and SPARC." The latter is far from true. 1. Solaris >=10 x86 has atapi-cd-dma-enabled (as already mentioned multiple times) 2. It does *not* apply to SPARC Solaris (see below). READMEs are as correct as they are in specific context of Solaris 9 x86! One shouldn't imply [or rather it wrong to imply] anything more than that. >> patching of ata binary driver on Solaris 9 x86 as the only way to engage >> DMA for optical ATAPI units. I don't recall when Solaris 10 was >> released, but from my >4 years personal experience with Solaris 10 x86 >> on Sun W1100z (Opteron-based workstation), it's perfectly possible to > > Opteron is not sparc... That's why I wrote "experience with Solaris 10 *x86*." >> Then there is enough evidence that the READMEs in question are not >> applicable to [any recent] SPARC Solaris release. At the very least on >> SPARC Solaris ATA is implemented by uata driver, which does not even >> have ata_init_drive_pcidma subroutine. Not to mention above information >> about DMA *defaults* for SPARC Solaris ATA support. > > As you could see, my patch is for sparc What "my patch is for sparc" are you talking about? One found in README.solaris-x86-ATAPI-DMA? If you meant "my patch is for x86", then how does it support your argument about DMA default being off on *SPARC* Solaris? > and you should know that with Solaris 11 > DMA is finally used by default. And so should you, and consequently should not imply that READMEs are perfectly up-to-date. And DMA is *finally* by default on in Solaris 11 x86[!]. On SPARC Solaris it was by default since *earlier*. > If you have been able to do something that other people could not do before > (using a DVD drive with DMA on a sparc system), it would be nice if you could > tell us how you did manage this. I did *nothing*! On the contrary, as mentioned earlier I had to patch uata binary to get rid of DMA! As already stated several times, *DMA is on by default on SPARC Solaris >=8* (maybe since earlier, I simply have no data on earlier releases). The setting appears to be negotiated upon uata driver initialization. If DMA ended up off on somebody's system, I would guess that driver failed to negotiate it. Maybe there is jumper on the unit, maybe specific unit is not fully compliant with ATA specification which can be reason for failure. I don't know. But it doesn't mean that one can draw conclusion that DMA is off by default and state "Solaris sparc *still* does not support DMA on ATA interfaces". A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov wrote: > On the other hand, looking through the information provided *beyond* > requested one allows to draw conclusion that DMA is *in fact* enabled > for optical drive in question. Once again, target1-dcd-options is 0xa2 > and more important read performance reaches 19MBps[!]. Indeed, there is > no way venerable Blade-100 can deliver that much over PIO at *portion* > of CPU power(*). As for value of 0xa2. Earlier I said that it denotes > UDMA-2. As it turns out this was inaccurate. Upper bits, ones > constituting 0xa?, do denote UDMA, but lower bits, ones constituting > 0x?2, don't denote UDMA *mode*. Lower bits are meaningful when UDMA is > disengaged and seem to denote PIO mode. In other words, while not being > specific about UDMA mode, the value still tells that UDMA is actually > enabled. This is indeed a real hint that there is DMA. > (*) Well, patching uata driver to avoid DMA in atapi_ routines have > shown that same experiment, pread(2) with fixed offset in loop, delivers > not more than 2.7MBps at 95% of CPU time! I would not expect more than 4 MB/s for PIO > Even though above is about SPARC Solaris 8 I found no evidence that DMA > default settings for ATA would be different on SPARC Solaris 10 and even > OpenSolaris for SPARC. Unfortunately I have no opportunity to confirm > this experimentally. The conclusion is based on once observed > target?-dcd-options value on SPARC Solaris 10, comparison of binary code > for uata driver in all three releases, and on comparison of source code > for Solaris 8 and OpenSolaris. The variable atapi-cd-dma-enabled was introduced for Solaris 10. Before _all_ CDs always had no DMA. This is a result of a bad bugtracking entry made by a Sun employee who incorrectly claimed that there are problems when DMA is enabled. As with Solaris 8 and 9 DMA was never used for CDs, I published the related patch that worked fine for Solaris 8 and 9 until recentliy with a Sun provided patch. > In the course of discussion it was also implied that cdrecord's "Solaris > DMA related READMEs" are up-to-date with accuracy of 12 months and apply > to *all* Solaris releases. To summarize, the READMEs discuss binary They are as correct as they can be with the feedback from users... I do have negative feedback from two sysadmins who both have been unable to use a DVD writer on a sparc based system because of the lack of DMA and the fact that the writer did not like to enable burn-free if DMA is not active. Both could however confirm that using slow DVD-RW media at 2x write speed works. > patching of ata binary driver on Solaris 9 x86 as the only way to engage > DMA for optical ATAPI units. I don't recall when Solaris 10 was > released, but from my >4 years personal experience with Solaris 10 x86 > on Sun W1100z (Opteron-based workstation), it's perfectly possible to Opteron is not sparc... > control DMA setting for optical ATAPI unit with atapi-cd-dma-enabled > boot parameter and no binary patching is required. This applies even to > OpenSolaris for x86 (where it's even properly documented in ata(7d)). > Then there is enough evidence that the READMEs in question are not > applicable to [any recent] SPARC Solaris release. At the very least on > SPARC Solaris ATA is implemented by uata driver, which does not even > have ata_init_drive_pcidma subroutine. Not to mention above information > about DMA *defaults* for SPARC Solaris ATA support. A. As you could see, my patch is for sparc and you should know that with Solaris 11 DMA is finally used by default. If you have been able to do something that other people could not do before (using a DVD drive with DMA on a sparc system), it would be nice if you could tell us how you did manage this. Well, the last sparc related feedback I received is more than a years old, so it is possible that a recent Solaris 10 patch fixed the problem. I did use sparc based systems at my primary desktop between 1988 and December 2007. I did always run the latest OS version and I was never able to see DMA for a PATA based DVD writer. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>>> If you like to prove that there >>> are Sparc machines with Solaris that behave different from what all other >>> users >>> reported, please send the related information: >>> >>> - exactly describe the machine type, the OS release and the drive type. >> Information can be found in attachments. > > Looking through the information does unfortunately not show anything that > verifies the presence of DMA for the CD-ROM drive in question. Looking through the *requested* information does not show anything that verifies the presence *or absence* of DMA for the CD-ROM drive in question. SPARC Solaris does not tell a squat about DMA settings in /vad/adm/messages, 'eeprom' or 'prtconf -p' outputs. On the other hand, looking through the information provided *beyond* requested one allows to draw conclusion that DMA is *in fact* enabled for optical drive in question. Once again, target1-dcd-options is 0xa2 and more important read performance reaches 19MBps[!]. Indeed, there is no way venerable Blade-100 can deliver that much over PIO at *portion* of CPU power(*). As for value of 0xa2. Earlier I said that it denotes UDMA-2. As it turns out this was inaccurate. Upper bits, ones constituting 0xa?, do denote UDMA, but lower bits, ones constituting 0x?2, don't denote UDMA *mode*. Lower bits are meaningful when UDMA is disengaged and seem to denote PIO mode. In other words, while not being specific about UDMA mode, the value still tells that UDMA is actually enabled. (*) Well, patching uata driver to avoid DMA in atapi_ routines have shown that same experiment, pread(2) with fixed offset in loop, delivers not more than 2.7MBps at 95% of CPU time! Even though above is about SPARC Solaris 8 I found no evidence that DMA default settings for ATA would be different on SPARC Solaris 10 and even OpenSolaris for SPARC. Unfortunately I have no opportunity to confirm this experimentally. The conclusion is based on once observed target?-dcd-options value on SPARC Solaris 10, comparison of binary code for uata driver in all three releases, and on comparison of source code for Solaris 8 and OpenSolaris. All this naturally doesn't mean that all versions of SPARC Solaris *unconditionally* use DMA with ATAPI, but it's enough to conclude that originating "Solaris sparc still does not support DMA on ATA interfaces" is not justifiable. In the course of discussion it was also implied that cdrecord's "Solaris DMA related READMEs" are up-to-date with accuracy of 12 months and apply to *all* Solaris releases. To summarize, the READMEs discuss binary patching of ata binary driver on Solaris 9 x86 as the only way to engage DMA for optical ATAPI units. I don't recall when Solaris 10 was released, but from my >4 years personal experience with Solaris 10 x86 on Sun W1100z (Opteron-based workstation), it's perfectly possible to control DMA setting for optical ATAPI unit with atapi-cd-dma-enabled boot parameter and no binary patching is required. This applies even to OpenSolaris for x86 (where it's even properly documented in ata(7d)). Then there is enough evidence that the READMEs in question are not applicable to [any recent] SPARC Solaris release. At the very least on SPARC Solaris ATA is implemented by uata driver, which does not even have ata_init_drive_pcidma subroutine. Not to mention above information about DMA *defaults* for SPARC Solaris ATA support. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > Jörg, thank you for looking at this problem again. > > > Please send the output from cdrecord -minfo and cdrecord -atip > > # cdrecord dev=5,0,0 -minfo > Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) > scsidev: '5,0,0' > scsibus: 5 target: 0 lun: 0 > Warning: Using USCSI interface. > Using libscg version 'schily-0.9'. > Device type: Removable CD-ROM > Version: 0 > Response Format: 2 > Capabilities : > Vendor_info: 'HL-DT-ST' > Identifikation : 'BD-RE BH08LS20 ' > Revision : '1.00' > 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 LAYER_JUMP > 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 Data 0 -1 0 > > Last session start address: 0 > Last session leadout start address: 0 > This definitely _is_ the well known firmware bug in the LG drives that is already known for DVD- and DVD+ I would need to implement a workaround in cdrecord.. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Jörg, thank you for looking at this problem again. > Please send the output from cdrecord -minfo and cdrecord -atip # cdrecord dev=5,0,0 -minfo Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) scsidev: '5,0,0' scsibus: 5 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' 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 LAYER_JUMP 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 Data 0 -1 0 Last session start address: 0 Last session leadout start address: 0 # cdrecord dev=5,0,0 -atip Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) scsidev: '5,0,0' scsibus: 5 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' 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 LAYER_JUMP Disk type: 'BDR' (BD-R) Disk class: 01 Manufacturer: 'RITEK' Media type: 'BR2' Disk: is not in cartridge Media cartrige: write protect is off Free Spare Blocks: 0 Alloc Spare Blocks: 0 Capacity Blklen/Sparesz. Format-type Type 12219392 151552 0x00 Unformated or Blank Media 1182617612288 0x00 Reserved (0) 1182617612288 0x32 Reserved (0) 7369728 151552 0x32 Reserved (0) 12088320 4096 0x32 Reserved (0)
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > > Do you still have problems with cdrecord on Solaris ? > Thank you for asking Jörg. Today I made some progress. > Sorry I have not had time to look at the USB driver bug. > > Previously I was using the JMicron JM20336 USB-SATA bridge. > Now I have the JM20329, apparently a simpler (and slower) chip. > The BH08LS20 drive connected via USB 2.0, using blank BD-R disc. > > Now I no longer get the I/O errors for cdrecord -atip (or -v -minfo). > However, even though cdrecord -atip shows that the disc is blank, > when I try to burn, cdrecord gives "capacity is unknown" message. > > Please advise me what to try next. > Here is the output from the attempt to burn image to BD-R. > Below that is the output from -v -checkdrive. > > # cdrecord -v dev=5,0,0 speed=2 driveropts=burnfree image.iso > cdrecord: No write mode specified. > cdrecord: Assuming -sao mode. > cdrecord: If your drive does not accept -sao, try -tao. > cdrecord: Future versions of cdrecord may have different drive dependent > defaults. > Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) Copyright (C) > 1995-2009 J\366rg Schilling > TOC Type: 1 = CD-ROM > scsidev: '5,0,0' > scsibus: 5 target: 0 lun: 0 > Warning: Using USCSI interface. > Using libscg version 'schily-0.9'. > Driveropts: 'burnfree' > SCSI buffer size: 64512 > atapi: 0 > Device type: Removable CD-ROM > Version: 0 > Response Format: 2 > Capabilities : > Vendor_info: 'HL-DT-ST' > Identifikation : 'BD-RE BH08LS20 ' > Revision : '1.00' > Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. > Current: BD-R sequential recording > Profile: BD-ROM > Profile: BD-R sequential recording (current) > Profile: BD-R random recording > Profile: BD-RE > Profile: DVD-RAM > Profile: DVD-R sequential recording > Profile: DVD-R/DL sequential recording > Profile: DVD-R/DL layer jump recording > Profile: DVD-RW sequential recording > Profile: DVD-RW restricted overwrite > Profile: DVD+RW > Profile: DVD+R > Profile: DVD+R/DL > Profile: DVD-ROM > Profile: CD-R > Profile: CD-RW > Profile: CD-ROM > Profile: Removable Disk > Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). > Driver flags : NO-CD BD MMC-3 BURNFREE > Supported modes: PACKET SAO LAYER_JUMP > Drive buf size : 2097152 = 2048 KB > Drive pbuf size: 3932160 = 3840 KB > Drive DMA Speed: 3724 kB/s 21x CD 2x DVD 0x BD > FIFO size : 4194304 = 4096 KB > Track 01: data 14911 MB > Total size: 14911 MB = 7634764 sectors > Current Secsize: 2048 > cdrecord: Disk capacity is unknown. > cdrecord: Data will not fit on any CD. > cdrecord: DVD/BD capacity is unknown. > cdrecord: Cannot write more than remaining DVD/BD capacity. Please send the output from cdrecord -minfo and cdrecord -atip. It may be that your drive has similar firmware bugs for BD-* as we know for DVD-* and DVD+* Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
> Do you still have problems with cdrecord on Solaris ? Thank you for asking Jörg. Today I made some progress. Sorry I have not had time to look at the USB driver bug. Previously I was using the JMicron JM20336 USB-SATA bridge. Now I have the JM20329, apparently a simpler (and slower) chip. The BH08LS20 drive connected via USB 2.0, using blank BD-R disc. Now I no longer get the I/O errors for cdrecord -atip (or -v -minfo). However, even though cdrecord -atip shows that the disc is blank, when I try to burn, cdrecord gives "capacity is unknown" message. Please advise me what to try next. Here is the output from the attempt to burn image to BD-R. Below that is the output from -v -checkdrive. # cdrecord -v dev=5,0,0 speed=2 driveropts=burnfree image.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) Copyright (C) 1995-2009 J\366rg Schilling TOC Type: 1 = CD-ROM scsidev: '5,0,0' scsibus: 5 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-R sequential recording Profile: BD-ROM Profile: BD-R sequential recording (current) Profile: BD-R random recording Profile: BD-RE Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R Profile: CD-RW Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 2097152 = 2048 KB Drive pbuf size: 3932160 = 3840 KB Drive DMA Speed: 3724 kB/s 21x CD 2x DVD 0x BD FIFO size : 4194304 = 4096 KB Track 01: data 14911 MB Total size: 14911 MB = 7634764 sectors Current Secsize: 2048 cdrecord: Disk capacity is unknown. cdrecord: Data will not fit on any CD. cdrecord: DVD/BD capacity is unknown. cdrecord: Cannot write more than remaining DVD/BD capacity. -- # cdrecord dev=5,0,0 -v -checkdrive Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) Copyright (C) 1995-2009 J\366rg Schilling TOC Type: 1 = CD-ROM scsidev: '5,0,0' scsibus: 5 target: 0 lun: 0 Warning: Using USCSI interface. Using libscg version 'schily-0.9'. SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'BD-RE BH08LS20 ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-R sequential recording Profile: BD-ROM Profile: BD-R sequential recording (current) Profile: BD-R random recording Profile: BD-RE Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R Profile: CD-RW Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 2097152 = 2048 KB Drive pbuf size: 3932160 = 3840 KB Drive DMA Speed: 3731 kB/s 21x CD 2x DVD 0x BD
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: Thank you Thomas for suggesting things to try. > ... spoil your joy of success Let us not digress too much - remember my definition of success: # cdrecord dev=3,0,0 speed=2 driveropts=burnfree image.iso >>> try to burn it via growisofs >> I have no idea how long it took > Probably rather 4 to 5 hours I agree, but should only take 30 minutes, with no errors. > Does it mount? Yes, I can see all of my files on the Windows machine too. > Can you read all 7634768 blocks? Wow, dd is really slow. I am still waiting for results. Did you specify block size? Depending on several things, the addition of "bs=2M" (2MB) will make a bunch of difference. -- Bill Davidsen Unintended results are the well-earned reward for incompetence. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > That would be 24220008448 bytes (~24.2GB) > growisofs pre-formatted the disc for 24.8GB > It took approximately 85 minutes for the dd read, > so dd read the disc at a rate around 4.75 MBps. > Maybe not really really slow, but still slow. I am not sure how you computed the number but this is roughly 1x speed. > > CentOS experiment with growisofs > Yes, but now I need to focus on cdrecord on solaris10. > How will the CentOS experiment help me with that? Do you still have problems with cdrecord on Solaris or did you find a solution? Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov wrote: > >> When it comes to accuracy of information meant for general public, it's > >> difference between implying things and spelling them in manner that > >> can't be interpreted differently by different people. > >> > 1. According to 'man ata' DMA is enabled by default on Solaris 10. To my > experience with Sun W1100z it holds true. > >>> Whis this is true for Solaris 10 x86 and hard disks, it is definitely not > >>> true > >>> for the other. > >> Original statement was "Solaris 10 in general does not by default enable > >> DMA." Any sane person not intimately familiar with subject would > >> interpret that Solaris 10 never uses DMA by default. > > > > > > Well, we are talking about CD/DVD/BluRay writing and it should be obvious > > for a > > scientist, that remarks are done here with thede constraints in mind. > > General public is far from scientific. But even if it was, it would be > even more incentive to stick to most accurate formulations. > > > I cannot see statements of interest in the rest. If you like to prove that > > there > > are Sparc machines with Solaris that behave different from what all other > > users > > reported, please send the related information: > > > > - exactly describe the machine type, the OS release and the drive type. > > Information can be found in attachments. Looking through the information does unfortunately not show anything that verifies the presence of DMA for the CD-ROM drive in question. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, > 4.75 MBps. > Maybe not really really slow, but still slow. At least it is clear that you do not suffer from USB 1. My BD-R get read about as fast as they get written. So ~ 9 MB/s would be the right speed. > The only way to verify this is to traverse through all > of the files in the iso image (mounted loopback) and > diff them with files on the blu-ray disc. No thanks. > I trust that growisofs recorded properly. But your data transport behaves suspicious. If there is a problem between you computer USB controller and the media then it could show up by readable blocks with altered data. So i advise to compare both images. Divide the size of the image file on disk by 2048 to get number_of_blocks. Then do dd if=/dev/dsk/c3t0d0s0 \ bs=2048 \ count=$number_of_blocks \ | diff .../image_on_disk - The media quality itself is out of suspicion because you could read the whole formatted capacity without i/o error. > > CentOS experiment with growisofs > Yes, but now I need to focus on cdrecord on solaris10. > How will the CentOS experiment help me with that? It will make clear whether the drive and its cabeling is slow or whether the Solaris computer is to blame. (I am also not so sure that you will always have success with growisofs.) Nevertheless, if growisofs works reliably on Solaris then i would stay with it. It is the better expert for DVD and BD anyway. (But still i have no idea what cdrecord would do wrong in this special case.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>>> The iso file has size of 15635996672 bytes >> Can you read all 7634768 blocks? > Wow, dd is really slow # date Tue Oct 13 16:18:12 EDT 2009 # dd bs=2048 if=/dev/dsk/c3t0d0s0 of=/dev/null 11826176+0 records in 11826176+0 records out # date # Tue Oct 13 17:43:11 EDT 2009 That would be 24220008448 bytes (~24.2GB) growisofs pre-formatted the disc for 24.8GB It took approximately 85 minutes for the dd read, so dd read the disc at a rate around 4.75 MBps. Maybe not really really slow, but still slow. > What USB SATA bridge would be that slow? The same one that is fast on the windows machine. > whether the media delivers all recorded blocks The only way to verify this is to traverse through all of the files in the iso image (mounted loopback) and diff them with files on the blu-ray disc. No thanks. I trust that growisofs recorded properly. > CentOS experiment with growisofs Yes, but now I need to focus on cdrecord on solaris10. How will the CentOS experiment help me with that?
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> USB1 full-speed is 12Mbps or 1.5MBps, right? > I am using USB 2.0 ports - 480 Mbps or 60 MBps. I unfortunately have no personal experience with USB storage on SPARC Solaris and can't advice on how to verify if system actually negotiated USB2 Hi-speed for unit in question. My comment was merely about Thomas' calculations. > Burning DVDs on the Plextor PX-716UF drive using cdrecord > from my Solaris10 (sparc) machine is pretty fast. Yes, but it doesn't exclude possibility that system failed to negotiate anticipated rate for the other unit. Though as just mentioned, I can only speculate on the matter of USB under SPARC Solaris and you should take it as such. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Andy Polyakov wrote: > USB1 full-speed is 12Mbps or 1.5MBps, right? 0.2x4390KBps is around half > the speed... Yes. But 0.2x was the average. At the end the run was around 0.35x. Given a certain overhead in the USB bit stream this is slightly too much. But i just read from Rob, 5 Oct 2009: > Note that my blu-ray drive is connected to my system via USB 2.0 and Rob freshly: > Burning DVDs on the Plextor PX-716UF drive using cdrecord > from my Solaris10 (sparc) machine is pretty fast. For USB 2 this would be truly awful performance. > > Does it mount? > Yes, I can see all of my files on the Windows machine too. This means the first few MB of the image are readable. The bulk of file content is not tested by showing a sound directory tree. Readable file content should be unaltered. If you find content deviations without seeing i/o errors then the data was altered after leaving the realm of the burn program and before being burned to media. > Wow, dd is really slow. I am still waiting for results. That's really a riddle. What USB SATA bridge would be that slow ? > should only take 30 minutes, with no errors. On unformatted BD-R i achieve 9 MB/s = 28 minutes for 7634768 blocks. Plus preparations and post production. Yep. 30 minutes is realistic. With growisofs that would need option -use-the-force-luke=spare:none which Andy does mention but not recommend in http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/ With formatted BD-R you have to live with half speed. That's still about 4 times faster than what you experience now. >>> :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error > It's harmless bug. It was discussed earlier. A. Sorry for not paying attention. We are getting quite multithreaded from time to time. :)) Well, i am curious whether the media delivers all recorded blocks. A CentOS experiment with growisofs-7.1 would be interesting too. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> When it comes to accuracy of information meant for general public, it's
>> difference between implying things and spelling them in manner that
>> can't be interpreted differently by different people.
>>
1. According to 'man ata' DMA is enabled by default on Solaris 10. To my
experience with Sun W1100z it holds true.
>>> Whis this is true for Solaris 10 x86 and hard disks, it is definitely not
>>> true
>>> for the other.
>> Original statement was "Solaris 10 in general does not by default enable
>> DMA." Any sane person not intimately familiar with subject would
>> interpret that Solaris 10 never uses DMA by default.
>
>
> Well, we are talking about CD/DVD/BluRay writing and it should be obvious for
> a
> scientist, that remarks are done here with thede constraints in mind.
General public is far from scientific. But even if it was, it would be
even more incentive to stick to most accurate formulations.
> I cannot see statements of interest in the rest. If you like to prove that
> there
> are Sparc machines with Solaris that behave different from what all other
> users
> reported, please send the related information:
>
> - exactly describe the machine type, the OS release and the drive type.
Information can be found in attachments.
> - send information from "prtconf -pv"
Attached.
> - Send the kernel verbose information from /var/adm/messages that
> indicate that DMA was in fact enabled for the related drive
Boot log from /var/adm/messages is attached.
> - send the eeprom(1) output that indicates that the DMA is not disabled
> for CD-ROM type drive even though the low level kernel layers did
> set up DMA.
eeprom output can be found in attached 'prtconf -pv' output in "Node
0xf002d22c" section.
> - Send a "cdrecord -v -checkdrive" output for the drive that verifies
> that the drive is capable to do IO in a speed that requires DMA and thus
> indicates that DMA is really in effect.
Attached.
-
Now for the rest of subscribers. None of attached information tells DMA
story. As already mentioned on SPARC Solaris (at least up to 10)
negotiated ATA mode can be found in 'prtconf -v' output. Here is
relevant portion from system in question:
ide, instance #0
Driver properties:
name length <4>
value <0x00a2>.
name length <4>
value <0x00a4>.
name length <4>
value <0x00a4>.
Here target0 is system disk and target1 - optical unit. As already
mentioned 0xa2 stands for UDMA-2. This can be confirmed experimentally
by running for example perl -e '$sz=32*1024;
while(1){syscall(173,0,"?"x$sz,$sz,0)}' < /vol/rdsk/noname' against
recorded media and monitoring system with iostat. syscall(173) is
pread(2) and idea is to make unit deliver 1st 32KB from buffer over and
over again. Here is snippet from 'iostat 5' output:
ttydad0 sd0 nfs1 nfs2 cpu
tin tout kps tps serv kps tps serv kps tps serv kps tps serv us sy
wt id
0 16 0 00 19840 62010 000 00 10
11 79 0
0 48 2 12 19847 62010 000 009
11 80 0
0 16 0 00 19885 62110 000 006
11 83 0
0 16 0 00 19834 62010 000 009
12 79 0
sd0 is the optical unit and as per above it delivers almost 20MBps at
~11% system time. Writing naturally can't be performed at 20MBps, but 2x
DVD recording [with growisofs] consumes ~8% system time:
ttydad0 sd0 nfs1 nfs2 cpu
tin tout kps tps serv kps tps serv kps tps serv kps tps serv us sy
wt id
0 78 0 00 2752 9200 000 001
8 26 65
0 78 0 00 2900 9700 000 001
9 27 62
0 78 4 14 2694 9000 000 001
5 28 66
0 47 0 00 2854 9500 000 001
8 28 64
A.
System Configuration: Sun Microsystems sun4u
Memory size: 512 Megabytes
System Peripherals (PROM Nodes):
Node 0xf0029e64
boot-retained-page:
energystar-v3:
idprom:
.......
scsi-initiator-id: 0007
reset-reason: 'POR'
breakpoint-trap: 007f
#size-cells: 0002
model: 'SUNW,375-0096'
name: 'SUNW,Sun-Blade-100'
clock-frequency: 04fca6ea
banner-name: 'Sun Blade 100 (UltraSPARC-IIe)'
device_type: 'upa'
stick-frequency: 0054c563
Node 0xf002cff8
name: 'packages'
Node 0xf0047a58
name: 'SUNW,builtin-drivers'
Node 0xf0051a18
disk-write-fix:
name: 'deblocker'
Node 0xf0051efc
name: 'disk-label'
Node 0xf0052850
Re: solaris cdrecord BH08LS20 drive BD-R problems
> USB1 full-speed is 12Mbps or 1.5MBps, right? I am using USB 2.0 ports - 480 Mbps or 60 MBps. Burning DVDs on the Plextor PX-716UF drive using cdrecord from my Solaris10 (sparc) machine is pretty fast.
Re: solaris cdrecord BH08LS20 drive BD-R problems
Thank you Thomas for suggesting things to try. > ... spoil your joy of success Let us not digress too much - remember my definition of success: # cdrecord dev=3,0,0 speed=2 driveropts=burnfree image.iso >>> try to burn it via growisofs >> I have no idea how long it took > Probably rather 4 to 5 hours I agree, but should only take 30 minutes, with no errors. > Does it mount? Yes, I can see all of my files on the Windows machine too. > Can you read all 7634768 blocks? Wow, dd is really slow. I am still waiting for results.
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> Checked it this morning, seems to have finished, >> and I have no idea how long it took. >> builtin_dd: 7634768*2KB out @ average 0.2x4390KBps > > Not faster than 7634768*2/(0.3*4390) seconds. > 3 hours 13 minutes at least. Probably rather > 4 to 5 hours. > > Very slow. But at the end a bit too fast for > USB 1. So that theory seems invalid, too. USB1 full-speed is 12Mbps or 1.5MBps, right? 0.2x4390KBps is around half the speed... Also keep in mind that if wire speed is not sufficient to sustain media speed, unit will be forced to make idle revolutions and performance can drop to *portion* of wire speed. >> :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error > > Uh oh. It is still ill. It's harmless bug. It was discussed earlier. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Rob W: > Checked it this morning, seems to have finished, > and I have no idea how long it took. > builtin_dd: 7634768*2KB out @ average 0.2x4390KBps Not faster than 7634768*2/(0.3*4390) seconds. 3 hours 13 minutes at least. Probably rather 4 to 5 hours. Very slow. But at the end a bit too fast for USB 1. So that theory seems invalid, too. > :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error Uh oh. It is still ill. Can you read all 7634768 blocks from the BD-R ? dd if=/dev/...block.device... \ of=/dev/null \ bs=2048 count=7634768 Does it mount ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> try to burn it via growisofs > Seems to be working for growisofs > started it tonight with a 15+ GB iso Checked it this morning, seems to have finished, and I have no idea how long it took. The iso file has size of 15635996672 bytes. 15577645056/15635996672 (99.6%) @0.3x, remaining 1:05 RBU 100.1% UBU 50.0% 15582494720/15635996672 (99.7%) @0.3x, remaining 0:59 RBU 100.0% UBU 50.0% 15587442688/15635996672 (99.7%) @0.3x, remaining 0:54 RBU 100.0% UBU 50.0% 15592718336/15635996672 (99.7%) @0.4x, remaining 0:48 RBU 100.0% UBU 50.0% 15597174784/15635996672 (99.8%) @0.3x, remaining 0:43 RBU 100.0% UBU 50.0% 15602384896/15635996672 (99.8%) @0.3x, remaining 0:37 RBU 100.0% UBU 50.0% 15607660544/15635996672 (99.8%) @0.4x, remaining 0:31 RBU 84.5% UBU 50.0% 15612379136/15635996672 (99.8%) @0.3x, remaining 0:26 RBU 70.4% UBU 50.0% 15617753088/15635996672 (99.9%) @0.4x, remaining 0:20 RBU 54.4% UBU 50.0% 15622340608/15635996672 (99.9%) @0.3x, remaining 0:15 RBU 40.7% UBU 50.0% 15627681792/15635996672 (99.9%) @0.4x, remaining 0:09 RBU 24.8% UBU 50.0% 15632826368/15635996672 (100.0%) @0.3x, remaining 0:03 RBU 9.5% UBU 50.0% builtin_dd: 7634768*2KB out @ average 0.2x4390KBps /dev/rdsk/c3t0d0s0: flushing cache /dev/rdsk/c3t0d0s0: closing track /dev/rdsk/c3t0d0s0: closing session :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error
Re: solaris cdrecord BH08LS20 drive BD-R problems
Norbert Preining wrote: > On Di, 13 Okt 2009, Joerg Schilling wrote: > > As I already mentioned: the SCSI error message above was caused by a > > defective > > Solaris kernel module and is not a result from a problem in cdrecord. > > No WHAT? Solaris has a defective kernel module? Incredible! Wow ... I > have to post that on lkml, another of that pets of JS is fallable!!! We all know that you did never send anything besides trolling to this mailing list. Your mail has been counted, you do not need to confirm your attitude anymore in future - thank you for being quiet in future! Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > > try to burn it via growisofs > > Seems to be working for growisofs. > I started it tonight with a 15+ GB iso file. > Will follow up with error messages, if any. > Got to go now ... Please note: the fact that this works does not verfiy that it will always work. It seems that growisofs does some heuristiics where cdrecord just asks the drive and at this point becomes a victim of the kernel problems. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
On Di, 13 Okt 2009, Joerg Schilling wrote: > As I already mentioned: the SCSI error message above was caused by a > defective > Solaris kernel module and is not a result from a problem in cdrecord. No WHAT? Solaris has a defective kernel module? Incredible! Wow ... I have to post that on lkml, another of that pets of JS is fallable!!! Enjoy --- Dr. Norbert PreiningAssociate Professor JAIST Japan Advanced Institute of Science and Technology prein...@jaist.ac.jp Vienna University of Technology prein...@logic.at Debian Developer (Debian TeX Task Force)prein...@debian.org gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- WRITTLE (vb.) Of a steel ball, to settle into a hole. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov wrote: > >>> cdrecord: I/O error. read disk info: scsi sendcmd: no error > >>> CDB: 51 00 00 00 00 00 00 00 04 00 > >>> status: 0x0 (GOOD STATUS) > >>> resid: 4 > >> on Fri, 9 Oct 2009 22:12:35 -0400: > >>> # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 > >>> ... > >>> READ DISC INFORMATION: > >>> Disc status: blank > >>> Number of Sessions:1 > >>> State of Last Session: empty > >>> "Next" Track: 1 > >>> Number of Tracks: 1 > >> This time the same SCSI command worked. > >> I also assume it worked in NeroLinux. > > > > This is not necessarily the same command.. > > Cdrecord is implemented in compliance to the SCSI standard. > > Without knowing whether dvd+rw-mediainfo is implemented compliant to the > > SCSI standard, > > It feels ridiculous that I have to say this, but what choice do I have > facing FUD? I can assure general public that dvd+rw-media, as well as > growisofs, is compliant with SCSI standard (modulo > http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html). A. I am sorry to see that you obviously try to spread FUD. If this is rather caused by the fact that youn don't understand, please stay quiet or ask! Just to repease the important sentence: "This is not necessarily the same command.." Cdrecord does implement things in a way that forgives problems in the drive and that is as SCSI compliant as possible. If growisofs does some _heuristics_ instead of asking the drive the way the SCSI standard suggests, this may result in different SCSI commands. As I already mentioned: the SCSI error message above was caused by a defective Solaris kernel module and is not a result from a problem in cdrecord. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov wrote: > When it comes to accuracy of information meant for general public, it's > difference between implying things and spelling them in manner that > can't be interpreted differently by different people. > > >> 1. According to 'man ata' DMA is enabled by default on Solaris 10. To my > >> experience with Sun W1100z it holds true. > > > > Whis this is true for Solaris 10 x86 and hard disks, it is definitely not > > true > > for the other. > > Original statement was "Solaris 10 in general does not by default enable > DMA." Any sane person not intimately familiar with subject would > interpret that Solaris 10 never uses DMA by default. Well, we are talking about CD/DVD/BluRay writing and it should be obvious for a scientist, that remarks are done here with thede constraints in mind. I cannot see statements of interest in the rest. If you like to prove that there are Sparc machines with Solaris that behave different from what all other users reported, please send the related information: - exactly describe the machine type, the OS release and the drive type. - send information from "prtconf -pv" - Send the kernel verbose information from /var/adm/messages that indicate that DMA was in fact enabled for the related drive - send the eeprom(1) output that indicates that the DMA is not disabled for CD-ROM type drive even though the low level kernel layers did set up DMA. - Send a "cdrecord -v -checkdrive" output for the drive that verifies that the drive is capable to do IO in a speed that requires DMA and thus indicates that DMA is really in effect. If you could verify this, you would be the first person to do so! Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Rob W: > Seems to be working for growisofs. > 12058624/15635996672 ( 0.1%) @0.1x, remaining 518:15 RBU 100.0% UBU 50.0% I hate to spoil your joy of success but this looks still quite unhealthy. Formatted BD-R are darn slow in respect to their size. Nevertheless your speed 0.1x is less than 1 MB per second. Even with poor media you should get something like 0.4x to 1.0x and it should vary from report line to report line. Another suspicious info is UBU 50.0%. That means the drive is hungry for data or it decided not to use half of its built-in buffer memory. Did the burn really last 500 minutes ? Mine (with an older drive and 2x BD-R) last about 80 minutes formatted or 40 minutes unformatted (resp. with Streaming bit set in the write command). Can it be the drive is attached to a USB 1 controller ? (Those are not even fast enough for DVD burning.) I still do not believe that the difference between success and failure here is in the burn programs used. I would bet that one can get similar success from cdrecord and get the known failures from growisofs if one only tries often enough. (We shall not forget the failure with CentOS and NeroLinux and the success on MS-Windows.) A first challenge would be to unplug and replug the drive and to test whether it still works with growisofs afterwards. It would be interesting to see whether growisofs on the CentOS x86 machine performs better with the drive. I assume it is a PC not older than five years and thus equipped with USB 2. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
> try to burn it via growisofs Seems to be working for growisofs. I started it tonight with a 15+ GB iso file. Will follow up with error messages, if any. Got to go now ... # growisofs -Z /dev/rdsk/c3t0d0s0=image.iso Executing 'builtin_dd if=image.iso of=/dev/rdsk/c3t0d0s0 obs=32k seek=0' /dev/rdsk/c3t0d0s0: pre-formatting blank BD-R for 24.8GB... /dev/rdsk/c3t0d0s0: "Current Write Speed" is 8.2x4390KBps. 4194304/15635996672 ( 0.0%) @0.3x, remaining 186:20 RBU 100.0% UBU 50.0% 4194304/15635996672 ( 0.0%) @0.0x, remaining 434:48 RBU 100.0% UBU 100.0% 6160384/15635996672 ( 0.0%) @0.1x, remaining 422:51 RBU 100.0% UBU 50.0% 8126464/15635996672 ( 0.1%) @0.1x, remaining 416:40 RBU 100.0% UBU 50.0% 9240576/15635996672 ( 0.1%) @0.1x, remaining 479:08 RBU 100.0% UBU 50.0% 10092544/15635996672 ( 0.1%) @0.1x, remaining 516:05 RBU 100.0% UBU 100.0% 12058624/15635996672 ( 0.1%) @0.1x, remaining 518:15 RBU 100.0% UBU 50.0%
Re: solaris cdrecord BH08LS20 drive BD-R problems
>>> cdrecord: I/O error. read disk info: scsi sendcmd: no error >>> CDB: 51 00 00 00 00 00 00 00 04 00 >>> status: 0x0 (GOOD STATUS) >>> resid: 4 >> on Fri, 9 Oct 2009 22:12:35 -0400: >>> # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 >>> ... >>> READ DISC INFORMATION: >>> Disc status: blank >>> Number of Sessions:1 >>> State of Last Session: empty >>> "Next" Track: 1 >>> Number of Tracks: 1 >> This time the same SCSI command worked. >> I also assume it worked in NeroLinux. > > This is not necessarily the same command.. > Cdrecord is implemented in compliance to the SCSI standard. > Without knowing whether dvd+rw-mediainfo is implemented compliant to the > SCSI standard, It feels ridiculous that I have to say this, but what choice do I have facing FUD? I can assure general public that dvd+rw-media, as well as growisofs, is compliant with SCSI standard (modulo http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html). A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
When it comes to accuracy of information meant for general public, it's difference between implying things and spelling them in manner that can't be interpreted differently by different people. >> 1. According to 'man ata' DMA is enabled by default on Solaris 10. To my >> experience with Sun W1100z it holds true. > > Whis this is true for Solaris 10 x86 and hard disks, it is definitely not true > for the other. Original statement was "Solaris 10 in general does not by default enable DMA." Any sane person not intimately familiar with subject would interpret that Solaris 10 never uses DMA by default. If it was "Solaris 10 x86 does not by default enable DMA for *optical units*," then it wouldn't have been a problem. Extra point if it was complemented with "this unfortunately is not properly documented in Solaris 10 manual pages" and reference to more descriptive on-line resource (for example Solaris 11 manual page for ata(7d)). >> 2. 'man eeprom' does not provide any information about DMA settings. > > Make a bug report against the man page... Original statement was "see eeprom(1)" in context of "Solaris 10 in general does not by default enable DMA." Any sane person not intimately familiar with subject would expect to find additional information in eeprom manual page. She would find nothing there. If statement was "eeprom(1) command can be used to examine and modify atapi-cd-dma-enabled variable," then it wouldn't have been a problem (except for questionable relevance, because original question was about SPARC Solaris). Extra point for mentioning that the value might be missing and allowable values of 0 and 1. >> 3. SPARC Solaris *is* capable of DMA on ATA. To my experience it holds >> true on Solaris 8 with Pioneer DVR-106: CPU load and performance was >> adequate in my DVD recording tests and I never had any problems engaging >> buffer underrun protection. Negotiated settings for every device can be >> verified with 'prtconf -v'. > > Solaris 8 definitely does not set up DMA, but Solaris 8 is 10 years old and > I do no longer have a machine Original statement was "Solaris sparc *still* does not support DMA on ATA interfaces." Any sane person not intimately familiar with subject would interpret "still" as "*whatever* installed on SPARC next to me." Can *you* confirm the statement on *any* SPARC machine with 'prtconf -v'? > to check whether I could enable DMA by patching > the drivers. The READMEs mentioned above contain instructions on how to patch > the ata driver for Solaris 9 (x86), but this unfortunately only works for the > original release and will no longer help if you installed an ATA patch. What does it have to do with SPARC Solaris? > As mentioned before: Due to the fact that many DVD drives do not allow to set > burnproof in case DMA is not enabled, this is a major problem on > Solaris/sparc. Is it the only criteria to judge? As mentioned I had no problem [with growisofs] enabling burnproof on Pioneer DVR-106 on SPARC Solaris 8. What do you make of it? If it's not the only criteria, what are others? > As a result, I did get a lot of negative feedback from users that have been > unable to write DVDs. The only workaround is to use slow DVD-RW media that > allows to write slow enough to work without DMA. What units did these users have? What were target?-dcd-options in 'prtconv -v'? If burnproof is the only criteria, is it really appropriate to generalize these experiences to the extent of "SPARC Solaris *still* does not support DMA on *ATA* interfaces"? As for "Solaris DMA related READMEs" up-to-date-ness. They contain information exclusively about Solaris 9 x86. I can't verify its accuracy, but I can confirm that atapi-cd-dma-enabled parameter is effective on Solaris >=10 x86[!], i.e. no binary code patching is required. They don't contain a word about SPARC Solaris and are not applicable to SPARC Solaris. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
"Thomas Schmitt" wrote: > Nevertheless one can learn a lot from studying > the operations of dvd+rw-tools and looking > them up in the SCSI specs. then please do it ;-) Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Rob W: > > > cdrecord: I/O error. read disk info: scsi sendcmd: no error > > > CDB: 51 00 00 00 00 00 00 00 04 00 > > > # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 > > > READ DISC INFORMATION: me: > > This time the same SCSI command worked. Joerg Schilling: > Without knowing whether dvd+rw-mediainfo is implemented compliant to the > SCSI standard, it may be that it just makes a guess on how much data is > available and for unknown reasons does not fail. Excuse my surprise but which part of "READ DISC INFORMATION" don't you find in MMC-5 6.22 READ DISC INFORMATION Command ? (That's the one with Operation Code 0x51 which cdrecord reports in its "CDB" message.) One does not even have to read the source of dvd+rw-mediainfo to see that its output is organized by SCSI commands and reports the typical keywords from SCSI specs. Nevertheless one can learn a lot from studying the operations of dvd+rw-tools and looking them up in the SCSI specs. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
"Thomas Schmitt" wrote: > Rob W on Mon, 5 Oct 2009 20:55:55 -0400: > > cdrecord: I/O error. read disk info: scsi sendcmd: no error > > CDB: 51 00 00 00 00 00 00 00 04 00 > > status: 0x0 (GOOD STATUS) > > resid: 4 > > on Fri, 9 Oct 2009 22:12:35 -0400: > > # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 > > ... > > READ DISC INFORMATION: > > Disc status: blank > > Number of Sessions:1 > > State of Last Session: empty > > "Next" Track: 1 > > Number of Tracks: 1 > > This time the same SCSI command worked. > I also assume it worked in NeroLinux. This is not necessarily the same command.. Cdrecord is implemented in compliance to the SCSI standard. Without knowing whether dvd+rw-mediainfo is implemented compliant to the SCSI standard, it may be that it just makes a guess on how much data is available and for unknown reasons does not fail. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > >> Will dvd+rw-mediainfo work on solaris 10 (sparc) ? > > you ought to use character-type device entry > > OK, it looks like it worked, and the results are below > > However, cdrecord -minfo still reports End Addr = -1 > Maybe I have some installation problems > solaris10 came with an older version of cdrecord > Perhaps the new cdrecord is linking in old shared libs? If your drive returns -1 although there is a recorded session, it looks like your drive has a firmware bug. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Rob W on Mon, 5 Oct 2009 20:55:55 -0400: > cdrecord: I/O error. read disk info: scsi sendcmd: no error > CDB: 51 00 00 00 00 00 00 00 04 00 > status: 0x0 (GOOD STATUS) > resid: 4 on Fri, 9 Oct 2009 22:12:35 -0400: > # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 > ... > READ DISC INFORMATION: > Disc status: blank > Number of Sessions:1 > State of Last Session: empty > "Next" Track: 1 > Number of Tracks: 1 This time the same SCSI command worked. I also assume it worked in NeroLinux. > 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 Seems ready for being written and worth a try to burn it via growisofs. man growisofs proposes for a single session with a preformatted image: growisofs -dvd-compat -Z /dev/dvd=image.iso You will have to read Andy's hints for Solaris and replace "/dev/dvd" by the appropriate device path. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> Will dvd+rw-mediainfo work on solaris 10 (sparc) ? > you ought to use character-type device entry OK, it looks like it worked, and the results are below However, cdrecord -minfo still reports End Addr = -1 Maybe I have some installation problems solaris10 came with an older version of cdrecord Perhaps the new cdrecord is linking in old shared libs? # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 INQUIRY:[HL-DT-ST][BD-RE BH08LS20 ][1.00] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Current Write Speed: 8.0x4495=35964KB/s Write Speed #0:8.0x4495=35964KB/s Write Speed #1:6.0x4495=26973KB/s Write Speed #2:4.0x4495=17982KB/s Write Speed #3:2.0x4495=8991KB/s GET [CURRENT] PERFORMANCE: Write Performance: 3.3x4495=14881KB/s...@0 -> 8.0x4495=35964KB/s...@12219391 Speed Descriptor#0:02/12219391 r...@3.3x4495=14881kb/s w...@8.0x4495 =35964KB/s Speed Descriptor#1:02/12219391 r...@3.3x4495=14881kb/s w...@6.0x4495 =26973KB/s Speed Descriptor#2:02/12219391 r...@3.3x4495=14881kb/s w...@4.0x4495 =17982KB/s Speed Descriptor#3:02/12219391 r...@3.3x4495=14881kb/s w...@2.0x4495=8991kb/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(3000): 11826176*2048=24220008448 32h(25000):7369728*2048=15093202944 32h(1000): 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: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > Thanks again Jörg. I have not given up on solaris yet. > > > > Here are the errors I see with cdrecord -atip ... > > In this case ... is not related to the media but to the USB drivers > > This is a Solaris USB kernel driver bug ... > > Do you remember the bug tracking ID so I can look at it? > Perhaps someone has worked that issue for the opensolaris project, > but more than likely the fixes would not work on sparc hardware. It is Bug ID 6800130. There are several issues: - There is a problem that is caused from not honoring timeouts correctly. - There is a problem with some commands that do not set up DMA (i.e. do not send or receive any data). - There is a problem with commands that try to receive an odd number of bytes of data. - The returned error information from such commands is illegal and this is why your SCSI error message looks strange. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov wrote: > > As you might know, I send accurate information, so what is your issue? > > It's not a forum for discussing "my issues." If you want to continue > discussion, counterargument following: Why do you then bring up your issues that seem to be caused by incorrect information at your side? If you carefully read the Solaris DMA related REAMDEs from cdrtools-2.01, you could get the related information. > 1. According to 'man ata' DMA is enabled by default on Solaris 10. To my > experience with Sun W1100z it holds true. Whis this is true for Solaris 10 x86 and hard disks, it is definitely not true for the other. > 2. 'man eeprom' does not provide any information about DMA settings. Make a bug report against the man page... > 3. SPARC Solaris *is* capable of DMA on ATA. To my experience it holds > true on Solaris 8 with Pioneer DVR-106: CPU load and performance was > adequate in my DVD recording tests and I never had any problems engaging > buffer underrun protection. Negotiated settings for every device can be > verified with 'prtconf -v'. A. Solaris 8 definitely does not set up DMA, but Solaris 8 is 10 years old and I do no longer have a machine to check whether I could enable DMA by patching the drivers. The READMEs mentioned above contain instructions on how to patch the ata driver for Solaris 9 (x86), but this unfortunately only works for the original release and will no longer help if you installed an ATA patch. As mentioned before: Due to the fact that many DVD drives do not allow to set burnproof in case DMA is not enabled, this is a major problem on Solaris/sparc. As a result, I did get a lot of negative feedback from users that have been unable to write DVDs. The only workaround is to use slow DVD-RW media that allows to write slow enough to work without DMA. Unless this changed during the past 12 months (and this would of curse only be possible for Solaris 10 that is still in maintenance), my information is of course correct and up to date. Hope this helps. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Rob W wrote: > The BH08LS20 drive has SATA interface, and the enclosure uses > an adapter with the JMicron JM20336 USB - SATA bridge. I got my BD drives attached in a similar way. The bridge controllers are from JMicron, too: /var/log/boot.msg of my Linux 2.6.18.2-34-default: <6>usb 1-5: new high speed USB device using ehci_hcd and address 3 <6>usb 1-5: new device found, idVendor=152d, idProduct=2338 <6>usb 1-5: new device strings: Mfr=1, Product=2, SerialNumber=5 <6>usb 1-5: Product: USB to ATA/ATAPI Bridge <6>usb 1-5: Manufacturer: JMicron <6>usb 1-5: SerialNumber: 528860D21142 I would assume that this resembles much your situation on the CentOS machine. The drives work fine (although i suspect that the USB-SATA transport hampers 16x DVD+R speed). Those bridge controllers came in USB boxes by Conceptronic, model CiS525U. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> > Will dvd+rw-mediainfo work on solaris 10 (sparc) ? >> It hasn't been tested on SPARC Solaris 10, but ... > > Andy, thank you for your helpful suggestions. > Unfortunately, I could not get dvd+rw-mediainfo to work. > > It fails on one of the ioctl() calls in Scsi_Command::associate() > # dvd+rw-mediainfo /dev/dsk/c4t0d0s0 > /dev/dsk/c4t0d0s0: unable to open: Inappropriate ioctl for device As http://fy.chalmers.se/~appro/linux/DVD+RW/ hints, you ought to use character-type device entry. i.e. /dev/rdsk/c4t0d0s0 in this case (note rdsk as opposite to dsk). A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Thanks again Jörg. I have not given up on solaris yet. > > Here are the errors I see with cdrecord -atip ... > In this case ... is not related to the media but to the USB drivers > This is a Solaris USB kernel driver bug ... Do you remember the bug tracking ID so I can look at it? Perhaps someone has worked that issue for the opensolaris project, but more than likely the fixes would not work on sparc hardware. > It may help to try out a different USB<->ATA/SATA adaptor Yes, especially since it does not work quite right for linux either. The BH08LS20 drive has SATA interface, and the enclosure uses an adapter with the JMicron JM20336 USB - SATA bridge. Now looking for a different adapter for experimentation. Perhaps solaris10 is trying to send SMART commands to the drive? The wiki for smartmontools says this is tricky for USB bridges. http://sourceforge.net/apps/trac/smartmontools/wiki/USB Another idea: could AHCI mode be a factor here? I found some interesting reading at the linux-ide archives: http://markmail.org/message/qfcwybk6z6nd3rh6
Re: solaris cdrecord BH08LS20 drive BD-R problems
> > Will dvd+rw-mediainfo work on solaris 10 (sparc) ? > It hasn't been tested on SPARC Solaris 10, but ... Andy, thank you for your helpful suggestions. Unfortunately, I could not get dvd+rw-mediainfo to work. It fails on one of the ioctl() calls in Scsi_Command::associate() # dvd+rw-mediainfo /dev/dsk/c4t0d0s0 /dev/dsk/c4t0d0s0: unable to open: Inappropriate ioctl for device Here is how I built your tools: $ echo $PATH /usr/bin:/usr/local/bin:/usr/sfw/bin:/usr/ccs/bin $ make CC -O -features=no%except,conststrings -w -D_REENTRANT -c \ -o growisofs_mmc.o growisofs_mmc.cpp cc -O -xstrconst -w -D_REENTRANT -D__`uname -s`=`uname -r | tr -d .` \ -c -o growisofs.o growisofs.c CC -O -features=no%except,conststrings -w -D_REENTRANT \ -o growisofs growisofs_mmc.o growisofs.o -staticlib=%all \ -lvolmgt -lrt -lpthread -ldl CC -O -features=no%except,conststrings -w -D_REENTRANT \ -c -o dvd+rw-format.o dvd+rw-format.cpp CC -O -features=no%except,conststrings -w -D_REENTRANT \ -o dvd+rw-format dvd+rw-format.o -staticlib=%all \ -lvolmgt -lrt -lpthread -ldl CC -O -features=no%except,conststrings -w -D_REENTRANT \ -c -o dvd+rw-booktype.o dvd+rw-booktype.cpp CC -O -features=no%except,conststrings -w -D_REENTRANT \ -o dvd+rw-booktype dvd+rw-booktype.o -staticlib=%all \ -lvolmgt -lrt -lpthread -ldl CC -O -features=no%except,conststrings -w -D_REENTRANT \ -c -o dvd+rw-mediainfo.o dvd+rw-mediainfo.cpp CC -O -features=no%except,conststrings -w -D_REENTRANT \ -o dvd+rw-mediainfo dvd+rw-mediainfo.o -staticlib=%all \ -lvolmgt -lrt -lpthread -ldl CC -O -features=no%except,conststrings -w -D_REENTRANT \ -c -o dvd-ram-control.o dvd-ram-control.cpp CC -O -features=no%except,conststrings -w -D_REENTRANT \ -o dvd-ram-control dvd-ram-control.o -staticlib=%all \ -lvolmgt -lrt -lpthread -ldl
Re: solaris cdrecord BH08LS20 drive BD-R problems
> Note that Solaris sparc still does not support DMA on ATA interfaces. It's natural to expect that "still" means from oldest SPARC Solaris implementing support for IDE through latest, isn't it? Well, I can't speak for oldest and latest ones, but otherwise SPARC Solaris is capable of DMA on ATA interfaces to my knowledge. Negotiated value is reflected in targetN-dcd-options in prtconf -v output. Value of 0x00a2 is common for optical media units and denotes UDMA-2 mode. >>> I am not sure about what you are interested in >> Accuracy of information provided to the public. > > As you might know, I send accurate information, so what is your issue? It's not a forum for discussing "my issues." If you want to continue discussion, counterargument following: 1. According to 'man ata' DMA is enabled by default on Solaris 10. To my experience with Sun W1100z it holds true. 2. 'man eeprom' does not provide any information about DMA settings. 3. SPARC Solaris *is* capable of DMA on ATA. To my experience it holds true on Solaris 8 with Pioneer DVR-106: CPU load and performance was adequate in my DVD recording tests and I never had any problems engaging buffer underrun protection. Negotiated settings for every device can be verified with 'prtconf -v'. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov wrote: > >>> Note that Solaris sparc still does not support DMA on ATA interfaces. > >> It's natural to expect that "still" means from oldest SPARC Solaris > >> implementing support for IDE through latest, isn't it? Well, I can't > >> speak for oldest and latest ones, but otherwise SPARC Solaris is capable > >> of DMA on ATA interfaces to my knowledge. Negotiated value is reflected > >> in targetN-dcd-options in prtconf -v output. Value of 0x00a2 is > >> common for optical media units and denotes UDMA-2 mode. > > > > I am not sure about what you are interested in > > Accuracy of information provided to the public. A. As you might know, I send accurate information, so what is your issue? Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Andy Polyakov wrote: > consequently non-CD-ROM multi-sessioning is not an option. Pity. This operating system needs help. >From googling i understand that CD/DVD/BD drives on Solaris are readable as block devices. (Up to now i tried xorriso on Solaris only with disk files. Testers would be highly welcome.) xorriso can copy files out of ISO images and it has provisions to scan for ISO "sessions" in alleged -ROM media which show only one track. I have widened this feature so that it will work with disk files and block devices too. xorriso -rom_toc_scan force \ -indev stdio:/dev/sr1 \ -toc \ (On Linux i have to disable MMC processing by prefix "stdio:". On Solaris the lack of libburn MMC transport will have the same effect.) On my test BD-R this recognizes all 60 sessions and loads the last one. Next it could extract files to hard disk: -extract It also works with DVD-R (7 sessions), DVD+R (5 sessions), and an USB stick (22 sessions). My record holder is this daily backup BD-R: libisoburn: UPDATE : Found 307 ISO sessions by scanning 109 MB in 58 seconds xorriso : NOTE : Loading ISO image tree from LBA 6978304 (Extreme media need extreme patience. The long scan time is due to the poor random access performance of my BD drives. The 109 MB consist mainly of 307 times 150 sectors of padding. One could reduce that by option -no-pad when writing new sessions. But it won't give much more scan speed.) If Solaris command mount_hsfs had an option to address the superblock (like Linux mount -o sbsector=...) then xorriso could compose a mount command line which would allow to access the most recent session via the Solaris filesystem. But i found no such option in web versions of man mount(1) or mount_hsfs(1M). Anybody has a better Solaris than that ? (If so, see xorriso option -session_string for composing an own mount command.) Test version of xorriso: http://scdbackup.sourceforge.net/xorriso-0.4.3.tar.gz with timestamp 2009.10.07.080042 or newer. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> On a side note for reference. >> My system is loaded with one of the newer versions of solaris 10 $ uname -a SunOS my_machine 5.10 Generic_139555-08 sun4u sparc sun4u >>> >>> Note that Solaris 10 in general does not by default enable DMA >> It's natural to expect that "Solaris 10 in general" covers x86, isn't? >> Quoting 'man ata' from Solaris 10: >> >> Direct Memory Access (DMA) and PCI-IDE Systems >> Direct Memory Access is enabled by default. To disable DMA >> ... >> >>> but you need it >>> for writing. See eeprom(1) >> eeprom(1) manual page contains no mention of DMA. >> >>> Note that Solaris sparc still does not support DMA on ATA interfaces. >> It's natural to expect that "still" means from oldest SPARC Solaris >> implementing support for IDE through latest, isn't it? Well, I can't >> speak for oldest and latest ones, but otherwise SPARC Solaris is capable >> of DMA on ATA interfaces to my knowledge. Negotiated value is reflected >> in targetN-dcd-options in prtconf -v output. Value of 0x00a2 is >> common for optical media units and denotes UDMA-2 mode. > > I am not sure about what you are interested in Accuracy of information provided to the public. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
>> It won't work in the sense that data >> recorded on later occasions won't be available on Solaris (it should be >> available on Linux though). In order to make it work on Solaris media >> has to be formatted for POW (see >> http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/) and recording has to >> be treated in special manner (growisofs and xorriso do this, > > So Solaris does really not inquire DISC INFO > and TRACK INFO to find the "superblock" ? Correct, Solaris does not inquire this information and consequently non-CD-ROM multi-sessioning is not an option. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov wrote: > On a side note for reference. > > >> My system is loaded with one of the newer versions of solaris 10 > >> $ uname -a > >> SunOS my_machine 5.10 Generic_139555-08 sun4u sparc sun4u > > > > > > Note that Solaris 10 in general does not by default enable DMA > > It's natural to expect that "Solaris 10 in general" covers x86, isn't? > Quoting 'man ata' from Solaris 10: > > Direct Memory Access (DMA) and PCI-IDE Systems > Direct Memory Access is enabled by default. To disable DMA > ... > > > but you need it > > for writing. See eeprom(1) > > eeprom(1) manual page contains no mention of DMA. > > > Note that Solaris sparc still does not support DMA on ATA interfaces. > > It's natural to expect that "still" means from oldest SPARC Solaris > implementing support for IDE through latest, isn't it? Well, I can't > speak for oldest and latest ones, but otherwise SPARC Solaris is capable > of DMA on ATA interfaces to my knowledge. Negotiated value is reflected > in targetN-dcd-options in prtconf -v output. Value of 0x00a2 is > common for optical media units and denotes UDMA-2 mode. A. I am not sure about what you are interested in The last time I checked Solaris on sparc, I was unable to write a DVD because of the lack of DMA support for ATA. Note that in order to be able to enable burnproof, most drives require DMA to be enabled too. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Andy Polyakov wrote: > It won't work in the sense that data > recorded on later occasions won't be available on Solaris (it should be > available on Linux though). In order to make it work on Solaris media > has to be formatted for POW (see > http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/) and recording has to > be treated in special manner (growisofs and xorriso do this, So Solaris does really not inquire DISC INFO and TRACK INFO to find the "superblock" ? libburn does not yet use BD-R SRM+POW but only SRM-POW. I.e. BD-R recording with libburn is much like DVD+R. That's because i do not want to give up the capability to access all older states of a multi-session media. This would require some adaptions of growisofs's SRM+POW method. My best idea up to now is a first track solely for the copied System Area and Volume descriptors and to use the second track for the first ISO "session". This way the Volume Descriptors of the first ISO "session" would survive the pseudo-overwritings of following ISO "sessions". All ISO "session" start addresses could be inquired as track start addresses. Problem is that experiments with BD-R are still quite expensive. (I also need to re-read everything we discussed in november 2008 under "Re: BD-R formatting help". Is it mandatory not to close the MMC session ?) Have a nice day :) -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote:
> Note that my blu-ray drive is connected to my system via USB 2.0
> I do not understand why DMA settings may be a problem for cdrecord.
> With cdrecord I can write to DVD (Plextor PX-716UF) over USB 2.0
See below
> Memorex (actually RITEK) is definitely not the highest quality media.
> However, cdrecord -minfo gives the same result with Verbatim discs.
-minfo may give the same results even while you use completely different media.
The media manufacturer and media sub-types are displayed by cdrecord -atip
> Here are the errors I see with the cdrecord -atip command:
In this case (-atip), your problem is not related to the media but to
the USB drivers.
> # cdrecord dev=3,0,0 -atip
>
> Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10)
> scsidev: '3,0,0'
> scsibus: 3 target: 0 lun: 0
> Warning: Using USCSI interface.
> Using libscg version 'schily-0.9'.
> Device type: Removable CD-ROM
> Version: 0
> Response Format: 2
> Capabilities :
> Vendor_info: 'HL-DT-ST'
> Identifikation : 'BD-RE BH08LS20 '
> Revision : '1.00'
> 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 LAYER_JUMP
> Disk type: 'BDR' (BD-R)
> Disk class: 01
> Manufacturer: 'RITEK'
> Media type: 'BR2'
> Disk: is not in cartridge
> Media cartrige: write protect is off
> {{{ ... gets_hung_for_long_time ... }}}
> cdrecord: I/O error. read disk info: scsi sendcmd: no error
> CDB: 51 00 00 00 00 00 00 00 04 00
> status: 0x0 (GOOD STATUS)
> resid: 4
> cmd finished after 0.029s timeout 240s
> cdrecord: Cannot get disk type.
> cdrecord: I/O error. prevent/allow medium removal: scsi sendcmd: no error
> CDB: 1E 00 00 00 00 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 0.039s timeout 100s
This is a Solaris USB kernel driver bug that I reported a year ago and that
does not seem to get fixed. It may help to try out a different USB<->ATA/SATA
adaptor.
> The next time I try to use cdrecord, it tells me to power cycle the drive.
It is sufficient to replug the USB cable to "fix" the hang inside the kernel.
> This LG drive (and Memorex media) works using Power2Go on Windows,
> but I need to use the drive to archive data on my solaris sparc machines.
> Please help me to get cdrecord able to read the media correctly,
> and then perhaps get it to write my ISO images to blu-ray discs.
You may try to use the USB adaptor from the Plextor drive ;-)
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de(uni)
joerg.schill...@fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > Thomas, thank you for suggesting dvd+rw-tools-7.1 > > Will dvd+rw-mediainfo work on solaris 10 (sparc) ? cdrecord -atip works, to get some more information, add -v Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, i read Rob W's mail to Joerg: > This LG drive (and Memorex media) works using Power2Go on Windows, > but I need to use the drive to archive data on my solaris sparc > machines. So forget my challenge to the drive seller. Is the CentOS x86 machine a different one than the Windows machine ? Ok, need to reconsider: There is no hard reason why a drive and a particular media should work with Windows and not with Solaris or Linux. I am quite sure that NeroLinux was tested with BD-R. I can write BD-R via a LG BD-RE GGW-H20L on Linux. NeroLinux reported a write error with no error indication from the drive. Can it be that not the drive is ill but the transport ? Out of suspicion for now are the machines (2 different ones failing). But what about the USB cable and the USB controller of the drive ? Does it help to unplug and replug the cable at both ends ? Is the success with Windows really reproducible in several attempts ? (I once hunted a bug with DVD-RW where cdrecord seemed to work ok, and libburn seemed to fail. After eight attempts, cdrecord began to fail and libburn began to show successes. Shrug.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
On a side note for reference. >> My system is loaded with one of the newer versions of solaris 10 >> $ uname -a >> SunOS my_machine 5.10 Generic_139555-08 sun4u sparc sun4u > > > Note that Solaris 10 in general does not by default enable DMA It's natural to expect that "Solaris 10 in general" covers x86, isn't? Quoting 'man ata' from Solaris 10: Direct Memory Access (DMA) and PCI-IDE Systems Direct Memory Access is enabled by default. To disable DMA ... > but you need it > for writing. See eeprom(1) eeprom(1) manual page contains no mention of DMA. > Note that Solaris sparc still does not support DMA on ATA interfaces. It's natural to expect that "still" means from oldest SPARC Solaris implementing support for IDE through latest, isn't it? Well, I can't speak for oldest and latest ones, but otherwise SPARC Solaris is capable of DMA on ATA interfaces to my knowledge. Negotiated value is reflected in targetN-dcd-options in prtconf -v output. Value of 0x00a2 is common for optical media units and denotes UDMA-2 mode. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
> Thomas, thank you for suggesting dvd+rw-tools-7.1 > > Will dvd+rw-mediainfo work on solaris 10 (sparc) ? It hasn't been tested on SPARC Solaris 10, but it was tested on SPARC Solaris 8 and x86 Solaris 10 and 11 (latter a.k.a. OpenSolaris). In other words there is no reason to believe that it wouldn't work on SPARC Solaris 10. Naturally provided that your unit generally works with Solaris. > I am definitely interested in the capabilities of growisofs. If you're into incremental BD-R recordings, then there is one thing to remember. Media originally recorded by cdrecord won't work for incremental recordings on Solaris. It won't work in the sense that data recorded on later occasions won't be available on Solaris (it should be available on Linux though). In order to make it work on Solaris media has to be formatted for POW (see http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/) and recording has to be treated in special manner (growisofs and xorriso do this, but latter is not available on Solaris). Rule of thumb is if you stick to growisofs, then incremental recordings should work everywhere. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, > Will dvd+rw-mediainfo work on solaris 10 (sparc) ? Afaik, it works on Solaris. In growisofs.c i read: * 5.6: ... * - Solaris 2.x support is merged, it's volume manager aware, i.e. * you can run it with or without volume manager; (5.6 is several years old. Current is 7.1.) > if not solaris, then on linux. On Linux i could offer my own burn software. :)) > > Do you get a different -minfo output from a BD-R > > which never was involved in a failed write attempt ? > NO, the results were the same. > I do not believe cdrecord even tried to write anything. If the media is in that state at first use then indeed cdrecord is not a suspect here. > I did try NeroLinux 4 on a CentOS 5.3 (x86) machine. > However, when I tried to burn, it failed with errors. > Perhaps maybe helpful, the log file is attached. And there are people who say that open source error messages are hard to read. :)) > 01:37:49 AM #22 SCSI -1 File SCSIInterface.cpp, Line 624 > SCSI Exec, HA 2, TA 0, LUN 0, buffer 0x0xab9cd040 > Status: 0x04 (0x01, SCSI_ERR) > HA-Status 0x00 (0x00, OK) > TA-Status 0x00 (0x00, OK) > Sense Key: 0x00 (KEY_NO_SENSE) > Sense Code: 0x00 > Sense Qual: 0x00 > CDB Data: 0x2A 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x20 0x00 0x00 > 0x00 Command 2Ah is the WRITE command. It fails at the attempt to write 32 blocks to address 0. The drive does not tell a plausible reason. This drive behavior is not ok. So currently no burn program seems to be able to write to your media via your drive. To find out which of them is ill, you will have to try other media with the same drive and/or the reluctant media with a different drive. In your situation i would consider to challenge the seller of the drive to prove that it burns BD-R with at least one burn program on at least one operating system. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Thomas, thank you for suggesting dvd+rw-tools-7.1 Will dvd+rw-mediainfo work on solaris 10 (sparc) ? I am definitely interested in the capabilities of growisofs. Hope to try it soon - if not solaris, then on linux. > Do you get a different -minfo output from a BD-R > which never was involved in a failed write attempt ? NO, the results were the same. I do not believe cdrecord even tried to write anything. > Did you try BD-RE yet ? I do not have BD-RE, and do not planned to use it. My application is for long term archives to blu-ray discs, and for now I am focusing on sparc solaris 10 machines. I did try NeroLinux 4 on a CentOS 5.3 (x86) machine. After trouble getting the device set up properly (/dev/scd0) nero was able to recognize the drive and read disc info. However, when I tried to burn, it failed with errors. Perhaps maybe helpful, the log file is attached. 8M1K-2084-HZM6-A9L4-5HAM-065W-- Linux (CentOS release 5.3 (Final)) 2.6.18-164.el5 (i686) Nero API version: 9.7.0.132 Using interface version: 9.0.1.4 Installed in: /usr/lib/nero/ Application: Nero AG\Nero Linux Internal Version: 9, 7, 0, 132 Recorder: Version: 1.00 - HA 2 TA 0 - 0.0.0.0 Adapter driver: HA 2 Drive buffer : 4096kB Bus Type : via Inquiry data Excluded drive IDs: WriteBufferSize: 83886080 (0) Byte BUFE : 0 Physical memory : 1010MB (1035080kB) Free physical memory: 337MB (346000kB) Memory in use : 66 % Uncached PFiles: 0x0 Global Bus Type: default (0) Check supported media : Disabled (0) 2.10.2009 NeroAPI 01:36:38 AM #1 Text 0 File Burncd.cpp, Line 3647 Turn on Disc-At-Once, using Blu-ray Disc media 01:36:40 AM #2 Text 0 File DlgWaitCD.cpp, Line 313 Total disc capacity: 1221939223866MB User data to be written: 3895340 7608MB Free space on disc: 1221939223866MB 01:36:40 AM #3 Text 0 File DlgWaitCD.cpp, Line 325 Write in overburning mode: NO 01:36:40 AM #4 Text 0 File DlgWaitCD.cpp, Line 2856 Recorder: HL-DT-ST BD-RE BH08LS20, Media type: BD-R (seq) 01:36:40 AM #5 Text 0 File DlgWaitCD.cpp, Line 500 >>> Protocol of DlgWaitCD activities: <<< = 01:36:40 AM #6 Text 0 File ThreadedTransferInterface.cpp, Line 734 Setup items (after recorder preparation) 0: TRM_DATA_MODE1 (2 - CD-ROM Mode 1, Joliet) 2 indices, index0 (150) not provided original disc pos #0 + 3895340 (3895340) = #3895340/865:37.65 not relocatable, disc pos for caching/writing not required/not required -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 3895340 blocks [HL-DT-ST BD-RE BH08LS20 (H:2 T:0)] -- 01:36:40 AM #7 Text 0 File ThreadedTransferInterface.cpp, Line 936 Prepare [HL-DT-ST BD-RE BH08LS20 (H:2 T:0)] for write in CUE-sheet-DAO DAO infos: == MCN: "" TOCType: 0x00; Session Closed, disc fixated Tracks 1 to 1: Idx 0 Idx 1 Next Trk 1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 7977656320, ISRC "" DAO layout: === ___Start_|Track_|_Idx_|_CtrlAdr_|_Size_|__NWA_|_RecDep__ 0 | lead-in | 0 |0x41 |0 |0 | 0x00 0 |1 | 0 |0x41 |0 |0 | 0x00 0 |1 | 1 |0x41 | 3895340 | 3895340 | 0x00 3895340 | lead-out | 1 |0x41 |0 |0 | 0x00 01:36:40 AM #8 Text 0 File Burncd.cpp, Line 4354 Caching options: cache CDRom or Network-No, small files-Yes (<32KB) 01:36:40 AM #9 Phase 24 File ExtendedProgress.cpp, Line 537 Caching of files started 01:36:40 AM #10 Text 0 File Burncd.cpp, Line 4476 Cache writing successful. 01:36:40 AM #11 Phase 25 File ExtendedProgress.cpp, Line 537 Caching of files completed 01:36:40 AM #12 Phase 36 File ExtendedProgress.cpp, Line 537 Burn process started at 2x (8990 KB/s) 01:36:41 AM #13 Text 0 File ThreadedTransferInterface.cpp, Line 2690 Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0 01:36:41 AM #14 Text 0 File Cdrdrv.cpp, Line 10169 Disc Structure (BD): Disc Information on BD (00h) Media Type: 1, Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050 --- Header --- Disc Information Identifier: Disc Information Format: 01 h Number of DI Units/Aux Frames in each DI block: 3 Number of (recording) layer to which this DI Unit
Re: solaris cdrecord BH08LS20 drive BD-R problems
Jörg, thank you for answering the formatting question.
Note that my blu-ray drive is connected to my system via USB 2.0
I do not understand why DMA settings may be a problem for cdrecord.
With cdrecord I can write to DVD (Plextor PX-716UF) over USB 2.0
Memorex (actually RITEK) is definitely not the highest quality media.
However, cdrecord -minfo gives the same result with Verbatim discs.
Here are the errors I see with the cdrecord -atip command:
# cdrecord dev=3,0,0 -atip
Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10)
scsidev: '3,0,0'
scsibus: 3 target: 0 lun: 0
Warning: Using USCSI interface.
Using libscg version 'schily-0.9'.
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities :
Vendor_info: 'HL-DT-ST'
Identifikation : 'BD-RE BH08LS20 '
Revision : '1.00'
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 LAYER_JUMP
Disk type: 'BDR' (BD-R)
Disk class: 01
Manufacturer: 'RITEK'
Media type: 'BR2'
Disk: is not in cartridge
Media cartrige: write protect is off
{{{ ... gets_hung_for_long_time ... }}}
cdrecord: I/O error. read disk info: scsi sendcmd: no error
CDB: 51 00 00 00 00 00 00 00 04 00
status: 0x0 (GOOD STATUS)
resid: 4
cmd finished after 0.029s timeout 240s
cdrecord: Cannot get disk type.
cdrecord: I/O error. prevent/allow medium removal: scsi sendcmd: no error
CDB: 1E 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 0.039s timeout 100s
The next time I try to use cdrecord, it tells me to power cycle the drive.
This LG drive (and Memorex media) works using Power2Go on Windows,
but I need to use the drive to archive data on my solaris sparc machines.
Please help me to get cdrecord able to read the media correctly,
and then perhaps get it to write my ISO images to blu-ray discs.
Thank you.
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrote: > Trying to burn ISO9660 image to blu-ray disc, and not having much luck. > Any help on how to do this on solaris 10 using cdrecord would be > appreciated. > I noticed some discussion about formatting BD-R discs. > Do I have to format new discs before using cdrecord? If so, how? You don't need to do so > My system is loaded with one of the newer versions of solaris 10 > $ uname -a > SunOS my_machine 5.10 Generic_139555-08 sun4u sparc sun4u Note that Solaris 10 in general does not by default enable DMA but you need it for writing. See eeprom(1) Note that Solaris sparc still does not support DMA on ATA interfaces. > Built cdrecord from source code (berlios.de) version 2.01.01a61 > The drive is LG model BH08LS20 connected via SATA to USB2.0 converter > The discs are Memorex single layer BD-R speed 1x - 4x Memorex may not be a high quality media. > If I use "-atip" or "-v -minfo" flags, cdrecord gets I/O errors > Below are the results of -minfo (without -v) and trying to write to disc This should not happen > - > > # cdrecord dev=3,0,0 -minfo > Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) Copyright (C) > 1995-2009 Jörg Schilling > scsidev: '3,0,0' > scsibus: 3 target: 0 lun: 0 > Warning: Using USCSI interface. > Using libscg version 'schily-0.9'. > Device type: Removable CD-ROM > Version: 0 > Response Format: 2 > Capabilities : > Vendor_info: 'HL-DT-ST' > Identifikation : 'BD-RE BH08LS20 ' > Revision : '1.00' > 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 LAYER_JUMP > 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 Data 0 -1 0 > > Last session start address: 0 > Last session leadout start address: 0 I see no error messages. Unless your OS prevents you from sending the needed commands, it seems that your drive has problem to deal with the media. Cdrecord cannot work if it does not get the capacity from the media. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, > Do I have to format new discs before using cdrecord? Given the fact that cdrecord prefers Disk-at-Once i would assume that it does not expect BD-R POW formatting (pseudo overwriteabe) but rather SRM (sequential recording). The MMC rules for SRM burning are the same with and without formatting. (But without it is about 2 times faster.) So the problem seems rather to sit in your local cdrecord's perception of your media. Yours: Cdrecord-ProDVD-ProBD-Clone 2.01.01a61 (sparc-sun-solaris2.10) Track Sess Type Start Addr End Addr Size == 1 1 Data 0 -1 0 Last session start address:0 Last session leadout start address: 0 Mine (BD-R unused unformatted): Cdrecord-ProDVD-ProBD-Clone 2.01.01a64 (x86_64-unknown-linux-gnu) Track Sess Type Start Addr End Addr Size == 1 1 Blank 0 12219391 12219392 Next writable address: 0 Remaining writable size:12219392 Do you get a different -minfo output from a BD-R which never was involved in a failed write attempt ? Did you try BD-RE yet ? Did you try to burn BD-R by help of growisofs ? (Be aware that the BD-R disc used up to now might already be spoiled. Best is to test with an unused disc.) (Sorry: I have no use for single session BD-R. So i will not try now whether my local cdrecord can burn my BD-R. I use own burning software which has no SCSI transport adapter for Solaris yet.) It would be interesting to learn what you get with command dvd+rw-mediainfo out of dvd+rw-tools-7.1 (growisofs). The output refers directly to SCSI/MMC inquiry commands and might allow further insight into the media state. I get: - $ dvd+rw-mediainfo /dev/sr1 INQUIRY:[HL-DT-ST][BD-RE GGW-H20L ][YL03] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: VERBAT/IMc Current Write Speed: 6.0x4495=26973KB/s Write Speed #0:6.0x4495=26973KB/s Write Speed #1:4.0x4495=17982KB/s Write Speed #2:2.0x4495=8991KB/s GET [CURRENT] PERFORMANCE: Write Performance: 2.5x4495=11161KB/s...@0 -> 6.0x4495=26972KB/s...@12219391 Speed Descriptor#0:02/12219391 r...@2.5x4495=11161kb/s w...@6.0x4495=26973kb/s Speed Descriptor#1:02/12219391 r...@2.5x4495=11161kb/s w...@4.0x4495=17982kb/s Speed Descriptor#2:02/12219391 r...@2.5x4495=11161kb/s w...@2.0x4495=8991kb/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 - Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
