crash frequenti,forse problema hardware?

Riconoscimento, installazione e configurazione delle periferiche.
milus
Prode Principiante
Messaggi: 50
Iscrizione: martedì 19 maggio 2009, 16:07

crash frequenti,forse problema hardware?

Messaggio da milus »

Salve a tutti,
da quando ho installato ubuntu si sono verificati troppo spesso dei crash di sistema,non legati mi pare all'utilizzo di un particolare programma,siccome i crash causano sempre problemi gravi al riavvio,nel senso di danneggiamenti vari al file system,che con alterne fortune riesco a mettere a posto con l'fsck,ho pensato anche potrebbe trattarsi di un problema hardware.
Ieri dopo un crash ho provato a riavviare da vari live cd e non funzionavano nemmeno quelli!
Alla fine è partito puppylinux grazie al quale con fsck son riuscito a far ripartire il pc.
Ho pensato quindi a blocchi dovui all'hd(anche se non ha manco un anno!)e da live cd di ubuntu prima,e da puppy poi,ho lanciato il comando badblocks...ma si blocca sempre! devo resettare,e riavviare..
ho provato a guardare in sistema<amministrazione<visualizzatore regitro..ma in effetti non so dove guardare.
Prima di cambiare so,o cambiare pc! perchè un altro eide mi sa che nn mi conviene comprarlo,mi piacerebbe sapere di che morte sto morendo..
spero mi possiate aiutare
grazie

ps:questa è una parte del log di smartctl -a che mi riporta alcuni errori

Codice: Seleziona tutto

SMART Error Log Version: 1
ATA Error Count: 54 (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 54 occurred at disk power-on lifetime: 1510 hours (62 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 00 14 7b fd e7  Error: UNC at LBA = 0x07fd7b14 = 134052628

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 11 7b fd e7 00      00:13:34.227  READ DMA
  27 00 00 00 00 00 e0 00      00:13:34.158  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 02      00:13:34.141  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 02      00:13:34.127  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:34.074  READ NATIVE MAX ADDRESS EXT

Error 53 occurred at disk power-on lifetime: 1510 hours (62 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 00 14 7b fd e7  Error: UNC at LBA = 0x07fd7b14 = 134052628

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 11 7b fd e7 00      00:13:34.227  READ DMA
  27 00 00 00 00 00 e0 00      00:13:34.158  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 02      00:13:34.141  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 02      00:13:34.127  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:34.074  READ NATIVE MAX ADDRESS EXT

Error 52 occurred at disk power-on lifetime: 1510 hours (62 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 00 14 7b fd e7  Error: UNC at LBA = 0x07fd7b14 = 134052628

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 11 7b fd e7 00      00:13:29.872  READ DMA
  27 00 00 00 00 00 e0 00      00:13:29.819  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 02      00:13:29.814  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 02      00:13:27.878  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:27.810  READ NATIVE MAX ADDRESS EXT

Error 51 occurred at disk power-on lifetime: 1510 hours (62 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 00 14 7b fd e7  Error: UNC at LBA = 0x07fd7b14 = 134052628

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 11 7b fd e7 00      00:13:29.872  READ DMA
  27 00 00 00 00 00 e0 00      00:13:29.819  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 02      00:13:29.814  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 02      00:13:27.878  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:27.810  READ NATIVE MAX ADDRESS EXT

Error 50 occurred at disk power-on lifetime: 1510 hours (62 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 00 14 7b fd e7  Error: UNC at LBA = 0x07fd7b14 = 134052628

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 11 7b fd e7 00      00:13:25.684  READ DMA
  27 00 00 00 00 00 e0 00      00:13:25.684  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 02      00:13:25.684  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 02      00:13:27.878  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:13:27.810  READ NATIVE MAX ADDRESS EXT
Ultima modifica di milus il martedì 30 giugno 2009, 11:12, modificato 1 volta in totale.
milus
Prode Principiante
Messaggi: 50
Iscrizione: martedì 19 maggio 2009, 16:07

Re: crash frequenti,forse problema hardware?

Messaggio da milus »

ennesimo crash,questa volta avevo lanciato da terminale

Codice: Seleziona tutto

sudo smartctl -t long /dev/sda
il controllo è partito e dopo una decina di minuti freeze totale...
adesso il kern.log all'ultima riga mi dice:

Codice: Seleziona tutto

Jun 30 12:05:13 giancarlo-desktop kernel: [   68.175655] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 30 12:05:39 giancarlo-desktop kernel: [   95.403578] ondemand governor failed, too long transition latency of HW, fallback to performance governor
mentre il sys.log

Codice: Seleziona tutto

Jun 30 12:05:39 giancarlo-desktop kernel: [   95.403578] ondemand governor failed, too long transition latency of HW, fallback to performance governor
Jun 30 12:10:01 giancarlo-desktop /USR/SBIN/CRON[3700]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
non so più che fare  >:(
Scrivi risposta

Ritorna a “Driver e periferiche”

Chi c’è in linea

Visualizzano questa sezione: 0 utenti iscritti e 5 ospiti