форумы  помощь  поиск  регистрация  майллист  ВХОД  слежка

Вариант для распечатки		Архивированная нить - только для чтения!  Пред. тема | След. тема
Форумы OpenNET: Виртуальная конференция (Public)
Изначальное сообщение		[Проследить за развитием треда]

"Помогите разобраться"
Сообщение от qwerty (??) on 01-Апр-05, 17:52  (MSK)
я так понимаю моему харду осталось жить совсем чуток? :) вот что выдала утилита SMART su-3.00# smartctl -a /dev/ad0 smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model:     ST320410A Serial Number:    3FB1VQJC Firmware Version: 3.60 Device is:        In smartctl database [for details use: -P show] ATA Version is:   6 ATA Standard is:  Exact ATA specification draft version not indicated Local Time is:    Fri Apr  1 17:50:59 2005 MSD SMART support is: Available - device has SMART capability. SMART support is: Enabled The SMART RETURN STATUS return value (smartmontools -H option/Directive) can not be retrieved with this version of ATAng, please do not rely on this value === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status:  (0x02) Offline data collection activity                                         was completed without error.                                         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:                 ( 420) seconds. Offline data collection capabilities:                    (0x1d) SMART execute Offline immediate.                                         No Auto Offline data collection support.                                         Abort Offline collection upon new                                         command.                                         Offline surface scan supported.                                         Self-test supported.                                         No Conveyance Self-test supported.                                         No 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.                                         No General Purpose Logging support. Short self-test routine recommended polling time:        (   1) minutes. Extended self-test routine recommended polling time:        (  22) minutes. 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   060   052   025    Pre-fail  Always       -       238942316   3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0   4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       468   5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0   7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       122077083   9 Power_On_Hours          0x0032   087   087   000    Old_age   Always       -       12155 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       880 194 Temperature_Celsius     0x0022   039   051   000    Old_age   Always       -       39 195 Hardware_ECC_Recovered  0x001a   100   253   000    Old_age   Always       -       0 197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0 198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0 199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0 200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0 202 TA_Increase_Count       0x0032   100   253   000    Old_age   Always       -       0 SMART Error Log Version: 1 ATA Error Count: 5         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 5 occurred at disk power-on lifetime: 602 hours (25 days + 2 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   -- -- -- -- -- -- --   00 51 ff 01 00 00 e0  Error:   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   a0 00 08 01 00 00 e0 00      00:00:13.669  PACKET   c8 00 08 13 69 a7 e1 02      00:00:00.023  READ DMA   a0 00 08 01 18 00 e0 00      00:00:12.602  PACKET   c8 00 08 cb 3a c3 e1 02      00:00:00.023  READ DMA   c8 00 08 cb 3a c3 e1 00      00:00:16.861  READ DMA Error 4 occurred at disk power-on lifetime: 602 hours (25 days + 2 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   -- -- -- -- -- -- --   00 51 08 13 69 a7 e1  Error:   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   a0 00 08 01 18 00 e0 00      00:00:12.602  PACKET   c8 00 08 cb 3a c3 e1 02      00:00:00.023  READ DMA   c8 00 08 cb 3a c3 e1 00      00:00:16.861  READ DMA   c8 00 08 eb e6 a2 e1 02      00:00:00.026  READ DMA   c8 00 08 c3 d9 6a e1 00      00:00:00.122  READ DMA Error 3 occurred at disk power-on lifetime: 584 hours (24 days + 8 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   -- -- -- -- -- -- --   00 50 08 2e 38 a7 e1   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   a0 00 08 01 18 00 e0 00      00:00:17.064  PACKET   c8 00 08 86 5a 3f e1 02      00:00:00.024  READ DMA   c8 00 08 86 5a 3f e1 00      00:00:17.453  READ DMA   c8 00 08 f6 32 bb e1 00      00:00:00.011  READ DMA   c8 00 08 b6 04 03 e1 00      00:00:00.123  READ DMA Error 2 occurred at disk power-on lifetime: 580 hours (24 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   -- -- -- -- -- -- --   00 50 08 86 5d bb e1   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   a0 00 08 00 00 00 e0 00      00:00:15.963  PACKET   c8 00 08 b6 65 77 e1 02      00:00:00.019  READ DMA   c8 00 08 b6 65 77 e1 00      00:00:13.265  READ DMA   c8 00 08 16 48 57 e1 02      00:00:00.020  READ DMA   c8 00 08 b6 04 03 e1 00      00:00:00.115  READ DMA Error 1 occurred at disk power-on lifetime: 499 hours (20 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   -- -- -- -- -- -- --   00 51 08 c7 63 5f e1  Error:   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   a0 00 10 10 7c 00 e0 00      00:00:15.873  PACKET   c8 00 10 3f 76 63 e1 02      00:00:00.020  READ DMA   c8 00 08 3f 76 63 e1 00      00:00:00.036  READ DMA   ca 00 08 17 08 33 e1 00      00:00:00.666  WRITE DMA   c8 00 08 87 ed 1e e1 00      00:00:17.846  READ DMA SMART Self-test log structure revision number 1 No self-tests have been logged.  [To run self-tests, use: smartctl -t] Device does not support Selective Self Tests/Logging
	Рекомендовать в FAQ | Cообщить модератору | Наверх

