Проблема с жестким диском

После полной переустановки Федоры 11 x86 Gnome, Palimpsest Disk Utility выдает сообщение о проблеме с жестким диском. Если посмотреть дополнительную информацию в утилите, то говорится, что Reallocated Sector Count 279 Sectors Failing. Самотестирование в этой утилите проходит только на малом уровне, т.е. большое тестирование или extended выдает после долгого молчания какую-то непонятную ошибку. Инфо в утилите так же показывает что assessment:passed но The disk has bad sectors Диск у меня 300 GB ATA ST3300831AS, система поставлена в LVM и зашифрована. Подскажите какие проблемы будут если пользоваться таким диском? Нужно ли им пользоваться? И как можно вылечить?

Ссылка

← Помогите выбрать линукс под железо

Помогите подобрать нетбук для поездок и повседневной работы →

# smartctl --all /dev/sd??

в студию.

Похоже, конец твоему диску -- 279 секторов, явно многовато.

~~gotf~~ ★
(01.08.09 12:19:26 MSK)

Ответ на: комментарий от gotf 01.08.09 12:19:26 MSK

[root@small gres]# smartctl --all /dev/sda
smartctl version 5.38 [i386-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.8 family
Device Model:     ST3300831AS
Serial Number:    5NF0HBXB
Firmware Version: 3.03
User Capacity:    300 069 052 416 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:    Sat Aug  1 12:22:52 2009 MSD
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: 		 ( 430) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No 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: 	 ( 101) minutes.

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   063   057   006    Pre-fail  Always       -       198171166
  3 Spin_Up_Time            0x0003   097   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1565
  5 Reallocated_Sector_Ct   0x0033   094   094   036    Pre-fail  Always       -       279
  7 Seek_Error_Rate         0x000f   086   060   030    Pre-fail  Always       -       429248658
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       10034
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1476
194 Temperature_Celsius     0x0022   045   054   000    Old_age   Always       -       45 (0 14 0 0)
195 Hardware_ECC_Recovered  0x001a   063   057   000    Old_age   Always       -       198171166
197 Current_Pending_Sector  0x0012   100   097   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   097   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: 3147 (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]

gres ★
(01.08.09 12:31:33 MSK) автор топика

Ответ на: комментарий от gres 01.08.09 12:31:33 MSK

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 3147 occurred at disk power-on lifetime: 2447 hours (101 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
  -- -- -- -- -- -- --
  10 51 49 a9 2f 45 e0  Error: IDNF 73 sectors at LBA = 0x00452fa9 = 4534185

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 80 60 2f 45 e0 00      02:14:32.405  READ DMA EXT
  35 00 18 c0 7d 8c e0 00      02:14:32.405  WRITE DMA EXT
  25 00 18 40 2f 45 e0 00      02:14:32.405  READ DMA EXT
  35 00 20 a0 7d 8c e0 00      02:14:32.404  WRITE DMA EXT
  25 00 20 20 2f 45 e0 00      02:14:32.404  READ DMA EXT

Error 3146 occurred at disk power-on lifetime: 2435 hours (101 days + 11 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 61 00 79 45 40  Error: UNC 97 sectors at LBA = 0x00457900 = 4552960

  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 88 9f 78 45 40 00      04:24:46.311  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:42.557  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:38.812  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:35.058  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:31.313  READ DMA

Error 3145 occurred at disk power-on lifetime: 2435 hours (101 days + 11 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 61 00 79 45 40  Error: UNC 97 sectors at LBA = 0x00457900 = 4552960

  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 88 9f 78 45 40 00      04:24:16.344  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:42.557  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:38.812  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:35.058  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:31.313  READ DMA

Error 3144 occurred at disk power-on lifetime: 2435 hours (101 days + 11 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 61 00 79 45 40  Error: UNC 97 sectors at LBA = 0x00457900 = 4552960

  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 88 9f 78 45 40 00      04:24:16.344  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:16.342  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:38.812  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:35.058  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:31.313  READ DMA

Error 3143 occurred at disk power-on lifetime: 2435 hours (101 days + 11 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 61 00 79 45 40  Error: UNC 97 sectors at LBA = 0x00457900 = 4552960

  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 88 9f 78 45 40 00      04:24:16.344  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:16.342  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:16.341  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:35.058  READ DMA
  c8 00 88 9f 78 45 40 00      04:24:31.313  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     10033         -
# 2  Extended offline    Aborted by host               90%     10022         -
# 3  Short offline       Completed without error       00%     10016         -
# 4  Extended offline    Aborted by host               90%     10012         -
# 5  Short offline       Completed without error       00%     10010         -
# 6  Extended offline    Aborted by host               90%     10009         -

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.

gres ★
(01.08.09 12:33:15 MSK) автор топика

Ответ на: комментарий от gres 01.08.09 12:33:15 MSK

Кроме большого количества перемещенных секторов, ничего криминального, вроде, нет. Стоит позаботиться о бэкапе, а потом прогнать проверку поверхности на испорченные сектора.

~~gotf~~ ★
(01.08.09 12:42:43 MSK)

Ответ на: комментарий от gotf 01.08.09 12:42:43 MSK

Там итак ничего нет. Я же писал что после полной переустановки системы. До переустановки сообщения от утилиты не было, теперь вот появляется при каждом включении компа. Может дело в том что диск зашифрован и утилита не может адекватно находить ошибки на диске? Кстаки как прогнать проверку на испорченные сектора из под Федоры?

gres ★
(01.08.09 13:10:34 MSK) автор топика