[Risolto]Ubuntu 16.04 ha riscontrato un errore interno

Domande e richieste di un principiante alle prime armi con Ubuntu e il mondo GNU/Linux in generale. Per domande specifiche, utilizzare le altre sezioni.
Regole della sezione
In questa sezione possono inserire nuove discussioni solo coloro che fanno parte del livello "Prode Principiante" e che non hanno superato i 100 messaggi, tutti gli altri possono comunque rispondere regolarmente. Se si fa parte di questo livello e si è registrati al forum prima del 24 aprile 2012, data del passaggio al nuovo forum, consultare questa discussione.

Immagine Come usare UbuntuPrimi passi su Ubuntu Immagine Amministrazione del sistemaComandi di baseInstallare programmiLog di sistemaRiga di comandoSudo
Gerry Ghetto

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Gerry Ghetto »

Prima cancella qualche log file (fai copia/incolla riga per riga).

Codice: Seleziona tutto

sudo rm -rf /var/log/kernbak
sudo rm -rf /var/log/syslogbak
sudo rm /var/log/kern.log.*
sudo rm /var/log/syslog.*
Poi copia le ultime 200 righe di kern.log e syslog

Codice: Seleziona tutto

tail -n200 /var/log/syslog > ~/syslog
tail -n200 /var/log/kern.log > ~/kern.log
Poi cancelli il contenuto di /var/log/kern.log e /var/log/syslog

Codice: Seleziona tutto

sudo -i
cd /var/log
> kern.log
> syslog
exit
Alla fine post il contentuto di ~/kern.log e ~/syslog. Puoi aprire i file con il tuo text editor preferito.

Puoi anche aggiornare il sistema con

Codice: Seleziona tutto

sudo apt update && sudo apt full-upgrade
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

Buongiorno Gerryghetto e buongiorno a tutti, i primi comandi che mi hai suggerito mi hanno restituito questo come output devo procedere con gli altri?
Se la risposta sarà si dove trovo le ultime 200 righe di kern.log e syslog?

Codice: Seleziona tutto

mirco@mirco-X541UAK:~$ sudo rm -rf /var/log/kernbak
[sudo] password di mirco: 
mirco@mirco-X541UAK:~$ sudo rm -rf /var/log/syslogbak
mirco@mirco-X541UAK:~$ sudo rm /var/log/kern.log.*
rm: impossibile rimuovere '/var/log/kern.log.*': File o directory non esistente
mirco@mirco-X541UAK:~$ sudo rm /var/log/syslog.*
mirco@mirco-X541UAK:~$ 
Grazie per la pazienza!
Gerry Ghetto

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Gerry Ghetto »

Se hai eseguito

Codice: Seleziona tutto

tail -n200 /var/log/syslog > ~/syslog
tail -n200 /var/log/kern.log > ~/kern.log
trovi i file nella tua home (/home/mirco/kern.log e /home/mirco/syslog).
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

Ok Gerry Ghetto ho trovato i file nella home, poi ho eseguito questo comando

Codice: Seleziona tutto

mirco@mirco-X541UAK:~$ sudo -i
[sudo] password di mirco: 
root@mirco-X541UAK:~# cd /var/log
root@mirco-X541UAK:/var/log# > kern.log
root@mirco-X541UAK:/var/log# > syslog
root@mirco-X541UAK:/var/log# exit
logout
spero di aver fatto tutto bene!
ho anche aggiornato,posto l'output

Codice: Seleziona tutto

mirco@mirco-X541UAK:~$ sudo apt update && sudo apt full-upgrade
Trovato:1 http://it.archive.ubuntu.com/ubuntu xenial InRelease                
Scaricamento di:2 http://it.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Scaricamento di:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
Scaricamento di:4 http://it.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Scaricamento di:5 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [833 kB]
Scaricamento di:6 http://it.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [754 kB]
Scaricamento di:7 http://it.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [678 kB]
Scaricamento di:8 http://it.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [619 kB]
Recuperati 3.207 kB in 6s (482 kB/s)                                           
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
1 pacchetto può essere aggiornato: eseguire "apt list --upgradable" per vederlo.
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Fatto
I seguenti pacchetti sono stati installati automaticamente e non sono più richiesti:
  linux-headers-4.13.0-45 linux-headers-4.13.0-45-generic
  linux-image-4.13.0-45-generic linux-image-extra-4.13.0-45-generic
