Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

kernel panic dopo ultimo aggiornamento

Forum italiano degli utenti Mepis
Message
Author
max_tre2000
Forum Novice
Forum  Novice
Posts: 35
Joined: Fri Mar 31, 2017 2:43 am

Re: kernel panic dopo ultimo aggiornamento

#51 Post by max_tre2000 » Sun Oct 07, 2018 4:32 pm

altre info sempre da Gsmartcontrol
Screenshot-1.png
ed il log errori

Code: Select all

Complete error log:

SMART Error Log Version: 1
ATA Error Count: 184 (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 184 occurred at disk power-on lifetime: 33908 hours (1412 days + 20 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
  -- -- -- -- -- -- --
  84 51 00 90 21 6e ee  Error: ICRC, ABRT at LBA = 0x0e6e2190 = 242098576

  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 00 90 21 6e ee 00      00:01:08.875  READ DMA
  c8 00 08 68 6b 1a e6 00      00:00:38.625  READ DMA
  c8 00 e0 90 af 71 ed 00      00:00:38.625  READ DMA
  ef 05 fe 00 00 00 40 00      00:00:38.437  SET FEATURES [Enable APM]
  c8 00 08 60 6b 1a e6 00      00:00:38.437  READ DMA

Error 183 occurred at disk power-on lifetime: 33748 hours (1406 days + 4 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
  -- -- -- -- -- -- --
  84 51 90 e0 63 bd e9  Error: ICRC, ABRT 144 sectors at LBA = 0x09bd63e0 = 163406816

  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 90 e0 63 bd e9 00      04:12:09.250  READ DMA
  ef 05 fe 00 00 00 40 00      04:11:38.187  SET FEATURES [Enable APM]
  c8 00 00 d0 62 bd e9 00      04:11:38.187  READ DMA
  c8 00 08 f8 b0 b3 e9 00      04:11:38.125  READ DMA
  c8 00 08 f0 b0 b3 e9 00      04:11:38.125  READ DMA

Error 182 occurred at disk power-on lifetime: 33748 hours (1406 days + 4 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
  -- -- -- -- -- -- --
  84 51 88 00 21 6e ee  Error: ICRC, ABRT 136 sectors at LBA = 0x0e6e2100 = 242098432

  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 88 00 21 6e ee 00      04:11:05.187  READ DMA
  c8 00 98 00 23 02 ea 00      04:10:34.250  READ DMA
  ef 05 fe 00 00 00 40 00      04:10:34.062  SET FEATURES [Enable APM]
  c8 00 88 78 20 6e ee 00      04:10:34.062  READ DMA
  c8 00 20 18 b2 1f ee 00      04:10:34.062  READ DMA

Error 181 occurred at disk power-on lifetime: 33731 hours (1405 days + 11 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
  -- -- -- -- -- -- --
  84 51 40 58 7b b7 e9  Error: ICRC, ABRT 64 sectors at LBA = 0x09b77b58 = 163019608

  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 40 58 7b b7 e9 00      00:01:11.500  READ DMA
  c8 00 88 f8 e4 e5 ee 00      00:00:41.312  READ DMA
  ef 05 fe 00 00 00 40 00      00:00:41.125  SET FEATURES [Enable APM]
  c8 00 20 38 7b b7 e9 00      00:00:41.125  READ DMA
  c8 00 38 40 a0 f2 e7 00      00:00:41.062  READ DMA

Error 180 occurred at disk power-on lifetime: 33483 hours (1395 days + 3 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
  -- -- -- -- -- -- --
  84 51 f0 48 1d f7 ee  Error: ICRC, ABRT 240 sectors at LBA = 0x0ef71d48 = 251075912

  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 f0 48 1d f7 ee 00      00:01:13.187  READ DMA
  ef 05 fe 00 00 00 40 00      00:00:42.250  SET FEATURES [Enable APM]
  c8 00 08 58 6b 1a e6 00      00:00:42.250  READ DMA
  c8 00 08 f8 b5 33 ea 00      00:00:42.250  READ DMA
  c8 00 f8 08 a2 f2 e9 00      00:00:42.250  READ DMA
You do not have the required permissions to view the files attached to this post.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: kernel panic dopo ultimo aggiornamento

#52 Post by fehlix » Sun Oct 07, 2018 4:35 pm

max_tre2000 wrote:
Sun Oct 07, 2018 4:28 pm
Trovata, ecco il log
Screenshot.png
Che cosa è la visualizzazione del log degli errori. E mostra gli atttributes.
33955 h Lifetime = End Of Life
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

max_tre2000
Forum Novice
Forum  Novice
Posts: 35
Joined: Fri Mar 31, 2017 2:43 am

Re: kernel panic dopo ultimo aggiornamento

#53 Post by max_tre2000 » Sun Oct 07, 2018 4:38 pm

attributes
Screenshot-3.png
You do not have the required permissions to view the files attached to this post.

max_tre2000
Forum Novice
Forum  Novice
Posts: 35
Joined: Fri Mar 31, 2017 2:43 am

Re: kernel panic dopo ultimo aggiornamento

#54 Post by max_tre2000 » Sun Oct 07, 2018 4:41 pm

error log e' da questa finestra
Screenshot-4.png
You do not have the required permissions to view the files attached to this post.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: kernel panic dopo ultimo aggiornamento

#55 Post by fehlix » Sun Oct 07, 2018 4:42 pm

max_tre2000 wrote:
Sun Oct 07, 2018 4:32 pm
altre info sempre da Gsmartcontrol
Screenshot-1.png
Prendi un HD/SD/USB esterno e prova a fare il backup il più possibile. E vi comprate una nuova unità SSD. :eek:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

max_tre2000
Forum Novice
Forum  Novice
Posts: 35
Joined: Fri Mar 31, 2017 2:43 am

Re: kernel panic dopo ultimo aggiornamento

#56 Post by max_tre2000 » Sun Oct 07, 2018 4:47 pm

E' cosi' grave la situazione del disco?
Unita' SSD? e come la metto su questo vecchio pc? monta ATA
E se provo a formattarlo, ovviamente dopo aver fatto un bel backup di tutto, e reinstallo tutto?

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: kernel panic dopo ultimo aggiornamento

#57 Post by fehlix » Sun Oct 07, 2018 5:05 pm

max_tre2000 wrote:
Sun Oct 07, 2018 4:47 pm
E' cosi' grave la situazione del disco?
Unita' SSD? e come la metto su questo vecchio pc? monta ATA
E se provo a formattarlo, ovviamente dopo aver fatto un bel backup di tutto, e reinstallo tutto?
Non scrivere di più sull'errore HD.CRC. :mad:
=>> PATA/IDE SSD
o
=>> PATA/IDE -> SATA adapter + SSD
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

max_tre2000
Forum Novice
Forum  Novice
Posts: 35
Joined: Fri Mar 31, 2017 2:43 am

Re: kernel panic dopo ultimo aggiornamento

#58 Post by max_tre2000 » Sun Oct 07, 2018 5:13 pm

Il problema e' che gli adattori sicuramente non vanno bene, il disco che c'e' ora si mette dentro tramite una slitta su cui [ fissato, e non ci sarebbe spazio.

max_tre2000
Forum Novice
Forum  Novice
Posts: 35
Joined: Fri Mar 31, 2017 2:43 am

Re: kernel panic dopo ultimo aggiornamento

#59 Post by max_tre2000 » Sun Oct 07, 2018 5:20 pm

Ho detto una stupidaggine, se ho capito bene esistono ssd con gli stessi attacchi del mio ATA?
Tipo questo?
pata_ssd.jpg
You do not have the required permissions to view the files attached to this post.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: kernel panic dopo ultimo aggiornamento

#60 Post by fehlix » Sun Oct 07, 2018 5:22 pm

max_tre2000 wrote:
Sun Oct 07, 2018 5:13 pm
Il problema e' che gli adattori sicuramente non vanno bene, il disco che c'e' ora si mette dentro tramite una slitta su cui [ fissato, e non ci sarebbe spazio.
Guarda semplicemente volte, ad esempio con Amazon e poi si vede cosa c'è. Ricerca per "PATA/IDE SSD".
E date anche un'occhiata ai salvataggi.....
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Post Reply

Return to “Forum Italiano”