0

I am doing this with USB 2.0 Flash Drive 8GB. Here is what i am doing: Open GParted: Gparted Then i am trying to create new partition and i've god this message: error_message After that i am going to Device/Create Partition Table and i am clicking Aply: error_message Then i am trying again to create a new partition and the same error: error_message

This is GParted console log:

======================
libparted : 2.3
======================

(gpartedbin:3854): GLib-CRITICAL **: Source ID 7 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 26 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 25 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 31 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 30 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 36 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 35 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 39 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 38 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 42 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 41 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 47 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 46 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 50 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 49 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 55 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 54 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 58 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 57 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 219 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 218 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 301 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 300 was not found when attempting to remove it
/dev/sdb: unrecognised disk label
/dev/sdb: unrecognised disk label

(gpartedbin:3854): GLib-CRITICAL **: Source ID 756 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 755 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 762 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 761 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 770 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 769 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 773 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 772 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 776 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 775 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 779 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 778 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 784 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 783 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 787 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 786 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 792 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 791 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 795 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 794 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 907 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 906 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 1001 was not found when attempting to remove it

(gpartedbin:3854): GLib-CRITICAL **: Source ID 1000 was not found when attempting to remove it
/dev/sdb: unrecognised disk label

I have also tried and:

(parted) print                                                            
Error: /dev/sdb: unrecognised disk label                                  
(parted) mklabel 
(parted) mklabel msdos
(parted) rescue                                                           
Start? 0                                                                  
End? 976773168                                                            // This was just a random guess.
Information: A ntfs primary partition was found at 32.3kB -> 500GB.  Do you want to add it to the partition table?
Yes/No/Cancel? yes                                                        
(parted) quit                                                             
Information: You may need to update /etc/fstab.

But after rescue i've go this:

radibg2@radibg2:~$ sudo parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                            
Error: /dev/sdb: unrecognised disk label                                  
(parted) mklabel                                                          
New disk label type? msdos                                                
(parted) mklabel msdos                                                    
(parted) rescue                                                           
Error: /dev/sdb: unrecognised disk label                                  
(parted)             

Also tried and low level format:

dd if=/dev/zero of=/dev/sdb bs=1M

and all above over but all the same again.

  • 1
    Error: /dev/sdb: unrecognised disk label makes me think the disk is either severely broken or contains a very obscure earlier format. Do you receive ANY read/write errors from sudo dd if=/dev/zero of=/dev/sdb bs=1M count=1 or from your try (above) with dd ? How about dmesg content just after such a try? – Hannu Sep 1 '14 at 17:07
  • A ntfs primary partition was found at 32.3kB -> 500GB and the size shown by gparted: 7.47 GiB doesn't match - yet another strange fact. The first might simply be wrong though. But as you have not stated what kind of disk/media this is... – Hannu Sep 1 '14 at 17:18
  • From this sudo dd if=/dev/zero of=/dev/sdb bs=1M count=1: 1+0 records in, 1+0 records out, 1048576 bytes (1,0 MB) copied, 0,0597242 s, 17,6 MB/s and from my try with dd i have no errors. dmesg - pastebin.com/cbqcN7qa – radibg2 Sep 1 '14 at 18:30
1

Problems with gparted may have different causes. Two of them will be discussed here:

  • The drive contains confusing data
  • The drive might be failing

Confusing data

Sometimes gparted is confused by the content of the partition table or some additional information for example the the drive has been used with RAID or as a boot drive made from a hybrid ISO file. In some of these cases some versions of gparted will refuse to create a new partition table and new file systems.

Then it is possible to wipe the confusing information. Most of the time it is enough to wipe the first megabyte (mibibyte), to overwrite it with zeros. It can be done with dd, but dd is a dangerous tool. mkusb 'wraps a safety belt' around dd, and helps you do it safer.

See this link: help.ubuntu.com/community/mkusb

enter image description here

