After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 587459 - Let user acknowledge and get rid of notifications until things get worse
Let user acknowledge and get rid of notifications until things get worse
Status: RESOLVED DUPLICATE of bug 579873
Product: gnome-disk-utility
Classification: Core
Component: notifications
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
: 607979 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-06-30 19:22 UTC by Patryk Zawadzki
Modified: 2012-11-12 20:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Patryk Zawadzki 2009-06-30 19:22:32 UTC
About a month ago a friend of mine dropped my laptop from a little height which resulted in 2 bad sectors. I've installed g-d-u a week ago and since then it has warned me about 14 times (I am forced to login twice a day) that my disk is going to die soon. The number constantly shows 2 damaged sectors.

To sum things up: 2 sectors for a month, no further damage over time, smart reports successful relocation and data is intact. I don't think I'm not going to replace the disk any time soon.

I'd like to get rid of the warning until something bad happens again as otherwise I'll likely get used to the warnings and just ignore them. Even if a meteor hits the HD plate and half of the mechanism evaporates. I'd like to know when that happens though :)
Comment 1 nodiscc 2012-04-06 01:36:49 UTC
Duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=587459
Comment 2 nodiscc 2012-07-28 01:16:54 UTC
*** Bug 607979 has been marked as a duplicate of this bug. ***
Comment 3 David Zeuthen (not reading bugmail) 2012-11-12 20:45:17 UTC
We no longer complain about damaged sectors, see bug 579873 for more information.

*** This bug has been marked as a duplicate of bug 579873 ***