Usare "sudo apt autoremove" per rimuoverli.
I seguenti pacchetti saranno aggiornati:
  xserver-common
1 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
È necessario scaricare 27,7 kB di archivi.
Dopo quest'operazione, verranno occupati 1.024 B di spazio su disco.
Continuare? [S/n] S
Scaricamento di:1 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 xserver-common all 2:1.18.4-0ubuntu0.8 [27,7 kB]
Recuperati 27,7 kB in 0s (165 kB/s)     
(Lettura del database... 255660 file e directory attualmente installati.)
Preparativi per estrarre .../xserver-common_2%3a1.18.4-0ubuntu0.8_all.deb...
Estrazione di xserver-common (2:1.18.4-0ubuntu0.8) su (2:1.18.4-0ubuntu0.7)...
Elaborazione dei trigger per man-db (2.7.5-1)...
Configurazione di xserver-common (2:1.18.4-0ubuntu0.8)...
mirco@mirco-X541UAK:~$ 
Gerry Ghetto

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Gerry Ghetto »

Qualcosa ti ha riempito i logfile, quindi sarebbe molto utile se tu postassi il contenuto di ~/kern.log e ~/syslog. Forse possiamo aiutarti a risolvere il problema.
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

Grazie Gerriy Ghetto! questo di seguito è il contenuto di ~/kern.log
Allegati
kern.log
(25.17 KiB) Scaricato 43 volte
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

E quà i file ~/syslog. che purtroppo non riesco a caricare come allegato

Codice: Seleziona tutto

Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855638] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855664] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855667] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855669] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855671] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855696] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855700] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855702] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855703] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855729] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855733] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855735] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855737] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855762] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855766] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855768] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855769] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855795] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855799] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855801] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855802] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855828] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855832] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855833] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855835] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855861] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855865] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855867] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855868] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855894] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855898] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855899] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855901] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855927] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855931] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855932] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855934] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855960] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855964] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855965] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855967] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855993] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855997] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.855998] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856000] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856026] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856029] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856031] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856032] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856058] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856062] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856064] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856065] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856091] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856095] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856097] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856098] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856124] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856128] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856130] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856131] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856157] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856161] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856163] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856164] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856190] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856194] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856196] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856197] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856223] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856227] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856229] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856230] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856256] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856260] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856261] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856263] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856289] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856293] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856294] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856296] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856322] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856326] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856327] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856329] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856355] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856358] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856360] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856361] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856388] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856391] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856393] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856394] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856420] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856424] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856426] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856427] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856453] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856457] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856459] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856460] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856486] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856490] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856492] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856493] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856519] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856523] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856525] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856526] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856552] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856556] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856558] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856559] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856644] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856655] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856658] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856661] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856666] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856673] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856674] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856685] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856687] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856695] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856700] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856705] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856711] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856721] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856726] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856729] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856735] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856743] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856756] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856762] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856767] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856770] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856784] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856788] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856791] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856793] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856818] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856823] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856825] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856827] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856850] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856855] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856859] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856864] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856885] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856891] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856895] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856899] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856915] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856921] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856923] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856926] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856950] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856955] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856957] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.856958] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857030] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857036] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857041] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857047] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857052] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857060] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857061] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857067] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857080] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857085] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857087] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857089] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857116] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857121] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857124] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857126] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857147] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857153] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857156] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857160] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857181] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857186] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857191] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857195] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857212] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857216] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857218] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857219] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857245] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857249] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857252] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857254] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857278] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857284] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857288] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857292] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857310] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857314] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857317] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857319] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 23 14:53:56 mirco-X541UAK kernel: [ 1685.857343] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Avatar utente
Filoteo
Entusiasta Emergente
Entusiasta Emergente
Messaggi: 1318
Iscrizione: venerdì 28 agosto 2015, 9:38
Desktop: Gnome
Distribuzione: Arch Linux

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Filoteo »

