Re: burncd error?
On Thu, 14 Aug 2008 08:21:11 -1000, Al Plant <[EMAIL PROTECTED]> wrote: > Install fails from these burned discs. > > Error message. > > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 Defective media? > /dev/acd0c used to work. Now you have to use /dev/acd0 (no c) to get > burncd to work. As far as I remember, /dev/acd0 instead of /dev/acd0c is to be used as device file for burning and reading since FreeBSD 5.0. > Can somebody enlighten me please. 1. Maybe you can try blank media from another manufacturer? 2. Maybe you can try another burning program (cdrecord)? 3. Maybe you can try to burn at a lower speed? Just some ideas... -- Polytropon >From 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 "[EMAIL PROTECTED]"
Re: burncd error
On 6/7/06, Josh Paetzel <[EMAIL PROTECTED]> wrote: On Wednesday 07 June 2006 14:46, you wrote: > On Wednesday 07 June 2006 11:04, Josh Paetzel wrote: > > I'm running 6.1-RELEASE > > > > Trying to burn iso's using burncd gives me an error. > > > > gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate > > > > next writeable LBA 0 > > writing from file i386pkg-3.0.iso size 710566 KB > > written this track 710566 KB (100%) total 710566 KB > > fixating CD, please wait.. > > burncd: ioctl(CDRIOCFIXATE): Input/output error > > > > The 'funny' thing about this is that the CDs I burn work fine. > > (I've tried several different ISOs and have checked the md5's on > > all of them.) > > > > Anyone have an idea of what is going on? I never tried to burn > > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > I've seen the same thing for the past several weeks (worked fine at > some point prior to 6.1). I'm running 6-STABLE, updated every > couple weeks. As near as I've been able to determine, the fixate > step doesn't actually do anything, so your CD's will still be > "open" but should work fine under any modern OS. As a workaround > you can repeat the fixate step at a lower speed: burncd -f > /dev/acd0 -s 4 fixate > > I haven't experimented enough to know at what speed the fixate step > breaks, but that does seem to be what's going on. I also haven't > tried turning off ATAPICAM, which would be another interesting data > point. If you or someone else has the time to figure out exactly > which (set of) commits started producing this behavior, that would > be excellent material for a PR. I may get around to it myself but > it's not a high priority. > > > dmesg is attached. > > Looks like you forgot it. In my case (using ATAPICAM): > > acd1: CDRW at ata1-slave UDMA33 > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 33.000MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not > present > > JN My client says it included a dmesg...wonder what's going on with that. I've tried using different burn speeds all the way down to 32x. I am using ATAPICAM, I wonder if it is somehow related to that? I think I'll unload that and give it a shot. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html Which tool to use to burn the CD depends on whether your CD burner is ATAPI or something else. ATAPI CD burners use the burncd program that is part of the base system. SCSI and USB CD burners should use cdrecord from the sysutils/cdrtools port. It is also possible to use cdrecord and other tools for SCSI drives on ATAPI hardware with the ATAPI/CAM module. -- Linux is for people who hate Micro$oft. BSD is for people who love Unix ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
On 6/8/06, Pablo Mora <[EMAIL PROTECTED]> wrote: On 6/7/06, Josh Paetzel <[EMAIL PROTECTED]> wrote: > On Wednesday 07 June 2006 14:46, you wrote: > > On Wednesday 07 June 2006 11:04, Josh Paetzel wrote: > > > I'm running 6.1-RELEASE > > > > > > Trying to burn iso's using burncd gives me an error. > > > > > > gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate > > > > > > next writeable LBA 0 > > > writing from file i386pkg-3.0.iso size 710566 KB > > > written this track 710566 KB (100%) total 710566 KB > > > fixating CD, please wait.. > > > burncd: ioctl(CDRIOCFIXATE): Input/output error > > > > > > The 'funny' thing about this is that the CDs I burn work fine. > > > (I've tried several different ISOs and have checked the md5's on > > > all of them.) > > > > > > Anyone have an idea of what is going on? I never tried to burn > > > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > > > I've seen the same thing for the past several weeks (worked fine at > > some point prior to 6.1). I'm running 6-STABLE, updated every > > couple weeks. As near as I've been able to determine, the fixate > > step doesn't actually do anything, so your CD's will still be > > "open" but should work fine under any modern OS. As a workaround > > you can repeat the fixate step at a lower speed: burncd -f > > /dev/acd0 -s 4 fixate > > > > I haven't experimented enough to know at what speed the fixate step > > breaks, but that does seem to be what's going on. I also haven't > > tried turning off ATAPICAM, which would be another interesting data > > point. If you or someone else has the time to figure out exactly > > which (set of) commits started producing this behavior, that would > > be excellent material for a PR. I may get around to it myself but > > it's not a high priority. > > > > > dmesg is attached. > > > > Looks like you forgot it. In my case (using ATAPICAM): > > > > acd1: CDRW at ata1-slave UDMA33 > > cd1 at ata1 bus 0 target 1 lun 0 > > cd1: Removable CD-ROM SCSI-0 device > > cd1: 33.000MB/s transfers > > cd1: Attempt to query device size failed: NOT READY, Medium not > > present > > > > JN > > My client says it included a dmesg...wonder what's going on with that. > > I've tried using different burn speeds all the way down to 32x. I am > using ATAPICAM, I wonder if it is somehow related to that? I think > I'll unload that and give it a shot. > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html Which tool to use to burn the CD depends on whether your CD burner is ATAPI or something else. ATAPI CD burners use the burncd program that is part of the base system. SCSI and USB CD burners should use cdrecord from the sysutils/cdrtools port. It is also possible to use cdrecord and other tools for SCSI drives on ATAPI hardware with the ATAPI/CAM module. http://www.freebsddiary.org/cdrecord-ide.php -- Linux is for people who hate Micro$oft. BSD is for people who love Unix ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
Napoleon Dynamite wrote: [ ...top posting recovered... ] On Wednesday 07 June 2006 10:44, Michael S wrote: I had the same kind of issue, also with 6.1-RELEASE, and just fixed it the Windows way - reboot. And it worked fine. I got that error pretty routinely for a while. The cd-r was always usable, though. I switched to k3b for cd burning and have not seen that error since. k3b uses dvd+rw-tools rather than burncd underneath. It's possible that they would work better for the original poster too. It also sounds like the issue with burncd is reproducible, anyone filed a PR...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
Josh Paetzel wrote: > I'm running 6.1-RELEASE > > Trying to burn iso's using burncd gives me an error. > > gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate > > next writeable LBA 0 > writing from file i386pkg-3.0.iso size 710566 KB > written this track 710566 KB (100%) total 710566 KB > fixating CD, please wait.. > burncd: ioctl(CDRIOCFIXATE): Input/output error > > The 'funny' thing about this is that the CDs I burn work fine. (I've > tried several different ISOs and have checked the md5's on all of > them.) > > Anyone have an idea of what is going on? I never tried to burn > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > dmesg is attached. Hi, Give it a go with cdrecord from cdrtools. /usr/ports/sysutils/cdrtools Cheers, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: http://www.webanoide.org PGP Key ID: 0x4E148A3B PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
I got that error pretty routinely for a while. The cd-r was always usable, though. I switched to k3b for cd burning and have not seen that error since. On Wednesday 07 June 2006 10:44, Michael S wrote: > I had the same kind of issue, also with 6.1-RELEASE, and just fixed it > the Windows way - reboot. And it worked fine. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" pgpW4vES9ohrR.pgp Description: PGP signature
Re: burncd error
On Wednesday 07 June 2006 14:46, you wrote: > On Wednesday 07 June 2006 11:04, Josh Paetzel wrote: > > I'm running 6.1-RELEASE > > > > Trying to burn iso's using burncd gives me an error. > > > > gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate > > > > next writeable LBA 0 > > writing from file i386pkg-3.0.iso size 710566 KB > > written this track 710566 KB (100%) total 710566 KB > > fixating CD, please wait.. > > burncd: ioctl(CDRIOCFIXATE): Input/output error > > > > The 'funny' thing about this is that the CDs I burn work fine. > > (I've tried several different ISOs and have checked the md5's on > > all of them.) > > > > Anyone have an idea of what is going on? I never tried to burn > > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > I've seen the same thing for the past several weeks (worked fine at > some point prior to 6.1). I'm running 6-STABLE, updated every > couple weeks. As near as I've been able to determine, the fixate > step doesn't actually do anything, so your CD's will still be > "open" but should work fine under any modern OS. As a workaround > you can repeat the fixate step at a lower speed: burncd -f > /dev/acd0 -s 4 fixate > > I haven't experimented enough to know at what speed the fixate step > breaks, but that does seem to be what's going on. I also haven't > tried turning off ATAPICAM, which would be another interesting data > point. If you or someone else has the time to figure out exactly > which (set of) commits started producing this behavior, that would > be excellent material for a PR. I may get around to it myself but > it's not a high priority. > > > dmesg is attached. > > Looks like you forgot it. In my case (using ATAPICAM): > > acd1: CDRW at ata1-slave UDMA33 > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 33.000MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not > present > > JN My client says it included a dmesg...wonder what's going on with that. I've tried using different burn speeds all the way down to 32x. I am using ATAPICAM, I wonder if it is somehow related to that? I think I'll unload that and give it a shot. -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
Josh Paetzel wrote: I'm running 6.1-RELEASE Trying to burn iso's using burncd gives me an error. gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate next writeable LBA 0 writing from file i386pkg-3.0.iso size 710566 KB written this track 710566 KB (100%) total 710566 KB fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error The 'funny' thing about this is that the CDs I burn work fine. (I've tried several different ISOs and have checked the md5's on all of them.) Anyone have an idea of what is going on? I never tried to burn anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE Have you tried with "-v"? And for different values of "-s"? Just curious, Kevin Kinsey -- Better to light one candle than to curse the darkness. -- motto of the Christopher Society ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote: > I'm running 6.1-RELEASE > > Trying to burn iso's using burncd gives me an error. > > gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate > > next writeable LBA 0 > writing from file i386pkg-3.0.iso size 710566 KB > written this track 710566 KB (100%) total 710566 KB > fixating CD, please wait.. > burncd: ioctl(CDRIOCFIXATE): Input/output error > > The 'funny' thing about this is that the CDs I burn work fine. (I've > tried several different ISOs and have checked the md5's on all of > them.) > > Anyone have an idea of what is going on? I never tried to burn > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE I've seen the same thing for the past several weeks (worked fine at some point prior to 6.1). I'm running 6-STABLE, updated every couple weeks. As near as I've been able to determine, the fixate step doesn't actually do anything, so your CD's will still be "open" but should work fine under any modern OS. As a workaround you can repeat the fixate step at a lower speed: burncd -f /dev/acd0 -s 4 fixate I haven't experimented enough to know at what speed the fixate step breaks, but that does seem to be what's going on. I also haven't tried turning off ATAPICAM, which would be another interesting data point. If you or someone else has the time to figure out exactly which (set of) commits started producing this behavior, that would be excellent material for a PR. I may get around to it myself but it's not a high priority. > dmesg is attached. Looks like you forgot it. In my case (using ATAPICAM): acd1: CDRW at ata1-slave UDMA33 cd1 at ata1 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
parv <[EMAIL PROTECTED]> wrote: > in message <[EMAIL PROTECTED]>, > wrote Oliver Fromme thusly... > > You can even go a step further and let mkisofs create Joliet and > > Apple (HFS) extensions on the CD. You will then have four > > different kinds of directory descriptions on the CD for the same > > content. The cool thing is that every operating system picks the > > one most suitable for itself. > > you forgot to mention one thing that having multiple OS > compatibility layers will result in much lower available space than > expected. It depends. The rockridge extensions don't take that much space. I often make CD-ROMs (always with rockridge, of course) that are very close to the 650 or 700 Mbyte limit of the respective CD-Rs. The overhead isn't that large, unless maybe you have _really_ many small files on it, i.e. several hundreds of thousands. As for the Joliet and Apple stuff, those _might_ take a bit more space, particularly the Apple/HFS filesystem data with its "resource forks". I don't normalle create CD-ROMs with HFS extensions on them, though. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
in message <[EMAIL PROTECTED]>, wrote Oliver Fromme thusly... > > Kevin Oberman <[EMAIL PROTECTED]> wrote: > > I suspected that both -allow-lowercase and -allow-multidot were > > implicit in -r, but I had never actually tried it. > > No, they're not implicit, but they're not necessary either. > > Let me explain ... thanks for the info. > You can even go a step further and let mkisofs create Joliet and > Apple (HFS) extensions on the CD. You will then have four > different kinds of directory descriptions on the CD for the same > content. The cool thing is that every operating system picks the > one most suitable for itself. you forgot to mention one thing that having multiple OS compatibility layers will result in much lower available space than expected. i once tried all those layers & after 500 MB or so, "file system full" messages were being generated... until somebody clued me in to use as minimum options to use as possible. those messages are in the (-questions, i think) archive somewhere. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
Kevin Oberman <[EMAIL PROTECTED]> wrote: > I suspected that both -allow-lowercase and -allow-multidot were > implicit in -r, but I had never actually tried it. No, they're not implicit, but they're not necessary either. Let me explain ... Standard ISO9660 filesystems have several limitations. For example, every filename has a maximum length of 31 characters (even though it's common to use only 8+3 because of old DOS- compatibility), only upper-case letters, numbers and under- scores, there must be exactly one dot (which must not be the first character of the name), a non-empty filename extension (after that dot), and a non-empty version number. Also note that ISO9660 does not support some of the standard UNIX UFS features, such as permission modes, ownership etc. There are several options to mkisofs that cause it to ignore some of those restrictions. This usually works most of the time, but might not work with an operating system (or other software) that enforces strict ISO9660 conformance. These options include -allow-lowercase, -allow-multidot, -d, -D, -L, -N, -relaxed-filenames, -U, -no-iso-translate. However, when you use the -R or -r option to create a rock- ridge extension, you actually have a second directory hierarchy laid over the existing ISO9660 directory hierachy (this is somewhat simplified, but the net effect is just that). Basically that means that, if you mount the CD with a rockridge-capable operating system (such as FreeBSD), you don't see the ISO9660 filenames at all, but only the rock- ridge filenames. Obviously, there is no restriction on the filenames in the rockridge extension, as it was specifically designed to store information for UNIX filesystems, including permissions and ownerships. The above-mentioned options (-allow-lowercase etc.) don't have any effect on the rock- ridge extension. Conversely, if you mount the CD with a non-rockridge-capable system (such as DOS), you only see the ISO9660 filenames with all of their limitations, possibly relaxed by the above- mentioned options (provided that it works, as those options produce non-standard CDs). If you expect emergency cases where you must be able to read a rockridge CD with DOS but still be able to reconstruct the real filenames somehow, mkisofs offers the -T option. It creates a simple text file called TRANS.TBL in every directory which contains a mapping between the ISO9660 filenames and the rockridge filenames, one per line. You can even go a step further and let mkisofs create Joliet and Apple (HFS) extensions on the CD. You will then have four different kinds of directory descriptions on the CD for the same content. The cool thing is that every operating system picks the one most suitable for itself. > > The remarkable thing was actually, that when I used the wrong option, > > mkisofs says it doesn't recognise the option, quits the program, and > > returns to the prompt in my xterm, but now my xterm shows up with > > unrecognisable characters (normally for me: root@hostname, now something > > like: %^(%^%(%^&()_)_*). > > > > Did I hit a bug? Indeed, it sounds like a bug. It seems that cdrecord fails to send the proper reset/init termcap sequences in that particular case, so the terminal is left in some unusual state. Actually I'm surprised that mkisofs would use termcap control sequences anyway. It doesn't really need to, IMO. BTW, you can manually reset an xterm by pointing your mouse pointer inside it, then press (and hold) the Ctrl key, then press the middle mouse button. This causes an xterm menu to pop up. Select "full reset" from that menu. Also, typing "reset", "tput reset init" and/or "stty sane" might help in some situations. If the terminal settings are seriously broken so that the enter key doesn't work anymore, use Ctrl-J instead of enter (you might even have to type the command blindly if the terminal echo was turned off). Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
On Fri, 4 Oct 2002, the wise Kevin Oberman spoke, and said: > > Date: Sat, 5 Oct 2002 00:29:48 +0200 (CEST) > > From: Marco Beishuizen <[EMAIL PROTECTED]> > > Sender: [EMAIL PROTECTED] > > > > Thanks! It worked great. I have one remark though: the option > > "-allow-lower-case" wasn't recognised by mkisofs. Looking at the manpage > > it should be "-allow-lowercase". :-) But this was of course one of those > > days... > > I really should have done a cut and paste on the command or pulled in > my shell script that runs mkisofs, but it's on a different system and > it seemed easier to just type it in. > > > > Eventually, I didn't use the option "-allow-lowercase", but the cd has no > > problems of using lowercase characters. All files I copied to the cd show > > up like the way they appear in FreeBSD. > > I suspected that both -allow-lowercase and -allow-multidot were > implicit in -r, but I had never actually tried it. > > > The remarkable thing was actually, that when I used the wrong option, > > mkisofs says it doesn't recognise the option, quits the program, and > > returns to the prompt in my xterm, but now my xterm shows up with > > unrecognisable characters (normally for me: root@hostname, now something > > like: %^(%^%(%^&()_)_*). > > > > Did I hit a bug? > > Could you have wound up using a different character set? If you do a > hard reset on the xterm, does it start working right? Do characters > echo correctly? I'll admit that I have never seen this. I never changed my character set since I installed FreeBSD. I did change it in applications such as Pine and LyX from ISO-8859-1 to ISO-8859-15 for special characters used in Europe, but never system wide. I am using the standard bourne shell in FreeBSD by the way. When I exit the xterm and restart it the problem is gone, and works it ok. > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: [EMAIL PROTECTED]Phone: +1 510 486-8634 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > Marco -- So far as I can remember, there is not one word in the Gospels in praise of intelligence. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
> Date: Sat, 5 Oct 2002 00:29:48 +0200 (CEST) > From: Marco Beishuizen <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > Thanks! It worked great. I have one remark though: the option > "-allow-lower-case" wasn't recognised by mkisofs. Looking at the manpage > it should be "-allow-lowercase". :-) But this was of course one of those > days... I really should have done a cut and paste on the command or pulled in my shell script that runs mkisofs, but it's on a different system and it seemed easier to just type it in. > > Eventually, I didn't use the option "-allow-lowercase", but the cd has no > problems of using lowercase characters. All files I copied to the cd show > up like the way they appear in FreeBSD. I suspected that both -allow-lowercase and -allow-multidot were implicit in -r, but I had never actually tried it. > The remarkable thing was actually, that when I used the wrong option, > mkisofs says it doesn't recognise the option, quits the program, and > returns to the prompt in my xterm, but now my xterm shows up with > unrecognisable characters (normally for me: root@hostname, now something > like: %^(%^%(%^&()_)_*). > > Did I hit a bug? Could you have wound up using a different character set? If you do a hard reset on the xterm, does it start working right? Do characters echo correctly? I'll admit that I have never seen this. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
On Fri, 4 Oct 2002, the wise Kevin Oberman spoke, and said: > Sigh! Some days you just can't win. (Or type.) > > I just read my own post and realized that I messed up the second > burncd command. the commands are: > mkisofs -allow-lower-case -allow-multidot -d -L -r -o ~/newcd.iso path > burncd -f /dev/acd0c blank > burncd -s 4 -f /dev/acd0c data ~/newcd.iso fixate > ^^---Moved to the correct place! > > TGIF! > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: [EMAIL PROTECTED]Phone: +1 510 486-8634 > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message Thanks! It worked great. I have one remark though: the option "-allow-lower-case" wasn't recognised by mkisofs. Looking at the manpage it should be "-allow-lowercase". :-) But this was of course one of those days... Eventually, I didn't use the option "-allow-lowercase", but the cd has no problems of using lowercase characters. All files I copied to the cd show up like the way they appear in FreeBSD. The remarkable thing was actually, that when I used the wrong option, mkisofs says it doesn't recognise the option, quits the program, and returns to the prompt in my xterm, but now my xterm shows up with unrecognisable characters (normally for me: root@hostname, now something like: %^(%^%(%^&()_)_*). Did I hit a bug? Marco -- Fresco's Discovery: If you knew what you were doing you'd probably be bored. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
On Friday 04 October 2002 04:49 pm, Marco Beishuizen wrote: | On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said: | > Marco Beishuizen <[EMAIL PROTECTED]> wrote: | > > That did the trick. I wrote a file to the cd and fixate worked | > > correctly. At least I think it did, because when I want to mount | > > the cd to look at it, mount gives me an "invalid argument" | > > error. | > > | > > So my new problem is how to access a cd-rw with data on it. | > | > What kind of file did you write to the CD? Of course, it | > has to be an image of a supported filesystem (usually an | > ISO9660 image), otherwise you wouldn't be able to mount it. | > You can only mount filesystems. | > | > To create an ISO9660 filesystem image, use mkisofs (from | > the ports collection). Afterwards, use burncd to write | > that image to a CD-R or CD-RW. | > | > You can, of course, write an arbitrary file (a .tar file or | > whatever) to a CD, but then you can't mount it. You can | > read it back with dd, though. | > | > Regards | >Oliver | | Yes, I wrote an arbitrary file to the cd. A .pdf file actually. I | already thought the mount error had something to do with a missing | filesystem or something like that. | | I want to use the cd-writer to make periodic backups of important | files. The easiest thing to do would be to just "copy" the files with | burncd, like I did with the .pdf file. But it looks that I have to do | a bit more than that to use the cd-writer as a backup medium. | | I think I have to learn more about mkisofs and creating images etc. | :-) | | Marco If you want to back up with burncd, I suggest using "cdbackup" which is a program I wrote. If I can get some feedback on it I'll try to make it into a proper port. For now, it is self-contained; just type "cdbackup" when you get it and put it where you want it to live and it should "install itself." Use the -h option for help. Let me know if you have any questions. And if others want to try it out, let me know. It's 70K, so I'm going to send it just to Marco (and any others who request it), not to the entire list. It support incremental backups; it does not support appending to an open CD, though I could consider adding that in the future, I suppose. In my case my problem is that I have far more files than there is a spaced on a CD, rather than vice-versa, so that's the problem it's mainly meant to solve. -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
Sigh! Some days you just can't win. (Or type.) I just read my own post and realized that I messed up the second burncd command. the commands are: mkisofs -allow-lower-case -allow-multidot -d -L -r -o ~/newcd.iso path burncd -f /dev/acd0c blank burncd -s 4 -f /dev/acd0c data ~/newcd.iso fixate ^^---Moved to the correct place! TGIF! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
> Date: Fri, 4 Oct 2002 22:49:45 +0200 (CEST) > From: Marco Beishuizen <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said: > > > Marco Beishuizen <[EMAIL PROTECTED]> wrote: > > > That did the trick. I wrote a file to the cd and fixate worked correctly. > > > At least I think it did, because when I want to mount the cd to look at > > > it, mount gives me an "invalid argument" error. > > > > > > So my new problem is how to access a cd-rw with data on it. > > > > What kind of file did you write to the CD? Of course, it > > has to be an image of a supported filesystem (usually an > > ISO9660 image), otherwise you wouldn't be able to mount it. > > You can only mount filesystems. > > > > To create an ISO9660 filesystem image, use mkisofs (from > > the ports collection). Afterwards, use burncd to write > > that image to a CD-R or CD-RW. > > > > You can, of course, write an arbitrary file (a .tar file or > > whatever) to a CD, but then you can't mount it. You can > > read it back with dd, though. > > > > Regards > >Oliver > > Yes, I wrote an arbitrary file to the cd. A .pdf file actually. I already > thought the mount error had something to do with a missing filesystem or > something like that. > > I want to use the cd-writer to make periodic backups of important files. > The easiest thing to do would be to just "copy" the files with burncd, > like I did with the .pdf file. But it looks that I have to do a bit more > than that to use the cd-writer as a backup medium. > > I think I have to learn more about mkisofs and creating images etc. :-) Under V5 we should have UDF support. If that gets finished, you will have exactly this ability. Last I heard ti could only read but most of the write code had been completed. Until then, only ISO 9660 is supported on CDs. I suggest that you write this with the Rockridge extensions to allow "normal" file names. The command I use for this is: mkisofs -allow-lower-case -allow-multidot -d -L -r -o ~/newcd.iso path burncd -f /dev/acd0c blank burncd -f -s 4 /dev/acd0c data ~/newcd.iso fixate This should do the trick. I suspect that I may have a couple of redundant options in the mkisofs line as -r might imply one or more of the others. Please read the man page for mkisofs as -L may not be appropriate. The resulting CD should mount and look "just like" the original files on the UFS disk. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said: > Marco Beishuizen <[EMAIL PROTECTED]> wrote: > > That did the trick. I wrote a file to the cd and fixate worked correctly. > > At least I think it did, because when I want to mount the cd to look at > > it, mount gives me an "invalid argument" error. > > > > So my new problem is how to access a cd-rw with data on it. > > What kind of file did you write to the CD? Of course, it > has to be an image of a supported filesystem (usually an > ISO9660 image), otherwise you wouldn't be able to mount it. > You can only mount filesystems. > > To create an ISO9660 filesystem image, use mkisofs (from > the ports collection). Afterwards, use burncd to write > that image to a CD-R or CD-RW. > > You can, of course, write an arbitrary file (a .tar file or > whatever) to a CD, but then you can't mount it. You can > read it back with dd, though. > > Regards >Oliver Yes, I wrote an arbitrary file to the cd. A .pdf file actually. I already thought the mount error had something to do with a missing filesystem or something like that. I want to use the cd-writer to make periodic backups of important files. The easiest thing to do would be to just "copy" the files with burncd, like I did with the .pdf file. But it looks that I have to do a bit more than that to use the cd-writer as a backup medium. I think I have to learn more about mkisofs and creating images etc. :-) Marco -- What garlic is to salad, insanity is to art. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
Marco Beishuizen <[EMAIL PROTECTED]> wrote: > That did the trick. I wrote a file to the cd and fixate worked correctly. > At least I think it did, because when I want to mount the cd to look at > it, mount gives me an "invalid argument" error. > > So my new problem is how to access a cd-rw with data on it. What kind of file did you write to the CD? Of course, it has to be an image of a supported filesystem (usually an ISO9660 image), otherwise you wouldn't be able to mount it. You can only mount filesystems. To create an ISO9660 filesystem image, use mkisofs (from the ports collection). Afterwards, use burncd to write that image to a CD-R or CD-RW. You can, of course, write an arbitrary file (a .tar file or whatever) to a CD, but then you can't mount it. You can read it back with dd, though. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
On Fri, 4 Oct 2002, the wise Oliver Fromme spoke, and said: > Marco Beishuizen <[EMAIL PROTECTED]> wrote: > > I am trying to burn cd's with burncd. The first thing I tried was to blank > > an already burned cd with: > > > > burncd -f /dev/acd1c -s 4 blank fixate > > Don't fixate a blank CD-RW. Fixation is only required after > recording something on a CD-R or CD-RW. > > Regards >Oliver That did the trick. I wrote a file to the cd and fixate worked correctly. At least I think it did, because when I want to mount the cd to look at it, mount gives me an "invalid argument" error. So my new problem is how to access a cd-rw with data on it. Marco -- In America, any boy may become president and I suppose that's just one of the risks he takes. -- Adlai Stevenson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
On Fri, Oct 04, 2002 at 09:15:00PM +0200, Marco Beishuizen wrote: > > Hi, > > I am trying to burn cd's with burncd. The first thing I tried was to blank > an already burned cd with: > > burncd -f /dev/acd1c -s 4 blank fixate > > It seems that blanking is going ok, but when it tries to fixate I get the > following error: > > burncd: ioctl(CDRIOCFIXATE): Input/output error > > When I try to mount the cd-rw after that I get: > > cd9660: /dev/acd1c: Input/output error > > Does anyone knows what is going wrong? > > Thanks, > Marco I am just guessing here, but if you have just blanked it, there isn't anything to mount is there ? Also I am not entirely sure you should fixate it after blanking it, there isn't anything on it to fixate. Just some wild guesses on my part. -- Regards Cliff Sarginson The Netherlands Email: [EMAIL PROTECTED] Tel : +31 (0)10 4764595 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: burncd error
Marco Beishuizen <[EMAIL PROTECTED]> wrote: > I am trying to burn cd's with burncd. The first thing I tried was to blank > an already burned cd with: > > burncd -f /dev/acd1c -s 4 blank fixate Don't fixate a blank CD-RW. Fixation is only required after recording something on a CD-R or CD-RW. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
