Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I'm using Ubuntu 12.04, and every time I try to write an Ubuntu ISO image to a disk so I can install it, Unetbootin says /dev/sdb1 isn't mounted. But Ubuntu mounts the drive automatically when it's inserted, right? What can I do to make Unetbootin recognize the drive is mounted?

share|improve this question
    
here is a nice trick! to foll unetbootin [how-do-i-use-unetbootin-to-make-a-bootable-windows-usb-installer][1] [1]: askubuntu.com/questions/162174/… –  user141867 Mar 20 '13 at 3:47
add comment

2 Answers

It's possible, as beeju has suggested, that you just need to manually mount the drive. However, you are correct--usually, Ubuntu will automatically mount a drive when it is attached or powered on.

There are two common situations where the problem you've described occurs:

  1. Technically, drives are not mounted. Volumes (i.e., partitions) are mounted. If there is no partition on the drive, Ubuntu cannot mount it (neither automatically nor otherwise). If there is, but it's damaged or (this is much less likely) of a type Ubuntu doesn't recognize, it will also not be mounted.

  2. Unetbootin requires that the partition to which you write the contents of an .iso image be formatted FAT16 or FAT32. (And you should use FAT32 unless your image is tiny and you know you need to use FAT16.) Furthermore, it should be the first partition on the disk, and unless you really know what you're doing and know you need to do something differently, it should be the only partition on the disk and it should take up all the available space. Furthermore (though you don't usually have to do anything to make this the case), it should be a primary (not a logical) partition and the disk's partition table should be of type MSDOS.

If you have valuable data on your disk, then you shouldn't be writing an .iso image to it anyway, because that would destroy the data. Otherwise, you can safely address either or both of the above problems by creating a new partition table on the disk, and then creating a single partition, taking up all the available space, of type FAT32.

One easy way to do this is with the GParted Partition Editor, which is provided by the gparted package. You can install that package in the Software Center. Then run GParted. Select the drive in the drop-down menu at the upper-right corner of the GParted window. Make sure you've selected the correct drive--it would be bad to perform these data-destroying operations on the wrong disk!

Do Edit > Create Partition Table and accept the defaults. Then create a FAT32 partition, also with everything the default. This will make it a primary partition and as big as possible.

Then apply your changes by clicking the green check-mark. You can now mount the drive (or take it out and put it back in, and it should mount automatically). When GParted finishes, close out of it. Then you can write an .iso image to it with Unetbootin.


Alternatively, you might consider using a different method to write the .iso image to the drive, which would let you skip over formatting and mounting the drive.

You can use Startup Disk Creator for this purpose, as described in the official installation instructions.

You can also use dd from the command-line. See dd(1). If you have an .iso image called ubuntu-12.04-desktop-i386.iso and located in your Downloads folder, and if you would write its contents to /dev/sdb1 in Unetbootin, then the corresponding dd command is:

cd ~/Downloads
sudo dd if=ubuntu-12.04-desktop-i386.iso of=/dev/sdb

It's very important that you tell it to output to /dev/sdb (or whatever drive you want it on), not /dev/sdb1 (i.e., not the first partition on the drive).

share|improve this answer
1  
I was struggling for a while too, it was the filesystem format of the stick that kept it hidden. Formatting it to FAT32 solves the problem. –  topless Oct 20 '12 at 14:31
    
This is a perfectly good answer. Why isn't it marked as accepted? –  Eran Harel Jan 22 at 19:21
add comment

I welcome you here!I think it is a common behavior by Ubuntu because the same I experienced on many occasions.What I do at these time that just click on the drive and open it in Nautilus window.Then come back to the particular application which need this drive.It is clearly described here.Moreover,it is better to see this drive is displayed in File system>Media.

share|improve this answer
add comment

Your Answer

 
discard

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.