Sziasztok!
A gépben az egyik winchesterre érdekes hibát jelez a smartmontools.
Időről időre jön egy e-mail a következővel:
The following warning/error was logged by the smartd daemon:
Device: /dev/sdd, ATA error count increased from 6 to 7
A syslog elég szűkszavú:
Aug 17 22:16:52 szerver smartd[3030]: Device: /dev/sdd, ATA error count increased from 6 to 7
Aug 17 22:16:52 szerver smartd[3030]: Sending warning via /usr/share/smartmontools/smartd-runner to ...
A smartctl -a /dev/sdd ezt írja:
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 ===
Device Model: WDC WD5001ABYS-01YNA0
Serial Number: WD-WCAS86300557
Firmware Version: 59.01D01
User Capacity: 500.107.862.016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Aug 17 23:00:59 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
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: (13200) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off 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.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 154) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
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 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0003 174 174 021 Pre-fail Always - 6283
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 37
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 11231
10 Spin_Retry_Count 0x0012 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0012 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 35
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 38
194 Temperature_Celsius 0x0022 099 093 000 Old_age Always - 51
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 0x0010 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 164 148 000 Old_age Offline - 2445
SMART Error Log Version: 1
ATA Error Count: 7 (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 7 occurred at disk power-on lifetime: 11230 hours (467 days + 22 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 a7 1b 0e 40
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 70 98 7f 1b 0e 2a 08 30d+00:37:32.866 READ FPDMA QUEUED
60 08 10 6f 87 0b 2a 08 30d+00:37:32.865 READ FPDMA QUEUED
60 f8 08 77 86 0b 2a 08 30d+00:37:32.848 READ FPDMA QUEUED
61 08 90 c7 67 54 29 08 30d+00:37:32.848 WRITE FPDMA QUEUED
61 08 88 9f 67 54 29 08 30d+00:37:32.848 WRITE FPDMA QUEUED
Error 6 occurred at disk power-on lifetime: 11108 hours (462 days + 20 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 a3 1b 0e 40
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 70 00 7f 1b 0e 2a 08 24d+23:01:42.529 READ FPDMA QUEUED
60 c0 00 df 8d 2e 2a 08 24d+23:01:42.516 READ FPDMA QUEUED
60 98 00 7f 0d 2a 2a 08 24d+23:01:42.495 READ FPDMA QUEUED
60 10 00 ef 79 2f 2a 08 24d+23:01:42.476 READ FPDMA QUEUED
60 08 00 07 78 26 2a 08 24d+23:01:42.461 READ FPDMA QUEUED
Error 5 occurred at disk power-on lifetime: 11108 hours (462 days + 20 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 1f a5 1b 0e 40
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 70 00 7f 1b 0e 2a 08 24d+22:52:02.581 READ FPDMA QUEUED
60 c0 00 df 8d 2e 2a 08 24d+22:52:02.568 READ FPDMA QUEUED
60 08 00 37 42 30 2a 08 24d+22:52:02.551 READ FPDMA QUEUED
60 68 00 17 0c 2a 2a 08 24d+22:52:02.550 READ FPDMA QUEUED
60 70 00 a7 0b 2a 2a 08 24d+22:52:02.538 READ FPDMA QUEUED
Error 4 occurred at disk power-on lifetime: 10633 hours (443 days + 1 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 3f 84 22 98 40
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 00 07 78 58 29 08 5d+03:03:00.722 WRITE FPDMA QUEUED
61 10 d0 57 77 58 29 08 5d+03:03:00.722 WRITE FPDMA QUEUED
61 08 e0 47 77 58 29 08 5d+03:03:00.722 WRITE FPDMA QUEUED
61 08 c8 4f 76 58 29 08 5d+03:03:00.712 WRITE FPDMA QUEUED
61 08 f0 97 75 58 29 08 5d+03:03:00.711 WRITE FPDMA QUEUED
Error 3 occurred at disk power-on lifetime: 10596 hours (441 days + 12 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 a6 1b 0e 40
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 70 00 7f 1b 0e 2a 08 3d+13:40:21.231 READ FPDMA QUEUED
60 c0 00 df 8d 2e 2a 08 3d+13:40:21.219 READ FPDMA QUEUED
60 98 00 7f 0d 2a 2a 08 3d+13:40:21.206 READ FPDMA QUEUED
60 10 00 cf a5 12 2a 08 3d+13:40:21.185 READ FPDMA QUEUED
60 18 00 67 de 0a 2a 08 3d+13:40:21.171 READ FPDMA QUEUED
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% 11210 -
# 2 Short offline Completed without error 00% 11186 -
# 3 Extended offline Completed without error 00% 11166 -
# 4 Short offline Completed without error 00% 11162 -
# 5 Short offline Completed without error 00% 11138 -
# 6 Short offline Completed without error 00% 11114 -
# 7 Short offline Completed without error 00% 11090 -
# 8 Short offline Completed without error 00% 11066 -
# 9 Short offline Completed without error 00% 11042 -
#10 Short offline Completed without error 00% 11018 -
#11 Extended offline Completed without error 00% 10998 -
#12 Short offline Completed without error 00% 10994 -
#13 Short offline Completed without error 00% 10970 -
#14 Short offline Completed without error 00% 10946 -
#15 Short offline Completed without error 00% 10922 -
#16 Short offline Completed without error 00% 10898 -
#17 Short offline Completed without error 00% 10874 -
#18 Short offline Completed without error 00% 10851 -
#19 Extended offline Completed without error 00% 10831 -
#20 Short offline Completed without error 00% 10827 -
#21 Short offline Completed without error 00% 10803 -
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.
Szóval látszólag nincs bad vagy pending sector. De akkor mi lehet a hiba? Mit jelent a READ FPDMA QUEUED üzenet?
- 2098 megtekintés
Hozzászólások
Szemelyes velemenyem szerint a SMART adatokat nem kell mindig olyan veresen komolyan venni. Amennyire en tudom, a SMART kulonfele adatokkal probaljak elorejelezni a merevlemez elorelathato elettartamat, az esetleges hibara utalo parameterek valtozasaibol kovetkezteteseket probalnak levonni arra vonatkozoan hogy ha ilyen utemben fog valtozni adott ertek akkor ennyi/annyi ido utan fogja magat teljesen megadni az eszkoz. De ezek az adatok annyira szerteagazoak es specik hogy szokszor eza elorejelzes biza befuccsol...
Szoval a cucc siman fog menni tovabb, de szamitani lehet ra hogy egyszer majd lesz baja - kb mint barmilyen desktop HDD vel :))
Szemely szerint en hasznalnam tovabb a hdd-t, esetleg a nagyon nagyon nagyon kritikus adatokrol keszitenek egy biztonsagi mentest. (ami egyebkent sem art sosem)
- A hozzászóláshoz be kell jelentkezni
Ezzel egyet értek.
Nekem van néhány olyan vinyóm, ami rackben működik. És szerintem a rack csatlakozások nem mindig 100%-osak. Biztosan mindenki járt már úgy, hogy bedugta a fiókot és a gép megakadt a HDD felimerése közben. A gépet kikapcsolva a fiókot ki-, majd visszahelyezve meg szépen ment minden. Én pont a napokban jártam így és a viszonyla új HDD-n keletkezett egy timeout hiba. (most nincs előttem de talán a Spin_Up_Time lett 6.xxx) ezért már jelez, hogy bibi van.
Amúgy meg semmi hibát sem tapasztalok rajta.
De hasonló okból (esetleg rackben túlmelegedés miatt) reallokált sectorok is növekednek.
--
не закурить! (Ne gyújts rá!) не куриться! (Ne dohányozz! Ne füstölögj!)
- A hozzászóláshoz be kell jelentkezni