From: Milos R. <mil...@dc...> - 2013-06-26 18:18:19
|
Dear all, I have smart read error in log report on quite young WD black 1TB in software raid. Do not know what do since the sector is readable by hdparm tool. Also tried to use selective test after the logged error and could not succeed I always get same error report in log. Here is smatctl -a report: === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (17160) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 199) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 175 021 Pre-fail Always - 4191 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 4422 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 5 194 Temperature_Celsius 0x0022 112 099 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Selective offline Completed: read failure 90% 4421 502093169 # 2 Short offline Completed: read failure 90% 4403 502093169 # 3 Selective offline Completed: read failure 90% 4388 502093169 # 4 Short offline Completed: read failure 90% 4388 502093169 # 5 Short offline Completed: read failure 90% 4343 502093169 # 6 Selective offline Completed: read failure 90% 4343 502093169 # 7 Short offline Completed: read failure 90% 4343 502093169 # 8 Conveyance offline Completed: read failure 90% 4304 502093169 # 9 Extended offline Completed: read failure 80% 4296 502093169 #10 Extended offline Completed without error 00% 2152 - #11 Short offline Completed without error 00% 2136 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 19 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. ------------------------ sudo hdparm --read-sector 502093169 /dev/sdb /dev/sdb: reading sector 502093169: succeeded 0573 03dd 8fa4 753e 269b 3c95 bba8 38a9 ba3f 2687 0f71 0139 5e5e 0faa 27f3 8332 91e6 b0af 7fb5 d0a2 3f07 cf59 587a e5f4 8bec 2ff9 b3b2 2bff c0f6 db7b d0af efa7 c7b0 b9ec 5bd9 4bee 02a5 65eb 7f83 a4f2 b687 7bde 795b d399 f436 dab0 6ae7 aadf 58ff f4ad 12bb ff97 724f 9dde 0fe9 3ff6 0a38 a6c4 626c ac1f 2ee3 9e22 e373 dfad fd0c f0ee 9d0e a2f6 be01 7eb3 8fb8 7b54 1d63 e867 d91b a6ff 7a25 0acd b6f7 44be 525e 820f 7acc 8144 87cc 7fd8 fe86 d156 1dd9 0529 5569 9de9 bf60 5b06 51ed 0ef1 37c2 b4c7 1f17 2fe6 9f33 e9ec 2e44 b531 9c37 5f7b 87eb 53db 7db4 d08f c64b b51e bed1 0cab adbe 2c07 ed6b 82a9 7a5c f0e2 b44e ecfd be27 e747 7bf9 3d26 bf1b 3767 0cd7 e86f 5e5d db5d b8bf 72e6 ed73 e319 15f1 57b2 0dd7 d777 ee9d 3fae 717f e5c3 4473 be7f c20b 9c78 b8be f5f3 bb9b 5f4c 04dd 825d cbe3 77f3 74c1 cdfb bf3d 2efc 5e98 0dff c3fa 6f5d dc3f f5ed e00f 772f fd7d bb8f fcbc 5dcb e320 ba78 10ff d94a e7f3 653f dd3e 977f f0b9 7fee dd99 4a9f a0df fd03 93e0 43fe e9ac 6c33 fd7f 7443 6f2e f9b4 daaf fedd fe8c bf38 0730 d883 a700 77fb 7e77 eefd 8046 9d63 26ff e9bc ddf6 4f3d f35c 79f7 d79d 32ef 2e9f 00df 09ec f2f6 bd3c 7640 dd73 fdc4 157d 8f70 ab9b c2a2 3cbc 00bd 6b2a 6e30 5df1 a016 e88f 1786 ef81 5fb5 ded1 16e1 267b e3e1 1f9b 52fa 1ef6 d44b 55ed 7410 7f94 b3d5 d437 6ded 9bd5 78ce 7b99 4e99 a1c7 597f ------------------------------- Kindly recommend an action for such situation. Regads, Milos |
From: Alex S. <ml...@os...> - 2013-06-26 18:23:02
|
On 06/26/2013 08:02 PM, Milos Rajsic wrote: > Dear all, > > I have smart read error in log report on quite young WD black 1TB in > software raid. > Do not know what do since the sector is readable by hdparm tool. > Also tried to use selective test after the logged error and could not > succeed I always get same error report in log. I would recommend to try to read all disk using ddrescue tool to see if this error is real. |
From: Christian F. <Chr...@t-...> - 2013-06-26 21:34:18
|
Milos Rajsic wrote: > I have smart read error in log report on quite young WD black 1TB in > software raid. > Do not know what do since the sector is readable by hdparm tool. > Also tried to use selective test after the logged error and could not > succeed I always get same error report in log. > > Here is smatctl -a report: > ... > 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 > 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1 > ... > > SMART Error Log Version: 1 > No Errors Logged This old error log does only support 28-bit LBA address fields. The disk firmware might not add any entry for errors above the 128GiB boundary. > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error > # 1 Selective offline Completed: read failure 90% 4421 502093169 > # 2 Short offline Completed: read failure 90% 4403 502093169 Similar issue for this old self-test log: The field width is 32-bit, but it officially only supports 28-bit LBA. Therefore the above (29-bit) LBA address might be bogus. The newer extended logs support 48-bit LBA. Please try: smartctl -l xerror -l xselftest ... or: smartctl -x ... > ... > # 7 Short offline Completed: read failure 90% 4343 502093169 > # 8 Conveyance offline Completed: read failure 90% 4304 502093169 > # 9 Extended offline Completed: read failure 80% 4296 502093169 > #10 Extended offline Completed without error 00% 2152 - It is not uncommon that self-tests are aborted immediately by the firmware if a pending sector still exists. Please check the full disk with some tool. I prefer GNU ddrescue, which was also suggested by Alex. Thanks, Christian |
From: Milos R. <mil...@dc...> - 2013-06-26 22:57:36
|
Thanks very much for support. Instead of ddrescue tried with badblocks to check full disk surface badblocks just finished without any error report -- Checking blocks 0 to 976762583 Checking for bad blocks (read-only test): done Pass completed, 0 bad blocks found. (0/0/0 errors) Unfortunately can not find anything more informative by using sudo smartctl -l xerror -l xselftest /dev/sdb -- smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-24-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Extended Comprehensive Error Log Version: 1 (6 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Selective offline Completed: read failure 90% 4421 502093169 # 2 Short offline Completed: read failure 90% 4403 502093169 # 3 Selective offline Completed: read failure 90% 4388 502093169 # 4 Short offline Completed: read failure 90% 4388 502093169 # 5 Short offline Completed: read failure 90% 4343 502093169 # 6 Selective offline Completed: read failure 90% 4343 502093169 # 7 Short offline Completed: read failure 90% 4343 502093169 # 8 Conveyance offline Completed: read failure 90% 4304 502093169 # 9 Extended offline Completed: read failure 80% 4296 502093169 #10 Extended offline Completed without error 00% 2152 - #11 Short offline Completed without error 00% 2136 - Thanks, Milos -- On 06/26/2013 11:34 PM, Christian Franke wrote: > Milos Rajsic wrote: >> I have smart read error in log report on quite young WD black 1TB in >> software raid. >> Do not know what do since the sector is readable by hdparm tool. >> Also tried to use selective test after the logged error and could not >> succeed I always get same error report in log. >> >> Here is smatctl -a report: >> ... >> 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 >> 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1 >> ... >> >> SMART Error Log Version: 1 >> No Errors Logged > This old error log does only support 28-bit LBA address fields. The disk > firmware might not add any entry for errors above the 128GiB boundary. > > >> SMART Self-test log structure revision number 1 >> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error >> # 1 Selective offline Completed: read failure 90% 4421 502093169 >> # 2 Short offline Completed: read failure 90% 4403 502093169 > Similar issue for this old self-test log: The field width is 32-bit, but > it officially only supports 28-bit LBA. Therefore the above (29-bit) LBA > address might be bogus. > > The newer extended logs support 48-bit LBA. Please try: > > smartctl -l xerror -l xselftest ... > > or: > > smartctl -x ... > > >> ... >> # 7 Short offline Completed: read failure 90% 4343 502093169 >> # 8 Conveyance offline Completed: read failure 90% 4304 502093169 >> # 9 Extended offline Completed: read failure 80% 4296 502093169 >> #10 Extended offline Completed without error 00% 2152 - > It is not uncommon that self-tests are aborted immediately by the > firmware if a pending sector still exists. > > Please check the full disk with some tool. I prefer GNU ddrescue, which > was also suggested by Alex. > > Thanks, > Christian > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support |
From: <ro...@sp...> - 2013-06-27 04:56:01
|
This is has been a very educational thread for me so far. A couple of [probably newbie] inline questions: > The newer extended logs support 48-bit LBA. Please try: > > smartctl -l xerror -l xselftest ... > > or: > > smartctl -x ... Does this mean I can't trust the SMART Attributes to give a complete picture of the hard drive health? > > It is not uncommon that self-tests are aborted immediately by the > firmware if a pending sector still exists. > > Please check the full disk with some tool. I prefer GNU ddrescue, which > was also suggested by Alex. I've used ddrescue once, but not for doing a pending sector read. Am I correct in guessing the command would something like: ddrescue /dev/sdb /dev/null If the purpose is to just force the disk to re-read the pending sector, wouldn't the other two methods work equally as well, i.e. sudo hdparm --read-sector 502093169 /dev/sdb or what Milos did badblocks /dev/sdb (perhaps with a -b and/or -c option to speed things up) BTW Milos, after you did the badblocks, did the pending sector go away? |
From: Milos R. <mil...@dc...> - 2013-06-27 06:47:39
|
Nothing changed the report is still the same. As far as I understand the system pending sector will be replaced only during write Also tried another short test and same error report occurred. Generally I have never seen smart error during test and empty Error log report where system places read errors or other problems. ddrescue is very powerful tool when you want to save the data from disk because it will reread wrong sector in different way several times. But according to my experience any other tool that (dd, badblocks, fsck, or hdparm) have problem with reading the sector will definitely make error report log to the system and it would be recorded into smart data with details. Thanks, Milos On 06/27/2013 06:55 AM, ro...@sp... wrote: > This is has been a very educational thread for me so far. A couple of > [probably newbie] inline questions: > >> The newer extended logs support 48-bit LBA. Please try: >> >> smartctl -l xerror -l xselftest ... >> >> or: >> >> smartctl -x ... > Does this mean I can't trust the SMART Attributes to give a complete > picture of the hard drive health? > >> It is not uncommon that self-tests are aborted immediately by the >> firmware if a pending sector still exists. >> >> Please check the full disk with some tool. I prefer GNU ddrescue, which >> was also suggested by Alex. > I've used ddrescue once, but not for doing a pending sector read. Am I > correct in guessing the command would something like: > > ddrescue /dev/sdb /dev/null > > If the purpose is to just force the disk to re-read the pending sector, > wouldn't the other two methods work equally as well, i.e. > sudo hdparm --read-sector 502093169 /dev/sdb > or what Milos did > badblocks /dev/sdb (perhaps with a -b and/or -c option to speed things up) > > BTW Milos, after you did the badblocks, did the pending sector go away? > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support |
From: Alex S. <ml...@os...> - 2013-06-27 06:46:36
|
On 06/27/2013 06:55 AM, ro...@sp... wrote: > This is has been a very educational thread for me so far. A couple of > [probably newbie] inline questions: > >> The newer extended logs support 48-bit LBA. Please try: >> >> smartctl -l xerror -l xselftest ... >> >> or: >> >> smartctl -x ... > Does this mean I can't trust the SMART Attributes to give a complete > picture of the hard drive health? SMART attributes are generated by drive firmware, and firmware may contain a bugs. >> It is not uncommon that self-tests are aborted immediately by the >> firmware if a pending sector still exists. >> >> Please check the full disk with some tool. I prefer GNU ddrescue, which >> was also suggested by Alex. > I've used ddrescue once, but not for doing a pending sector read. Am I > correct in guessing the command would something like: > > ddrescue /dev/sdb /dev/null > > If the purpose is to just force the disk to re-read the pending sector, > wouldn't the other two methods work equally as well, i.e. > sudo hdparm --read-sector 502093169 /dev/sdb Purpose is to re-read all sectors. BTW, smart test stops at first failed sector so you don`t have information how much sectors are actually failing. |
From: <ro...@sp...> - 2013-06-27 14:12:12
|
Another inline question. <snip> >>> It is not uncommon that self-tests are aborted immediately by the >>> firmware if a pending sector still exists. >>> >>> Please check the full disk with some tool. I prefer GNU ddrescue, which >>> was also suggested by Alex. >> I've used ddrescue once, but not for doing a pending sector read. Am I >> correct in guessing the command would something like: >> >> ddrescue /dev/sdb /dev/null >> >> If the purpose is to just force the disk to re-read the pending sector, >> wouldn't the other two methods work equally as well, i.e. >> sudo hdparm --read-sector 502093169 /dev/sdb > Purpose is to re-read all sectors. BTW, smart test stops at first failed > sector so you don`t have information how much sectors are actually > failing. According to the wikipedia SMART page (http://en.wikipedia.org/wiki/S.M.A.R.T.) for Current Pending Sector Count, "...If an unstable sector is subsequently read successfully, this value is decreased and the sector is not remapped...". So why didn't Milos original hdparm test clear the count? It appeared from his post the sector was read correctly. Obviously, if the read failed, then the count wouldn't have been touched , "...Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written..." Second question: Is there anything close to a black and white answer as to how many pending sectors before you say it's time to get a new drive? I know from somewhere, probably from this list, someone said one or two bad sectors doesn't make a bad hard drive. Thanks for your patience and time. |
From: Gregory S. <gr...@sl...> - 2013-06-27 15:03:51
|
I realized I sent this to one of the thread participants, not the list...sorry...here's my post. --- My comments are probably useless, as this is out at the edge of my knowledge - but I seem to recall that a failed read may/will continue to have problems until a write is made to the same problem block. Once a write is attempted, it will either succeed, in which case you should be able to read it [transient error - not likely though], or [much more likely] it will fail to write the block, and will mark it as "bad" and remap it to one of the reserved spare blocks and future reads will then succeed. But that re-mapping doesn't occur on *reads*, only *writes.* So, until something tries to write to the problem block that it can't read now, the "read" failure will continue. So, provided that's right - an operation to force a write on that problem block should right things. [The main question before doing this is, do you have real data on need in the block currently. If no, then just attempt to write it. If yes, then recover the data using ddrescue or similar before writing to it.] HTH - but take with a grain of salt - I'm not completely sure I'm right - but that's the way I understand it. -Greg --- rscn> Another inline question. rscn> <snip> >>>> It is not uncommon that self-tests are aborted immediately by the >>>> firmware if a pending sector still exists. >>>> >>>> Please check the full disk with some tool. I prefer GNU ddrescue, which >>>> was also suggested by Alex. >>> I've used ddrescue once, but not for doing a pending sector read. Am I >>> correct in guessing the command would something like: >>> >>> ddrescue /dev/sdb /dev/null >>> >>> If the purpose is to just force the disk to re-read the pending sector, >>> wouldn't the other two methods work equally as well, i.e. >>> sudo hdparm --read-sector 502093169 /dev/sdb >> Purpose is to re-read all sectors. BTW, smart test stops at first failed >> sector so you don`t have information how much sectors are actually >> failing. rscn> According to the wikipedia SMART page rscn> (http://en.wikipedia.org/wiki/S.M.A.R.T.) for Current Pending Sector rscn> Count, "...If an unstable sector is subsequently read successfully, this rscn> value is decreased and the sector is not remapped...". rscn> So why didn't Milos original hdparm test clear the count? It appeared from rscn> his post the sector was read correctly. Obviously, if the read failed, rscn> then the count wouldn't have been touched , "...Read errors on a sector rscn> will not remap the sector immediately (since the correct value cannot be rscn> read and so the value to remap is not known, and also it might become rscn> readable later); instead, the drive firmware remembers that the sector rscn> needs to be remapped, and will remap it the next time it's written..." rscn> Second question: Is there anything close to a black and white answer as to rscn> how many pending sectors before you say it's time to get a new drive? I rscn> know from somewhere, probably from this list, someone said one or two bad rscn> sectors doesn't make a bad hard drive. rscn> Thanks for your patience and time. rscn> ------------------------------------------------------------------------------ rscn> This SF.net email is sponsored by Windows: rscn> Build for Windows Store. rscn> http://p.sf.net/sfu/windows-dev2dev rscn> _______________________________________________ rscn> Smartmontools-support mailing list rscn> Sma...@li... rscn> https://lists.sourceforge.net/lists/listinfo/smartmontools-support -- Gregory Sloop, Principal: Sloop Network & Computer Consulting Voice: 503.251.0452 x82 EMail: gr...@sl... http://www.sloop.net --- |
From: Milos R. <mil...@dc...> - 2013-06-27 14:38:15
|
Thanks this looks logical Since the disk is working in raid 1. Even the sector is readable I am thinking of two possible solutions: a) dd if=/dev/sda of=/dev/sdb count=1 bs=512 skip=502093169 b) remove from raid and then return to raid for synchronization Somehow I am close to believe that only somekind of writing to that sector will make changes in the smart log. Regards, Milos On 06/27/2013 03:52 PM, Gregory Sloop wrote: > My comments are probably useless, as this is out at the edge of my > knowledge - but I seem to recall that a failed read will continue to > have problems until a write is made to the same problem block. > > Once a write is attempted, it will either succeeed, in which case you > should be able to read it [transient error - not likely though], > > or [much more likely] it will fail to write the block, and > will mark it as "bad" and remap it to one of the reserved spare > blocks and future reads will then succeed. > > But that re-mapping doesn't occur on reads, only writes. So, until > something tries to write to the problem block that it can't read now, > the "read" failure will continue. > > So, provided that's right - an operation to force a write on that > problem block should right things. [The main question before doing > this is, do you have real data on need in the block currently. If no, > then just attempt to write it. If yes, then recover the data using > ddrescue or similar before writing to it.] > > HTH - but take with a grain of salt - I'm not completely sure I'm > right - but that's the way I understand it. > > -Greg > > > > MR> Nothing changed the report is still the same. > MR> As far as I understand the system pending sector will be replaced only > MR> during write > MR> Also tried another short test and same error report occurred. > > MR> Generally I have never seen smart error during test and empty Error log > MR> report where system places read errors or other problems. > > MR> ddrescue is very powerful tool when you want to save the data from disk > MR> because it will reread wrong sector in different way several times. But > MR> according to my experience any other tool that (dd, badblocks, fsck, or > MR> hdparm) have problem with reading the sector will definitely make error > MR> report log to the system and it would be recorded into smart data with > MR> details. > > MR> Thanks, > > MR> Milos > > MR> On 06/27/2013 06:55 AM,ro...@sp... wrote: >>> This is has been a very educational thread for me so far. A couple of >>> [probably newbie] inline questions: >>> >>>> The newer extended logs support 48-bit LBA. Please try: >>>> >>>> smartctl -l xerror -l xselftest ... >>>> >>>> or: >>>> >>>> smartctl -x ... >>> Does this mean I can't trust the SMART Attributes to give a complete >>> picture of the hard drive health? >>> >>>> It is not uncommon that self-tests are aborted immediately by the >>>> firmware if a pending sector still exists. >>>> >>>> Please check the full disk with some tool. I prefer GNU ddrescue, which >>>> was also suggested by Alex. >>> I've used ddrescue once, but not for doing a pending sector read. Am I >>> correct in guessing the command would something like: >>> >>> ddrescue /dev/sdb /dev/null >>> >>> If the purpose is to just force the disk to re-read the pending sector, >>> wouldn't the other two methods work equally as well, i.e. >>> sudo hdparm --read-sector 502093169 /dev/sdb >>> or what Milos did >>> badblocks /dev/sdb (perhaps with a -b and/or -c option to speed things up) >>> >>> BTW Milos, after you did the badblocks, did the pending sector go away? >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Smartmontools-support mailing list >>> Sma...@li... >>> https://lists.sourceforge.net/lists/listinfo/smartmontools-support > MR> ------------------------------------------------------------------------------ > MR> This SF.net email is sponsored by Windows: > > MR> Build for Windows Store. > > MR>http://p.sf.net/sfu/windows-dev2dev > MR> _______________________________________________ > MR> Smartmontools-support mailing list > MR>Sma...@li... > MR>https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Christian F. <Chr...@t-...> - 2013-06-30 12:42:50
|
Milos Rajsic wrote: > Thanks this looks logical > Since the disk is working in raid 1. > > Even the sector is readable I am thinking of two possible solutions: > > a) dd if=/dev/sda of=/dev/sdb count=1 bs=512 skip=502093169 Don't forget to add 'seek=502093169', otherwise this would copy sector 502093169 from sda to sector 0 of sdb :-) > b) remove from raid and then return to raid for synchronization Yes, this may help. > Somehow I am close to believe that only somekind of writing to that > sector will make changes in the smart log. In the past, I've seen a similar behavior with some Samsung F1 disk: There were no actual read errors, but attribute 197 raw value reports 40 sectors. Zero-filling the whole disk helped to clear the attribute. Thanks, Christian |
From: Milos R. <mil...@dc...> - 2013-06-30 13:26:38
|
Good point. Yes this is very important including "seek" option is must under the solution a) :) Anyway this means that smart tools can make wrong judgement about sector state under some conditions. May be it would be good to implement an option to be able to somehow force reset log in such situations instead of doing any writing to sectors which can be somehow dangerous. Thanks for note. Milos Rajsic Business Development Director Dynamic Communications Group Cara Nikolaja II 90 11000 Beograd, Serbia Tel: +381 11 3515122 Fax: +381 11 3515122 Mob: +381 63 267589 E-mail: mil...@dc... http://www.dcg.rs http://www.belre.org On 06/30/2013 02:42 PM, Christian Franke wrote: > Milos Rajsic wrote: >> Thanks this looks logical >> Since the disk is working in raid 1. >> >> Even the sector is readable I am thinking of two possible solutions: >> >> a) dd if=/dev/sda of=/dev/sdb count=1 bs=512 skip=502093169 > > Don't forget to add 'seek=502093169', otherwise this would copy sector > 502093169 from sda to sector 0 of sdb :-) > >> b) remove from raid and then return to raid for synchronization > > Yes, this may help. > > >> Somehow I am close to believe that only somekind of writing to that >> sector will make changes in the smart log. > > In the past, I've seen a similar behavior with some Samsung F1 disk: > There were no actual read errors, but attribute 197 raw value reports > 40 sectors. Zero-filling the whole disk helped to clear the attribute. > > Thanks, > Christian > |