Imelik väljalülitumine

kessu · Postitus Postitas **kessu** » 17.05.2015, 22:40

Millegipärast on täna arvuti mitu korda teinud graafilisest liidesest väljalülituse ja läinud üle imelikule "konsooliteatele", millest mina midagi aru ei oska saada. Äkki keegi saab sellest aru.

akbgf · Postitus Postitas **akbgf** » 17.05.2015, 23:31

kessu kirjutas:Millegipärast on täna arvuti mitu korda teinud graafilisest liidesest väljalülituse ja läinud üle imelikule "konsooliteatele", millest mina midagi aru ei oska saada. Äkki keegi saab sellest aru.

Pilt on küll udune, aga lõpus vaatab vastu 'kernel panic', mis tähendab, et OS jooksis kinni.

Kuskil miski on vigane, kas raudvara või failisüsteem. Ma alustaksin kontrollimisi kas mälupulgalt või CD-lt käivitades memtestiga. Kui see poole tunni või tunni jooksul ühtegi viga ei näita, siis failsüsteemi kontrollimiseks on roodu käsk fsck.

kessu · Postitus Postitas **kessu** » 17.05.2015, 23:39

Panin ka ise tähele, et selles suuruses pildil, mida siia üles kannatab laadida pole see info just kõige loetavam ... kahjuks hilja

ertserts · Postitus Postitas **ertserts** » 18.05.2015, 11:54

Vaata linki How to set NOMODESET and other kernel boot options in grub2 ehk on abi.

Informatiivsem on sealne alalõik How to permanently set kernel boot options on an installed OS (not wubi).

kessu · Postitus Postitas **kessu** » 18.05.2015, 12:46

Mõtlesin siin omaette, et kas ei või see olla seotud minu teise teemaga Mint ja mälu suurus, äkki tekitab selline mälu rohkus ka sellist asja?

Veidi hiljem: tundub, et mitte, just oli kaks korda uuesti ja ma olin juba ühe mälupulga eemaldanud. Panen neist nüüd uploadi pildid, ehk loeb sealt midagi välja.

https://www.upload.ee/image/4730176/P5180005.JPG
https://www.upload.ee/image/4730175/P5180004.JPG

Postitus Postitas **sander85** » 18.05.2015, 13:51

Seda vaadates võiks kahtlustada ka kõvaketast. Ma ei tea, kas Mintil on olemas, küll aga Ubuntul - selline pakk nagu gsmartcontrol - soovitaks sellega oma ketastele "otsa" vaadata, et ega mõni neist vigu ei evi. Memtest kulub ka endiselt ära.

kessu · Postitus Postitas **kessu** » 18.05.2015, 14:04

Hakkasin eile öösel memtesti tegema ... natuke kaua võttis aega. Täna kell 11.00 tegin restardi, sest 12h testi on natuke palju minu jaoks ja minust ta pooleli jäi

sadiini · Postitus Postitas **sadiini** » 18.05.2015, 14:05

sander85 kirjutas:Seda vaadates võiks kahtlustada ka kõvaketast. Ma ei tea, kas Mintil on olemas, küll aga Ubuntul - selline pakk nagu gsmartcontrol - soovitaks sellega oma ketastele "otsa" vaadata, et ega mõni neist vigu ei evi. Memtest kulub ka endiselt ära.

gsmartcontrol on täiesti olemas.

kessu · Postitus Postitas **kessu** » 18.05.2015, 14:17

Lühike self-test erroreid ei leidnud. Küll aga on Error Log tabil: ATA Error Count: 8 (Note: Usually only the last five errors are stored.)

Kood: Vali kõik

Complete error log:

SMART Error Log Version: 1
Warning: ATA error count 8 inconsistent with error log pointer 1
ATA Error Count: 8 (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 8 occurred at disk power-on lifetime: 33096 hours (1379 days + 0 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 d6 ba 04 e1  Error: UNC at LBA = 0x0104bad6 = 17087190

  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 d0 ba 04 01 08      00:53:36.396  READ DMA
  c8 00 08 a0 0b 00 00 08      00:53:36.395  READ DMA
  c8 00 80 d8 ba 04 01 08      00:53:36.381  READ DMA
  ec 00 00 00 00 00 00 08      00:53:36.372  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 08      00:53:36.365  SET FEATURES [Set transfer mode]

Error 7 occurred at disk power-on lifetime: 33096 hours (1379 days + 0 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 d6 ba 04 e1  Error: UNC at LBA = 0x0104bad6 = 17087190

  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 98 ba 04 01 08      00:53:33.440  READ DMA
  c8 00 08 98 0b 00 00 08      00:53:33.440  READ DMA
  c8 00 20 78 ba 04 01 08      00:53:33.440  READ DMA
  c8 00 08 90 0b 00 00 08      00:53:33.440  READ DMA
  c8 00 08 70 ba 04 01 08      00:53:33.439  READ DMA

Error 6 occurred at disk power-on lifetime: 33096 hours (1379 days + 0 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 d6 ba 04 e1  Error: UNC at LBA = 0x0104bad6 = 17087190

  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 80 ba 04 01 08      00:43:52.768  READ DMA
  c8 00 08 78 ba 04 01 08      00:43:52.768  READ DMA
  c8 00 08 70 ba 04 01 08      00:43:52.768  READ DMA
  c8 00 f0 58 b9 04 01 08      00:43:52.766  READ DMA
  c8 00 08 50 b9 04 01 08      00:43:52.766  READ DMA

Error 5 occurred at disk power-on lifetime: 33096 hours (1379 days + 0 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 d6 ba 04 e1  Error: UNC at LBA = 0x0104bad6 = 17087190

  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 80 ba 04 01 08      00:41:11.767  READ DMA
  c8 00 08 78 ba 04 01 08      00:41:11.767  READ DMA
  c8 00 08 70 ba 04 01 08      00:41:11.766  READ DMA
  c8 00 f0 58 b9 04 01 08      00:41:11.765  READ DMA
  c8 00 08 50 b9 04 01 08      00:41:11.765  READ DMA

Error 4 occurred at disk power-on lifetime: 33096 hours (1379 days + 0 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 d6 ba 04 e1  Error: UNC at LBA = 0x0104bad6 = 17087190

  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 80 ba 04 01 08      00:38:05.400  READ DMA
  c8 00 08 78 ba 04 01 08      00:38:05.399  READ DMA
  c8 00 08 70 ba 04 01 08      00:38:05.399  READ DMA
  c8 00 f0 58 b9 04 01 08      00:38:05.398  READ DMA
  c8 00 08 50 b9 04 01 08      00:38:05.397  READ DMA

Eemaldasin 2G Ram-i ja tegin uuesti memtesti kah: kõik korras.

https://www.upload.ee/image/4731195/P5180003.JPG

Pingviini veeb

Imelik väljalülitumine

Imelik väljalülitumine

Re: Imelik väljalülitumine