[Risolto] login troppo lento Kubuntu 16.04.1
[Risolto] login troppo lento Kubuntu 16.04.1
Durante la fase di installazione non ho avuto nessun problema, quando però vado a fare il login mi ritrovo con una schermata nera che dura 1-2 minuti a seconda del caso, poi compare la schermata di login la quale va in freeze appena inizio a digitare la password o al movimento del mouse. Anzi se digito la password e aspetto che il freeze si stabilizzi se muovo il mouse la schermata si blocca per almeno un altro minuto.
Dopo che premo invio ci vogliono 2-3 minuti per accedere all'OS, una volta dentro è perfetto, non ci sono problemi di nessun tipo (almeno per ora).
Il mio pc è nuovo, il processore è un i7-6700K su una asrock extreme 6, perciò sono andato a leggere tutte le discussioni che parlavano dei problemi relativi alla 16.04, ma anche provando tutto quello indicato non cambia nulla, ho anche installato i driver reperibili qui https://01.org/linuxgraphics/intel-linu ... -firmwares.
A questo punto cosa posso provare?
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
http://forum.ubuntu-it.org/viewtopic.ph ... 5#p4891031
salva e chiudi e prova un paio di riavvii
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Codice: Seleziona tutto
DefaultTimeoutStopSec=90s
mentre
Codice: Seleziona tutto
DefaultRestartSec=100ms
Il problema è che è come se andasse in crash o in overload, rimane fermo, sparisce il puntatore o rimane bloccato per alcuni minuti e poi posso scrivere nuovamente, quando premo invio rimane di nuovo bloccata, per far capire anche l'orologio non va avanti e rimane bloccato a quel preciso momento, poi riesco ad entrare e ad usare tutto senza problemi.
Alcune volte invece devo riavviare perché dopo 10 minuti non posso ancora digitare la password. Ho provato anche a reinstallare ma il problema rimane lo stesso.
- wilecoyote
- 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: Login lungo 3-10 minuti Kubuntu 16.04.1
Ciao
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.
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Ho deciso di investigare meglio e ho aperto il file in /etc/log/syslog per dare un'occhiata, ho trovato più di 1700 righe solo nella fase di avvio, le prime mille hanno un timestamp identico, poi iniziano a passare i secondi e a verificarsi alcuni errori. Ho fatto tanti riavvii e confrontato i log e ho visto che spesso compare
Codice: Seleziona tutto
ModemManager[2885]: <info> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin
Codice: Seleziona tutto
systemd[1]: NetworkManager-dispatcher.service: Start operation timed out. Terminating.
Codice: Seleziona tutto
Aug 16 18:52:15 user-desktop kernel: [ 37.817627] ata8.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
Aug 16 18:52:15 user-desktop kernel: [ 37.817644] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817655] ata8.00: cmd 61/08:00:b8:10:c0/00:00:00:00:00/40 tag 0 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.817655] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817680] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817688] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817699] ata8.00: cmd 61/08:08:c0:11:c0/00:00:00:00:00/40 tag 1 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.817699] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817723] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817731] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817741] ata8.00: cmd 61/08:10:60:18:c1/00:00:00:00:00/40 tag 2 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.817741] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817765] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817773] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817784] ata8.00: cmd 61/08:18:58:28:c1/00:00:00:00:00/40 tag 3 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.817784] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817808] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817815] ata8.00: failed command: SEND FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817826] ata8.00: cmd 64/01:20:00:00:00/00:00:00:00:00/a0 tag 4 ncq 512 out
Aug 16 18:52:15 user-desktop kernel: [ 37.817826] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817850] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817857] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817868] ata8.00: cmd 60/28:28:70:05:61/00:00:00:00:00/40 tag 5 ncq 20480 in
Aug 16 18:52:15 user-desktop kernel: [ 37.817868] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817897] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817905] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817915] ata8.00: cmd 60/20:30:60:cf:9e/00:00:00:00:00/40 tag 6 ncq 16384 in
Aug 16 18:52:15 user-desktop kernel: [ 37.817915] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817939] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817946] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817957] ata8.00: cmd 60/08:38:10:08:40/00:00:00:00:00/40 tag 7 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.817957] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.817981] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.817989] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.817999] ata8.00: cmd 61/08:40:30:08:00/00:00:00:00:00/40 tag 8 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.817999] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818024] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818031] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818042] ata8.00: cmd 61/08:48:08:08:40/00:00:00:00:00/40 tag 9 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.818042] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818066] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818073] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818084] ata8.00: cmd 61/08:50:40:09:40/00:00:00:00:00/40 tag 10 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.818084] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818108] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818116] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818126] ata8.00: cmd 61/08:58:50:09:40/00:00:00:00:00/40 tag 11 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.818126] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818150] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818158] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818168] ata8.00: cmd 61/08:60:70:0d:40/00:00:00:00:00/40 tag 12 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.818168] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818192] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818200] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818210] ata8.00: cmd 61/08:68:48:09:41/00:00:00:00:00/40 tag 13 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.818210] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818235] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818242] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818253] ata8.00: cmd 61/08:70:78:09:41/00:00:00:00:00/40 tag 14 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.818253] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818277] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818285] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818295] ata8.00: cmd 60/08:78:78:12:40/00:00:00:00:00/40 tag 15 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.818295] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818319] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818327] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818337] ata8.00: cmd 60/08:80:80:12:40/00:00:00:00:00/40 tag 16 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.818337] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818362] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818369] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818380] ata8.00: cmd 60/08:88:88:12:40/00:00:00:00:00/40 tag 17 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.818380] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.818404] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.818411] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.818422] ata8.00: cmd 60/08:90:90:12:40/00:00:00:00:00/40 tag 18 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.818422] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.819550] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.820099] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.820663] ata8.00: cmd 61/08:98:00:08:c0/00:00:00:00:00/40 tag 19 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.820663] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.821783] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.822375] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.822940] ata8.00: cmd 61/08:a0:80:08:c0/00:00:00:00:00/40 tag 20 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.822940] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.824055] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.824618] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.825180] ata8.00: cmd 60/08:a8:a8:12:40/00:00:00:00:00/40 tag 21 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.825180] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.826305] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.826861] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.827412] ata8.00: cmd 60/08:b0:b0:12:40/00:00:00:00:00/40 tag 22 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.827412] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.828540] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.829101] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.829656] ata8.00: cmd 61/08:b8:58:10:c0/00:00:00:00:00/40 tag 23 ncq 4096 out
Aug 16 18:52:15 user-desktop kernel: [ 37.829656] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.830793] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.831346] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.831912] ata8.00: cmd 60/08:c0:c0:12:40/00:00:00:00:00/40 tag 24 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.831912] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.833042] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.833598] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.834170] ata8.00: cmd 60/08:c8:c8:12:40/00:00:00:00:00/40 tag 25 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.834170] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.835291] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.835857] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.836422] ata8.00: cmd 60/08:d0:d0:12:40/00:00:00:00:00/40 tag 26 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.836422] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.837547] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.838116] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.838683] ata8.00: cmd 60/08:d8:d8:12:40/00:00:00:00:00/40 tag 27 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.838683] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.839808] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.840373] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.840939] ata8.00: cmd 60/08:e0:e0:12:40/00:00:00:00:00/40 tag 28 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.840939] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.842067] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.842632] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.843198] ata8.00: cmd 60/08:e8:e8:12:40/00:00:00:00:00/40 tag 29 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.843198] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.844325] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.844881] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:52:15 user-desktop kernel: [ 37.845448] ata8.00: cmd 60/08:f0:f0:12:40/00:00:00:00:00/40 tag 30 ncq 4096 in
Aug 16 18:52:15 user-desktop kernel: [ 37.845448] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:52:15 user-desktop kernel: [ 37.846591] ata8.00: status: { DRDY }
Aug 16 18:52:15 user-desktop kernel: [ 37.847153] ata8: hard resetting link
Aug 16 18:52:16 user-desktop kernel: [ 38.337628] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 16 18:52:16 user-desktop kernel: [ 38.337937] ata8.00: supports DRM functions and may not be fully accessible
Aug 16 18:52:16 user-desktop kernel: [ 38.380535] ata8.00: supports DRM functions and may not be fully accessible
Aug 16 18:52:16 user-desktop kernel: [ 38.381391] ata8.00: configured for UDMA/133
Aug 16 18:52:16 user-desktop kernel: [ 38.381398] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381401] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381404] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381407] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381410] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381414] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381417] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381420] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381423] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381426] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381429] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381432] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381435] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381437] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381440] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381443] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381446] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381449] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381452] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381455] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381457] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381460] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381463] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381466] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381468] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381485] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381485] ata8.00: device reported invalid CHS sector 0
Aug 16 18:52:16 user-desktop kernel: [ 38.381496] sd 7:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.381498] sd 7:0:0:0: [sda] tag#15 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.381500] sd 7:0:0:0: [sda] tag#15 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.381501] sd 7:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 00 40 12 78 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.381502] blk_update_request: I/O error, dev sda, sector 4199032
Aug 16 18:52:16 user-desktop kernel: [ 38.382080] sd 7:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.382081] sd 7:0:0:0: [sda] tag#16 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.382082] sd 7:0:0:0: [sda] tag#16 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.382083] sd 7:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 40 12 80 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.382084] blk_update_request: I/O error, dev sda, sector 4199040
Aug 16 18:52:16 user-desktop kernel: [ 38.382640] sd 7:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.382640] sd 7:0:0:0: [sda] tag#17 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.382641] sd 7:0:0:0: [sda] tag#17 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.382642] sd 7:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 00 40 12 88 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.382643] blk_update_request: I/O error, dev sda, sector 4199048
Aug 16 18:52:16 user-desktop kernel: [ 38.383204] sd 7:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.383205] sd 7:0:0:0: [sda] tag#18 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.383206] sd 7:0:0:0: [sda] tag#18 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.383207] sd 7:0:0:0: [sda] tag#18 CDB: Read(10) 28 00 00 40 12 90 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.383207] blk_update_request: I/O error, dev sda, sector 4199056
Aug 16 18:52:16 user-desktop kernel: [ 38.383760] sd 7:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.383760] sd 7:0:0:0: [sda] tag#21 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.383761] sd 7:0:0:0: [sda] tag#21 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.383762] sd 7:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 00 40 12 a8 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.383763] blk_update_request: I/O error, dev sda, sector 4199080
Aug 16 18:52:16 user-desktop kernel: [ 38.384310] sd 7:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.384311] sd 7:0:0:0: [sda] tag#22 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.384311] sd 7:0:0:0: [sda] tag#22 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.384312] sd 7:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 00 40 12 b0 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.384313] blk_update_request: I/O error, dev sda, sector 4199088
Aug 16 18:52:16 user-desktop kernel: [ 38.384843] sd 7:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.384844] sd 7:0:0:0: [sda] tag#24 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.384845] sd 7:0:0:0: [sda] tag#24 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.384846] sd 7:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 00 40 12 c0 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.384846] blk_update_request: I/O error, dev sda, sector 4199104
Aug 16 18:52:16 user-desktop kernel: [ 38.385384] sd 7:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.385385] sd 7:0:0:0: [sda] tag#25 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.385385] sd 7:0:0:0: [sda] tag#25 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.385386] sd 7:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 00 40 12 c8 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.385387] blk_update_request: I/O error, dev sda, sector 4199112
Aug 16 18:52:16 user-desktop kernel: [ 38.385921] sd 7:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.385922] sd 7:0:0:0: [sda] tag#26 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.385923] sd 7:0:0:0: [sda] tag#26 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.385924] sd 7:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 00 40 12 d0 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.385925] blk_update_request: I/O error, dev sda, sector 4199120
Aug 16 18:52:16 user-desktop NetworkManager[2946]: <info> [1471366336.1979] SettingsPlugin-Ofono: (38044720) ... get_connections.
Aug 16 18:52:16 user-desktop NetworkManager[2946]: <info> [1471366336.1979] SettingsPlugin-Ofono: (38044720) connections count: 0
Aug 16 18:52:16 user-desktop NetworkManager[2946]: <info> [1471366336.1979] get unmanaged devices count: 0
Aug 16 18:52:16 user-desktop systemd[1]: Received SIGRTMIN+21 from PID 1104 (plymouthd).
Aug 16 18:52:16 user-desktop dbus[2923]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Aug 16 18:52:16 user-desktop kernel: [ 38.386440] sd 7:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 16 18:52:16 user-desktop kernel: [ 38.386441] sd 7:0:0:0: [sda] tag#27 Sense Key : Illegal Request [current] [descriptor]
Aug 16 18:52:16 user-desktop kernel: [ 38.386441] sd 7:0:0:0: [sda] tag#27 Add. Sense: Unaligned write command
Aug 16 18:52:16 user-desktop kernel: [ 38.386442] sd 7:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 00 40 12 d8 00 00 08 00
Aug 16 18:52:16 user-desktop kernel: [ 38.386443] blk_update_request: I/O error, dev sda, sector 4199128
Aug 16 18:52:16 user-desktop kernel: [ 38.386963] ata8: EH complete
Aug 16 18:52:16 user-desktop kernel: [ 38.387008] ata8.00: Enabling discard_zeroes_data
Aug 16 18:52:16 user-desktop whoopsie[2896]: [18:52:16] Using lock path: /var/lock/whoopsie/lock
Aug 16 18:52:16 user-desktop /usr/lib/snapd/snapd[2948]: daemon.go:212: DEBUG: adding /
Aug 16 18:52:16 user-desktop systemd[1]: Starting Hostname Service...
Codice: Seleziona tutto
Aug 16 18:53:23 user-desktop kernel: [ 105.826496] ata8.00: exception Emask 0x0 SAct 0x380000 SErr 0x0 action 0x6 frozen
Aug 16 18:53:23 user-desktop kernel: [ 105.826508] ata8.00: failed command: READ FPDMA QUEUED
Aug 16 18:53:23 user-desktop kernel: [ 105.826518] ata8.00: cmd 60/40:98:18:2a:44/00:00:01:00:00/40 tag 19 ncq 32768 in
Aug 16 18:53:23 user-desktop kernel: [ 105.826518] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:53:23 user-desktop kernel: [ 105.826523] ata8.00: status: { DRDY }
Aug 16 18:53:23 user-desktop kernel: [ 105.826528] ata8.00: failed command: WRITE FPDMA QUEUED
Aug 16 18:53:23 user-desktop kernel: [ 105.826536] ata8.00: cmd 61/10:a0:60:2a:44/00:00:00:00:00/40 tag 20 ncq 8192 out
Aug 16 18:53:23 user-desktop kernel: [ 105.826536] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:53:23 user-desktop kernel: [ 105.826540] ata8.00: status: { DRDY }
Aug 16 18:53:23 user-desktop kernel: [ 105.826543] ata8.00: failed command: SEND FPDMA QUEUED
Aug 16 18:53:23 user-desktop kernel: [ 105.826550] ata8.00: cmd 64/01:a8:00:00:00/00:00:00:00:00/a0 tag 21 ncq 512 out
Aug 16 18:53:23 user-desktop kernel: [ 105.826550] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 16 18:53:23 user-desktop kernel: [ 105.826554] ata8.00: status: { DRDY }
Aug 16 18:53:23 user-desktop kernel: [ 105.826560] ata8: hard resetting link
Aug 16 18:53:24 user-desktop kernel: [ 106.318461] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 16 18:53:24 user-desktop kernel: [ 106.318732] ata8.00: supports DRM functions and may not be fully accessible
Aug 16 18:53:24 user-desktop kernel: [ 106.319929] ata8.00: supports DRM functions and may not be fully accessible
Aug 16 18:53:24 user-desktop kernel: [ 106.320785] ata8.00: configured for UDMA/133
Aug 16 18:53:24 user-desktop kernel: [ 106.320793] ata8.00: device reported invalid CHS sector 0
Aug 16 18:53:24 user-desktop kernel: [ 106.320797] ata8.00: device reported invalid CHS sector 0
Aug 16 18:53:24 user-desktop kernel: [ 106.320806] ata8: EH complete
Aug 16 18:53:24 user-desktop kernel: [ 106.320849] ata8.00: Enabling discard_zeroes_data
Aug 16 18:53:24 user-desktop NetworkManager[2946]: <info> [1471366404.1379] dhcp4 (enp0s31f6): dhclient started with pid 3173
Aug 16 18:53:24 user-desktop sddm-greeter[3115]: Reading from "/usr/share/xsessions/plasma.desktop"
Aug 16 18:53:24 user-desktop sddm[3089]: Message received from greeter: Login
Codice: Seleziona tutto
ata8.00: failed command: READ FPDMA QUEUED
Allora dato che compare spesso il tentativo di connessione e configurazione del network manager prima di qualsiasi errore FPDMA ho pensato fosse la rete, ho scollegato il cavo di rete e ho provato diversi riavvii, alcune volte ottengo solo una serie di errori FPDMA, altre nessuno riducendo il tempo di avvio a 7 secondi per arrivare alla schermata di login, che diventano 47 per accedere alla scrivania perché dopo aver inserito la password ci mette comunque ancora del tempo, ma è un grande passo avanti.
Quindi ora mi serve un consiglio su come comportarmi, possono essere i driver o è il network manager? come faccio a capirlo?
P.S: se può servire posso caricare un log di quando si verifica il problema, ma essendo veramente molto lungo non so se sia il caso.
- wilecoyote
- 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: Login lungo 3-10 minuti Kubuntu 16.04.1
1 guarderei in Impostazioni di sistema -> Avvio e spegnimento -> Avvio automatico se i servizi elencati nel log sono presenti come avvio automatico e li disattiverei , quindi proverei a riavviare il computer.
2 proverei con una Live di Kubuntu Trusty 14.04.5 LTS, usa KDE4, in caso positivo se funziona tutto, spazio permettendo, l'installerei in una partizione di 60-100 GB, quindi proverei ad avviare il computer.
Oppure aspetta altri pareri, senz'altro discordi dai miei.
Ciao
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.
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Ho provato disattivando tutti i servizi all'avvio, ma non cambia nulla.
Se accedo mantenendo il cavo di rete staccato e poi lo inserisco il sistema va lo stesso in freeze, l'unica cosa che posso fare è muovere il mouse ma non succede nulla, se prima che stabilisca correttamente la connessione premo sull'icona del network manager c'è un altro leggero freeze.
Anche io pensavo ci fossero dei problemi con KDE, perciò ho anche installato una versione di ubuntu 16.04.1, ma il problema è lo stesso, mentre con le live non sembra si noti (forse è coperto nella fase di caricamento).
Da terminale eseguendo
Codice: Seleziona tutto
lspci -nnk | grep -i net -A2
Codice: Seleziona tutto
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
Subsystem: ASRock Incorporation Ethernet Connection (2) I219-V [1849:15b8]
Kernel driver in use: e1000e
Kernel modules: e1000e
Ho provato più volte a reinstallare e anche con Ubuntu 16.04.1, il problema potrebbe trovarsi nel kernel?
- steff
- Moderatore Globale
- Messaggi: 40299
- Iscrizione: domenica 18 febbraio 2007, 19:48
- Desktop: LXQt+labwc
- Distribuzione: Arch; Debian; Ubuntu Server
- Sesso: Maschile
- Località: Toscana
- Contatti:
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Vedo parecchie I/O errori:
Codice: Seleziona tutto
Aug 16 18:52:16 user-desktop kernel: [ 38.386443] blk_update_request: I/O error, dev sda, sector 4199128
La Documentazione da consultare e la FAQ sul uso del forum
Sistemi: LXQt - semplice, modulare e configurabile + *ubuntu in Vbox
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Non ho trovato nessun segno che il disco non sia in salute, inoltre quando accendo il pc senza il cavo di rete inserito va più veloce, se poi provo ad inserirlo ci sono diversi freeze, non so bene se dovuti al plasma o altro.U-Tonto#1 [url=http://forum.ubuntu-it.org/viewtopic.php?p=4906476#p4906476][img]http://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto: Dato che sul forum ho letto che questo genere di errori può essere legato al disco ho fatto diversi test con smart tools e dato che ho una partizione con windows 10 ho usato il software crucial (è un mx300), hd tune pro e crystal disk info e non è stato riscontrato nessun tipo di errore.
Allora dato che compare spesso il tentativo di connessione e configurazione del network manager prima di qualsiasi errore FPDMA ho pensato fosse la rete, ho scollegato il cavo di rete e ho provato diversi riavvii, alcune volte ottengo solo una serie di errori FPDMA, altre nessuno riducendo il tempo di avvio a 7 secondi per arrivare alla schermata di login, che diventano 47 per accedere alla scrivania perché dopo aver inserito la password ci mette comunque ancora del tempo, ma è un grande passo avanti.
in .xsession-errors non mi è parso di trovare errori relativi al disco, però tanti errori di questo genere:
Codice: Seleziona tutto
Known plasmoid ids: QHash(("org.kde.kdeconnect", 51)("org.kde.plasma.networkmanagement", 57)("org.kde.plasma.volume", 55)("org.kde.plasma.printmanager", 54)("org.kde.plasma.devicenotifier", 52)("org.kde.discovernotifier", 49)("org.kde.plasma.battery", 56)("org.kde.plasma.clipboard", 50)("org.kde.plasma.notifications", 53))
org.kde.plasma: unversioned plugin detected, may result in instability
<Unknown File>: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
- steff
- Moderatore Globale
- Messaggi: 40299
- Iscrizione: domenica 18 febbraio 2007, 19:48
- Desktop: LXQt+labwc
- Distribuzione: Arch; Debian; Ubuntu Server
- Sesso: Maschile
- Località: Toscana
- Contatti:
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
La Documentazione da consultare e la FAQ sul uso del forum
Sistemi: LXQt - semplice, modulare e configurabile + *ubuntu in Vbox
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Ho tentato anche l'installazione della 14.04.4, maè molto più instabile, non posso fare nulla perché i freeze sono continui.
Non ho idea di cosa cercare o come venirne fuori.
Possono essere dei problemi legati all'installazione UEFI? Il disco è suddiviso in
sda1 /
sda2 /home
sda3 efi
sda4 windows
sda5 riservata per windows
Non so più a cosa pensare.
- adamoa
- Prode Principiante
- Messaggi: 4
- Iscrizione: mercoledì 17 agosto 2016, 20:58
- Desktop: ubuntu
- Distribuzione: Ubuntu 16.04.1 LTS - x86_64
- Sesso: Maschile
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Il problema è il disco di swap. Systemd, il gestore di avvio dei servizi introdotto con il 16.04 (o forse anche 15.04?) provvede autonomamente a crearlo e confligge con la direttiva in fstab.
Apri un terminale ed edita:
$ sudo vi /etc/fstab
Individua il driver montato come swap e disattivalo mettendo in prima posizione un #. Es:
....
# swap was on /dev/sdb3 during installation
#UUID=86690bf1-d292-425c-b2d3-e8d5519a480d none swap sw 0 0
....
Riavvia, il problema dovrebbe essere risolto.
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
- adamoa
- Prode Principiante
- Messaggi: 4
- Iscrizione: mercoledì 17 agosto 2016, 20:58
- Desktop: ubuntu
- Distribuzione: Ubuntu 16.04.1 LTS - x86_64
- Sesso: Maschile
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Codice: Seleziona tutto
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=686b226f-1496-2654-f89e-759113e47b6e / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda3 during installation
UUID=36EA-2598 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda2 during installation
UUID=ec26a334-ac5b-4fc7-b662-1f5ea56cfd1e /home ext4 defaults 0 2
- wilecoyote
- 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: Login lungo 3-10 minuti Kubuntu 16.04.1
Codice: Seleziona tutto
sudo smartctl -a /dev/sda
Poi per confronto ho indicato di provare l'installazione del 14.04.5 LTS non di 16.04.1 LTS, l'uso abitualmente ed è stabile.
Ciao
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.
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Ho usato gli Smartmontools su Ubuntu per il primo test ed il test è stato superato, al momento sto tentando di installare nuovamente tutto modificando anche la partizione efi, nel caso ci sia una qualche sorta di conflitto, perciò non ti posso copiare tutto l'output.U-Tonto#1 [url=http://forum.ubuntu-it.org/viewtopic.php?p=4906665#p4906665][img]http://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto:Ho provato con una installazione pulita di lubuntu 16.04.1 e niente, identico problema, nessun errore I/O, solo una serie di ata8.00: failed command: READ FPDMA QUEUED come nelle precedenti e un sacco di tentativi con il network manager.
Ho tentato anche l'installazione della 14.04.4, ma è molto più instabile, non posso fare nulla perché i freeze sono continui.
Comunque sembra essere più un problema di configurazione piuttosto che un problema fisico.
-
- Tenace Tecnocrate
- Messaggi: 17934
- Iscrizione: giovedì 8 aprile 2010, 18:41
- Desktop: diversi
- Distribuzione: debian
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
Re: Login lungo 3-10 minuti Kubuntu 16.04.1
@wilecoyote, anche con l'installazione nuova e pulizia della partizione efi il problema persiste, ecco l'output sulla nuova installazione:
dando
Codice: Seleziona tutto
sudo smartctl -t long /dev/sda
sudo smartctl -l selftest /dev/sda
Codice: Seleziona tutto
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-31-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== 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 Extended offline Completed without error 00% 47 -
- wilecoyote
- 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: Login lungo 3-10 minuti Kubuntu 16.04.1
Se anche il Trusty 14.04.4 LTS da problemi da installato motivo in più per leggere con calma com'è messo il disco rigido, nonché com'è composto il hardware per scoprire eventuali incompatibilità, puoi farlo usando Inxi:
Codice: Seleziona tutto
inxi -Fz
Ciao
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.
Chi c’è in linea
Visualizzano questa sezione: 0 utenti iscritti e 10 ospiti