Gparted starts very very slow and "buggy"

[AkumA]

Binary package hint: gparted

Hi!
I'm working on few problem with my partitions and i've noticed that GParted in Ubuntu Gutsy is very slow: i have to wait about 5-6 minutes before the devices appear.
After a successful operation the device reading takes once again a lot of time but ends by closing GParted.

I've tried Ubuntu 7.04 live cd and it loads immediatly, operations where successful without any problem.
I've tried to uninstall and purge GParted but nothing changes..

[Andrea Corbellini (andrea.corbellini)]

Thanks for taking time report this bug!
GParted crashes at the end of the operations is a known bug, but it shouldn't be slow. Could you please attach here the output of the command `sudo fdisk -l`?
Also, is your disk too much fragmented?

[Robert Crosbie (swingincelt)]

I have the some problem after upgrade from 7.4 to 7.10. System application are very sluggish to start in general, but gparted takes about 5 minutes to start.

:~$ sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000f404a

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 4866 39086113+ 7 HPFS/NTFS
/dev/sda2 4867 4988 979965 83 Linux
/dev/sda3 4989 18042 104856255 83 Linux
/dev/sda4 18043 60801 343461667+ 5 Extended
/dev/sda5 60280 60801 4192965 82 Linux swap / Solaris
/dev/sda6 18043 60279 339268639+ 83 Linux

Partition table entries are not in disk order

[Robert Crosbie (swingincelt)]

Here is the console output:
:~$ gksu gparted
======================
libparted : 1.7.1
======================
Unable to open /dev/fd0 read-write (Read-only file system). /dev/fd0 has been opened read-only.
Unable to open /dev/fd0 - unrecognised disk label.
Unable to open /dev/hda read-write (Read-only file system). /dev/hda has been opened read-only.
Unable to open /dev/hda - unrecognised disk label.

There is about a minute or more before each message.

This curious because I don't have a floppy disk nor do I have any connected IDE drives. I only have a sata drive which is attached to /dev/sda.

[AkumA (zio-protestante)]

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x14211421

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 2611 20972826 7 HPFS/NTFS
/dev/sda2 2612 8149 44483985 83 Linux
/dev/sda3 8150 8672 4200997+ 82 Linux swap / Solaris
/dev/sda4 8673 38913 242910832+ 5 Extended
/dev/sda5 8673 10630 15727603+ 83 Linux
/dev/sda6 10631 12588 15727603+ 83 Linux
/dev/sda7 12589 38913 211455531 83 Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000001

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 16907 135805446 7 HPFS/NTFS
/dev/sdb2 16908 19457 20482875 83 Linux

I confirm that it takes too much time to start..
Ubuntu 7.04 Live CD has a Lightning Fast GParted that reads and mounts the same partitions almost instantaneously..

[Andrea Corbellini (andrea.corbellini)]

Thanks to all!
AkumA, can you please add a traceback too? To to this run `sudo gparted` in a terminal and attach here the output you see.

[vanbosco (vanbosco)]

Same problem (5-6 minutes to wait before gparted start) with kubuntu gutsy.
This is the console output:
======================
libparted : 1.7.1
======================
Impossibile aprire /dev/fd0 in lettura/scrittura (File system in sola lettura). /dev/fd0 è stato aperto in sola lettura.
Impossibile aprire /dev/fd0 - etichetta del disco sconosciuta.

And this is the result of fdisk -l:
Disco /dev/hda: 300.0 GB, 300090728448 byte
255 heads, 63 sectors/track, 36483 cylinders
Units = cilindri of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000001

Dispositivo Boot Start End Blocks Id System
/dev/hda1 * 1 3824 30716248+ 83 Linux
/dev/hda2 3825 36352 261281160 f W95 Esteso (LBA)
/dev/hda3 36353 36483 1052257+ 82 Linux swap / Solaris
/dev/hda5 3825 8923 40957686 83 Linux
/dev/hda6 8924 22636 110149641 83 Linux
/dev/hda7 22637 36352 110173738+ 83 Linux

Disco /dev/hdb: 41.1 GB, 41110142976 byte
255 heads, 63 sectors/track, 4998 cylinders
Units = cilindri of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ed33e

Dispositivo Boot Start End Blocks Id System
/dev/hdb1 * 1 1824 14651248+ 83 Linux
/dev/hdb2 1825 3411 12747577+ 83 Linux
/dev/hdb3 3412 4998 12747577+ 83 Linux

[AkumA (zio-protestante)]

@ Andrea: eccotelo qua :)

Here it is:
======================
libparted : 1.7.1
======================
Unable to open /dev/fd0 read-write (Read-only file system). /dev/fd0 has been opened read-only.
Unable to open /dev/fd0 - unrecognised disk label.

[Xandi (launchpad-net-20-taube)]

Same problem to me:

guru@guru-desktop:~$ sudo fdisk -l

