[Risolto] avvio diventato lento dopo reinstallazione grub

Ciao a tutti ,
ieri a causa di un aggiornamento di windows insider preview,non lo aggiornavo da tanto ,ma visto il tempo libero … , ho dovuto reinstallare il grub , Fedora 31 non si avviava ,ma da un altro hd installato con F30 sono riuscito a rimettere tutto a posto.
Ma l’avvio è diventato molto lento. ho tentato varie sluzioni seguendo i post che sono sul forum ,ma non ho ottenuto molto.

$ systemd-analyze Startup finished in 2.910s (kernel) + 1min 23.419s (initrd) + 8.936s (userspace) = 1min 35.266s graphical.target reached after 3.487s in userspace

$ systemd-analyze blame 1min 22.610s dracut-initqueue.service > 6.448s NetworkManager-wait-online.service > 1.100s systemd-udev-settle.service > 748ms lvm2-monitor.service > 698ms udisks2.service > 678ms initrd-switch-root.service > 652ms systemd-logind.service > 593ms libvirtd.service > 550ms abrtd.service > 435ms firewalld.service > 353ms upower.service > 301ms systemd-udevd.service > 287ms systemd-machined.service > 267ms dnf-makecache.service > 231ms fwupd.service > 230ms sssd.service > 226ms systemd-journald.service > 166ms [email protected] > 141ms cups.service > 140ms ModemManager.service > 123ms initrd-parse-etc.service > 114ms avahi-daemon.service > 103ms rtkit-daemon.service

[code]$ systemd-analyze blame
1min 22.610s dracut-initqueue.service >
6.448s NetworkManager-wait-online.service >
1.100s systemd-udev-settle.service >
748ms lvm2-monitor.service >
698ms udisks2.service >
678ms initrd-switch-root.service >
652ms systemd-logind.service >
593ms libvirtd.service >
550ms abrtd.service >
435ms firewalld.service >
353ms upower.service >
301ms systemd-udevd.service >
287ms systemd-machined.service >
267ms dnf-makecache.service >
231ms fwupd.service >
230ms sssd.service >
226ms systemd-journald.service >
166ms [email protected] >
141ms cups.service >
140ms ModemManager.service >
123ms initrd-parse-etc.service >
114ms avahi-daemon.service >
103ms rtkit-daemon.service >

$ systemd-analyze critical-chain
The time when unit became active or started is printed after the “@” character.
The time the unit took to start is printed after the “+” character.

graphical.target @3.487s
└─multi-user.target @3.487s
└─libvirtd.service @2.892s +593ms
└─systemd-logind.service @2.237s +652ms
└─nss-user-lookup.target @2.233s
└─sssd.service @2.002s +230ms
└─basic.target @1.991s
└─dbus-broker.service @2.010s +68ms
└─dbus.socket @1.988s
└─sysinit.target @1.986s
└─systemd-update-utmp.service @1.977s +8ms
└─auditd.service @1.943s +33ms
└─systemd-tmpfiles-setup.service @1.898s +41ms
└─import-state.service @1.875s +22ms
└─local-fs.target @1.873s
└─home.mount @1.861s +11ms
└─[email protected]\x2duuid-ac9139f8\x2d20>
└─local-fs-pre.target @1.831s
└─lvm2-monitor.service @572ms +748ms
└─dm-event.socket @565ms
└─-.mount
└─systemd-journald.socket
└─-.mount
└─…
[/code]

[code]# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● mcelog.service loaded failed failed Machine Check Exception Logging Daemon

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.[/code]

# journalctl --disk-usage Archived and active journals take up 896.7M in the file system.

ma ho messo nel file /etc/systemd/journald.conf SystemMaxUse=250M

$ uname -r 5.6.6-200.fc31.x86_64

grazie
ciao

Ciao ,
scusate se aggiungo questo : ho provato a fare il boot con il kernel più vecchio ,dei tre in memoria, e l’avvio è decisamente più veloce.

[code]$ systemctl --state=failed
0 loaded units listed.

$ systemd-analyze
Startup finished in 2.938s (kernel) + 2.073s (initrd) + 9.422s (userspace) = 14.434s
graphical.target reached after 4.429s in userspace
[/code]

$ uname -r 5.5.16-200.fc31.x86_64

grazie
ciao

molto probabilmente era il kernel 5.6.6-200.fc31.x86_64 con dei problemi sulla mia macchina ,con altri kernel sembra risolto .
grazie
ciao