Su askubuntu suggeriscono di aggiungere un parametro di avvio del kernel:

Apri il file di configurazione di grub

Codice: Seleziona tutto

sudo nano /etc/default/grub
Muoviti con i tasti freccia e vai su questa riga

Codice: Seleziona tutto

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Quindi modificala in questo modo

Codice: Seleziona tutto

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"
Salva con CTRL-O e esci con CTRL-X.

Aggiorna il grub

Codice: Seleziona tutto

sudo update-grub
Riavvia, quindi esegui

Codice: Seleziona tutto

tail -f /var/log/syslog
Se ha funzionato, non dovresti più nuove righe di pcieport che inondano il terminale (e riempiono il tuo disco), quindi fai CTRL-C per chiudere.
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

Non mi fa uscire dal grub con CTRL X e rimango bloccato in questa situazione

Codice: Seleziona tutto

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
Nome del file in cui salvare: /etc/default/grub                                 
^G Guida        M-D Formato DOS M-A Accoda      M-B File di back
^C Annulla      M-M Formato Mac M-P Scrivi in te^T Sfoglia
Avatar utente
Filoteo
Entusiasta Emergente
Entusiasta Emergente
Messaggi: 1318
Iscrizione: venerdì 28 agosto 2015, 9:38
Desktop: Gnome
Distribuzione: Arch Linux

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Filoteo »

Scusami, era CTRL-O, poi INVIO per confermare e infine CTRL-X per uscire.
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

Siete Grandi ha funzionato!!! :popopo: ora resta questo messaggio che compare all'accensione, che vi invio come allegato.
Grazie a tutti!
Allegati
Schermata del 2018-08-24 15-28-02.png
Avatar utente
wilecoyote
Tenace Tecnocrate
Tenace Tecnocrate
Messaggi: 15349
Iscrizione: giovedì 20 agosto 2009, 16:21
Desktop: Kubuntu et alii
Distribuzione: 9.04 32bit 14/18/20/22.04 LTS 64bit
Sesso: Maschile
Località: Ceranesi - Ge

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da wilecoyote »

:) Salve, clicca su Esamina… e leggi cosa riporta.

:ciao: Ciao
ACER Extensa 5230E 2,2 Ghz cpu Celeron 900 hdd 160 GB Ram 1 GB scheda video Intel GM500
ACER Extensa 5635Z 2,2 Ghz cpu Celeron T3100 hdd 320 GB Ram 4 GB scheda video Intel Mobile 4
Quando una Finestra chiusa incontra un Pinguino la Finestra chiusa è una Finestra aperta.
Avatar utente
giulux
Amministratore
Amministratore
Messaggi: 25422
Iscrizione: domenica 10 gennaio 2010, 12:17
Desktop: ubuntu 18.04
Distribuzione: Ubuntu 18.04.3 LTS x86_64
Sesso: Maschile
Località: Roma

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da giulux »

Dai nel terminale

Codice: Seleziona tutto

 sudo apt-get autoremove
"Non è una segno di buona salute l'essere ben adattato ad una società malata". (Jiddu Krishnarmurti)
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

Posto le immagini
[img][img]https://s22.postimg.cc/6q3t0bmvx/Utilizzo_disco1.png[/img][/img]
Non so se si riesce a vedere!
Gerry Ghetto

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Gerry Ghetto »

Posta per favore

Codice: Seleziona tutto

ls -lhs /var/log/
ilsoldino
Prode Principiante
Messaggi: 68
Iscrizione: giovedì 17 aprile 2014, 13:50

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da ilsoldino »

Eccolo quà

Codice: Seleziona tutto

mirco@mirco-X541UAK:~$ ls -lhs /var/log/
totale 161G
   0 -rw-r--r-- 1 root              root    0 ago 13 01:08 alternatives.log
