LinuxQuestions.org - Weird failures burning iso

- Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)

- - Weird failures burning iso (https://www.linuxquestions.org/questions/ubuntu-63/weird-failures-burning-iso-514650/)

Quote:

Originally Posted by duns0014

This is weird. It turns out it did crap out at 732 MB, even though both the iso and the cd are smaller than that. I had a bs of 2048 and a count of 357565, that last number was also how many records in and out I got when dd'd the file.

yeah, i just did a dd of my ubuntu 6.10 cd and it does give "732 MB"... i guess it's due to the thing about a megabyte being 1000 bytes to some and 1024 bytes to others...

Code:

win32sux@candystore:~$ dd if=/dev/cdrom bs=2048 count=357565 conv=notrunc,noerror | md5sum

357565+0 records in

357565+0 records out

732293120 bytes (732 MB) copied, 160.036 seconds, 4.6 MB/s

b950a4d7cf3151e5f213843e2ad77fe3  -

as you can see, my MD5SUM does check-out, though... my guess is your problem lies in your cdrecord command, but since you haven't posted it i have no way to tell...

Quote:

I saw that the install icon on the desktop links to gksudo --desktop %k ubiquity gtkui, can I just run ubiquity from the command line to see output, or won't that work?

i have no idea what you are talking about, but i'm sure someone else does, though...

Yeah, I was just going to post that about 1000 or 1024 bytes. I don't know if it's cdrecord because I tried the same thing with some windows program and that didn't work either. What exact command should I use for cdrecord? Can I use dd to burn an iso?

Once Ubuntu gets to the desktop, there's the Install icon. That's what I was talking about with regard to ubiquity.

Quote:

Originally Posted by duns0014

What exact command should I use for cdrecord?

optimally you'd wanna burn with a command like this (adjust your speed of course):

Code:

cdrecord dev=/dev/cdrom speed=32 padsize=63s -pad -dao -v /home/win32sux/iso/ubuntu-6.10-desktop-i386.iso

i put in bold the parts which people typically forget (and consequently end-up with I/O errors such as what it sounds like you are getting)...

Quote:

Can I use dd to burn an iso?

i seriously doubt it...

Quote:

Once Ubuntu gets to the desktop, there's the Install icon. That's what I was talking about with regard to ubiquity.

oh, okay... well, i'm not sure...

Ok, I tried that cdrecord command and it didn't work. The md5sum still didn't check out and it still hung while trying to install. One thing it said while I was burning was

warning: drive returns bad startsec (0) using -150

No idea what that means. It also said total size = 802MB and there was a padsize of 126kB. What's with that? What's the pad for anyway? How can it even be this difficult to burn an iso? I think I may have to order them from the website.

Quote:

Originally Posted by duns0014

well, i'd google the error to see if i'd find something useful if i was you...

Quote:

No idea what that means. It also said total size = 802MB and there was a padsize of 126kB. What's with that? What's the pad for anyway?

from "man cdrecord":

Code:

      -pad  If the track is a data track, 15 sectors of zeroed data will  be

              added  to  the  end  of this and each subsequent data track.  In

              this case, the -pad option is superseded by the padsize= option.

              It  will  remain however as a shorthand for padsize=15s.  If the

              -pad option refers to an audio  track,  cdrecord  will  pad  the

              audio  data  to  be  a  multiple  of 2352 bytes.  The audio data

              padding is done with binary zeroes which is  equal  to  absolute

              silence.



              -pad remains valid until disabled by -nopad.



      padsize=#

              Set  the  amount  of  data to be appended as padding to the next

              track to #.  Opposed to the behavior of  the  -pad  option,  the

              value  for  padsize=  is  reset  to  zero  for  each  new track.

              Cdrecord assumes a sector size of 2048 bytes  for  the  padsize=

              option,  independent  from  the real sector size and independent

              from the write mode.  The megabytes  mentioned  in  the  verbose

              mode output however are counting the output sector size which is

              e.g. 2448 bytes when writing in RAW/RAW96 mode.  See fs=  option

              for  possible arguments.  To pad the equivalent of 20 minutes on

              a CD, you may write padsize=20x60x75s.  Use this option if  your

              CD-drive  is  not able to read the last sectors of a track or if

              you want to be able to read the CD on a Linux  system  with  the

              ISO-9660  filesystem  read  ahead bug.  If an empty file is used

              for track data, this option may be used to create a disk that is

              entirely made of padding.  This may e.g. be used to find out how

              much overburning is possible with a specific media.

Quote:

How can it even be this difficult to burn an iso? I think I may have to order them from the website.

well, the difficulty is subjective... i find it pretty simple and easy to run a single command and have my ISO burned to perfection... maybe you have a hardware compatibility issue or something, i don't know... perhaps you'll get a better idea of where you stand if you google the latest error message you got...

that said, maybe you'd be more comfortable (and have better luck) using a GUI burning tool - there's tons of them and your distro should indeed include one... of course, ordering a pressed CD is also great, but if i was you i'd hang in there and try to fix this issue cuz it really sucks to not be able to burn proper CDs...

I googled it, no help. As for gui tools, I'd love to use k3b, but my mepis install was hosed and I can't use X in it now. That's why I tried gui tools in windows. And all of that is why I need to do a complete reinstall.

When I said it was difficult, I meant that I thought there was pretty much one way to burn an iso and that's it. I can see tags for speed and drive, but what's with that other stuff? I still don't understand why there's a pad.