пригодны ли харды к использованию?

подцепил старенькие харды. посмотрел атрибуты S.M.A.R.T....
согласно выводов, битых секторов вроде нет,
но напрягают атрибуты Raw_Read_Error_Rate и Seek_Error_Rate
подскажите, с хардами sdC и sdD все плохо?

SDB
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   235   235   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       192
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   076   076   000    Old_age   Always       -       10725
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       192
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       71
193 Load_Cycle_Count        0x0012   001   001   000    Old_age   Always       -       1597851
194 Temperature_Celsius     0x0002   153   153   000    Old_age   Always       -       39 (Min/Max 17/48)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       35
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SDC
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   116   099   006    Pre-fail  Always       -       102783480
  3 Spin_Up_Time            0x0003   096   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       401
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   074   060   030    Pre-fail  Always       -       25903666
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14294
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       253
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   057   057   000    Old_age   Always       -       43
190 Airflow_Temperature_Cel 0x0022   056   049   045    Old_age   Always       -       44 (Min/Max 41/50)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       196
193 Load_Cycle_Count        0x0032   068   068   000    Old_age   Always       -       64027
194 Temperature_Celsius     0x0022   044   051   000    Old_age   Always       -       44 (0 16 0 0 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       -       34

SDD
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   117   099   006    Pre-fail  Always       -       147520079
  3 Spin_Up_Time            0x0003   095   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1462
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   073   060   030    Pre-fail  Always       -       12960648814
  9 Power_On_Hours          0x0032   073   073   000    Old_age   Always       -       23879
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       683
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   055   055   000    Old_age   Always       -       45
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       8590196755
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   056   044   045    Old_age   Always   In_the_past 44 (0 2 48 40 0)
194 Temperature_Celsius     0x0022   044   056   000    Old_age   Always       -       44 (0 17 0 0 0)
195 Hardware_ECC_Recovered  0x001a   039   008   000    Old_age   Always       -       147520079
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
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       69900592766667
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3283338224
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3120569585

есть ошибки:
sdC
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 35 (device log contains only the most recent 4 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
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 35 [2] occurred at disk power-on lifetime: 667 hours (27 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 02 f0 00 00 00 04 45 98 00 00  Error: ICRC, ABRT at LBA = 0x00044598 = 279960

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 04 00 00 10 00 00 00 43 49 78 40 00     00:22:50.784  WRITE FPDMA QUEUED
  61 00 78 00 08 00 00 00 43 49 00 40 00     00:22:50.783  WRITE FPDMA QUEUED
  61 04 00 00 50 00 00 00 43 45 00 40 00     00:22:50.781  WRITE FPDMA QUEUED
  61 04 00 00 48 00 00 00 43 41 00 40 00     00:22:50.779  WRITE FPDMA QUEUED
  61 04 00 00 40 00 00 00 43 3d 00 40 00     00:22:50.777  WRITE FPDMA QUEUED

Error 34 [1] occurred at disk power-on lifetime: 667 hours (27 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 02 20 00 00 00 04 0e e8 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  2f 00 00 00 01 00 00 00 00 00 10 a0 00     00:22:50.366  READ LOG EXT
  61 04 00 00 20 00 00 00 04 25 08 40 00     00:22:50.325  WRITE FPDMA QUEUED
  61 04 00 00 18 00 00 00 04 21 08 40 00     00:22:50.325  WRITE FPDMA QUEUED
  61 04 00 00 10 00 00 00 04 1d 08 40 00     00:22:50.319  WRITE FPDMA QUEUED
  61 04 00 00 30 00 00 00 04 19 08 40 00     00:22:50.315  WRITE FPDMA QUEUED

Error 33 [0] occurred at disk power-on lifetime: 667 hours (27 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 00 60 00 00 00 03 7c a0 00 00  Error: ICRC, ABRT at LBA = 0x00037ca0 = 228512

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 04 00 00 58 00 00 00 03 d9 00 40 00     00:17:33.636  WRITE FPDMA QUEUED
  61 04 00 00 50 00 00 00 03 d5 00 40 00     00:17:33.634  WRITE FPDMA QUEUED
  61 04 00 00 48 00 00 00 03 d1 00 40 00     00:17:33.632  WRITE FPDMA QUEUED
  61 04 00 00 40 00 00 00 03 cd 00 40 00     00:17:33.630  WRITE FPDMA QUEUED
  61 04 00 00 38 00 00 00 03 c9 00 40 00     00:17:33.630  WRITE FPDMA QUEUED

Error 32 [3] occurred at disk power-on lifetime: 667 hours (27 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 00 68 00 00 00 02 f9 d4 00 00  Error: ICRC, ABRT at LBA = 0x0002f9d4 = 195028

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 a8 00 58 00 00 00 03 0c 9c 40 00     00:10:14.156  WRITE FPDMA QUEUED
  61 00 a8 00 50 00 00 00 03 0b f4 40 00     00:10:14.156  WRITE FPDMA QUEUED
  61 00 a8 00 48 00 00 00 03 0b 4c 40 00     00:10:14.156  WRITE FPDMA QUEUED
  61 00 a8 00 40 00 00 00 03 0a a4 40 00     00:10:14.155  WRITE FPDMA QUEUED
  61 00 a8 00 38 00 00 00 03 09 fc 40 00     00:10:14.155  WRITE FPDMA QUEUED
sdD
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 45 (device log contains only the most recent 20 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
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 45 [4] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:11:46.018  READ DMA EXT
  25 da d8 00 01 00 00 00 00 00 00 e0 00     09:11:45.972  READ DMA EXT
  25 da d8 00 80 00 00 69 a2 dc 0f e0 00     09:11:43.229  READ DMA EXT
  25 da d8 00 01 00 00 00 00 00 00 e0 00     09:11:43.141  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:11:40.414  READ DMA EXT

Error 44 [3] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 80 00 00 69 a2 dc 0f e0 00     09:11:43.229  READ DMA EXT
  25 da d8 00 01 00 00 00 00 00 00 e0 00     09:11:43.141  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:11:40.414  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 47 e0 00     09:11:40.413  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 57 e0 00     09:11:40.413  READ DMA EXT

Error 43 [2] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:11:40.414  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 47 e0 00     09:11:40.413  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 57 e0 00     09:11:40.413  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 0f e0 00     09:11:40.404  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 27 e0 00     09:11:40.403  READ DMA EXT

Error 42 [1] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:09:02.294  READ DMA EXT
  25 da d8 00 01 00 00 00 00 00 00 e0 00     09:09:02.294  READ DMA EXT
  25 da d8 00 08 00 00 69 a2 dc 57 e0 00     09:09:02.294  READ DMA EXT
  35 da d8 00 80 00 00 64 87 54 3f e0 00     09:09:02.293  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 53 bf e0 00     09:09:02.293  WRITE DMA EXT

Error 41 [0] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:08:59.513  READ DMA EXT
  35 da d8 00 80 00 00 64 87 51 3f e0 00     09:08:59.512  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 50 bf e0 00     09:08:59.512  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 50 3f e0 00     09:08:59.511  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 4f bf e0 00     09:08:59.511  WRITE DMA EXT

Error 40 [19] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:08:56.726  READ DMA EXT
  35 da d8 00 80 00 00 64 87 4e 3f e0 00     09:08:56.725  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 4d bf e0 00     09:08:56.724  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 4d 3f e0 00     09:08:56.723  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 4c bf e0 00     09:08:56.722  WRITE DMA EXT

Error 39 [18] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:08:53.987  READ DMA EXT
  35 da d8 00 80 00 00 64 87 4a 3f e0 00     09:08:53.187  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 49 bf e0 00     09:08:53.186  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 49 3f e0 00     09:08:53.185  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 48 bf e0 00     09:08:53.185  WRITE DMA EXT

Error 38 [17] occurred at disk power-on lifetime: 6650 hours (277 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 69 a2 dc 1a 00 00  Error: UNC at LBA = 0x69a2dc1a = 1772280858

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 da d8 00 08 00 00 69 a2 dc 17 e0 00     09:08:49.097  READ DMA EXT
  35 da d8 00 80 00 00 64 87 42 3f e0 00     09:08:48.187  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 41 bf e0 00     09:08:48.186  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 41 3f e0 00     09:08:48.186  WRITE DMA EXT
  35 da d8 00 80 00 00 64 87 40 bf e0 00     09:08:48.185  WRITE DMA EXT
Прогнать whdd.
Под не сильно важные данные пойдёт ИМХО. А для пущего успокоения прогнать лучше не whdd, а badblocks в режиме чтение/запись.
Затестить скорость, сравнить с паспортной.
lampslave
прогнать лучше ... badblocks в режиме чтение/запись.
Это так, но был случай, когда тест на запись/чтение (0xaa, 0x55, 0xff, 0x00) проходил нормально, но после установки системы массово вываливались бэд блоки. Поэтому я бы еще посоветовал рандомно заполнить проблемный хард, а через несколько часов проверить блоки на чтение. При этом iostat запустить на предмет загрузки системы винчестером.
ЗЫ. В случае положительного результата, список битых блоков, разумеется, можно скормить e2fsck или mke2fs (отдельно для каждого раздела).
Aivar
Поэтому я бы еще посоветовал рандомно заполнить проблемный хард, а через несколько часов проверить блоки на чтение.
Тогда уж, наверное, дней, а не часов. Проверка винта на 500 гигов и так идёт часов 18.
Если винт имеет большое количество битых блоков - да, процесс займет очень много времени. Раздел в 40 гиг проверялся, емнип, часов шесть. Если бэд блоков нет - точно не вспомню, но весь винт - дело одного-двух десятков минут (только чтение).
Только на чтение - это не проверка, обязательно надо проверять на запись, если есть какие-то сомнения в здоровье винта.
lampslave
А для пущего успокоения прогнать лучше не whdd, а badblocks в режиме чтение/запись.
whdd - It is capable of testing a hard drive with reading and writing, providing intuitive visualization of the process.

badblocks что-нибудь покажет при наличии секторов с относительно большим временем чтения (~500ms)?
lampslave, спорить не стану, но и повторяться не буду.
 
Зарегистрироваться или войдите чтобы оставить сообщение.