4,0K -rw-r--r-- 1 root              root  704 ago 10 00:35 alternatives.log.1
4,0K -rw-r--r-- 1 root              root  568 lug 19 15:34 alternatives.log.2.gz
4,0K -rw-r--r-- 1 root              root  481 giu 13 22:48 alternatives.log.3.gz
4,0K -rw-r--r-- 1 root              root  215 mag 27 23:23 alternatives.log.4.gz
4,0K -rw-r--r-- 1 root              root  303 apr 24 15:49 alternatives.log.5.gz
4,0K -rw-r--r-- 1 root              root  159 apr  1 20:10 alternatives.log.6.gz
4,0K -rw-r--r-- 1 root              root  351 mar  9 08:45 alternatives.log.7.gz
4,0K -rw-r--r-- 1 root              root 3,8K feb  3  2018 alternatives.log.8.gz
   0 -rw-r----- 1 root              adm     0 ago 24 15:15 apport.log
4,0K -rw-r----- 1 root              adm  2,2K ago 24 14:50 apport.log.1
4,0K -rw-r----- 1 root              adm   544 ago 23 11:30 apport.log.2.gz
4,0K -rw-r----- 1 root              adm   532 ago 22 12:23 apport.log.3.gz
4,0K -rw-r----- 1 root              adm  1,2K ago 21 10:53 apport.log.4.gz
4,0K -rw-r----- 1 root              adm   348 ago 19 20:48 apport.log.5.gz
4,0K -rw-r----- 1 root              adm   939 ago 17 12:32 apport.log.6.gz
4,0K -rw-r----- 1 root              adm   598 ago 13 01:06 apport.log.7.gz
4,0K drwxr-xr-x 2 root              root 4,0K ago 13 01:08 apt
 48K -rw-r----- 1 syslog            adm   42K ago 24 17:22 auth.log
 24K -rw-r----- 1 syslog            adm   20K ago 21 10:51 auth.log.1
4,0K -rw-r----- 1 syslog            adm  2,3K ago 13 01:03 auth.log.2.gz
 20K -rw-r----- 1 syslog            adm   17K ago  7 09:44 auth.log.3.gz
 12K -rw-r----- 1 syslog            adm  9,2K lug  8 00:25 auth.log.4.gz
8,0K -rw-r--r-- 1 root              root 4,9K ago 24 16:22 boot.log
 60K -rw-r--r-- 1 root              root  57K ago  1  2017 bootstrap.log
4,0K -rw------- 1 root              utmp  384 ago 24 15:24 btmp
4,0K -rw------- 1 root              utmp  768 lug 22 01:21 btmp.1
4,0K drwxr-xr-x 2 root              root 4,0K ago 24 15:15 cups
4,0K drwxr-xr-x 2 root              root 4,0K lug 19  2017 dist-upgrade
4,0K -rw-r----- 1 root              adm    31 ago  1  2017 dmesg
108K -rw-r--r-- 1 root              root 103K ago 24 16:26 dpkg.log
 68K -rw-r--r-- 1 root              root  63K ago 10 00:39 dpkg.log.1
 12K -rw-r--r-- 1 root              root 8,4K lug 19 15:38 dpkg.log.2.gz
4,0K -rw-r--r-- 1 root              root 3,1K giu 13 22:49 dpkg.log.3.gz
8,0K -rw-r--r-- 1 root              root 6,5K mag 27 23:28 dpkg.log.4.gz
8,0K -rw-r--r-- 1 root              root 5,7K apr 24 15:50 dpkg.log.5.gz
8,0K -rw-r--r-- 1 root              root 5,5K apr  1 20:10 dpkg.log.6.gz
 16K -rw-r--r-- 1 root              root  14K mar  9 08:48 dpkg.log.7.gz
