LINUX.ORG.RU

Сбойные блоки


0

0

Сейчас попробую описать свою проблему.Мне понадобилось восстановить удаленный файл.Я,конечно,полез в гугл.И нашел статью на хабре про утилиту scalpel.Установил её.Запустил.Но окончания работы утилиты не дождался,а завершил,закрыв консоль.Посерфил инет.И пошел спать.На следующий день при входе в систему Palimsest выдал,что «На диске много сбойных блоков».Подробности на скриншоте.Откуда вдруг взялось МНОГО битых блоков?Что делать? P.S. ext 4/Ubuntu 9.10

сделал скан винта с помощью mdd-http://img683.imageshack.us/img683/8237/005nz.jpg + log

самое интересное,что я сделал проверку командой badblocks и она ничего не нашла



Последнее исправление: gerstal (всего исправлений: 1)

вот результат команды smartctl --all /dev/sda

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: Seagate Barracuda 7200.10 family
Device Model: ST3320620A
Serial Number: 9QF7B79H
Firmware Version: 3.AAF
User Capacity: 320 072 933 376 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 22 13:56:42 2010 SAMT
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: ( 115) 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 114 100 006 Pre-fail Always - 62869376
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1736
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 167812019
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 4160
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1700
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 450
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 060 055 045 Old_age Always - 40 (Lifetime Min/Max 26/42)
194 Temperature_Celsius 0x0022 040 045 000 Old_age Always - 40 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 068 060 000 Old_age Always - 116834578
197 Current_Pending_Sector 0x0012 001 001 000 Old_age Always - 4294967295
198 Offline_Uncorrectable 0x0010 001 001 000 Old_age Offline - 4294967295
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: 468 (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 468 occurred at disk power-on lifetime: 2426 hours (101 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
 — -- — -- — -- --
40 51 01 2d 09 29 e0 Error: UNC at LBA = 0x0029092d = 2689325

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 — -- — -- — -- — -- ---------------- --------------------
42 00 01 2d 09 29 e0 00 00:26:38.852 READ VERIFY SECTOR(S) EXT
42 00 01 2c 09 29 e0 00 00:26:38.844 READ VERIFY SECTOR(S) EXT
42 00 02 2e 09 29 e0 00 00:26:38.827 READ VERIFY SECTOR(S) EXT
42 00 02 2c 09 29 e0 00 00:26:37.275 READ VERIFY SECTOR(S) EXT
42 00 04 2c 09 29 e0 00 00:26:37.258 READ VERIFY SECTOR(S) EXT

Error 467 occurred at disk power-on lifetime: 2426 hours (101 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
 — -- — -- — -- --
40 51 01 2d 09 29 e0 Error: UNC at LBA = 0x0029092d = 2689325

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 — -- — -- — -- — -- ---------------- --------------------
42 00 02 2c 09 29 e0 00 00:26:38.852 READ VERIFY SECTOR(S) EXT
42 00 04 2c 09 29 e0 00 00:26:38.844 READ VERIFY SECTOR(S) EXT
42 00 04 28 09 29 e0 00 00:26:38.827 READ VERIFY SECTOR(S) EXT
42 00 08 30 09 29 e0 00 00:26:37.275 READ VERIFY SECTOR(S) EXT
42 00 08 28 09 29 e0 00 00:26:37.258 READ VERIFY SECTOR(S) EXT

Error 466 occurred at disk power-on lifetime: 2426 hours (101 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
 — -- — -- — -- --
40 51 03 2d 09 29 e0 Error: UNC at LBA = 0x0029092d = 2689325

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 — -- — -- — -- — -- ---------------- --------------------
42 00 04 2c 09 29 e0 00 00:26:38.852 READ VERIFY SECTOR(S) EXT
42 00 04 28 09 29 e0 00 00:26:38.844 READ VERIFY SECTOR(S) EXT
42 00 08 30 09 29 e0 00 00:26:38.827 READ VERIFY SECTOR(S) EXT
42 00 08 28 09 29 e0 00 00:26:37.275 READ VERIFY SECTOR(S) EXT
42 00 10 38 09 29 e0 00 00:26:37.258 READ VERIFY SECTOR(S) EXT

gerstal
() автор топика

Error 465 occurred at disk power-on lifetime: 2426 hours (101 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  — -- — -- — -- -- 40 51 03 2d 09 29 e0 Error: UNC at LBA = 0x0029092d = 2689325

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name  — -- — -- — -- — -- ---------------- -------------------- 42 00 08 28 09 29 e0 00 00:26:31.005 READ VERIFY SECTOR(S) EXT 42 00 10 38 09 29 e0 00 00:26:31.004 READ VERIFY SECTOR(S) EXT 42 00 10 28 09 29 e0 00 00:26:30.984 READ VERIFY SECTOR(S) EXT 42 00 20 48 09 29 e0 00 00:26:37.275 READ VERIFY SECTOR(S) EXT 42 00 20 28 09 29 e0 00 00:26:37.258 READ VERIFY SECTOR(S) EXT

Error 464 occurred at disk power-on lifetime: 2426 hours (101 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  — -- — -- — -- -- 40 51 0b 2d 09 29 e0 Error: UNC at LBA = 0x0029092d = 2689325

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name  — -- — -- — -- — -- ---------------- -------------------- 42 00 10 28 09 29 e0 00 00:26:31.005 READ VERIFY SECTOR(S) EXT 42 00 20 48 09 29 e0 00 00:26:31.004 READ VERIFY SECTOR(S) EXT 42 00 20 28 09 29 e0 00 00:26:30.984 READ VERIFY SECTOR(S) EXT 42 00 40 28 09 29 e0 00 00:26:29.441 READ VERIFY SECTOR(S) EXT 42 00 40 e8 08 29 e0 00 00:26:29.438 READ VERIFY SECTOR(S) EXT

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% 4160 - # 2 Short offline Completed without error 00% 4151 - # 3 Short offline Completed without error 00% 4151 - # 4 Short offline Aborted by host 80% 4150 - # 5 Short offline Completed without error 00% 3684 -

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.

gerstal
() автор топика
Ответ на: комментарий от gerstal

проверь мулек разьем он скорее всяго отходить

enep ★★★★★
()

Так мне копить деньги на новый диск? Я так понимаю,что current pending count(или по-русски-количество текущих ожидающих секторов)-это потенциальные bad-сектора.У меня на диске такой один.Но почему Palimpsest «кричит»,что их много?

gerstal
() автор топика
Ответ на: комментарий от gerstal

Спасибо, так гораздо удобнее.
Кстати, у Вас на скриншоте написано, что сбойных блоков = -1. Это весьма странно.

AITap ★★★★★
()
Ответ на: комментарий от gerstal

Вероятно, что-то с контроллером. Я не знаю, что могло заставить его считать, что сбойных блоков меньше нуля. Сюда нужны люди, разбирающиеся в предмете! Вы уже забекапили важные данные? Попробуйте ещё спросить на канале #linux RusNet'а.

AITap ★★★★★
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.