UPD: Re: РЕШЕНО Долгая загрузка 18.04

[RB]

UPD:

В Ubuntu 18.04 такие же проблемы - долгая загрука.

Файла /etc/initramfs-tools/conf.d/resume нет,

решение другое:

     Ubuntu 18.04 , how to diagnose/fix very slow boot - Ask Ubuntu
 
https://askubuntu.com/questions/1030867/ubuntu-18-04-how-to-diagnose-fix-very-slow-boot/1032761



  1.

     Edit the file |/etc/default/grub| file so that the string |noresume| is included in the
     |GRUB_CMDLINE_LINUX_DEFAULT| line, for example:

     |GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noresume" |

  2.

     Run this command to update GRUB:

     |sudo update-grub |

  3.

     Reboot the computer




========================================================================

27.05.2018 22:11, radiobox на mtu-net.ru пишет:
> Думал, что и в Ubuntu 18.04 такие же проблемы, поэтому написал сюда.
> 
> 
> 
> 
> Bug #1763611 “Lubuntu bionic boots slower than the other Ubuntu ...” : Bugs : ubiquity 
> package : Ubuntu
> 
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
> 
> "I followed the suggestion to modify
> /etc/initramfs-tools/conf.d/resume
> and replaced the line RESUME=UUID= ..... by RESUME=none "
> 
> "after modifying /etc/initramfs-tools/conf.d/resume as described it is necessary to do
> 
> sudo update-initramfs -u "
> 
> 
> 
> 
> Помогло
> 
> ~$ systemd-analyze time
> Startup finished in 2.850s (kernel) + 6.995s (userspace) = 9.845s
> graphical.target reached after 6.983s in userspace
> 
> 
> 
> 
> 
> Date: Mon, 21 May 2018 11:43:08 +0300
> From: RB <radiobox на mtu-net.ru>
> 
>>
>> Обновился до 18.04
>>
>> Долгая загрузка ~45 секунд:
>>
>> ~$ systemd-analyze
>> Startup finished in 35.673s (kernel) + 6.998s (userspace) = 42.671s
>> graphical.target reached after 6.974s in userspace
>>
>>
>>
>> фрагмент dmesg:
>>
>> ...
>> [    2.929796] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio2/input/input9
>> [   34.676981] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
>> ...
>>
>> /ets/fstab смотрел, /swap пробовал комментировать - не помогло.
>>
>> Переименовались UUID?
>> Сверял с blkid, кажется, те же.
>>
>> Что можно сделать?
> 
>