Boot Ubuntu 16.04 lento

[Eremita83]

Ciao tutti,
dopo anni sono ritornato ad utilizzare ubuntu... e devo dire che lo trovo molto migliorato

Il mio problema come da titolo del post è il caricamento lento sia prima che dopo essermi loggato, cercando in giro nel web e nel forum, ho visto che anche altri
hanno riscontrato il mio stesso problema ed alcuni grazie alla community sono riusciti a risolverlo, spero quindi in un vostro aiuto.
Come nelle altre discussioni che ho letto, posto il risultato del comando systemd-analyze blame:

Codice: Seleziona tutto

         25.255s udisks2.service
         24.155s grub-common.service
         23.438s apport.service
         23.270s thermald.service
         23.224s speech-dispatcher.service
         23.202s gpu-manager.service
         23.200s pppd-dns.service
         23.165s avahi-daemon.service
         10.587s mnt-win10.mount
          7.573s dev-sda7.device
          7.444s accounts-daemon.service
          6.506s NetworkManager-wait-online.service
          5.440s mnt-dati.mount
          3.297s rsyslog.service
          2.562s slapd.service
          2.509s ModemManager.service
          2.221s NetworkManager.service
          2.182s colord.service
          2.082s user@1000.service
          2.027s systemd-logind.service
          1.981s lightdm.service
          1.847s networking.service
          1.786s apache2.service
          1.512s systemd-rfkill.service
          1.421s plymouth-start.service
          1.385s systemd-udevd.service
          1.023s dev-mqueue.mount
          1.020s ufw.service
           957ms systemd-backlight@backlight:acpi_video0.service
           935ms systemd-tmpfiles-setup-dev.service
           898ms systemd-modules-load.service
           858ms systemd-backlight@backlight:acpi_video1.service
           818ms systemd-journald.service
           804ms sys-kernel-debug.mount
           804ms dev-hugepages.mount
           709ms apparmor.service
           633ms systemd-backlight@backlight:radeon_bl0.service
           575ms iio-sensor-proxy.service
           404ms systemd-random-seed.service
           385ms wpa_supplicant.service
           312ms systemd-sysctl.service
           260ms kmod-static-nodes.service
           252ms systemd-tmpfiles-setup.service
           232ms systemd-journal-flush.service
           209ms upower.service
           184ms irqbalance.service
           180ms polkitd.service
           143ms systemd-remount-fs.service
           136ms systemd-localed.service
           132ms systemd-update-utmp.service
           130ms systemd-udev-trigger.service
           121ms systemd-tmpfiles-clean.service
           117ms sys-fs-fuse-connections.mount
           106ms console-setup.service
            70ms ondemand.service
            57ms plymouth-read-write.service
            43ms systemd-hostnamed.service
            27ms systemd-timesyncd.service
            14ms alsa-restore.service
             7ms dns-clean.service
             6ms systemd-user-sessions.service
             5ms ureadahead-stop.service
             5ms systemd-update-utmp-runlevel.service
             4ms rtkit-daemon.service
             4ms resolvconf.service
             3ms rc-local.service
             1ms plymouth-quit-wait.service
           493us snapd.socket

Un grazie anticipato a tutti

[GjMan78]

Lento e veloce sono termini soggettivi e parecchio relativi.
Nel caso specifico relativi all'hardware... di che pc parliamo?

[Eremita83]

Parliamo di un hp... modello G62.. un i3 con 4 gb di ram scheda video ati

Nb. scusa il ritardo della risposta, ma pensavo di ricevere una mail/notifica nel caso in cui qualcuno rispondesse al post.

[GjMan78]

Tempi di caricamento davvero troppo elevati per quell'hardware.

Posta

Codice: Seleziona tutto

cat /etc/fstab

Codice: Seleziona tutto

sudo blkid

Codice: Seleziona tutto

systemctl --failed

Codice: Seleziona tutto

systemd-analize critical-chain

[Eremita83]

Ecco:

Codice: Seleziona tutto

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda7 during installation
UUID=320437d7-35db-4caf-8f6d-28f236c4f5f3 /               ext4    errors=remount-ro 0       1
# /mnt/dati was on /dev/sda5 during installation
UUID=4214DB6114DB570F /mnt/dati       ntfs    defaults,umask=007,gid=46 0       0
# /mnt/win10 was on /dev/sda2 during installation
UUID=F648EEE548EEA419 /mnt/win10      ntfs    defaults,umask=007,gid=46 0       0
# swap was on /dev/sda6 during installation
UUID=788910c2-8e48-4286-be16-2250d8068776 none            swap    sw              0       0

