Re: growisofs burns dvd successfully, but
Hi, Ingo Krabbe wrote: When I eject the DVD and reinsert it into the drive the damaged flag is turned on and the DVD cannot mount anymore. My Yamaha DVD Player connected to my TV cannot read the DVD too, another DVD drive cannot read the DVD. So it was not properly written. As long as I don't eject the drive, the DVD can be mounted and dvd+rw-mediainfo reports a good track state. If in this state the file contents on DVD match the file contents on hard disk then it is clear that it is only the RMA which does not get written properly. The drive still knows the state of the media and does not have to read it from RMA until the media gets ejected. From then on, the state and table-of-content would be lost because the RMA is not properly readable. You should try a different drive. 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: growisofs burns dvd successfully, but
Ingo Krabbe ingo.kra...@eoa.de wrote: I recommend you to use cdrecord ftp://ftp.berlios.de/pub/cdrecord/alpha/ instead. Note that you also have defective software installed an you don't use mkisofs but a defective fork called genisoimage. I see. I updated to cdrecord and that seems to work now. Update: No, it still has the same problems. When I eject the DVD and reinsert it into the drive the damaged flag is turned on and the DVD cannot mount anymore. My Yamaha DVD Player connected to my TV cannot read the DVD too, another DVD drive cannot read the DVD. If yo see a problem please describe it in a way that allows me to help you. I need sufficient information about your problem. As long as I don't eject the drive, the DVD can be mounted and dvd+rw-mediainfo reports a good track state. What does cdrecord -minfo report? There was actually no change to when I used genisoimage/growisofs builtin dd or mkisofs/cdrecord. Both produce the same problems. Is there a flag for cdrecord that handles the dvd in a different way, that I may write the fixation/index entry later in another way? Cdrecord does things automatically correct. If you have problems please send related information. 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: growisofs burns dvd successfully, but
Ingo Krabbe ingo.kra...@eoa.de wrote: As you recommended I changed my usage of growisofs/genisoimage into mkisofs/cdrecord. The minfo command gives me: # cdrecord -minfo dev=1000,1,0 Cdrecord-ProDVD-ProBD-Clone 2.01.01a57 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2009 JÃ?rg Schilling scsidev: '1000,1,0' scsibus: 1000 target: 1 lun: 0 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-4570A ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE Supported modes: PACKET SAO cdrecord: Warning: The DMA speed test has been skipped. WARNING: Phys disk size 1846172 differs from rzone size 0! Prerecorded disk? WARNING: Phys start: 196608 Phys end 2042779 WARNING: Drive returns zero media size. Using media size from ADIP. Mounted media class: DVD Mounted media type: DVD-R sequential recording Disk Is not erasable data type:standard disk status: complete session status: complete 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 18461711846172 Last session start address: 0 Last session leadout start address: 1846172 When I write the DVD I get no failure messages in dmesg nor on terminal. If its a problem of the drive I would exchange it, but I don't have instant access to another drive. I see no crash and everything is OK, you may verify this by e.g. calling: readcd f=/dev/null to read back the content. 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 wrob0...@gmail.com 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
Thomas Schmitt scdbac...@gmx.net 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
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 scdbac...@gmx.net 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: growisofs burns dvd successfully, but
On Mon, Oct 12, 2009 at 02:47:11PM +0200, Joerg Schilling wrote: Ingo Krabbe ingo.kra...@eoa.de wrote: As you recommended I changed my usage of growisofs/genisoimage into mkisofs/cdrecord. I see no crash and everything is OK, you may verify this by e.g. calling: Yes you are right. This disk was recorded with mkisofs -dvd-video and actually works. So maybe cdrecord isn't the problem after all, though reading the data from the dvd with readcd gives me an image I can mount with mount -oloop imgfile /mnt/image I would really like to fix this, as it seems to be possible to write dvd disks with cdrecord, but still it fails to write the toc without showing an error report. -dvd-video seems to create a UDF Filesystem. It seems that the toc format of UDF is more stable, which leads me to the assumption that there might be a trick to get the iso9660 filesystem onto the dvd. Otherwise I would have quit this topic, but I just can't see where my drive or any other component fails here. If there is really a failure that should be reported somewhere. Anyway I think it would be helpfull if you give me a short hint about debug=# and kdebug=# numbers. thx ingo readcd f=/dev/null to read back the content. Jörg -- 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
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
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
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