Disk /dev/sda: 360.0 GB, 360080695296 bytes
255 heads, 63 sectors/track, 43777 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd294d294

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 3872 31101808+ 7 HPFS/NTFS
/dev/sda2 3873 9951 48829567+ 83 Linux
/dev/sda3 9952 10401 3614625 82 Linux swap / Solaris
/dev/sda4 10402 43777 268092720 83 Linux

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
1 heads, 34 sectors/track, 14364622 cylinders
Units = cylinders of 34 * 512 = 17408 bytes
Disk identifier: 0x00070ffb

   Device Boot Start End Blocks Id System
/dev/sdb1 2 14364473 244196009+ 83 Linux
guru@guru-desktop:~$ sudo gparted
======================
libparted : 1.7.1
======================
Kann /dev/fd0 nicht zum Schreiben öffnen (Read-only file system). /dev/fd0 wurde nur zum Lesen geöffnet.
/dev/fd0 kann nicht geöffnet werden - unerkanntes Disklabel.
guru@guru-desktop:~$

[alapidas (alapidas)]

Same problem, fresh install of gusty x86, running gparted:

======================
libparted : 1.7.1
======================
Unable to open /dev/fd0 read-write (Read-only file system). /dev/fd0 has been opened read-only.
Unable to open /dev/fd0 - unrecognised disk label.

[Pierre-Yves (py-bretecher)]

Same problem for me.
I can also add that it is the same with Hardy Alpha2 :

Dec 31 18:18:26 pc-fixe2 kernel: [ 4383.667240] end_request: I/O error, dev fd0, sector 0
Dec 31 18:19:31 pc-fixe2 kernel: [ 4448.438064] Buffer I/O error on device fd0, logical block 0

py@pc-fixe2:~$ sudo fdisk -l
[sudo] password for py:

Disque /dev/sda: 74.3 Go, 74355769344 octets
255 heads, 63 sectors/track, 9039 cylinders
Units = cylindres of 16065 * 512 = 8225280 bytes
Disk identifier: 0x1ef61ef5

Périphérique Amorce Début Fin Blocs Id Système
/dev/sda1 * 1 2550 20482843+ 7 HPFS/NTFS
/dev/sda2 2551 6005 27752287+ 83 Linux
/dev/sda3 6006 6248 1951897+ 82 Linux swap / Solaris
/dev/sda4 7711 9024 10549248 de Dell Utility

Disque /dev/sdb: 203.9 Go, 203928109056 octets
255 heads, 63 sectors/track, 24792 cylinders
Units = cylindres of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe4f5e90f

Périphérique Amorce Début Fin Blocs Id Système
/dev/sdb1 1 20230 162497443+ b W95 FAT32

[richteel (richteel)]

I just installed gusty, applied all updates and have the same problem with gparted. Is there a fix or a workaround besides using the live cd?

administrator@richteel-ws:~/Desktop$ sudo fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ca556

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 37457 300873321 83 Linux
/dev/sda2 37458 38913 11695320 5 Extended
/dev/sda5 37458 38913 11695288+ 82 Linux swap / Solaris

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0002bbc3

   Device Boot Start End Blocks Id System
/dev/sdb1 1 38913 312568641 83 Linux

Disk /dev/sdc: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d1bcd

   Device Boot Start End Blocks Id System
/dev/sdc1 1 38913 312568641 83 Linux

Disk /dev/sdd: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003fefb

   Device Boot Start End Blocks Id System
/dev/sdd1 1 38913 312568641 83 Linux

[crf (chrisfahlman)]

Maybe because it is scanning for floppy drives?
There are already bugs about that issue in launchpad, and in gnome bugzilla.
http://bugzilla.gnome.org/show_bug.cgi?id=351753
It says that the problem should have been solved in their new release in libparted (which gparted uses), which is not in ubuntu at present.

A workaround to specify the device you want to work with, as described at the link above. http://bugzilla.gnome.org/show_bug.cgi?id=351753#c13
Or you can perhaps disable the floppy drive in the bios.

[adder1972 (adder1972)]

I had the same problem, i.e. very long scan time when starting Gparted in Ubuntu 7.10 64-bit.

I disabled Floppy in the BIOS (I have no floppy installed), and the problem was solved.

[IKT (ikt)]

I had the same problem, i.e. very long scan time when starting Gparted in Ubuntu 7.10 32-bit.

I disabled Floppy in the BIOS (I have no floppy installed), and the problem was solved.

[black (blackborn)]

Should this be fixed in ubuntu 8.04?
Because gparted is still slow on ubuntu 8.04, if i doesn't disable the floppy in the bios

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

This is fixed in Jaunty now. Thanks for reporting.

[Pedric (pedric)]

I found gparted to suffer of a extremly slow start with one of my few remaining fat32 partitions. While scanning for devices, gparted runs dosfsck -a -v, which, when automatically scans for errors and tries to repair them. For large fats, this takes a long time and greatly impairs the ability to use gparted at all...

