Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is happening on both Ubuntu 12.04 and Lubuntu 12.04 (the latter after I got frustrated to the point of formatting and reinstalling).

I have an Asus Eee with a built in SD card slot. I used to use an 8GB card for storage with no problems, but recently upgraded to a 32GB card. When I insert the card, nothing happens. It is not automatically mounted like the 8GB one was. When I type in sudo fdisk -l, the information for /dev/sda appears immediately, but the computer then pauses several minutes before giving the information about /dev/sdb (which is the SD card slot).

I have to manually mount the card via sudo mount /dev/sdb1 /media/SIGMA. This takes even longer than fdisk; up to ten minutes. The drive is then mounted and accessible, but does not appear in the Places section of the Lubuntu file manager.

I don't know very much about diagnostics. Is there any way to tell whether the new SD card is damaged? Alternatively, can you suggest how to work out what is going wrong and how to fix it?

EDIT: Should point out that the SD card mounted with no problems on Windows 7.

EDIT2: The output from sudo blkid was:

/dev/sdb1: LABEL="SIGMA" UUID="148ACD4F8ACD2E54" TYPE="ntfs" 

EDIT3: See my comment to fabricator4's answer below. I added the SD card to the fstab file with the following line. The card now mounts automatically on boot, however it still takes a very long time for this to mount, which means booting the computer now takes several minutes longer than it used to. Have you got any idea what may be causing it to take so long?

/dev/sdb1 /media/SIGMA ntfs nls=utf8,umask=000,uid=1000,gid=1000 0 0
share|improve this question

I've just put a 32GB verbatim SD card in my EeePC 900SD and have it mounting as /home. It's working great. I did delete the partition table and remade it with gparted as I've seen problems with Verbatim partition tables on SD cards and USB sticks.

Have a look at the this question and my my answer for possible reasons for the problem and the solution.

In particular you might try this test from that that answer to verify the problem:

  • Running fdisk -l on the thumbdrive will often declare that it has no partition table, even though you know there is one and can write data to it if it is still mounting OK.

If you have a 900SD or similar I can recommend using the SD card to mount as /home, since the SSD is generally only 8GB - fine for Ubuntu but a bit tight if you store any work or data on it at all.

share|improve this answer
Also, fdisk -l never gave any errors about the partition table. – thornate Jan 12 '13 at 9:31
I followed those instructions to delete and rewrite the partition table, but it didn't make a difference. – thornate Jan 14 '13 at 10:23
OK, we'll try adding the card to the fstab file which will allow L/ubuntu to know exactly what it is mounting, but I'll need a bit more information about how Ubuntu is seeing the card. Please edit your question and add the output of the command "sudo blkid" – fabricator4 Jan 14 '13 at 10:58
I've added the information to the original post. I also tried adding the SD card to fstab. Referring to the drive by the UUID didn't work (error message saying "The disk drive for /media/SIGMA is not ready yet or not present"), but referring to it in fstab as /dev/sdb1 did work. However, the long delay in mounting still occurred, which means that it took ages for the computer to boot. – thornate Jan 15 '13 at 13:23

if it is a hardware issue it should be mentioned in the log-files (Gnome Log File Viewer or the output of dmesg should do) just search for the vendor name or other device references (sdb1) and see if any errors or warnings are mentioned

But: I think its more likely to be a problem with ntfs. Ether the partition( a had some compatibility problems with window/linux created partitions) or the driver on your linux.
Make sure you have the latest ntfs-3g installed and check the volume for errors (enforce a full check)

share|improve this answer
How do I check for errors? – thornate Jan 20 '13 at 12:32

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.