Thank for the advise.
however, I run
smartctl -t long /dev/sdc
smartctl 6.2 2014-07-16 r3952 [x86_64-linux-3.17.8-200.fc20.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line
Drive command "Execute SMART Extended self-test routine immediately in off-line
Testing has begun.
Please wait 38 minutes for test to complete.
Test will complete after Thu Jan 29 01:54:45 2015
and I did not get much feedback!
smartctl -A /dev/sdc
does not provides change compared with before.
Is there a log file?
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
Sent: Thursday, January 29, 2015 at 12:52 AM
From: "Chris Murphy" <lists(a)colorremedies.com>
To: "Community support for Fedora users" <users(a)lists.fedoraproject.org>
Subject: Re: CurrentPendingSector
On Wed, Jan 28, 2015 at 4:19 PM, Patrick Dupre <pdupre(a)gmx.com> wrote:
> 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always -
Right. So just use smartctl -t long on the drive. In the next section
you didn't paste in, it'll tell you the LBA for the bad sector and
that's what you need to write over to fix this.
The smartmontools resource previously cited has useful information on
how to find out what you've lost in this sector. If it's filesystem
metadata it's rather important to e2fsck -f the file system (or
xfs_repair, or btrfs scrub) to fix this so it doesn't end up causing
worse problems down the road. A block of missing metadata can usually
be reconstructed - but not always. Better to find out now.
users mailing list
To unsubscribe or change subscription options:
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Have a question? Ask away: http://ask.fedoraproject.org