[mickey57 (mickeycook1957)]

Not fixed.Running karmic:
Jun 1 16:14:51 mickey-desktop kernel: [27533.593044] end_request: I/O error, dev fd0, sector 0
Jun 1 16:14:53 mickey-desktop kernel: [27535.169070] end_request: I/O error, dev fd0, sector 0
Jun 1 16:15:01 mickey-desktop kernel: [27543.009045] end_request: I/O error, dev fd0, sector 0
Jun 1 16:15:13 mickey-desktop kernel: [27555.189051] end_request: I/O error, dev fd0, sector 0
Jun 1 16:15:28 mickey-desktop kernel: [27570.189068] end_request: I/O error, dev fd0, sector 0
Jun 1 16:15:38 mickey-desktop kernel: [27580.185046] end_request: I/O error, dev fd0, sector 0
Jun 1 16:15:53 mickey-desktop kernel: [27595.185032] end_request: I/O error, dev fd0, sector 0
Jun 1 16:16:12 mickey-desktop kernel: [27614.049044] end_request: I/O error, dev fd0, sector 0
Jun 1 16:16:18 mickey-desktop kernel: [27620.133052] end_request: I/O error, dev fd0, sector 0
Jun 1 16:16:36 mickey-desktop kernel: [27638.033046] end_request: I/O error, dev fd0, sector 0
Jun 1 16:16:48 mickey-desktop kernel: [27650.185057] end_request: I/O error, dev fd0, sector 0
Jun 1 16:17:01 mickey-desktop kernel: [27663.109078] end_request: I/O error, dev fd0, sector 0
Jun 1 16:17:13 mickey-desktop kernel: [27675.189046] end_request: I/O error, dev fd0, sector 0
Jun 1 16:17:28 mickey-desktop kernel: [27690.185044] end_request: I/O error, dev fd0, sector 0
Jun 1 16:17:48 mickey-desktop kernel: [27710.185061] end_request: I/O error, dev fd0, sector 0
Jun 1 16:18:12 mickey-desktop kernel: [27734.045045] end_request: I/O error, dev fd0, sector 0
Jun 1 16:18:18 mickey-desktop kernel: [27740.185048] end_request: I/O error, dev fd0, sector 0
Jun 1 16:18:43 mickey-desktop kernel: [27765.185047] end_request: I/O error, dev fd0, sector 0
Jun 1 16:19:03 mickey-desktop kernel: [27785.185044] end_request: I/O error, dev fd0, sector 0
Jun 1 16:19:23 mickey-desktop kernel: [27805.185046] end_request: I/O error, dev fd0, sector 0
Jun 1 16:19:28 mickey-desktop kernel: [27810.185040] end_request: I/O error, dev fd0, sector 0
Jun 1 16:19:40 mickey-desktop kernel: [27822.033041] end_request: I/O error, dev fd0, sector 0
Jun 1 16:19:48 mickey-desktop kernel: [27830.185042] end_request: I/O error, dev fd0, sector 0
Jun 1 16:19:59 mickey-desktop kernel: [27841.277043] end_request: I/O error, dev fd0, sector 0
Jun 1 16:20:00 mickey-desktop kernel: [27842.125064] end_request: I/O error, dev fd0, sector 0
Jun 1 16:20:08 mickey-desktop kernel: [27850.185041] end_request: I/O error, dev fd0, sector 0
Jun 1 16:20:18 mickey-desktop kernel: [27860.185069] end_request: I/O error, dev fd0, sector 0
Jun 1 16:20:28 mickey-desktop kernel: [27870.185053] end_request: I/O error, dev fd0, sector 0
Jun 1 16:20:36 mickey-desktop kernel: [27878.757048] end_request: I/O error, dev fd0, sector 0
Jun 1 16:20:42 mickey-desktop kernel: [27883.893062] end_request: I/O error, dev fd0, sector 0
Jun 1 16:20:53 mickey-desktop kernel: [27895.185050] end_request: I/O error, dev fd0, sector 0
Jun 1 16:21:23 mickey-desktop kernel: [27925.185067] end_request: I/O error, dev fd0, sector 0

[Andrea Corbellini (andrea.corbellini)]

@mickey57: Are you using gparted (Gnome) or qtparted (KDE)?

[Jonathan Thomas (echidnaman)]

QtParted is unmaintained, so this will likely not be fixed.
KDE users are now recommended to use the "partionmanager" package to manage their paritions.

[pq (pqnet)]

don't know if it's related: gparted is running a "ntfsresize --info" for each unmounted ntfs partition, to see if it's possible to resize it, each time it reloads the list of partitions. If you have a large disk it could be taking a lot of time. I think it runs a similar check for other kinds of partitions.

That seems stupid implementation more than a bug. Being very time consuming it should be done only if I express interest in resizing a particular partition.