G parted takes forever to scan all devices

[jamesmayxt]

    I have used G parted on many occasions & never had to wait 8 to 9 minutes for G parted
    to run thru its initial scan usually its seconds not minutes .I am using the LXDE version
     fully updated I have removed & reinstalled G parted still the same problem
     Any one else having similar problems ?                                          thanks   

[ThirdOfSix]

On the chance that it is one of your drives causing the problem, why don't you download the livecd version of gparted and boot with it and see what happens?

At least then you will know whether it is hardware or your installation of PCLOS.

Also, you need to tell us what your hardware is, what version of PCLOS you are using, whether it is up to date, and how much RAM is on your machine.

By the way, when I ask which version of PCLOS, I mean which ISO did you install, and did you update it?

[jamesmayxt]

   OK I have checked out your suggestions I have a copy of G Parted on Parted Magic &
   everything worked as expected, milliseconds to scan all devices.I Also put in the LXDE
   C-D I installed the system from installed G Parted from synaptic & once again 8 to 9 minutes
  to scan all devices so that would suggest its a problem within the LXDE enviroment
      thanx

[Just17]

Try, as root, launching it in a terminal to see if it gives any indication of what might be wrong.

[jamesmayxt]

   nothing extra was generated libparted 2.4 still took 8-9 mins

[agmg]

Why did you post this under "Broken Packages"?

One person having a problem with a package or an application doesn't verify that it is broken.

I use GParted on two 32bit installs and never had any issues...


Have you tried diskdrake?

[jamesmayxt]

    I too have never had a problem with G-Parted.I noticed a problem with LXDE about 6 weeks
    ago from the first install.
     If you think that doing even doing the most basic thing with G Parted takes 20mins when
    it should be instantaneous . Then our ideas of Broken Packages our obviously different
       thanx     Jim

[Just17]

The point is that Gparted itself is NOT broken.

It works here also.

Apparently there is something the matter with the LXDE release that causes Gparted to act this way ................

Also put in the LXDE  C-D I installed the system from
 installed G Parted from synaptic & once again 8 to 9 minutes to scan all devices
 so that would suggest its a problem within the LXDE enviroment

So, it is not a broken Gparted that is causing the grief .....

[Yankee]

How old is your LXDE ?

It may after many months picked up a fragment(s)
causing it to stall like that.  Are you using ext3 or
ext 4 ?

Can you take a fsarchiver backup and restore ?    Or
a "cp -av source target" backup and restore ?

Those are file-based backups and would eliminate
a fragment caused problem.

My Gparted works in a few seconds also.

regards,


FF


Probably S/B Software Forum

[ThirdOfSix]

I for one still do not know which lxde ISO was used for the install with problems.

If it is one of the 64 bit versions, this problem is interesting but does not belong here as there is officially no support for that version.

I do not know if the new install was done with the same old disk or a new one.

Just because a system has been updated with synaptic, that does not mean that any problems introduced during an install from a faulty ISO will have been fixed.

EDIT   Oops, you did say it was the same disk. You might try a new one just in case.

[Yankee]

When you look at gparted-view-filesystem support...

Are you trying to scan partitions without the drivers
installed ?

[xr200]

I have the same problem running gparted on a KDE install on my desktop, fully up to date, running the
3.2.18-pclos2.bfs kernel.

I believe the problem is with "/sbin/blkid", which gparted calls.

Logged in as root on my desktop, I temporarily moved /sbin/blkid to /sbin/o.blkid and started gparted
(the official PCLOS version), and it worked fine.   I restored /sbin/blkid and ran gparted again
and it hung.

I then tried booting up the old kernel (2.6.38.8.pclos3.bfs) and blkid and gparted worked fine.

So it appears to me that something odd is going on with blkid and the 3.2.18 kernel.
I installed a different 3.2.18 kernel (the non-bfs one) and gparted hung.

In an Xterm, as root, I ran an strace blkid in both kernel instances.   With the old kernel, I didn't see anything
strange.  But with the new kernel, I saw this:

open("/dev/sda1", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
open("/dev/sda2", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
etc, for each of my partitions.

With the old kernel, these open's succeeded.  I don't know how/why root can't open
an existing device ...

Is anyone experiencing this problem with the old kernel?

If you are experiencing this problem (with the new kernel), try temporarily mv-ing /sbin/blkid to a different
file and then run gparted and see if it works.   Don't forget to restore /sbin/blkid.

Hopefully this information will give someone else some insight as to what's going on....

xr200

[CaptainSarcastic]

Same behavior here under KDE with the 3.2.18 PAE BFS kernel.  I started Gparted several minutes ago, and it is still sitting with the "Scanning all devices..." bar going back and forth.

Two SATA hard drives, 8GB of RAM and a Phenom II Black Edition 965 processor for hardware.

Edit:  I just checked for updates, and see that Gparted is in the list.  I'm updating now, and will try again after I reboot.  Going to dinner with family, so might be a couple hours before I can check.

[xr200]

Please try mv-ing /sbin/blkid to a temporary file and then
rerunning gparted and post your results.   
(Then mv the tmp file back to /sbin/blkid).

xr200

[CaptainSarcastic]

Tried after rebooting from the update, and there was no change in the behavior - still just scans and scans.

I closed Gparted, tried renaming blkid, and then Gparted wouldn't launch at all.  I changed it back, and decided to try the PCLOS Control Center.  According to the logs, it calls blkid, and fires up normally.