Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have a CD that's created from an ISO file which I use to install a custom version of Ubuntu via plop linux.

The cd works fine but I'd like to use a bootable USB drive instead. I used the command dd to try and create the bootable USB:

dd if=filename.iso of=/dev/sdb1 bs=4k

Now this does copy the files and make the USB bootable but I get the error "Missing operating system"

Any ideas?

share|improve this question
Do you only have access to the command line? There are interfaces like Unetbootin that work very well and run on linux.. – dashboard May 3 '13 at 21:38
@dashboard I would prefer command line because it is available on every linux machine. – xsdf May 6 '13 at 12:40
@dashboard - The GUI tools never seem to work well for me, and this has consistently been true over many years. I'm happy to know the command line method. I find it easier and more reliable. It is a lot less frustrating! – MountainX Sep 18 at 20:36

2 Answers 2

up vote 32 down vote accepted

Ok after some research I've figured out a solution, and I'll go through it step by step. Problem was two-fold.

  1. Plug in the USB flash drive and determine the device it's mounted on with the command:

    sudo fdisk -l

    This time around it was /dev/sdc1 for me, so I'll use that as my example.

  2. Umount the device

    umount /dev/sdc1
  3. Not sure if necessary but I formatted the drive in FAT32, just in case

    sudo mkdosfs -n 'USB-Drive-Name' -I /dev/sdc -F 32
  4. Now my ISO was using isolinux not syslinux. I knew it worked with CDs so I figured out that I needed to call the isohybrid command, which allows for an ISO to be recognized by the BIOS from a hard drive.

     isohybrid filename.iso

    You can find out more about this command here, but this was the cause of the message "Missing Operating System" The first problem was fixed, but now it said "isolinux.bin was missing or corrupt"

  5. The next step is to copy the iso. My second problem lay here, where I was copying to the partition, sdc1, not the device, sdc.

    sudo dd if=filename.iso of=/dev/sdc bs=4k

    This seems to work just fine, but the forum where I got the last fix, it was recommended to do the following before unplugging the device:

    sudo eject /dev/sdc
share|improve this answer
Here's a way to check for dd's progress: – Nikos Alexandris May 29 '14 at 7:00
Making an assumption here, I think the mkdosfs command may not be necessary, since the iso has a filesystem located on it already (probably including an MBR, not sure) that is copied over to the beginning of the block device. Man, isohybrid is a cool command, didn't know about it! – Ehtesh Choudhury Oct 9 '14 at 3:55
for windows 7 bootable install USB, also see… – cwd Oct 16 '14 at 0:34
Step #3 is unnecessary; the dd command in step #5 will obliterate the newly created filesystem with the contents of the ISO. – ewhac Feb 18 at 23:53

This is a common issue with SanDisk USB sticks, or sticks not formatted in FAT32.

If not either of those it is most certainly an issue with your stick partition order or the syslinux.cfg file.

share|improve this answer
USB flash drive is from Verbatim. I reformatted in FAT32 just to be sure and still got same error. – xsdf May 3 '13 at 20:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.