blkid and gparted are extremely slow in a persistent live session

[sudodus]

sudo blkid is extremely slow in a persistent live session (9 min 20 seconds)
but finally it finds loop mounted devices and zRAM devices
sudo blkid /dev/sd* is responsive as usual, also
sudo blkid /dev/[hslz]* but not
sudo blkid /dev/f*

Is the problem that it spends this time searching for a non-existing floppy drive?

This is not a problem in previous Ubuntu systems, for example the main installed system Ubuntu 12.04.2 precise

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: util-linux 2.20.1-5.1ubuntu9
ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
Uname: Linux 3.10.0-5-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
CasperVersion: 1.335
Date: Fri Jul 26 07:27:38 2013
LiveMediaBuild: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130723.1)
MarkForUpload: True
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.hwclock.save.conf: [deleted]

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1205199

[sudodus (nio-wiklund)]

Gparted is also extremely slow (but finally finds what it should find). I think it is because of this same problem that makes blkid slow.

[sudodus (nio-wiklund)]

I installed Lubuntu Saucy from the persistent live system, and the installed system does not suffer from this bug (in the same computer).

[Curtis Gedak (gedakc)]

GParted uses blkid to acquire information about partitions so it is not surprising that GParted is also impacted by this blkid behaviour.

This problem can happen in GParted if the BIOS indicates that a floppy drive is present, but no physical floppy device is installed.

A work-around to this problem is to disable the floppy drive in the BIOS.

See http://gparted.org/faq.php#faq-11

[Phillip Susi (psusi)]

Yes, if you do not have a floppy drive, then your bios must not be configured to think that you do.