CurrentPendingSector
Patrick Dupre
pdupre at gmx.com
Thu Jan 29 00:17:48 UTC 2015
Hello,
Here is the log file:
Complete error log:
SMART Error Log Version: 1
ATA Error Count: 2
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 2 occurred at disk power-on lifetime: 6854 hours (285 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 27 f2 ab d5 00 Error: UNC 39 sectors at LBA = 0x00d5abf2 = 14003186
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 b8 61 ab d5 e6 08 3d+05:49:05.047 READ DMA
ea 00 00 50 ab d5 a0 08 3d+05:49:04.952 FLUSH CACHE EXT
c8 00 18 39 ab d5 e6 08 3d+05:49:04.866 READ DMA
ca 00 08 39 0b 4a e5 08 3d+05:49:04.864 WRITE DMA
c8 00 00 41 48 06 e5 08 3d+05:49:04.792 READ DMA
Error 1 occurred at disk power-on lifetime: 6839 hours (284 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 27 f2 ab d5 00 Error: UNC 39 sectors at LBA = 0x00d5abf2 = 14003186
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 b8 61 ab d5 e6 08 49d+05:52:51.329 READ DMA
c8 00 18 39 ab d5 e6 08 49d+05:52:51.256 READ DMA
c8 00 00 e9 83 ae e4 08 49d+05:52:50.544 READ DMA
ca 00 08 81 38 06 e6 08 49d+05:52:50.456 WRITE DMA
ca 00 08 19 38 06 e6 08 49d+05:52:50.433 WRITE DMA
smartctl -t long /dev/sdc is running for 38 mn
===========================================================================
Patrick DUPRÉ | | email: pdupre at 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 at colorremedies.com>
> To: "Community support for Fedora users" <users at lists.fedoraproject.org>
> Subject: Re: CurrentPendingSector
>
> On Wed, Jan 28, 2015 at 4:19 PM, Patrick Dupre <pdupre at gmx.com> wrote:
>
> > 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 1
>
> 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.
>
>
> --
> Chris Murphy
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
More information about the users
mailing list