132K -rw-r--r-- 1 root              root 130K feb  3  2018 dpkg.log.8.gz
8,0K -rw-r--r-- 1 root              root  32K ago 17 15:24 faillog
4,0K -rw-r--r-- 1 root              root 4,0K ago 21 11:24 fontconfig.log
4,0K drwxr-xr-x 2 root              root 4,0K ago  1  2017 fsck
4,0K -rw-r--r-- 1 root              root 1,9K ago 24 16:22 gpu-manager.log
4,0K drwxr-xr-x 3 root              root 4,0K ago  1  2017 hp
4,0K drwxrwxr-x 2 root              root 4,0K gen 13  2018 installer
 81G -rw-r----- 1 syslog            adm   81G ago 24 17:22 kern.log
 40K -rw-rw-r-- 1 root              utmp 286K ago 17 15:24 lastlog
4,0K drwxr-xr-x 2 root              root 4,0K ago 24 15:15 lightdm
4,0K drwx------ 2 speech-dispatcher root 4,0K feb 18  2016 speech-dispatcher
776K -rw-r----- 1 syslog            adm  774K ago 24 17:22 syslog
 81G -rw-r----- 1 syslog            adm   81G ago 24 15:15 syslog.1
4,0K drwxr-x--- 2 root              adm  4,0K ago 23 11:33 unattended-upgrades
4,0K drwxr-xr-x 2 root              root 4,0K mag 19  2016 upstart
 96K -rw-rw-r-- 1 root              utmp  89K ago 24 16:22 wtmp
 84K -rw-rw-r-- 1 root              utmp  78K ago  7 09:42 wtmp.1
 40K -rw-r--r-- 1 root              root  38K ago 24 16:48 Xorg.0.log
 40K -rw-r--r-- 1 root              root  38K ago 24 15:50 Xorg.0.log.old
 40K -rw-r--r-- 1 root              root  37K ago 17 15:38 Xorg.1.log
 36K -rw-r--r-- 1 root              root  35K ago 10 00:20 Xorg.1.log.old
 36K -rw-r--r-- 1 root              root  34K ago 10 00:20 Xorg.failsafe.log
 36K -rw-r--r-- 1 root              root  34K ago  7 00:49 Xorg.failsafe.log.old
mirco@mirco-X541UAK:~$ 
Avatar utente
Filoteo
Entusiasta Emergente
Entusiasta Emergente
Messaggi: 1318
Iscrizione: venerdì 28 agosto 2015, 9:38
Desktop: Gnome
Distribuzione: Arch Linux

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Filoteo »

Vediamo di nuovo le ultime righe dei log, può essere che rimanga solo da cancellare syslog.1 e svuotare kern.log:

Codice: Seleziona tutto

tail -50 /var/log/kern.log
tail -50 /var/log/syslog
Gerry Ghetto

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Gerry Ghetto »

/var/log/kern.log e /var/log/syslog sono ancora grandi, quindi rifai

Codice: Seleziona tutto

sudo -i
cd /var/log
> kern.log
> syslog
exit
Controlla ogni tanto con

Codice: Seleziona tutto

ls -lsh /var/log | awk '{ print $6 "\t" $10 }'
Se hai un log file con più di 10MB, postalo qua.
Avatar utente
Filoteo
Entusiasta Emergente
Entusiasta Emergente
Messaggi: 1318
Iscrizione: venerdì 28 agosto 2015, 9:38
Desktop: Gnome
Distribuzione: Arch Linux

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Filoteo »

In realtà è syslog.1 il secondo file molto grande

Codice: Seleziona tutto

81G -rw-r----- 1 syslog            adm   81G ago 24 15:15 syslog.1
Gerry Ghetto

Re: Ubuntu 16.04 ha riscontrato un errore interno

Messaggio da Gerry Ghetto »

Filoteo [url=https://forum.ubuntu-it.org/viewtopic.php?p=5076706#p5076706][img]https://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto:In realtà è syslog.1 il secondo file molto grande

Codice: Seleziona tutto

81G -rw-r----- 1 syslog            adm   81G ago 24 15:15 syslog.1
Sì, giusto.
Scrivi risposta

Ritorna a “Dilemmi del principiante”

Chi c’è in linea

Visualizzano questa sezione: corradoventu e 6 ospiti