Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.
 Użytkownik
	Witam wszystkich
Ost na mojej maszynie przy probie kopiowania zaczely sie pojawiac dziwne bledy nt dysku w konsoli. nie moglem znalesc logow nigdzie. objawialo sie tym ze system kompletnie sie odcinal. pojawialy sie tylko bledy nt SDA
postanowilem zainstalowac ten bardzo przydatny program smartmontools i oto co dostalem 
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 111 099 006 Pre-fail Always - 36777682 3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 81 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 2042 7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 25960176661 9 Power_On_Hours 0x0032 078 078 000 Old_age Always - 19771 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 108 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 094 000 Old_age Always - 333 189 High_Fly_Writes 0x003a 076 076 000 Old_age Always - 24 190 Airflow_Temperature_Cel 0x0022 063 056 045 Old_age Always - 37 (Lifetime Min/Max 37/37) 194 Temperature_Celsius 0x0022 037 044 000 Old_age Always - 37 (0 15 0 0) 195 Hardware_ECC_Recovered 0x001a 037 030 000 Old_age Always - 36777682 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 5 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 5 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
ponizej wiecej info: to dysk Seagare 500GB
Device Model: ST3500320NS Serial Number: 5QM1BLLE Firmware Version: SN04 User Capacity: 500,107,862,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2 Local Time is: Sun Jan 23 11:57:54 2011 GMT SMART support is: Available - device has SMART capability. SMART support is: Enabled
a tu reszta raporu:
SMART Error Log Version: 1
ATA Error Count: 33 (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 33 occurred at disk power-on lifetime: 19723 hours (821 days + 19 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec ff 04 9d 00 32 a0 00      08:50:39.970  IDENTIFY DEVICE
  a1 ff 01 01 00 00 a0 00      08:50:39.568  IDENTIFY PACKET DEVICE
  00 00 00 00 00 00 00 04      08:50:34.946  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:31.851  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:31.731  NOP [Abort queued commands]
Error 32 occurred at disk power-on lifetime: 19723 hours (821 days + 19 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 ff 01 01 00 00 a0 00      08:50:39.568  IDENTIFY PACKET DEVICE
  00 00 00 00 00 00 00 04      08:50:34.946  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:31.851  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:31.731  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:30.939  NOP [Abort queued commands]
Error 31 occurred at disk power-on lifetime: 19723 hours (821 days + 19 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec ff 04 9d 00 32 a0 00      08:50:25.258  IDENTIFY DEVICE
  a1 ff 01 01 00 00 a0 00      08:50:24.855  IDENTIFY PACKET DEVICE
  00 00 00 00 00 00 00 04      08:50:16.182  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:13.088  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:12.968  NOP [Abort queued commands]
Error 30 occurred at disk power-on lifetime: 19723 hours (821 days + 19 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 ff 01 01 00 00 a0 00      08:50:24.855  IDENTIFY PACKET DEVICE
  00 00 00 00 00 00 00 04      08:50:16.182  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:13.088  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:12.968  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      08:50:12.176  NOP [Abort queued commands]
Error 29 occurred at disk power-on lifetime: 19723 hours (821 days + 19 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 02      08:46:27.298  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      08:46:27.290  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      08:46:27.134  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      08:46:22.106  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      08:46:22.098  IDENTIFY DEVICE
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 minute delay.teraz moje pytanie jest czy ktos potrafi stwierdzic: do wymiany albo jest ok
bo mi sie wydaje ze ja tu widze bardzo niedobre odczyty :(((
prosze o pomoc bo musze szybko decyzje podjac czy kupowac nowe dyski
dzieki!!
Ostatnio edytowany przez mqluke (2011-01-24 13:13:29)
Offline


 Użytkownik
	


ST3500320NS to jest czarna seria, wystarczy poczytać opinie, musisz jak najszybciej uaktualnić firmware do nowszej wersji, zanim dysk przestanie w ogóle widzieć w biosie, ale to i tak teraz raczej nic nie pomoże, konieczna będzie wymiana.
Offline
 Użytkownik