Индекс форумов | Темы | Пред. тема | След. тема

Сообщения по теме

1. "Помогите разобраться"
Сообщение от lavr on 01-Апр-05, 18:15  (MSK)
>я так понимаю моему харду осталось жить совсем чуток? :) >вот что выдала утилита SMART >su-3.00# smartctl -a /dev/ad0 >smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen >Home page is http://smartmontools.sourceforge.net/ > >=== START OF INFORMATION SECTION === >Device Model:     ST320410A >Serial Number:    3FB1VQJC >Firmware Version: 3.60 >Device is:        In smartctl database >[for details use: -P show] >ATA Version is:   6 >ATA Standard is:  Exact ATA specification draft version not indicated >Local Time is:    Fri Apr  1 17:50:59 2005 >MSD >SMART support is: Available - device has SMART capability. >SMART support is: Enabled > >The SMART RETURN STATUS return value (smartmontools -H option/Directive) > can not be retrieved with this version of ATAng, please do >not rely on this value >=== START OF READ SMART DATA SECTION === >SMART overall-health self-assessment test result: PASSED > >General SMART Values: >Offline data collection status:  (0x02) Offline data collection activity >             >           >           >      was completed without error. >             >           >           >      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:           >      ( 420) seconds. >Offline data collection >capabilities:             >        (0x1d) SMART execute >Offline immediate. >             >           >           >      No Auto Offline data collection >support. >             >           >           >      Abort Offline collection upon new > >             >           >           >      command. >             >           >           >      Offline surface scan supported. >             >           >           >      Self-test supported. >             >           >           >      No Conveyance Self-test supported. >             >           >           >      No 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. >             >           >           >      No General Purpose Logging support. > >Short self-test routine >recommended polling time:        (   > 1) minutes. >Extended self-test routine >recommended polling time:        (   >22) minutes. > >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   060 >  052   025    Pre-fail   >Always       -     >   238942316 >  3 Spin_Up_Time         >   0x0003   098   098   > 000    Pre-fail  Always     >   -       0 > >  4 Start_Stop_Count        0x0032 >  100   100   020   > Old_age   Always       >-       468 >  5 Reallocated_Sector_Ct   0x0033   100   >100   036    Pre-fail  Always   >     -       > 0 >  7 Seek_Error_Rate         >0x000f   081   060   030   >  Pre-fail  Always       >-       122077083 >  9 Power_On_Hours         > 0x0032   087   087   000 >   Old_age   Always     >  -       12155 > 10 Spin_Retry_Count        0x0013   > 100   100   097     >Pre-fail  Always       -   >     0 > 12 Power_Cycle_Count       0x0032   >100   100   020    Old_age >  Always       -   >     880 >194 Temperature_Celsius     0x0022   039   >051   000    Old_age   Always >      -     >  39 >195 Hardware_ECC_Recovered  0x001a   100   253   >000    Old_age   Always     >   -       0 > >197 Current_Pending_Sector  0x0012   100   100   >000    Old_age   Always     >   -       0 > >198 Offline_Uncorrectable   0x0010   100   100   > 000    Old_age   Offline   >   -       0 > >199 UDMA_CRC_Error_Count    0x003e   200   200 >  000    Old_age   Always   >     -       > 0 >200 Multi_Zone_Error_Rate   0x0000   100   253   > 000    Old_age   Offline   >   -       0 > >202 TA_Increase_Count       0x0032   100 >  253   000    Old_age   > Always       -   >    0 > >SMART Error Log Version: 1 >ATA Error Count: 5 >        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 5 occurred at disk power-on lifetime: 602 hours (25 days + >2 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 >  -- -- -- -- -- -- -- >  00 51 ff 01 00 00 e0  Error: > >  Commands leading to the command that caused the error were: > >  CR FR SC SN CL CH DH DC   >Powered_Up_Time  Command/Feature_Name >  -- -- -- -- -- -- -- --  ---------------- > -------------------- >  a0 00 08 01 00 00 e0 00   >   00:00:13.669  PACKET >  c8 00 08 13 69 a7 e1 02   >   00:00:00.023  READ DMA >  a0 00 08 01 18 00 e0 00   >   00:00:12.602  PACKET >  c8 00 08 cb 3a c3 e1 02   >   00:00:00.023  READ DMA >  c8 00 08 cb 3a c3 e1 00   >   00:00:16.861  READ DMA > >Error 4 occurred at disk power-on lifetime: 602 hours (25 days + >2 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 >  -- -- -- -- -- -- -- >  00 51 08 13 69 a7 e1  Error: > >  Commands leading to the command that caused the error were: > >  CR FR SC SN CL CH DH DC   >Powered_Up_Time  Command/Feature_Name >  -- -- -- -- -- -- -- --  ---------------- > -------------------- >  a0 00 08 01 18 00 e0 00   >   00:00:12.602  PACKET >  c8 00 08 cb 3a c3 e1 02   >   00:00:00.023  READ DMA >  c8 00 08 cb 3a c3 e1 00   >   00:00:16.861  READ DMA >  c8 00 08 eb e6 a2 e1 02   >   00:00:00.026  READ DMA >  c8 00 08 c3 d9 6a e1 00   >   00:00:00.122  READ DMA > >Error 3 occurred at disk power-on lifetime: 584 hours (24 days + >8 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 >  -- -- -- -- -- -- -- >  00 50 08 2e 38 a7 e1 > >  Commands leading to the command that caused the error were: > >  CR FR SC SN CL CH DH DC   >Powered_Up_Time  Command/Feature_Name >  -- -- -- -- -- -- -- --  ---------------- > -------------------- >  a0 00 08 01 18 00 e0 00   >   00:00:17.064  PACKET >  c8 00 08 86 5a 3f e1 02   >   00:00:00.024  READ DMA >  c8 00 08 86 5a 3f e1 00   >   00:00:17.453  READ DMA >  c8 00 08 f6 32 bb e1 00   >   00:00:00.011  READ DMA >  c8 00 08 b6 04 03 e1 00   >   00:00:00.123  READ DMA > >Error 2 occurred at disk power-on lifetime: 580 hours (24 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 >  -- -- -- -- -- -- -- >  00 50 08 86 5d bb e1 > >  Commands leading to the command that caused the error were: > >  CR FR SC SN CL CH DH DC   >Powered_Up_Time  Command/Feature_Name >  -- -- -- -- -- -- -- --  ---------------- > -------------------- >  a0 00 08 00 00 00 e0 00   >   00:00:15.963  PACKET >  c8 00 08 b6 65 77 e1 02   >   00:00:00.019  READ DMA >  c8 00 08 b6 65 77 e1 00   >   00:00:13.265  READ DMA >  c8 00 08 16 48 57 e1 02   >   00:00:00.020  READ DMA >  c8 00 08 b6 04 03 e1 00   >   00:00:00.115  READ DMA > >Error 1 occurred at disk power-on lifetime: 499 hours (20 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 >  -- -- -- -- -- -- -- >  00 51 08 c7 63 5f e1  Error: > >  Commands leading to the command that caused the error were: > >  CR FR SC SN CL CH DH DC   >Powered_Up_Time  Command/Feature_Name >  -- -- -- -- -- -- -- --  ---------------- > -------------------- >  a0 00 10 10 7c 00 e0 00   >   00:00:15.873  PACKET >  c8 00 10 3f 76 63 e1 02   >   00:00:00.020  READ DMA >  c8 00 08 3f 76 63 e1 00   >   00:00:00.036  READ DMA >  ca 00 08 17 08 33 e1 00   >   00:00:00.666  WRITE DMA >  c8 00 08 87 ed 1e e1 00   >   00:00:17.846  READ DMA > >SMART Self-test log structure revision number 1 >No self-tests have been logged.  [To run self-tests, use: smartctl -t] > > > >Device does not support Selective Self Tests/Logging только одна неприятность: WRITE DMA ERROR, на сколько она серьезная, сказать трудно. READ DMA ERROR не страшно. Могу посоветовать перевести в другой DMA режим, менее скоростной. И потом, использовался short режим тестирования, он показал суммарные зафиксированные ошибки за время работы с момента включения и все сбои где-то в одном районе. Прим: smartmontools достаточно сырая вещь для freebsd или правильней, freebsd не очень то пока заточена для работы под ней таких утилит.
	Рекомендовать в FAQ | Cообщить модератору | Наверх

	2. "Помогите разобраться"
	Сообщение от qwerty (??) on 01-Апр-05, 18:32  (MSK)
	Спасибо за помощь! немного успокоили меня :)
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	3. "Помогите разобраться"
	Сообщение от lavr on 01-Апр-05, 18:40  (MSK)
	>Спасибо за помощь! >немного успокоили меня :) нет не супокоил, современные винты могут осыпаться за неделю или за день! я бы попробовал загрузиться в single-user mode и несколько раз запустить dd на сырой диск: # dd if=/dev/adX of=/dev/null взять листок и выписывать сбойные сектора если есть другая машина с FreeBSD, попробовать подцепить туда и снова dd на сырой диск (верхний тест только на чтение) и посмотреть зависимость от контроллера, если сбои повторились и в тех же местах (смотреть еще и логи) то можно попробовать mhdd32 с возможностью remap сбойных секторов Вобщем к качеству дисков PATA/SATA сейчас тьма нареканий, надо покупать не абы какие, а из списков рекомендованных проивзодителями ata-raid'ов 3ware и promise
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	4. "Помогите разобраться"
	Сообщение от qwerty (??) on 01-Апр-05, 18:53  (MSK)
	ad0: 19092MB <ST320410A/3.60> [38792/16/63] at ata0-master UDMA33
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	5. "Помогите разобраться"
	Сообщение от lavr on 01-Апр-05, 21:52  (MSK)
	>ad0: 19092MB <ST320410A/3.60> [38792/16/63] at ata0-master UDMA33 ни о чем не говорит, только недавно два новых сигейта в помойку выбросил а выше и вовсе старая модель
		Рекомендовать в FAQ | Cообщить модератору | Наверх

Удалить

Индекс форумов | Темы | Пред. тема | След. тема

Пожалуйста, прежде чем написать сообщение, ознакомьтесь с данными рекомендациями.