[Bug 345013] Re: incorrect management of damaged external hard disks
Launchpad Bug Tracker
345013 at bugs.launchpad.net
Mon Mar 5 04:18:19 UTC 2012
[Expired for gparted (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gparted (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gparted in Ubuntu.
https://bugs.launchpad.net/bugs/345013
Title:
incorrect management of damaged external hard disks
Status in “gparted” package in Ubuntu:
Expired
Bug description:
Binary package hint: gparted
There is a case where Ubuntu is very bad : when nothing works !
Here we have a gorgeous example which concern HAL, nautilus, and
gparted .
On my hard drive I have 3 partitions, one of them is formated by ext3 but it's damaged.
When I plug my hard drive, nautilus is able to open others 2 partitions, but not the 3th partition.
There are some error messages :
Unable to mount 156.2 GB Media
DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
and
Cannot mount volume.
Error org.freedesktop.DBus.Error.NoReply.
The message did not receive a reply ( time out by message bus )
On nautilus there are not the arrow ( which appear when the partition
is mounted ) right next to the 3th partition, so the 3th partition
will not be mounted ( as I think, as it should be ).
To repair it , I use Gparted but Gparted don't like this error and
runs in a loop on "Scanning all devices ..." ( Issue#1 )
I can't use gparted to repair this error !! What can a lambda user do to fix this if gparted not works ?
Anyway, I test some solutions :
First of all I close gparted ( which runs in a loop ) , and I launched
it again. But no window appear ! On terminal I have :
sudo gparted
error: libhal_acquire_global_interface_lock: org.freedesktop.Hal.Device.InterfaceAlreadyLocked: The interface org.freedeskdesktop.Hal.Device.Storage is already exclusively locked either by someone else or it's already locked by yourself
Apparently Gparted is not normally close ( however I close it with the
cross ). I guess it still scanning all devices ... ( Issue#2 )
So I kill it !! yeahh
menoft at menoft:~$ sudo killall gparted
menoft at menoft:~$ sudo killall gparted
menoft at menoft:~$ sudo killall gparted
(==> no "gparted: no process killed" !! )
gksu need to be killed before !! Aha ! ( issue#3)
menoft at menoft:~$ sudo killall gksu
menoft at menoft:~$ sudo killall gparted
gparted: no process killed
But gpartedbin persist ! ( issue#4 )
menoft at menoft:~$ ps -A | grep gpart
7146 ? 00:00:09 gpartedbin <defunct>
menoft at menoft:~$ sudo killall gpartedbin
menoft at menoft:~$ sudo killall gpartedbin
menoft at menoft:~$ ps -A | grep gpart
7146 ? 00:00:09 gpartedbin <defunct>
menoft at menoft:~$ sudo kill -9 7146
cps -A | grep gpar
7146 ? 00:00:09 gpartedbin <defunct>
I don't understand !!
In addition I need to kill hal-lock ( gpartedbin depend of this )
menoft at menoft:~$ sudo killall hal-lock
AND at the end , after all this manipulations, gparted can be launched
again ( very complicated :-) ) but I don't do this.
After some manipulations ( open/kill gparted ), check what I have :
ps -A | grep gpar
7146 ? 00:00:09 gpartedbin <defunct>
10700 pts/0 00:00:07 gpartedbin <defunct>
13246 pts/0 00:00:05 gpartedbin <defunct>
15833 pts/0 00:00:16 gpartedbin <defunct>
16310 ? 00:00:00 gpartedbin <defunct>
16987 pts/0 00:00:00 gpartedbin <defunct>
Looks very nice , isn't it ?
Now I will talk about nautilus !
When I want umount other partitions, I have this message ( writing
data to device, ... ) but arrays not disappear and drive still mounted
! I must umount manually all partition because it not works with
nautilus. When I do this and after the unpluging drive, partitions
don't disappear on nautilus ( issue#1212121 ) ( directories don't
remove in /media/ ! )
Finally with the mouse, it is impossible to fix this, I open a
terminal and do this :
sudo fsck /dev/sdb1
[sudo] password for aslan:
fsck 1.41.3 (12-Oct-2008)
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Device or resource busy while trying to open /dev/sdb1
Filesystem mounted or opened exclusively by another program?
Ok , I got tired, so I've restarted my computer and I do all fixing
manipulation on console mode after killing gmd
sudo fsck /dev/sdb1 works ! And it fixed all problems on my partition.
Now on graphic mode, this not works ! fsck not works correctly. But I
will fix this later.
Thanks for reading.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/345013/+subscriptions
More information about the foundations-bugs
mailing list