Ubuntu.pl 🇺🇦️ - Forum Ubuntu

Polskie forum użytkowników Ubuntu
https://ubuntu.pl/forum/

Bad sectors - jak działa realokacja?

https://ubuntu.pl/forum/viewtopic.php?t=158942

Strona 1 z 1

Bad sectors - jak działa realokacja?

: 27 maja 2012, 12:04
autor: rob006
Kilka dni temu miałem nieciekawą sytuację - podczas oglądania filmu nagle nastąpił zwis systemu: dysk mielił non stop, responsywność systemu zerowa. Po kilku minutach zniecierpliwiony zabiłem go twardym resetem, niestety uruchomić ponownie już się nie chciał - objawy te same: mielenie dysku i brak postępów w ładowaniu systemu. Po kilku próbach udało mi się go uruchomić, o dziwo system działał ok, żadnych objawów czy spowolnień. Po restarcie powtórka z rozgrywki - znowu system nie chce się uruchomić, po kilku próbach - powodzenie. Syslog zawalony czymś takim:

Kod: Zaznacz cały

May 26 20:20:21 robert-laptop collectdmon[2054]: Warning: collectd was terminated by signal 7
May 26 20:20:21 robert-laptop collectdmon[2054]: Warning: restarting collectd
May 26 20:20:21 robert-laptop kernel: [  318.457212] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 26 20:20:21 robert-laptop kernel: [  318.457217] ata1.00: irq_stat 0x40000008
May 26 20:20:21 robert-laptop kernel: [  318.457221] ata1.00: failed command: READ FPDMA QUEUED
May 26 20:20:21 robert-laptop kernel: [  318.457228] ata1.00: cmd 60/08:00:24:d1:7f/00:00:01:00:00/40 tag 0 ncq 4096 in
May 26 20:20:21 robert-laptop kernel: [  318.457230]          res 41/40:08:29:d1:7f/00:00:01:00:00/00 Emask 0x409 (media error) <F>
May 26 20:20:21 robert-laptop kernel: [  318.457233] ata1.00: status: { DRDY ERR }
May 26 20:20:21 robert-laptop kernel: [  318.457236] ata1.00: error: { UNC }
May 26 20:20:21 robert-laptop kernel: [  318.461474] ata1.00: configured for UDMA/133
May 26 20:20:21 robert-laptop kernel: [  318.461490] sd 0:0:0:0: [sda] Unhandled sense code
May 26 20:20:21 robert-laptop kernel: [  318.461494] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 26 20:20:21 robert-laptop kernel: [  318.461500] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
May 26 20:20:21 robert-laptop kernel: [  318.461508] Descriptor sense data with sense descriptors (in hex):
May 26 20:20:21 robert-laptop kernel: [  318.461512]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
May 26 20:20:21 robert-laptop kernel: [  318.461528]         01 7f d1 29 
May 26 20:20:21 robert-laptop kernel: [  318.461534] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
May 26 20:20:21 robert-laptop kernel: [  318.461542] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 01 7f d1 24 00 00 08 00
May 26 20:20:21 robert-laptop kernel: [  318.461556] end_request: I/O error, dev sda, sector 25153833
May 26 20:20:21 robert-laptop kernel: [  318.461583] ata1: EH complete
May 26 20:20:21 robert-laptop collectd[2473]: Initialization complete, entering read-loop.
May 26 20:20:24 robert-laptop kernel: [  321.057761] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
May 26 20:20:24 robert-laptop kernel: [  321.057767] ata1.00: irq_stat 0x40000008
May 26 20:20:24 robert-laptop kernel: [  321.057772] ata1.00: failed command: READ FPDMA QUEUED
May 26 20:20:24 robert-laptop kernel: [  321.057779] ata1.00: cmd 60/08:10:24:d1:7f/00:00:01:00:00/40 tag 2 ncq 4096 in
May 26 20:20:24 robert-laptop kernel: [  321.057781]          res 41/40:08:29:d1:7f/00:00:01:00:00/00 Emask 0x409 (media error) <F>
May 26 20:20:24 robert-laptop kernel: [  321.057784] ata1.00: status: { DRDY ERR }
May 26 20:20:24 robert-laptop kernel: [  321.057786] ata1.00: error: { UNC }
May 26 20:20:24 robert-laptop kernel: [  321.062061] ata1.00: configured for UDMA/133
May 26 20:20:24 robert-laptop kernel: [  321.062076] ata1: EH complete
May 26 20:20:26 robert-laptop kernel: [  323.452268] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 26 20:20:26 robert-laptop kernel: [  323.452273] ata1.00: irq_stat 0x40000008
May 26 20:20:26 robert-laptop kernel: [  323.452276] ata1.00: failed command: READ FPDMA QUEUED
May 26 20:20:26 robert-laptop kernel: [  323.452284] ata1.00: cmd 60/08:00:24:d1:7f/00:00:01:00:00/40 tag 0 ncq 4096 in
May 26 20:20:26 robert-laptop kernel: [  323.452285]          res 41/40:08:29:d1:7f/00:00:01:00:00/00 Emask 0x409 (media error) <F>
May 26 20:20:26 robert-laptop kernel: [  323.452289] ata1.00: status: { DRDY ERR }
May 26 20:20:26 robert-laptop kernel: [  323.452291] ata1.00: error: { UNC }
May 26 20:20:26 robert-laptop kernel: [  323.456556] ata1.00: configured for UDMA/133
May 26 20:20:26 robert-laptop kernel: [  323.456567] ata1: EH complete
May 26 20:20:29 robert-laptop kernel: [  325.947646] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 26 20:20:29 robert-laptop kernel: [  325.947651] ata1.00: irq_stat 0x40000008
May 26 20:20:29 robert-laptop kernel: [  325.947655] ata1.00: failed command: READ FPDMA QUEUED
May 26 20:20:29 robert-laptop kernel: [  325.947662] ata1.00: cmd 60/08:00:24:d1:7f/00:00:01:00:00/40 tag 0 ncq 4096 in
May 26 20:20:29 robert-laptop kernel: [  325.947664]          res 41/40:08:29:d1:7f/00:00:01:00:00/00 Emask 0x409 (media error) <F>
May 26 20:20:29 robert-laptop kernel: [  325.947667] ata1.00: status: { DRDY ERR }
May 26 20:20:29 robert-laptop kernel: [  325.947670] ata1.00: error: { UNC }
May 26 20:20:29 robert-laptop kernel: [  325.951905] ata1.00: configured for UDMA/133
May 26 20:20:29 robert-laptop kernel: [  325.951922] ata1: EH complete
May 26 20:20:31 robert-laptop kernel: [  328.566852] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 26 20:20:31 robert-laptop kernel: [  328.566857] ata1.00: irq_stat 0x40000008
May 26 20:20:31 robert-laptop kernel: [  328.566860] ata1.00: failed command: READ FPDMA QUEUED
May 26 20:20:31 robert-laptop kernel: [  328.566867] ata1.00: cmd 60/08:00:24:d1:7f/00:00:01:00:00/40 tag 0 ncq 4096 in
May 26 20:20:31 robert-laptop kernel: [  328.566869]          res 41/40:08:29:d1:7f/00:00:01:00:00/00 Emask 0x409 (media error) <F>
May 26 20:20:31 robert-laptop kernel: [  328.566872] ata1.00: status: { DRDY ERR }
May 26 20:20:31 robert-laptop kernel: [  328.566875] ata1.00: error: { UNC }
May 26 20:20:31 robert-laptop kernel: [  328.571111] ata1.00: configured for UDMA/133
May 26 20:20:31 robert-laptop kernel: [  328.571122] ata1: EH complete
May 26 20:20:34 robert-laptop kernel: [  331.205179] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 26 20:20:34 robert-laptop kernel: [  331.205185] ata1.00: irq_stat 0x40000008
May 26 20:20:34 robert-laptop kernel: [  331.205189] ata1.00: failed command: READ FPDMA QUEUED
May 26 20:20:34 robert-laptop kernel: [  331.205196] ata1.00: cmd 60/08:00:24:d1:7f/00:00:01:00:00/40 tag 0 ncq 4096 in
May 26 20:20:34 robert-laptop kernel: [  331.205197]          res 41/40:08:29:d1:7f/00:00:01:00:00/00 Emask 0x409 (media error) <F>
May 26 20:20:34 robert-laptop kernel: [  331.205201] ata1.00: status: { DRDY ERR }
May 26 20:20:34 robert-laptop kernel: [  331.205203] ata1.00: error: { UNC }
May 26 20:20:34 robert-laptop kernel: [  331.209414] ata1.00: configured for UDMA/133
May 26 20:20:34 robert-laptop kernel: [  331.209427] ata1: EH complete
May 26 20:20:37 robert-laptop kernel: [  333.780434] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 26 20:20:37 robert-laptop kernel: [  333.780439] ata1.00: irq_stat 0x40000008
May 26 20:20:37 robert-laptop kernel: [  333.780443] ata1.00: failed command: READ FPDMA QUEUED
May 26 20:20:37 robert-laptop kernel: [  333.780450] ata1.00: cmd 60/08:00:24:d1:7f/00:00:01:00:00/40 tag 0 ncq 4096 in
May 26 20:20:37 robert-laptop kernel: [  333.780452]          res 41/40:08:29:d1:7f/00:00:01:00:00/00 Emask 0x409 (media error) <F>
May 26 20:20:37 robert-laptop kernel: [  333.780455] ata1.00: status: { DRDY ERR }
May 26 20:20:37 robert-laptop kernel: [  333.780457] ata1.00: error: { UNC }
May 26 20:20:37 robert-laptop kernel: [  333.784685] ata1.00: configured for UDMA/133
May 26 20:20:37 robert-laptop kernel: [  333.784704] sd 0:0:0:0: [sda] Unhandled sense code
May 26 20:20:37 robert-laptop kernel: [  333.784710] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 26 20:20:37 robert-laptop kernel: [  333.784720] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
May 26 20:20:37 robert-laptop kernel: [  333.784732] Descriptor sense data with sense descriptors (in hex):
May 26 20:20:37 robert-laptop kernel: [  333.784739]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
May 26 20:20:37 robert-laptop kernel: [  333.784766]         01 7f d1 29 
May 26 20:20:37 robert-laptop kernel: [  333.784776] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
May 26 20:20:37 robert-laptop kernel: [  333.784788] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 01 7f d1 24 00 00 08 00
May 26 20:20:37 robert-laptop kernel: [  333.784812] end_request: I/O error, dev sda, sector 25153833
May 26 20:20:37 robert-laptop kernel: [  333.784842] ata1: EH complete
SMART:

