Principal » Foro » Hardware » Otros dispositivos

posibilidad de dsico duro dañado

Publicado: 21 Octubre, 2011 - 23:03 posibilidad de dsico duro dañado

Tengo mi pc con problemas de repente se apaga o se pega, puede que el disco se haya dañado?
Hice lo siguiente:

# smartctl -l selftest -i /dev/sda
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11 family
Device Model:     ST3750630AS
Serial Number:    9QK23T3Q
Firmware Version: SD1A
User Capacity:    750,156,374,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Oct 21 18:52:55 2011 CLST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       60%     10553         655857
# 2  Short offline       Completed: read failure       90%     10529         141077877
# 3  Conveyance offline  Completed: read failure       90%     10525         141077780

Luego hice

# smartctl -a /dev/sda
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11 family
Device Model:     ST3750630AS
Serial Number:    9QK23T3Q
Firmware Version: SD1A
User Capacity:    750,156,374,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Oct 21 18:58:45 2011 CLST
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:      ( 118) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 634) 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: (   1) minutes.
Extended self-test routine
recommended polling time: ( 174) minutes.
Conveyance self-test routine
recommended polling time: (   2) minutes.
SCT capabilities:        (0x103b) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

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   084   078   006    Pre-fail  Always       -       39265691
  3 Spin_Up_Time            0x0003   098   090   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       852
  5 Reallocated_Sector_Ct   0x0033   043   043   036    Pre-fail  Always       -       1179
  7 Seek_Error_Rate         0x000f   070   060   030    Pre-fail  Always       -       30153678248
  9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       10553
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       2
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       852
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       410
188 Command_Timeout         0x0032   100   096   000    Old_age   Always       -       8590066708
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   051   044   045    Old_age   Always   In_the_past 49 (0 11 49 49)
194 Temperature_Celsius     0x0022   049   056   000    Old_age   Always       -       49 (0 15 0 0)
195 Hardware_ECC_Recovered  0x001a   031   020   000    Old_age   Always       -       39265691
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       868
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       868
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 939 (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 939 occurred at disk power-on lifetime: 10552 hours (439 days + 16 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 00      00:01:28.942  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      00:01:28.942  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:01:28.785  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 00      00:01:13.420  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      00:01:13.419  IDENTIFY DEVICE

Error 938 occurred at disk power-on lifetime: 10552 hours (439 days + 16 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      00:01:28.942  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:01:28.785  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 00      00:01:13.420  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      00:01:13.419  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:01:13.263  NOP [Abort queued commands]

Error 937 occurred at disk power-on lifetime: 10552 hours (439 days + 16 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 00      00:01:13.420  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      00:01:13.419  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:01:13.263  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      00:01:12.936  NOP [Abort queued commands]
  ec 00 00 00 00 00 a0 00      00:01:07.939  IDENTIFY DEVICE

Error 936 occurred at disk power-on lifetime: 10552 hours (439 days + 16 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      00:01:13.419  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:01:13.263  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      00:01:12.936  NOP [Abort queued commands]
  ec 00 00 00 00 00 a0 00      00:01:07.939  IDENTIFY DEVICE
  2f 00 01 10 00 00 a0 00      00:01:07.907  READ LOG EXT

Error 935 occurred at disk power-on lifetime: 10552 hours (439 days + 16 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      00:01:07.939  IDENTIFY DEVICE
  2f 00 01 10 00 00 a0 00      00:01:07.907  READ LOG EXT
  60 00 20 08 f0 62 43 00      00:01:04.458  READ FPDMA QUEUED
  60 00 08 00 f0 62 43 00      00:01:04.161  READ FPDMA QUEUED
  60 00 20 08 f0 22 43 00      00:01:04.159  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: read failure       60%     10553         655857
# 2  Short offline       Completed: read failure       90%     10529         141077877
# 3  Conveyance offline  Completed: read failure       90%     10525         141077780

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

Cualquier ayuda se agradece

Publicado: 22 Octubre, 2011 - 00:25 Re: posibilidad de dsico duro dañado #1
Citar

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Creo que esto aclara bastante, ¿no?

Sea lo que sea, es poco probable que se trate del disco duro.

Publicado: 22 Octubre, 2011 - 00:28 Re: posibilidad de dsico duro dañado #2

¿Controlaste la temperatura del/los micros ?

Publicado: 22 Octubre, 2011 - 01:21 Re: posibilidad de dsico duro dañado #3

estan bien las temperaturas, instale los gnome sensors y anda todo alrededor de 32º

Quizas sea la fuente de poder?

Publicado: 22 Octubre, 2011 - 09:33 Re: posibilidad de dsico duro dañado #4
sibur escribió:

Quizas sea la fuente de poder?

Tal vez, pero tendrás que verificar tensiones y/o probar con fuente de alimentación.

Saludos wink

Publicado: 22 Octubre, 2011 - 12:37 Re: posibilidad de dsico duro dañado #5
quilloquepasa escribió:
sibur escribió:

Quizas sea la fuente de poder?

Tal vez, pero tendrás que verificar tensiones y/o probar con fuente de alimentación.

Saludos wink

Si usas adaptador para la alimentación sata es muy probable que este dando, si no tienes un reemplazo puedes probar de intercambiarlo con el de la grabadora de dvd,