è da un paio di giorni che ogni 10-12 ore il server va down
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.10.23-xxxx-grs-ipv6-64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA DT01ACA100
Serial Number: 13OYNJMPS
LU WWN Device Id: 5 000039 ff2e9aadc
Firmware Version: MS2OA750
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu Mar 6 21:39:53 2014 CET
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: ( 33) The self-test routine was interrupted
by the host with a hard or soft reset.
Total time to complete Offline
data collection: ( 7847) 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: ( 131) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control 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 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 140 140 054 Pre-fail Offline - 76
3 Spin_Up_Time 0x0007 125 125 024 Pre-fail Always - 183 (Average 185)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 15
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 118 118 020 Pre-fail Offline - 33
9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 8092
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 15
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 16
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 16
194 Temperature_Celsius 0x0002 142 142 000 Old_age Always - 42 (Min/Max 16/63)
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 - 2
SMART Error Log Version: 1
ATA Error Count: 2
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 2 occurred at disk power-on lifetime: 7764 hours (323 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
-- -- -- -- -- -- --
84 51 11 5f e3 c7 0b Error: ICRC, ABRT at LBA = 0x0bc7e35f = 197649247
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 40 00 30 e3 c7 40 00 1d+10:40:10.264 READ FPDMA QUEUED
60 20 00 10 e3 c7 40 00 1d+10:40:10.264 READ FPDMA QUEUED
60 08 00 48 2f 4d 40 00 1d+10:40:10.252 READ FPDMA QUEUED
60 08 00 58 0b 35 40 00 1d+10:40:10.223 READ FPDMA QUEUED
60 e0 00 30 e2 c7 40 00 1d+10:40:10.181 READ FPDMA QUEUED
Error 1 occurred at disk power-on lifetime: 7764 hours (323 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
-- -- -- -- -- -- --
84 51 21 47 f2 78 0b Error: ICRC, ABRT at LBA = 0x0b78f247 = 192475719
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 80 00 e8 f1 78 40 00 1d+10:25:59.363 READ FPDMA QUEUED
60 08 08 e0 f1 78 40 00 1d+10:25:59.363 READ FPDMA QUEUED
60 40 00 a0 f1 78 40 00 1d+10:25:59.363 READ FPDMA QUEUED
60 20 00 80 f1 78 40 00 1d+10:25:59.357 READ FPDMA QUEUED
60 20 00 60 f1 78 40 00 1d+10:25:59.356 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Interrupted (host reset) 10% 8066 -
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.
non essendo praticissimo, non so se il problema sia derivato da questi due errori, fatto sta che ogni volta che cerco di trasferire su backup i file
puntualmente il server va in down e corrompe il backup...
sto provando adesso a trasferire il backup su un altro server(sempre kimsufi) e non sul server di backup(quello da 100gb) sperando che vada a buon fine, comunque mi domandavo in caso di sostituzione di un hard disk è possibile eventualmente richiedere un backup e se si ha un costo?
non vorrei perdere il materiale per questo motivo, purtroppo questo susseguirsi di eventi ha corrotto il backup(quello su server di backup da 100gb)
ps: il backup è di 82gb il trasferimento verso l'altro server avverrà entro circa 5 ore (salvo altri down)
grazie per le eventuali risposte