After wiping you can use gparted again. Create a partition table and after that you can create partitions with file systems.

enter image description here

The drive might be failing

If mkusb cannot fix the problem, the drive might be failing. It often starts with the symptom that the drive is read only (not only the partitions with file system, but the drive itself). This can happen with USB pendrives and memory cards, and is the first stage in the failing process. It is sometimes called 'gridlock'.

But there might be other causes of the problem, so it is worth trying a few things before you give up.

When a pendrive or memory card is read-only

  • On some pendrives and on many memory cards there is a small mechanical switch for write protection, that can toggle between read/write and read-only. - You might have set it read-only without intention.
  • Reboot the computer and try again to wipe the first megabyte with mkusb.
  • Disconnect other USB devices. Sometimes USB devices can disturb the function for each other.
  • Try other USB ports and another computer.
  • Try another operating system (Windows, MacOS) in another computer.
  • If you still cannot wipe the first megabyte of the drive, and the drive is read-only, it is 'gridlocked', and the next stage is that it will be completely 'bricked'.

You can find more details at the following link: Pendrive lifetime

0

On the top bar of Gparted there is tab called "Device", it has the option called "Create Partition Table", or maybe you can try using any other partioning tool, "Disks" comes installed with ubuntu 14.04

  • As you can see i already tried with Create Partition Table. And when i type Disks in the terminal it says Disks: command not found, i am using Ubuntu 14.04.1 – radibg2 Sep 1 '14 at 15:42
  • 1
    @user307938 The tool is called Disks, but the command is gnome-disks. Or you can search for Disks in the Launcher. – muru Sep 1 '14 at 15:43
  • When i open Disks the only active menus are Power Off the device, Eject the medium in the drive and Settings/Power off... – radibg2 Sep 1 '14 at 15:47
0

I'd try good old fdisk and see if that can create the partition. I'd also use dmesg to see if there are any disk IO errors appearing to indicate that perhaps it's not been able to write.

What's the disk - is it a normal USB flash drive or something special?

  • It is normal USB flash drive 8gb – radibg2 Sep 1 '14 at 18:23
  • I had similar issues with a Lexar brand thumb drive. I eventually had to format it on a Windows machine. – Organic Marble Sep 1 '14 at 19:07
  • I have tried and on Windows with no success. – radibg2 Sep 2 '14 at 7:27
  • If all of the partition tools you tried fail to write to the flash drive, this suggests that something is preventing write actions. If the flash drive has a write protect switch, then be sure to enable write actions. Otherwise it is possible that the flash drive is failing. You can check for hardware errors by running the dmesg command and looking for problems related to the flash drive device. – Curtis Gedak Sep 4 '14 at 16:50
-1
  1. Create a Primary partition with ext4 file system

    • Right-click on unallocated USB (/dev/sdb) and choose first option new ( insert )
    • Choose File system type ext4 and click Add. see image below.

      Gparted USB format

    • Now complete this pending operation using green right icon above to the disk information panel.

    Note: Sometimes you can get an error, but don't panic, unplug and plug back, first do unmount the USB /dev/sdb using context menu of /dev/sdb and repeat step 1

  2. Format to fat32

    • After the completion of above operation , again right-click on /dev/sdb and choose Format to > and choose fat32 (If you require this USB to be used on Windows too)

    • Apply to complete this operation .

Now your USB is formatted with read write permission

To confirm this: navigate to the USB location from Places and right-click on opened USB , you can see that the Create new folder and Create new document options are now active.

I hope this helps you.

  • Thank you @karel for fixing grammar.I would be more thankful if you suggest/tell me any particular link where I can improve. gives a set of essential words for technical terms and including professional sentence structure example. – diEcho Jan 13 '15 at 8:58
  • 2
    As far as I know, the classic book about writing in English generally is The Elements of Style which can be downloaded from archive.org. For help decoding technobabble I like the Linux Action Show and Coder Radio. – karel Jan 13 '15 at 11:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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