-
1. Data: 2009-07-22 15:45:59
Temat: dysk twardy - Palimpsest Disk Utility 0.3 mówi o błędzie
Od: Grzegorz Szymczykiewicz <g...@w...pl>
Po zainstalowaniu nowej wersji fedory (11), za każdym razem po
uruchomieniu systemu dostaję komunikat o błędzie dysku(z programu
Palimpsest Disk Utility 0.3). w detalach przy jednym parametrze jest
FAILING
1 Read Error Rate current: 200 worst: 1 threshold: 51 value: 0 status:
FAILING type: pre-fail updates: online
Reszta parametrów jest ok. Co oznacza ten błąd? Czy powinienem się
martwić i szykować kasę na nowy dysk? Czy to jeszcze nic strasznego?
Załączam poniżej wynik programu smartctl --all /dev/sdb. Wyświetla on
kilka informacji o błędach, czy dobrze rozumiem że wystąpiły one dawno
temu (at disk power-on lifetime: 840 hours)?
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: Western Digital Caviar family
Device Model: WDC WD800BB-00DKA0
Serial Number: WD-WCAHL4001472
Firmware Version: 77.07W77
User Capacity: 80,023,182,848 bytes
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: Wed Jul 22 17:37:58 2009 CEST
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
See vendor-specific Attribute list for marginal Attributes.
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: (2475) seconds.
Offline data collection
capabilities: (0x79) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 38) minutes.
Conveyance self-test routine
recommended polling time: ( 5) 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 0x000b 200 001 051 Pre-fail
Always In_the_past 0
3 Spin_Up_Time 0x0007 099 089 021 Pre-fail
Always - 1575
4 Start_Stop_Count 0x0032 092 092 040 Old_age
Always - 8960
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000b 100 253 051 Pre-fail
Always - 0
9 Power_On_Hours 0x0032 079 079 000 Old_age
Always - 15335
10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail
Always - 0
11 Calibration_Retry_Count 0x0013 100 100 051 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 092 092 000 Old_age
Always - 8785
194 Temperature_Celsius 0x0022 103 253 000 Old_age Always
- 40
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always
- 0
197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always
- 0
198 Offline_Uncorrectable 0x0012 200 200 000 Old_age Always
- 0
199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always
- 0
200 Multi_Zone_Error_Rate 0x0009 200 085 051 Pre-fail
Offline - 0
SMART Error Log Version: 1
ATA Error Count: 47457 (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 47457 occurred at disk power-on lifetime: 840 hours (35 days + 0
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 40 8a 96 81 e5 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
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 c8 00 00 40 00 00 00:13:57.100 NOP [Abort queued commands]
01 00 c6 00 00 16 bd 00 00:13:57.100 [RESERVED]
00 00 ca 00 00 08 00 00 00:13:57.100 NOP [Abort queued commands]
00 00 c8 00 00 08 00 00 00:13:57.100 NOP [Abort queued commands]
05 00 81 00 00 4f 96 00 00:13:57.100 [RESERVED]
Error 47456 occurred at disk power-on lifetime: 840 hours (35 days + 0
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 40 8a 96 81 e5 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
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 c8 00 00 40 00 00 00:13:55.100 NOP [Abort queued commands]
01 00 c6 00 00 d6 bf 00 00:13:55.100 [RESERVED]
00 00 ca 00 00 08 00 00 00:13:55.100 NOP [Abort queued commands]
00 00 00 00 00 00 00 00 00:13:55.100 NOP [Abort queued commands]
00 00 ca 00 00 08 00 00 00:13:55.100 NOP [Abort queued commands]
Error 47455 occurred at disk power-on lifetime: 840 hours (35 days + 0
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 40 8a 96 81 e5 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
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 c8 00 00 40 00 00 00:13:53.200 NOP [Abort queued commands]
00 00 c8 00 00 20 00 00 00:13:53.200 NOP [Abort queued commands]
00 00 60 00 00 8f 7b 00 00:13:53.200 NOP [Abort queued commands]
00 00 ca 00 00 08 00 00 00:13:53.200 NOP [Abort queued commands]
05 00 81 00 00 4f 96 00 00:13:53.200 [RESERVED]
Error 47454 occurred at disk power-on lifetime: 840 hours (35 days + 0
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 40 8a 96 81 e5 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
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 c8 00 00 40 00 00 00:13:51.150 NOP [Abort queued commands]
01 00 c6 00 00 f6 bc 00 00:13:51.150 [RESERVED]
00 00 ca 00 00 08 00 00 00:13:51.150 NOP [Abort queued commands]
00 00 c8 00 00 01 00 00 00:13:51.150 NOP [Abort queued commands]
07 00 94 00 00 bf 4b 00 00:13:51.150 [RESERVED]
Error 47453 occurred at disk power-on lifetime: 840 hours (35 days + 0
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 40 8a 96 81 e5 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
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 c8 00 00 40 00 00 00:13:49.200 NOP [Abort queued commands]
01 00 c6 00 00 46 bf 00 00:13:49.200 [RESERVED]
00 00 ca 00 00 10 00 00 00:13:49.200 NOP [Abort queued commands]
00 00 00 00 00 d7 4d 00 00:13:49.200 NOP [Abort queued commands]
00 00 c8 00 00 01 00 00 00:13:49.200 NOP [Abort queued commands]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 41
-
# 2 Short offline Completed without error 00% 41
-
# 3 Conveyance offline Completed without error 00% 77
-
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.
--
Pozdrawiam Grzegorz
-
2. Data: 2009-07-26 12:05:34
Temat: Re: dysk twardy - Palimpsest Disk Utility 0.3 mówi o błędzie
Od: Radosław Sokół <r...@m...com.pl>
W dniu 22.07.2009 17:45, Grzegorz Szymczykiewicz pisze:
> 1 Read Error Rate current: 200 worst: 1 threshold: 51 value: 0 status:
> FAILING type: pre-fail updates: online
>
> Reszta parametrów jest ok. Co oznacza ten błąd? Czy powinienem się
> martwić i szykować kasę na nowy dysk? Czy to jeszcze nic strasznego?
Oznacza, że w jakimś momencie pracy dysku wystąpiło sporo
błędów odczytu. Trudno dociekać przyczyny, mogło to być na-
trafienie przez dysk na uszkodzony obszar (wyłączony potem
z użycia). Wskaźnik jednak wrócił do normalnej wartości,
więc dysk nie jest "umierający". Warto na pewno poobserwo-
wać, czy ta wartość znowu nie będzie spadać (im mniej, tym
gorzej) i jak zwykle warto mieć kopię zapasową danych, ale
nie ma raczej powodu do paniki.
--
|"""""""""""""""""""""""""""""""""""""""""""""""""""
"""""""|
| Radosław Sokół | http://www.grush.one.pl/ |
| | Politechnika Śląska |
\................... Microsoft MVP ......................../
-
3. Data: 2009-07-27 10:41:08
Temat: Re: dysk twardy - Palimpsest Disk Utility 0.3 mówi o błędzie
Od: Grzegorz Szymczykiewicz <g...@w...pl>
W dniu 26.07.2009 14:05, Radosław Sokół pisze:
> Oznacza, że w jakimś momencie pracy dysku wystąpiło sporo
> błędów odczytu. Trudno dociekać przyczyny, mogło to być na-
> trafienie przez dysk na uszkodzony obszar (wyłączony potem
> z użycia). Wskaźnik jednak wrócił do normalnej wartości,
> więc dysk nie jest "umierający". Warto na pewno poobserwo-
> wać, czy ta wartość znowu nie będzie spadać (im mniej, tym
> gorzej) i jak zwykle warto mieć kopię zapasową danych, ale
> nie ma raczej powodu do paniki.
Dzięki za pomoc:) czegoś takiego się spodziewałem, ale nie byłem pewien.
--
Pozdrawiam
Grzesiek