Kod: Zaznacz cały

smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     ST9500325AS
Serial Number:    6VE7AVKA
Firmware Version: 0003SDM1
User Capacity:    500,107,862,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri May 25 11:23:18 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== 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: 		 (   0) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 142) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103b)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   084   084   006    Pre-fail  Always       -       48764490
  3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1220
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   080   060   030    Pre-fail  Always       -       108389753
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6964
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   037   020    Old_age   Always       -       1220
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       980
188 Unknown_Attribute       0x0032   100   097   000    Old_age   Always       -       20
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   065   049   045    Old_age   Always       -       35 (Lifetime Min/Max 35/36)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       28
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       48
193 Load_Cycle_Count        0x0032   092   092   000    Old_age   Always       -       17349
194 Temperature_Celsius     0x0022   035   051   000    Old_age   Always       -       35 (0 16 0 0)
195 Hardware_ECC_Recovered  0x001a   042   036   000    Old_age   Always       -       48764490
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
254 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1839 (device log contains only the most recent five errors)
	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 1839 occurred at disk power-on lifetime: 6964 hours (290 days + 4 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 00 29 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 24 d1 7f 41 00      00:14:00.501  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:14:00.501  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:14:00.500  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:14:00.499  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:14:00.499  READ NATIVE MAX ADDRESS EXT

Error 1838 occurred at disk power-on lifetime: 6964 hours (290 days + 4 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 00 29 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 24 d1 7f 41 00      00:13:57.862  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:13:57.861  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:13:57.860  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:13:57.859  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:57.859  READ NATIVE MAX ADDRESS EXT

Error 1837 occurred at disk power-on lifetime: 6964 hours (290 days + 4 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 00 29 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 24 d1 7f 41 00      00:13:55.219  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:13:55.218  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:13:55.217  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:13:55.216  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:55.216  READ NATIVE MAX ADDRESS EXT

Error 1836 occurred at disk power-on lifetime: 6964 hours (290 days + 4 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 00 29 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 24 d1 7f 41 00      00:13:52.535  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:13:52.534  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:13:52.533  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:13:52.532  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:52.532  READ NATIVE MAX ADDRESS EXT

Error 1835 occurred at disk power-on lifetime: 6964 hours (290 days + 4 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 00 29 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 24 d1 7f 41 00      00:13:49.881  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:13:49.881  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:13:49.879  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:13:49.879  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:49.878  READ NATIVE MAX ADDRESS EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      6964         25153833
# 2  Short offline       Completed: read failure       90%      6964         25153833

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  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.
Smart poza jednym podejrzanym sektorem wydawał się być ok, ale dysk nie przechodził żadnego testu. Przeskanowałem dysk mhdd i wyniki były nieciekawe: 11 martwych sektorów i ponad 20 kandydatów na kolejne.

SMART po skanowaniu wyglądał już inaczej:

Kod: Zaznacz cały

robert@robert-laptop:~$ sudo smartctl -a /dev/sda 
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     ST9500325AS
Serial Number:    6VE7AVKA
Firmware Version: 0003SDM1
User Capacity:    500,107,862,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun May 27 11:08:10 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== 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:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		 (   0) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 142) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103b)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   087   084   006    Pre-fail  Always       -       141905288
  3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1233
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x000f   080   060   030    Pre-fail  Always       -       109485314
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6996
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   037   020    Old_age   Always       -       1233
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       3082
188 Unknown_Attribute       0x0032   100   097   000    Old_age   Always       -       22
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   063   049   045    Old_age   Always       -       37 (Lifetime Min/Max 36/38)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       29
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       55
193 Load_Cycle_Count        0x0032   092   092   000    Old_age   Always       -       17377
194 Temperature_Celsius     0x0022   037   051   000    Old_age   Always       -       37 (0 16 0 0)
195 Hardware_ECC_Recovered  0x001a   043   036   000    Old_age   Always       -       141905288
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       11
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       11
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
254 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 3915 (device log contains only the most recent five errors)
	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 3915 occurred at disk power-on lifetime: 6982 hours (290 days + 22 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 00 30 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 0c ce 82 41 00      00:14:38.881  WRITE FPDMA QUEUED
  61 00 08 44 c4 82 41 00      00:14:38.880  WRITE FPDMA QUEUED
  61 00 08 44 c2 82 41 00      00:14:38.877  WRITE FPDMA QUEUED
  61 00 08 7c ac 82 41 00      00:14:38.876  WRITE FPDMA QUEUED
  61 00 08 5c ac 82 41 00      00:14:38.875  WRITE FPDMA QUEUED

Error 3914 occurred at disk power-on lifetime: 6982 hours (290 days + 22 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 00 30 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 0c 3a 82 41 00      00:14:35.998  WRITE FPDMA QUEUED
  61 00 08 0c 36 82 41 00      00:14:35.997  WRITE FPDMA QUEUED
  61 00 08 74 34 82 41 00      00:14:35.993  WRITE FPDMA QUEUED
  61 00 08 64 34 82 41 00      00:14:35.990  WRITE FPDMA QUEUED
  61 00 08 54 34 82 41 00      00:14:35.989  WRITE FPDMA QUEUED

Error 3913 occurred at disk power-on lifetime: 6982 hours (290 days + 22 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 00 30 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 2c d1 7f 41 00      00:14:33.286  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:14:33.286  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:14:33.284  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:14:33.284  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:14:33.283  READ NATIVE MAX ADDRESS EXT

Error 3912 occurred at disk power-on lifetime: 6982 hours (290 days + 22 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 00 30 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 2c d1 7f 41 00      00:14:30.720  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:14:30.720  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:14:30.718  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:14:30.718  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:14:30.718  READ NATIVE MAX ADDRESS EXT

Error 3911 occurred at disk power-on lifetime: 6982 hours (290 days + 22 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 00 30 d1 7f 01

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 2c d1 7f 41 00      00:14:28.220  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:14:28.220  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:14:28.218  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:14:28.218  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:14:28.217  READ NATIVE MAX ADDRESS EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      6979         25153833
# 2  Extended offline    Completed: read failure       90%      6969         25153833
# 3  Conveyance offline  Completed: read failure       90%      6969         25153833
# 4  Short offline       Completed: read failure       90%      6964         25153833
# 5  Short offline       Completed: read failure       90%      6964         25153833

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  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.
Liczba relokowanych sektorów podkoczyła z 0 do 1 - najwyrażniej podejrzany wcześniej sektor został w końcu relokowany. Badsectory wykryte przez mhdd w końcu pojawiły się w smart.
I teraz pytanie klucz - kiedy te błędne sektory zostaną realokowane? Poprzedni podejrzany sektor czekał na to ponad 2 dni, dopiero po przeskanowaniu mhdd coś ruszyło. Czy warto przeskanować dysk mhdd z opcją remp? Wszystkie bady są w jednym miejscu.
Dysk, a właściwie laptop, jest jeszcze 4 miesiące na gwarancji, i chętnie bym go wymienił, ale:
- zbliża mi się deadline pewnego projektu, dodatkowo koniec roku akademickiego i bez laptopa będzie ciężko.
- jeśli w serwisie tylko wyzerują mi ten dysk, to ja dziękuję, sam mogę sobie coś takiego zrobić.
Wolałbym więc przetrzymać go jeszcze 2-3 tygodnie, tym bardziej że komputer działa, tylko jest bardzo oporny przy jego włączaniu :P

Re: Bad sectors - jak działa realokacja?

: 28 maja 2012, 09:56
autor: linuxozaurus
masz podobną sytuację co u mnie była czeka ciebie wymiana dysku.

Ja ze swoim Dellem nie miałam problemu i mi wymienili dysk (w domu właściciela) , ale starego zabrali.

A więc moja rada skopiuj co masz ważne zgłoś awarię tego podzespołu.
Strefa czasowa UTC+02:00
Strona 1 z 1

Technologię dostarcza phpBB® Forum Software © phpBB Limited

Polski pakiet językowy dostarcza phpBB.pl