Re: Burning CDs on FreeBSD 7.2
On Wed, 16 Jun 2010 03:03:02 -0700 (PDT), Mark Terribile materrib...@yahoo.com wrote: Thanks to Jerrymc and Polyoptron. Things are working, sort of. I'm using the atapicam/cdrecord solution. But when I do a dd read to verify the write, the read ends on an I/O error rather than an EOF. (I'm not sure that this problem is new.) There is a very long delay between dd's report and the program end (delay on close?) And sometimes the eject command after the dd locks up and eventually fails. There are plenty of console messages, including READ_BIG retrying, READ_BIG timed out, TEST_UNIT_READY freeing zombie taskqueue request, and PREVENT_ALLOW taskqueue timeout - compiing request directly . I start wondering if this may be due to a defective drive, or wrong cable, or even through DMA incompatibilites... Instead of using dd (have you made sure to use the correct block size?) try using readcd (comes with cdrecord); see man cdrecord for details and examples. This is definitely NOT reliable enough to put into a script (which would make handling the many file names more reliable). True. cdrecord reports --- scsidev: '4,0,0' scsibus: 4 target: 0 lun: 0 SCSI buffer size: 64512 Track 01: Total bytes read/written: 103874560/103874560 (50720 sectors). Writing time: 41.290s Average write speed 20.8x. Try to force a lower value, maybe drive and discs are not compatible. With -speed 8 it should be slow enough and fast enough for a test. You can use -prcap to find out what the drive tells cdrecord about itself. I would be grateful for any clues about what is still wrong here. I'd slowly expect a defective drive... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Burning CDs on FreeBSD 7.2
On Wed, 16 Jun 2010 03:28 am, Mark Terribile wrote: Hi, I have several systems, one on 5.4 and two on 7.2 . I keep the 5.4 system because every time I upgrade something breaks and cannot be fixed without (apparently) weeks of effort. I *am* trying to get off it. Now: my 5.4 system is down until I replace some hardware. In the meantime I need to burn about forty data CDs. I've been using burncd on 5.4 but when I try it on 7.2 the drive and process lock up during the fixate step. Clearing them requires a reboot. Does anyone have advice, pointers, etc.? If you point me to pseudo-SCSI, please give me pointers to all parts of the solution, since the various man pages don't have proper links to each other. (Hint to man page authors: the SEE ALSO entries are very important, and you must consider ALL levels, from other apps to the system calls used.) I seem to recall having some difficulty when trying to burn CDs on a DVD capable drive using burncd. Some incompatibility of burncd and the DVD drives. I suspect either the software or the drives have improved so that with more modern components it works. Meanwhile I believe I avoided the problem using atapicam and cdrecord. But I don't recall needing to reboot. (And it could have all been a dream?) Malcolm Thank you for your help. Mark Terribile ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Burning CDs on FreeBSD 7.2
Polytropon, I'm using the atapicam/cdrecord solution. But when I do a dd read to verify the write, the read ends on an I/O error rather than an EOF. (I'm not sure that this problem is new.) ... There are plenty of console messages, including READ_BIG retrying, READ_BIG timed out, TEST_UNIT_READY freeing zombie taskqueue request, and PREVENT_ALLOW taskqueue timeout - compiing request directly . I start wondering if this may be due to a defective drive, or wrong cable, or even through DMA incompatibilites... I tried taking the drive out of the 5.4 machine. No difference. Also, the ATAPICAM subsystem gets into a state where the eject program will report drive busy but cdrecord can still operate the drive. I think that in doing whatever was needed to accomodate DVDs, the subsystem was broken. It looks like cdrecord manages to work around it. Instead of using dd (have you made sure to use the correct block size?) try using readcd (comes with cdrecord); see man cdrecord for details and examples. I'll try it. I am using the correct block size, and the data retrieved cmp's correctly against the iso fs image used to create the disk. dd was means for exactly such purposes, and if it can't work, the OS is doing a bad job. This is definitely NOT reliable enough to put into a script (which would make handling the many file names more reliable). Under 5.4 I did this by script routinely. Question is, under which category do I report this? Mark Terribile ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Burning CDs on FreeBSD 7.2
On Thu, Jun 17, 2010 at 07:24:46AM -0700, Mark Terribile wrote: Polytropon, I'm using the atapicam/cdrecord solution. But when I do a dd read to verify the write, the read ends on an I/O error rather than an EOF. (I'm not sure that this problem is new.) ... There are plenty of console messages, including READ_BIG retrying, READ_BIG timed out, TEST_UNIT_READY freeing zombie taskqueue request, and PREVENT_ALLOW taskqueue timeout - compiing request directly . I start wondering if this may be due to a defective drive, or wrong cable, or even through DMA incompatibilites... I tried taking the drive out of the 5.4 machine. No difference. Also, the ATAPICAM subsystem gets into a state where the eject program will report drive busy but cdrecord can still operate the drive. I think that in doing whatever was needed to accomodate DVDs, the subsystem was broken. It looks like cdrecord manages to work around it. Well, the drive will be busy if any process/shell is cd-ed to any directory on the device or any process/shell has any file on the device open, no matter what is being done to it. Probably you already know that, but it makes your statement above easily a not-surprising situation. jerry Instead of using dd (have you made sure to use the correct block size?) try using readcd (comes with cdrecord); see man cdrecord for details and examples. I'll try it. I am using the correct block size, and the data retrieved cmp's correctly against the iso fs image used to create the disk. dd was means for exactly such purposes, and if it can't work, the OS is doing a bad job. This is definitely NOT reliable enough to put into a script (which would make handling the many file names more reliable). Under 5.4 I did this by script routinely. Question is, under which category do I report this? Mark Terribile ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Burning CDs on FreeBSD 7.2
Thanks to Jerrymc and Polyoptron. Things are working, sort of. I'm using the atapicam/cdrecord solution. But when I do a dd read to verify the write, the read ends on an I/O error rather than an EOF. (I'm not sure that this problem is new.) There is a very long delay between dd's report and the program end (delay on close?) And sometimes the eject command after the dd locks up and eventually fails. There are plenty of console messages, including READ_BIG retrying, READ_BIG timed out, TEST_UNIT_READY freeing zombie taskqueue request, and PREVENT_ALLOW taskqueue timeout - compiing request directly . This is definitely NOT reliable enough to put into a script (which would make handling the many file names more reliable). cdrecord reports --- scsidev: '4,0,0' scsibus: 4 target: 0 lun: 0 SCSI buffer size: 64512 cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Cdrecord-Clone 2.01 (i386-unknown-freebsd7.2) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.8'. atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'ATAPI ' Identifikation : 'DVD A DH20A4H ' Revision : 'QP53' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0016 Profile: 0x0015 Profile: 0x0014 Profile: 0x0013 Profile: 0x0012 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A Profile: 0x0009 (current) Profile: 0x0008 Profile: 0x0002 Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 988416 = 965 KB FIFO size : 4194304 = 4096 KB Track 01: data99 MB Total size: 113 MB (11:16.29) = 50722 sectors Lout start: 114 MB (11:18/22) = 50722 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable Disk sub type: Medium Type C, low Beta category (C-) (6) ATIP start of lead in: -11567 (97:27/58) ATIP start of lead out: 359849 (79:59/74) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 12 Manufacturer: Mitsui Chemicals, Inc. Blocks total: 359849 Blocks current: 359849 Blocks remaining: 309127 Forcespeed is OFF. Starting to write CD/DVD at speed 48 in real TAO mode for single session. Last chance to quit, starting real write in 9 seconds. 8 seconds. 7 seconds. 6 seconds. 5 seconds. 4 seconds. 3 seconds. 2 seconds. 1 seconds. 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is OFF. Performing OPC... Starting new track at sector: 0 Track 01:0 of 99 MB written. Track 01:1 of 99 MB written (fifo 100%) [buf 98%] 2.7x. Track 01:2 of 99 MB written (fifo 100%) [buf 98%] 21.3x. Track 01:3 of 99 MB written (fifo 100%) [buf 99%] 22.1x. Track 01:4 of 99 MB written (fifo 100%) [buf 99%] 21.5x. Track 01:5 of 99 MB written (fifo 100%) [buf 98%] 22.3x. Track 01:6 of 99 MB written (fifo 100%) [buf 98%] 21.7x. Track 01:7 of 99 MB written (fifo 100%) [buf 98%] 22.5x. Track 01:8 of 99 MB written (fifo 98%) [buf 98%] 21.9x. Track 01:9 of 99 MB written (fifo 100%) [buf 99%] 22.6x. Track 01: 10 of 99 MB written (fifo 100%) [buf 99%] 22.0x. Track 01: 11 of 99 MB written (fifo 100%) [buf 90%] 21.6x. Track 01: 12 of 99 MB written (fifo 100%) [buf 98%] 23.5x. Track 01: 13 of 99 MB written (fifo 100%) [buf 98%] 23.0x. Track 01: 14 of 99 MB written (fifo 100%) [buf 98%] 22.3x. Track 01: 15 of 99 MB written (fifo 98%) [buf 99%] 23.1x. Track 01: 16 of 99 MB written (fifo 100%) [buf 99%] 22.5x. Track 01: 17 of 99 MB written (fifo 100%) [buf 98%] 23.2x. Track 01: 18 of 99 MB written (fifo 100%) [buf 98%] 22.6x. Track 01: 19 of 99 MB written (fifo 98%) [buf 98%] 23.3x. Track 01: 20 of 99 MB written (fifo 100%) [buf 98%] 22.6x. Track 01: 21 of 99 MB written (fifo 100%) [buf 98%] 23.4x. Track 01: 22 of 99 MB written (fifo 100%) [buf 98%] 22.7x. Track 01: 23 of 99 MB written (fifo 100%) [buf 98%] 23.4x. Track 01: 24 of 99 MB written (fifo 100%) [buf 98%] 22.8x. Track 01: 25 of 99 MB written (fifo 100%) [buf 99%] 23.5x. Track 01: 26 of 99 MB written (fifo 100%) [buf 99%] 22.8x. Track 01: 27 of 99 MB written (fifo 100%) [buf 98%] 23.6x. Track 01: 28 of 99 MB written (fifo 98%) [buf
Burning CDs on FreeBSD 7.2
Hi, I have several systems, one on 5.4 and two on 7.2 . I keep the 5.4 system because every time I upgrade something breaks and cannot be fixed without (apparently) weeks of effort. I *am* trying to get off it. Now: my 5.4 system is down until I replace some hardware. In the meantime I need to burn about forty data CDs. I've been using burncd on 5.4 but when I try it on 7.2 the drive and process lock up during the fixate step. Clearing them requires a reboot. Does anyone have advice, pointers, etc.? If you point me to pseudo-SCSI, please give me pointers to all parts of the solution, since the various man pages don't have proper links to each other. (Hint to man page authors: the SEE ALSO entries are very important, and you must consider ALL levels, from other apps to the system calls used.) Thank you for your help. Mark Terribile ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Burning CDs on FreeBSD 7.2
On Tue, 15 Jun 2010 10:58:22 -0700 (PDT), Mark Terribile materrib...@yahoo.com wrote: Does anyone have advice, pointers, etc.? If you point me to pseudo-SCSI, please give me pointers to all parts of the solution, since the various man pages don't have proper links to each other. First of all, load the kernel module for ATAPICAM: # kldload atapicam You can also make this permanent by adding atapicam_load=YES to /boot/loader.conf. Of course, you can also recompile your kernel with device atapicam added. If the module is loaded successfully, see what SCSI equipment will show up: # camcontrol devlist HL-DT-ST DVD-RAM GSA-H58N 1.01 at scbus2 target 0 lun 0 (cd0,pass0) This is an example of how a ATAPI recorder shows up as a SCSI device: it's the device 2:0:0, corresponding to /dev/cd0 and /dev/pass0. Unless you're burning CDs with root permissions, you need to make sure your user will have proper writing access to the following files, e. g. by using the group operator for your user: own cd0 root:operator permcd0 0664 own xpt0root:operator permxpt00660 own pass0 root:operator permpass0 0660 This is an example from /etc/devfs.conf. Make sure devfs is restarted to reflect those changes. In the following example, I just assume commands will be issued by root. If you want to burn data CDs, I recommend using cdrecord. In step 1, you prepare the ISO to be burned: # cd /path/to/your/files/ # mkisofs -r -J -o /tmp/cd1.iso vol1/ Then you burn it: # cdrecord dev=2,0,0 speed=16 -v -eject -tao -data /tmp/cd1.iso You can of course combine both steps: # cd /path/to/your/files/ # mkisofs -r -J vol1/ | cdrecord dev=2,0,0 speed=16 -v -eject -tao -data - An addition: I have setup an alias for burning data CDs in ~/.cshrc for less typing: alias burndata 'cdrecord dev=2,0,0 speed=16 -v -eject -tao -data' This makes it more easy to deal with existing ISO files, which often is the way I go (instead of the combined method). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Burning CDs on FreeBSD 7.2
On Tue, Jun 15, 2010 at 10:58:22AM -0700, Mark Terribile wrote: Hi, I have several systems, one on 5.4 and two on 7.2 . I keep the 5.4 system because every time I upgrade something breaks and cannot be fixed without (apparently) weeks of effort. I *am* trying to get off it. Now: my 5.4 system is down until I replace some hardware. In the meantime I need to burn about forty data CDs. I've been using burncd on 5.4 but when I try it on 7.2 the drive and process lock up during the fixate step. Clearing them requires a reboot. Does anyone have advice, pointers, etc.? If you point me to pseudo-SCSI, please give me pointers to all parts of the solution, since the various man pages don't have proper links to each other. (Hint to man page authors: the SEE ALSO entries are very important, and you must consider ALL levels, from other apps to the system calls used.) Here is the command string I use successfully to burn a dir of picture files on FreeBSD 7.1 system. /usr/sbin/burncd -f /dev/acd0c -s max data PIC2005-cdimage fixate I don't remember what I did to create the PIC2005-cdimage file. I was having trouble with the system trying to run the burner too fast with I had a speed argument in the command line. Without it, it runs fast enough for the few I was making. jerry Thank you for your help. Mark Terribile ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
