5

GParted misbehaving

view full story
linux-howto

http://forums.fedoraforum.org – Hi, all. I don't know if this is an actual 'bug' or a configuration error I've made. I'm running a system with an AMD Athlon X2 64-bit, 4 Gb RAM, etc. Currently, the primary boot system is Fedora 11 (64-bit) but this is not the only system installed; there were several OS predecessors - both 32-bit and 64-bit. My question is: why does the current version of GParted (i.e. run when Fedora is active) produce the following error message every time I start or refresh it? [ Failed to mount "<labelname>". ] [ The enclosing drive for the volume is locked. ] The errors are limited to the primary and logical partitions which are NOT supposed to be mounted in the current F11 environment (e.g. utility boot of GParted, all the unique / isolated partitions for F10, unused data partitions, ...) The current software includes: GParted 0.4.5-1.fc11.x86-64 Gnome 2.26.2-1.fc11.x86-64 Kernel 2.6.29.5-191.fc11.x86-64 Updates are run weekly. I've never seen this problem with earlier versions of GParted or Fedora. In earlier Fedoras, those partitions which were supposed to be unmounted (or not used) were just simplly ignored. Any suggestions or background information? Thx >>PhoenixAtos (HowTos)