Re: burncd input output error
On Sat, Sep 17, 2005 at 08:30:33PM -0700, Andrew Sparrow wrote: On Sat, Sep 17, 2005 at 12:42:39PM -0400, Chuck Swiger wrote: Andreas Klemm wrote: [ ... ] - burncd leaves cdrom in a way that CD cannot be mounted after burning, one has to open and re-close CD tray manually before one is able to mount the frshly burned CD. This is an issue with the drive firmware more than anything to do with software. Most drives won't re-read the disk's table-of-contents after burning an image to a blank, until you eject and reload the disk. Ho, sorry, this is simply not true. Although I don't use burncd so can't comment on it, I've been using cdrecord since FreeBSD 2.x (1997-8, IIRC), on a wide variety of burners - none of which have ever required me to eject/reload the disk to mount it, unless an operation aborted/failed. In which case the disk burnt was generally a coaster anyway. Even now, using cdrecord with ATAPICAM, this is never necesary on my current burners (NED ND6500A, Plextor PX-712A). I simply burn and then mount immediately. I see this needs more investigation. Maybe it has to deal with the exit status I had (!=0). I will do a test burn now with burncd reading from a file instead from a pipe. Let's see if it behaves different then. Hmm even if reading from a file I get this exit status 74. [EMAIL PROTECTED] /export/isos burncd -v -s max data xxx.iso fixate adding type 0x08 file xxx.iso size 238792 KB 119396 blocks next writeable LBA 0 addr = 0 size = 244523008 blocks = 119396 writing from file xxx.iso size 238792 KB written this track 238792 KB (100%) total 238792 KB fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error Exit 74 Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.4 Need a magic printfilter today ? - http://www.apsfilter.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd input output error
On Sun, Sep 18, 2005 at 10:09:54AM +0200, Andreas Klemm wrote: I see this needs more investigation. Maybe it has to deal with the exit status I had (!=0). I will do a test burn now with burncd reading from a file instead from a pipe. Let's see if it behaves different then. Hmm even if reading from a file I get this exit status 74. [EMAIL PROTECTED] /export/isos burncd -v -s max data xxx.iso fixate adding type 0x08 file xxx.iso size 238792 KB 119396 blocks next writeable LBA 0 addr = 0 size = 244523008 blocks = 119396 writing from file xxx.iso size 238792 KB written this track 238792 KB (100%) total 238792 KB fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error Exit 74 Have you tried cdrecord? You pretty much only need to add ATAPICAM to the kernel, although If you don't already have SCSI support on the machine, you'll need to add that (cd, scbus, pass) too, of course. Even if you get the same error, it'll provide much more detailed diagnostic information (maybe there's a flag to burncd to switch that on?). What brand of blank are you using? There's some really cheesy generics - and some even worse Chinese pirates - around... Also, if the drive's firmware mis-identifies the blank, this could cause it to use a poor (or downright wrong) strategy for it, which likely would cause you problems as well. Handy to have some RWs around for testing like this, too. Good luck! AS Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.4 Need a magic printfilter today ? - http://www.apsfilter.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd input output error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Sep 17, 2005 at 03:03:44PM +0200, Andreas Klemm wrote: 2 problems with FreeBSD 5.4 stable: - burncd has strange exit status when reading ISO file from stdin according to manual page possible: [...] gunzip -c file.iso.gz | burncd -f /dev/acd0 data - fixate [...] - burncd leaves cdrom in a way that CD cannot be mounted after burning, one has to open and re-close CD tray manually before one is able to mount the frshly burned CD. *** trying to burn ISO file I've run into this with one CD burner, a Plextor, IIRC. I did some cursory googling, other folks had the problem, no solutions posted. I just (as you seem to be doing) work around it, as the CDs burned without problems. I never put much effort into solving it. FWIW, it happened no matter which machine had the CD burner, through 5.x and 6.x. (I haven't put that burner in a box running CURRENT.) I just made a little script to open and close the cd tray (using the older version of eject, as the newer version lacks the -t to close the tray option) but you can do the same with cdcontrol using the eject and close options. Not that this helps, but just letting you know you're not alone. :) - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Giles: I need you to take Spike for a few days. Xander: What? Spike: What? Anya: What? Spike: I'm not stayin' with him. Giles: I have a friend who's coming to town, and I'd like us to be alone. Anya: Oh, you mean an orgasm friend? Giles: Yes, that's exactly the most appalling thing you could have said. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDLBwE+lTVdes0Z9YRAmHlAJ9v8u5xIOJq5d9eke2bxbCvIZS7igCgt9tV 64XyVC0ABeQVZnvr61m0e/M= =U1CE -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd input output error
Andreas Klemm wrote: [ ... ] - burncd leaves cdrom in a way that CD cannot be mounted after burning, one has to open and re-close CD tray manually before one is able to mount the frshly burned CD. This is an issue with the drive firmware more than anything to do with software. Most drives won't re-read the disk's table-of-contents after burning an image to a blank, until you eject and reload the disk. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd input output error
On Sat, Sep 17, 2005 at 12:42:39PM -0400, Chuck Swiger wrote: Andreas Klemm wrote: [ ... ] - burncd leaves cdrom in a way that CD cannot be mounted after burning, one has to open and re-close CD tray manually before one is able to mount the frshly burned CD. This is an issue with the drive firmware more than anything to do with software. Most drives won't re-read the disk's table-of-contents after burning an image to a blank, until you eject and reload the disk. Ho, sorry, this is simply not true. Although I don't use burncd so can't comment on it, I've been using cdrecord since FreeBSD 2.x (1997-8, IIRC), on a wide variety of burners - none of which have ever required me to eject/reload the disk to mount it, unless an operation aborted/failed. In which case the disk burnt was generally a coaster anyway. Even now, using cdrecord with ATAPICAM, this is never necesary on my current burners (NED ND6500A, Plextor PX-712A). I simply burn and then mount immediately. Regards, AS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