Codice: Seleziona tutto

/dev/sda1: LABEL="SYSTEM" UUID="28CAEC64CAEC2FAC" TYPE="ntfs" PARTUUID="cd5f8e42-01"
/dev/sda2: LABEL="OS" UUID="F648EEE548EEA419" TYPE="ntfs" PARTUUID="cd5f8e42-02"
/dev/sda4: LABEL="RECOVERY" UUID="94669AAC669A8F1C" TYPE="ntfs" PARTUUID="cd5f8e42-04"
/dev/sda5: LABEL="Volume" UUID="4214DB6114DB570F" TYPE="ntfs" PARTUUID="cd5f8e42-05"
/dev/sda6: UUID="da17c66d-7a54-4e14-8da9-cbaaecd01241" TYPE="swap" PARTUUID="cd5f8e42-06"
/dev/sda7: UUID="320437d7-35db-4caf-8f6d-28f236c4f5f3" TYPE="ext4" PARTUUID="cd5f8e42-07"
/dev/sdb1: SEC_TYPE="msdos" UUID="4A9F-24F2" TYPE="vfat" PARTUUID="70707573-01"

Codice: Seleziona tutto

  UNIT                  LOAD   ACTIVE SUB    DESCRIPTION
[color=#FF0000]● snapd.refresh.service[/color] loaded [color=#FF0000]failed failed[/color] Automatically refresh installed snaps

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

Codice: Seleziona tutto

The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @2min 13.970s
└─multi-user.target @2min 13.970s
  [color=#FF0000]└─slapd.service @2min 9.437s +4.532s[/color]
    └─network-online.target @2min 9.425s
      └─NetworkManager-wait-online.service @2min 652ms +8.772s
        [color=#FF0000]└─NetworkManager.service @1min 57.336s +3.309s
          └─dbus.service @1min 33.185s[/color]
            └─basic.target @1min 33.151s
              └─sockets.target @1min 33.151s
                [color=#FF0000]└─snapd.socket @1min 33.107s +43ms[/color]
                  └─sysinit.target @1min 32.974s
                    [color=#FF0000]└─apparmor.service @13.332s +4.997s[/color]
                      └─local-fs.target @13.127s
                       [color=#FF0000] └─mnt-win10.mount @11.419s +1.707s[/color]
                          └─dev-disk-by\x2duuid-F648EEE548EEA419.device @11.349s

Grazie

Nb. credevo che si potesse usare il tag colore dentro il tag codice.... invece no

[GjMan78]

Prova a disabilitare il montaggio automatico delle partizioni ntfs e controlla se la situazione migliora.

Commenta queste righe nel file /etc/fstab

Codice: Seleziona tutto

UUID=4214DB6114DB570F /mnt/dati       ntfs    defaults,umask=007,gid=46 0       0
UUID=F648EEE548EEA419 /mnt/win10      ntfs    defaults,umask=007,gid=46 0       0

[Eremita83]

Disabilitate le due righe... non noto nessun miglioramento.

Ri-posto l'output del comando systemd-analyze blame:

Codice: Seleziona tutto

          24.646s grub-common.service
         10.234s dev-sda7.device
          9.808s apparmor.service
          8.439s accounts-daemon.service
          8.122s snapd.firstboot.service
          7.062s NetworkManager-wait-online.service
          5.239s udisks2.service
          3.918s ModemManager.service
          3.861s networking.service
          3.466s NetworkManager.service
          3.277s thermald.service
          3.274s rsyslog.service
          3.270s avahi-daemon.service
          3.171s console-setup.service
          2.852s slapd.service
          2.083s colord.service
          2.083s user@1000.service
          1.936s keyboard-setup.service
          1.899s apache2.service
          1.805s systemd-tmpfiles-setup-dev.service
          1.767s gpu-manager.service
          1.599s dns-clean.service
          1.516s systemd-update-utmp.service
          1.515s lightdm.service
          1.486s iio-sensor-proxy.service
          1.383s systemd-tmpfiles-setup.service
          1.344s systemd-journald.service
          1.283s systemd-udevd.service
          1.277s systemd-backlight@backlight:acpi_video0.service
          1.126s systemd-modules-load.service
          1.100s systemd-backlight@backlight:acpi_video1.service
           986ms systemd-timesyncd.service
           977ms systemd-rfkill.service
           938ms systemd-logind.service
           876ms sys-kernel-debug.mount
           875ms dev-mqueue.mount
           688ms irqbalance.service
           610ms ufw.service
           609ms kmod-static-nodes.service
           536ms dev-hugepages.mount
           517ms systemd-random-seed.service
           516ms systemd-udev-trigger.service
           452ms systemd-sysctl.service
           436ms systemd-backlight@backlight:radeon_bl0.service
           333ms apport.service
           303ms polkitd.service
           278ms wpa_supplicant.service
           255ms resolvconf.service
           199ms upower.service
           144ms systemd-journal-flush.service
           114ms systemd-remount-fs.service
           103ms systemd-hostnamed.service
            67ms ondemand.service
            61ms speech-dispatcher.service
            30ms systemd-user-sessions.service
            22ms plymouth-start.service
            22ms setvtrgb.service
            18ms plymouth-read-write.service
            14ms alsa-restore.service
            11ms systemd-update-utmp-runlevel.service
             8ms pppd-dns.service
             8ms snapd.boot-ok.service
             6ms sys-fs-fuse-connections.mount
             6ms rtkit-daemon.service
             5ms ureadahead-stop.service
             4ms rc-local.service
             2ms plymouth-quit-wait.service
             2ms snapd.socket

e del comando systemd-analyze:

Codice: Seleziona tutto

Startup finished in 10.014s (kernel) + 3min 3.527s (userspace) = 3min 13.542s

3 minuti???

Nb. c'è la possibilità di ricevere una mail in caso di risposte ai post sul forum?

Grazie

[trekfan1]

In alto c'è il link "Visualizza propri interventi" per visualizzare le discussioni a cui si è ricevuto risposta, altrimenti in basso c'è la voce "Abbonati alla discussione", per il tuo problema: apri il gestore dischi (DISKS) di ubuntu e guarda lo stato SMART altrimenti posta l'output di

Codice: Seleziona tutto

sudo smartctl -a /dev/sda

se non è installato installa smartmontools (che lo contiene) con

Codice: Seleziona tutto

sudo apt install smartmontools

[Eremita83]

In alto c'è il link "Visualizza propri interventi" per visualizzare le discussioni a cui si è ricevuto risposta, altrimenti in basso c'è la voce "Abbonati alla discussione", per il tuo problema: apri il gestore dischi (DISKS) di ubuntu e guarda lo stato SMART altrimenti posta l'output di

Codice: Seleziona tutto

sudo smartctl -a /dev/sda

se non è installato installa smartmontools (che lo contiene) con

Codice: Seleziona tutto

sudo apt install smartmontools

ecco a te:

Codice: Seleziona tutto

smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 5400.6
Device Model:     ST9500325AS
Serial Number:    5VEG95MD
LU WWN Device Id: 5 000c50 037e181b5
Firmware Version: 0005HPM1
User Capacity:    500.107.862.016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sun Sep 18 10:47:17 2016 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 142) minutes.
SCT capabilities: 	       (0x103f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   117   099   006    Pre-fail  Always       -       136109472
  3 Spin_Up_Time            0x0002   098   098   000    Old_age   Always       -       0
  4 Start_Stop_Count        0x0033   098   098   000    Pre-fail  Always       -       2261
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   085   060   030    Pre-fail  Always       -       386076610
  9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       7993
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0033   098   098   020    Pre-fail  Always       -       2217
183 Runtime_Bad_Block       0x0032   100   253   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   097   097   000    Old_age   Always       -       3
188 Command_Timeout         0x0032   100   092   000    Old_age   Always       -       1723
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   065   041   045    Old_age   Always   In_the_past 35 (0 89 35 25 0)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       26
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       43
193 Load_Cycle_Count        0x0032   083   083   000    Old_age   Always       -       35101
194 Temperature_Celsius     0x0022   035   059   000    Old_age   Always       -       35 (0 13 0 0 0)
195 Hardware_ECC_Recovered  0x001a   054   044   000    Old_age   Always       -       136109472
196 Reallocated_Event_Count 0x0033   100   100   036    Pre-fail  Always       -       0
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 3
	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 3 occurred at disk power-on lifetime: 2322 hours (96 days + 18 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 f4 d8 57 05  Error: UNC at LBA = 0x0557d8f4 = 89643252

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 78 f0 d8 57 e5 00      00:00:37.665  READ DMA EXT
  25 00 78 f0 d8 57 e5 00      00:00:30.003  READ DMA EXT
  25 00 78 48 92 55 e5 00      00:00:21.080  READ DMA EXT
  25 00 78 d0 91 55 e5 00      00:00:21.068  READ DMA EXT
  25 00 78 b8 9b 45 e5 00      00:00:12.429  READ DMA EXT

Error 2 occurred at disk power-on lifetime: 2322 hours (96 days + 18 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 f4 d8 57 05  Error: UNC at LBA = 0x0557d8f4 = 89643252

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 78 f0 d8 57 e5 00      00:00:30.003  READ DMA EXT
  25 00 78 48 92 55 e5 00      00:00:21.080  READ DMA EXT
  25 00 78 d0 91 55 e5 00      00:00:21.068  READ DMA EXT
  25 00 78 b8 9b 45 e5 00      00:00:12.429  READ DMA EXT
  25 00 78 40 9b 45 e5 00      00:00:12.420  READ DMA EXT

Error 1 occurred at disk power-on lifetime: 2322 hours (96 days + 18 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 f4 d8 57 05  Error: UNC at LBA = 0x0557d8f4 = 89643252

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 78 48 92 55 e5 00      00:00:21.080  READ DMA EXT
  25 00 78 d0 91 55 e5 00      00:00:21.068  READ DMA EXT
  25 00 78 b8 9b 45 e5 00      00:00:12.429  READ DMA EXT
  25 00 78 40 9b 45 e5 00      00:00:12.420  READ DMA EXT
  25 00 78 c8 9a 45 e5 00      00:00:12.418  READ DMA EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      7453         -
# 2  Short offline       Completed without error       00%      7442         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[Marym]

Se ti può consolare anche il mio I7 con 8 gb di ram ci impiega un po' più di 3 minuti, ha un disco Seagate a 5400 come il tuo, e tempo fa ho fatto un post simile al tuo. Siamo giunti alla conclusione che qualche diffettuccio del hdd c'è, ovviamente insufficiente per una sostituzione in garanzia, ed ora non lo è più, dunque non mi pongo più il problema, finchè dura...e comunque non da altri problemi a parte la lentezza in avvio.
Il tuo disco ad occhio è messo peggio, però aspetta il parere dei più esperti.
Se hai Windows puoi provare il tool di diagnostica Seagate, cioè Seatools.

[ziocane]

Ciao a tutti,

mi associo alla discussione in corso per segnalare il medesimo problema. Da anni effettuavo gli upgrade senza riscontrare particolari problemi, ma una volta aggiornato alla 16.04 ho notato dei rallentamenti del sistema e in particolare del boot. Ho imputato la causa al fatto che non avessi fatto l'installazione pulita. Oggi ho piallato tutto e reinstallato da 0, ma il boot rimane biblico.

Il portatile è un acer aspire 5553G con un AMD quad core e 4 GB di ram.


Allego i risultati dei test:

Codice: Seleziona tutto

marco@marco-Aspire-5553G:~$ systemd-analyze
Startup finished in 10.219s (kernel) + 2min 44.613s (userspace) = 2min 54.833

Codice: Seleziona tutto

marco@marco-Aspire-5553G:~$ systemd-analyze blame
    1min 32.382s apparmor.service
    1min 32.170s plymouth-read-write.service
      1min 859ms gpu-manager.service
         59.131s plymouth-quit-wait.service
          7.327s dev-sda1.device
          2.973s plymouth-start.service
          1.922s NetworkManager.service
          1.823s accounts-daemon.service
          1.605s ModemManager.service
          1.588s upower.service
          1.382s grub-common.service
          1.296s thermald.service
          1.078s systemd-udevd.service
          1.058s systemd-journald.service
           939ms keyboard-setup.service
           927ms systemd-udev-trigger.service
           866ms systemd-tmpfiles-setup-dev.service
           689ms networking.service
           666ms iio-sensor-proxy.service
           631ms systemd-modules-load.service
           569ms systemd-user-sessions.service
           563ms avahi-daemon.service
           504ms dev-mqueue.mount

Codice: Seleziona tutto

marco@marco-Aspire-5553G:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=47b89f6a-1ea0-4dc7-b818-a6068363b2be /               ext4    errors=remount-ro 0       1
# /Dati was on /dev/sda7 during installation
UUID=b8ca2419-5d31-4f20-87c1-d43926c04787 /Dati           ext4    defaults        0       2
# /home was on /dev/sda5 during installation
UUID=fbf15813-3b59-4ca3-a622-ab922d234f8f /home           ext4    defaults        0       2
# swap was on /dev/sda6 during installation
UUID=7eee7372-7136-4ef5-b2ac-0a779a4de8a3 none            swap    sw              0       0

Codice: Seleziona tutto

marco@marco-Aspire-5553G:~$ sudo blkid
[sudo] password di marco: 
/dev/sda1: UUID="47b89f6a-1ea0-4dc7-b818-a6068363b2be" TYPE="ext4" PARTUUID="000eef48-01"
/dev/sda5: UUID="fbf15813-3b59-4ca3-a622-ab922d234f8f" TYPE="ext4" PARTUUID="000eef48-05"
/dev/sda6: UUID="7eee7372-7136-4ef5-b2ac-0a779a4de8a3" TYPE="swap" PARTUUID="000eef48-06"
/dev/sda7: UUID="b8ca2419-5d31-4f20-87c1-d43926c04787" TYPE="ext4" PARTUUID="000eef48-07"

Codice: Seleziona tutto

marco@marco-Aspire-5553G:~$ systemctl list-unit-files
UNIT FILE                                  STATE   
proc-sys-fs-binfmt_misc.automount          static  
org.freedesktop.hostname1.busname          static  
org.freedesktop.locale1.busname            static  
org.freedesktop.login1.busname             static  
org.freedesktop.network1.busname           static  
org.freedesktop.resolve1.busname           static  
org.freedesktop.systemd1.busname           static  
org.freedesktop.timedate1.busname          static  
dev-hugepages.mount                        static  
dev-mqueue.mount                           static  
proc-sys-fs-binfmt_misc.mount              static  
sys-fs-fuse-connections.mount              static  
sys-kernel-config.mount                    static  
sys-kernel-debug.mount                     static  
acpid.path                                 enabled 
cups.path                                  enabled 
systemd-ask-password-console.path          static  
systemd-ask-password-plymouth.path         static  
systemd-ask-password-wall.path             static  
systemd-networkd-resolvconf-update.path    static  
accounts-daemon.service                    enabled 
acpid.service                              disabled

Al momento ho provato a far partire il sistema in maniera testuale ma non noto problematiche rilevanti.
Ho modificato il bios da ahci boot a ide boot
Ho tolto qualche servizio all'avvio (orca, bluetooth)

Idee?

Grazie per l'eventuale aiuto.

Ciao
MRC

[trekfan1]

Test dell'HD?

[ziocane]

Ciao Trek,

grazie per la celere risposta. Il gestore di dischi dice che "Il disco è in buono stato".
Dici sia il caso di fare test più approfonditi?

Grazie

ciao
MRC

[trekfan1]

Posta la schermata dei dati smart

[ziocane]

Ciao Trek,

allego lo screenshot.

Grazie
MRC

[Marym]

Devi premere il tasto menù in alto, e selezionare 'dati smart', e postare l'immagine, è quella che diceva trek.

[ziocane]

Azz, sono proprio uno scemo...

Eccolo!E..grazie!

[Marym]

I dati smart vanno bene.
Il problema, se c'è, è da cercare altrove.
Dalla mia esperienza, provando altre distro, le Mint o Kubuntu, i tempi di avvio si son ridotti notevolmente.
Kubuntu si avvia in 30 secondi, contro Ubuntu, 3 minuti e qualcosa.

[ziocane]

Ciao,grazie della risposta.

Che ubuntu si sia appesantito è cosa nota, però trovo strano che nel mio PC le ripercussioni siano solo al boot.
Non sono un guru ma noto che apparmor e plymouth ci mettono tanto ad avviarsi. Se togli quei due minuti e mezzo mi sembra che si ritorni a una quarantina di secondi di avvio che secondo me sono la norma se non si ha un ssd.

Grazie
Ciao
MRC