[OT] HELP! Problemi con disco?
Sto usando una debian testing e forse ho problemi con un disco.
Ovviamente non e` colpa di debian, ma se mi muore il disco perdo anche
tutti i dati compresa l'installazione di debian. E credo che nessuno
voglia la morte di una debian. :)
Quello che vorrei capire e` se il problema c'e` davvero oppure se e`
stato un caso oppure se e` un problema del controller o altro.
Ieri il pc e` stato spostato e quindi il problema potrebbe non essere
nel disco... lo so, la speranza e` l'ultima a morire... ma in questo
momento sto facendo il backup e non mi sta dando nessun errore. ^^;;;
Il pc si e` freezato ed ho dovuto riavviare. Al riavvio ho avuto
parecchi errori sul disco tipo questi:
Sep 30 13:25:29 Q kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Sep 30 13:25:29 Q kernel: ide1 at 0x170-0x177,0x376 on irq 15
Sep 30 13:25:29 Q kernel: hda: attached ide-disk driver.
Sep 30 13:25:29 Q kernel: hda: 398297088 sectors (203928 MB) w/8192KiB
Cache, CHS=24792/255/63, UDMA(100)
Sep 30 13:25:29 Q kernel: Partition check:
Sep 30 13:25:29 Q kernel: /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4
Sep 30 13:25:29 Q kernel: Journalled Block Device driver loaded
Sep 30 13:25:29 Q kernel: EXT3-fs: INFO: recovery required on readonly
filesystem.
Sep 30 13:25:29 Q kernel: EXT3-fs: write access will be enabled during
recovery.
Sep 30 13:25:29 Q kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 30 13:25:29 Q kernel: hda: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=887957, high=0, low=887957,sector=4256
Sep 30 13:25:29 Q kernel: end_request: I/O error, dev 03:03 (hda),
sector 4256
Sep 30 13:25:29 Q kernel: JBD: Failed to read block at offset 12
Sep 30 13:25:29 Q kernel: JBD: recovery failed
Sep 30 13:25:29 Q kernel: EXT3-fs: error loading journal.
Sep 30 13:25:29 Q kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 30 13:25:29 Q kernel: hda: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=887957, high=0, low=887957,sector=4264
Sep 30 13:25:29 Q kernel: end_request: I/O error, dev 03:03 (hda),
sector 4264
Sep 30 13:25:29 Q kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 30 13:25:29 Q kernel: hda: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=887957, high=0, low=887957,sector=4272
Sep 30 13:25:29 Q kernel: end_request: I/O error, dev 03:03 (hda),
sector 4272
Sep 30 13:25:29 Q kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 30 13:25:29 Q kernel: hda: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=887957, high=0, low=887957,sector=4280
Sep 30 13:25:29 Q kernel: end_request: I/O error, dev 03:03 (hda),
sector 4280
Sep 30 13:25:29 Q kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 30 13:25:29 Q kernel: hda: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=887957, high=0, low=887957,sector=4288
Sep 30 13:25:29 Q kernel: end_request: I/O error, dev 03:03 (hda),
sector 4288
Sep 30 13:25:29 Q kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Poi appena sono riuscito a riavviarlo correttamente ho installato e
lanciato lo smart:
$ /usr/sbin/smartctl -H /dev/hda
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
E qui sembra non avere problemi.
Poi pero` ho provato a dare un altro comando e questo sembra segnalare
degli errori. Lo smart non l'ho praticamente mai usato e quindi non
riesco a capire la gravita` della situazione.
$ /usr/sbin/smartctl --all /dev/hda
=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax 10 family
Device Model: Maxtor 6B200P0
Serial Number: B407ZH6H
Firmware Version: BAH41B10
User Capacity: 203,928,109,056 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Fri Sep 30 14:53:25 2005 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: (0x80) Offline data collection activity
was never started.
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: (1622) 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.
No General Purpose Logging
support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 82) 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
3 Spin_Up_Time 0x0027 207 201 063 Pre-fail Always
- 11583
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always
- 511
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always
- 1
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always
- 0
8 Seek_Time_Performance 0x0027 251 242 187 Pre-fail Always
- 32909
9 Power_On_Minutes 0x0032 244 244 000 Old_age Always
- 1090h+52m
10 Spin_Retry_Count 0x002b 253 249 157 Pre-fail Always
- 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always
- 552
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always
- 0
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always
- 0
194 Temperature_Celsius 0x0032 044 253 000 Old_age Always
- 31
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always
- 3948
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age
Offline - 1
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always
- 0
201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always
- 0
202 TA_Increase_Count 0x000a 253 252 000 Old_age Always
- 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always
- 0
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always
- 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always
- 0
207 Spin_High_Current 0x002a 253 249 000 Old_age Always
- 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always
- 0
209 Offline_Seek_Performnce 0x0024 239 239 000 Old_age
Offline - 177
210 Unknown_Attribute 0x0032 253 252 000 Old_age Always
- 0
211 Unknown_Attribute 0x0032 253 252 000 Old_age Always
- 0
212 Unknown_Attribute 0x0032 253 253 000 Old_age Always
- 0
SMART Error Log Version: 1
ATA Error Count: 50 (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 50 occurred at disk power-on lifetime: 3069 hours (127 days + 21
hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
38 4a 28 97 8c 0d e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e0 00 28 97 8c 0d e0 00 00:01:56.171 STANDBY IMMEDIATE
e0 00 08 8f 8c 0d e0 00 00:01:54.654 STANDBY IMMEDIATE
e0 00 10 87 8c 0d e0 00 00:01:53.155 STANDBY IMMEDIATE
e0 00 18 7f 8c 0d e0 00 00:01:51.664 STANDBY IMMEDIATE
e0 00 20 77 8c 0d e0 00 00:01:50.172 STANDBY IMMEDIATE
Error 49 occurred at disk power-on lifetime: 3069 hours (127 days + 21
hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
38 4a 08 8f 8c 0d e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e0 00 08 8f 8c 0d e0 00 00:01:54.654 STANDBY IMMEDIATE
e0 00 10 87 8c 0d e0 00 00:01:53.155 STANDBY IMMEDIATE
e0 00 18 7f 8c 0d e0 00 00:01:51.664 STANDBY IMMEDIATE
e0 00 20 77 8c 0d e0 00 00:01:50.172 STANDBY IMMEDIATE
e0 00 28 6f 8c 0d e0 00 00:01:48.672 STANDBY IMMEDIATE
Error 48 occurred at disk power-on lifetime: 3069 hours (127 days + 21
hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
38 4a 10 87 8c 0d e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e0 00 10 87 8c 0d e0 00 00:01:53.155 STANDBY IMMEDIATE
e0 00 18 7f 8c 0d e0 00 00:01:51.664 STANDBY IMMEDIATE
e0 00 20 77 8c 0d e0 00 00:01:50.172 STANDBY IMMEDIATE
e0 00 28 6f 8c 0d e0 00 00:01:48.672 STANDBY IMMEDIATE
e0 00 30 67 8c 0d e0 00 00:01:47.173 STANDBY IMMEDIATE
Error 47 occurred at disk power-on lifetime: 3069 hours (127 days + 21
hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
38 4a 18 7f 8c 0d e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e0 00 18 7f 8c 0d e0 00 00:01:51.664 STANDBY IMMEDIATE
e0 00 20 77 8c 0d e0 00 00:01:50.172 STANDBY IMMEDIATE
e0 00 28 6f 8c 0d e0 00 00:01:48.672 STANDBY IMMEDIATE
e0 00 30 67 8c 0d e0 00 00:01:47.173 STANDBY IMMEDIATE
e0 00 38 5f 8c 0d e0 00 00:01:45.673 STANDBY IMMEDIATE
Error 46 occurred at disk power-on lifetime: 3069 hours (127 days + 21
hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
38 4a 20 77 8c 0d e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e0 00 20 77 8c 0d e0 00 00:01:50.172 STANDBY IMMEDIATE
e0 00 28 6f 8c 0d e0 00 00:01:48.672 STANDBY IMMEDIATE
e0 00 30 67 8c 0d e0 00 00:01:47.173 STANDBY IMMEDIATE
e0 00 38 5f 8c 0d e0 00 00:01:45.673 STANDBY IMMEDIATE
e0 00 40 57 8c 0d e0 00 00:01:44.173 STANDBY IMMEDIATE
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
Il backup l'ho gia` avviato ma vorrei sapere se devo comprare un altro
disco oppure se mi posso fidare di questo. Grazie.
--
| Massimo ;-) -> http://maq.altervista.org | (o- POWERED |
|- BABYLON 5 -> http://babylon5.altervista.org | (/)_ BY LINUX |
|- STARGATE -> http://sg1screw.altervista.org | And the sky |
|- USSTRIBOLO -> http://usstribolo.altervista.org | full of stars |
Reply to: