Skocz do zawartości

r   e   k   l   a   m   a

Zdjęcie

bad sektory na dysku


  • Zaloguj się, aby dodać odpowiedź
5 odpowiedzi w tym temacie

#1 fasaber

fasaber
  • Użytkownicy
  • 85 postów

Napisano 02.01.2010 - 00:06

wyskoczył mi komunikat ze mam bad sektory:
Dołączona grafika
więc wpisałem w terminalu:
sudo apt-get install smartmontools
aby zainstalowac program, następnie wpisałem:
sudo smartctl -a /dev/sda8
poniewaz podejrzewam że właśnie na sda8 są błędy, wyskoczyły dane:
darek@darek-laptop:~$ sudo smartctl -a /dev/sda8
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio family
Device Model:     WDC WD1600BEVS-00RST0
Serial Number:    WD-WXE907002987
Firmware Version: 04.01G04
User Capacity:    160,041,885,696 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Jan  1 19:59:31 2010 CET
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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		 (7560) 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: 	 (  97) minutes.
Conveyance self-test routine
recommended polling time: 	 (   6) minutes.
SCT capabilities: 	       (0x103f)	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     0x000f   200   200   051    Pre-fail  Always       -       45
  3 Spin_Up_Time            0x0003   187   185   021    Pre-fail  Always       -       1625
  4 Start_Stop_Count        0x0032   096   096   000    Old_age   Always       -       4509
  5 Reallocated_Sector_Ct   0x0033   149   149   140    Pre-fail  Always       -       404
  7 Seek_Error_Rate         0x000f   100   253   051    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1296
 10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1240
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       431
193 Load_Cycle_Count        0x0032   193   193   000    Old_age   Always       -       21252
194 Temperature_Celsius     0x0022   117   097   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   167   167   000    Old_age   Always       -       33
197 Current_Pending_Sector  0x0012   200   199   000    Old_age   Always       -       13
198 Offline_Uncorrectable   0x0010   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0009   100   253   051    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 490 (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 490 occurred at disk power-on lifetime: 1295 hours (53 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
  -- -- -- -- -- -- --
  01 51 00 66 86 b4 e1  Error: AMNF at LBA = 0x01b48666 = 28608102

  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 08 64 86 b4 01 00      00:51:18.428  READ DMA
  27 00 00 00 00 00 00 00      00:51:18.428  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 00      00:51:18.427  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 00      00:51:18.427  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 00      00:51:18.390  READ NATIVE MAX ADDRESS EXT

Error 489 occurred at disk power-on lifetime: 1295 hours (53 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
  -- -- -- -- -- -- --
  01 51 00 66 86 b4 e1  Error: AMNF at LBA = 0x01b48666 = 28608102

  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 08 64 86 b4 01 08      00:51:15.216  READ DMA
  27 00 00 00 00 00 00 08      00:51:15.215  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      00:51:15.215  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 08      00:51:15.215  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      00:51:15.214  READ NATIVE MAX ADDRESS EXT

Error 488 occurred at disk power-on lifetime: 1295 hours (53 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
  -- -- -- -- -- -- --
  01 51 00 66 86 b4 e1  Error: AMNF at LBA = 0x01b48666 = 28608102

  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 08 64 86 b4 01 08      00:51:12.362  READ DMA
  27 00 00 00 00 00 00 08      00:51:12.362  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      00:51:12.362  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 08      00:51:12.362  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      00:51:12.361  READ NATIVE MAX ADDRESS EXT

Error 487 occurred at disk power-on lifetime: 1295 hours (53 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
  -- -- -- -- -- -- --
  01 51 00 66 86 b4 e1  Error: AMNF at LBA = 0x01b48666 = 28608102

  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 08 64 86 b4 01 08      00:51:09.511  READ DMA
  27 00 00 00 00 00 00 08      00:51:09.510  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      00:51:09.510  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 08      00:51:09.510  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      00:51:09.509  READ NATIVE MAX ADDRESS EXT

Error 486 occurred at disk power-on lifetime: 1295 hours (53 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
  -- -- -- -- -- -- --
  01 51 00 66 86 b4 e1  Error: AMNF at LBA = 0x01b48666 = 28608102

  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 08 64 86 b4 01 08      00:51:06.659  READ DMA
  27 00 00 00 00 00 00 08      00:51:06.658  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      00:51:06.658  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 08      00:51:06.658  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      00:51:06.658  READ NATIVE MAX ADDRESS EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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 min
co robić ??
niestety domyślam sie dlaczego wyskoczyły... troche na sylwetra zaszaleliśmy i zacząłem walić w laptopa pięścią bo mi sie wieszał... to mogło być od tego
jakoś się tego nie da obejść np. czytałem coś że w miejsce nie bad sektorów nie robić partycji, poprostu je omijac

#2 bogna2009

bogna2009
  • Użytkownicy
  • 213 postów

Napisano 02.01.2010 - 00:34

troche na sylwetra zaszaleliśmy i zacząłem walić w laptopa pięścią bo mi sie wieszał...

omgh :o

Polecam MHDD (live cd) chyba najlepszy program do diagnozy i ew. naprawy.
Możliwe że trzeba tylko naprawić sektory (jeśli faktycznie padły), jeśli nie to remap.
Wszystko ładnie opisane tutaj:
http://www.nirvanowi...ka.pl/MHDD.html
Tylko lamy podłączają modem/router przez USB, i później są problemy :P
Uwielbiam offtopować :P

#3 fasaber

fasaber
  • Użytkownicy
  • 85 postów

Napisano 02.01.2010 - 00:40

ok, to mogłobyć od tego ?? :)

#4 bogna2009

bogna2009
  • Użytkownicy
  • 213 postów

Napisano 02.01.2010 - 01:01

ok, to mogłobyć od tego

Mogło być od wszystkiego, zależy jak ciężka była Twoja pięść.
Generalnie z kręcącym się dyskiem należy obchodzić się jak z jajkiem a nie jak z przeciwnikiem.
Spróbuj jeszcze zrobić chkdsk z opcją automatycznie napraw uszkodzone sektory.
Tylko lamy podłączają modem/router przez USB, i później są problemy :P
Uwielbiam offtopować :P

#5 Robin-Otzi

Robin-Otzi
  • Użytkownicy
  • 514 postów

Napisano 02.01.2010 - 09:34

jeśli uszkodzenia są w jakimś konkretnym miejscu dysku i nie są za bardzo rozproszone to ja już tak robiłem, że obliczałem ile MB jest zdrowych potem ile trzeba zostawić bez partycji i znowu czysta partycja itd. niestety czasem może ci wyjść kilka partycji
i niema gwarancji, że dalej się nie posypie
AMD Athlon 64 x2 4000+Asus M2A-VM 8GB DDR2-800 Radeon 5450 itd.

#6 technik_elektro

technik_elektro
  • Użytkownicy
  • 8422 postów

Napisano 02.01.2010 - 11:42

podaj wartość parametru realocated sectour count
Asus G73JH i7-720QM 8G 1TB HD5870 Win 7, 256GB SSD
MBA mid 2011