Context : when I run the new VM Ubuntu via virtualbox with
ubuntu-18.04.4-desktop-amd64.iso under W10.
Error : the find below the log at the starting ubuntu : [Failed to start wait
until snpad is fully seeded.]
It's stuck and I have no prompt for more details (systemctl command).
Could you know
I see the same issue as Chris Hutzler(post above) while installing ubntu
18.04.2LTS on a machine with SSD only, and don't think any of the
workarounds (e.g. apt install something) will serve when trying to
install ubuntu in the first place - how should I proceeed?
--
You received this bug
I'm seeing this same thing when trying to install the latest 18.04.2LTS
during the ISO's boot process for installation if it helps anyone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Seems the root ccause is lack of /dev/sda or /dev/sdb. I am trying to install
ubuntu server on machine with hardware raid, no /dev/sda or dev/sdb. Instlaler
complaisn aand then enters the loop.
As soon as I remove the hard disks from raid, it works, so workaround- make
sure you have /dev/sda or
You might be right - installing haveged definitely didn't make any difference.
Pressing shift seemed to work last boot (could've gotten lucky too of course).
I'll see if I can find time to open a new bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Woonjas, if you're having an issue, it's probably not this one as the
problem was found and fixed.
Can you please open a separate bug, and include the same details
requested above for your machine, so we can investigate in more detail?
Thank you.
--
You received this bug notification because
I'm on snapd 2.34.2 with 4.15.0-33 kernel and I'm still running into
this. It takes me on average 3 tries to get my system to boot (I don't
have patience to wait to see if snapd decides to play ball or not)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm bug is fixed with following versions:
snapd 2.33.1+18.04ubuntu2
kernel 4.15.0-29-generic
Thanks :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when
"sudo apt get haveged" is workaround solution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when starting Ubuntu.
To manage notifications about this bug go to:
I have 18.04 install ed on SSD, btrfs and same problem :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when starting Ubuntu.
To manage notifications about this bug
@ Nathaniel
I'm also running a SSD on my real (not virtual) machine.
@ Gustavo
Thanks for the info and fix.
I can confirm that bug exists with snapd V2.33.1 and kernel V4.15.0-24
But snapd V2.33.1 and kernel V4.15.0-23 works, no problem.
I have not yet tried later versions of kernel.
--
You
When attempting to boot 18.04 on a virtualbox vm, this problem occurs if
I have "solid state drive" selected in the options for the virtual hard
disk. System will not boot due to start process running for snappy
daemon. If I uncheck "solid state drive", the system boots normally. Not
sure if this
The problem here is lack of entropy in the kernel. A CVE was reported in
the kernel related to low entropy, and the modification prevented the
data from going out. Unfortunately that means any programs at early boot
that attempted to obtain a few bytes of random data would get stuck,
potentially
Workaround to entirely remove snapd service (assuming you're not using
it for any programs):
sudo apt purge snapd ubuntu-core-launcher squashfs-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also affected by this. Included journalctl -u snapd output. Have
experienced boot times of up to 50min from hanging on the snapd service.
** Attachment added: "journalctl_-u_snapd.txt"
Will post data as requested later this week. Bug affects my home PC but
I'm away from home for a few days. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when
Also could you confirm the version of snapd in play. Finally, could you
try installing the current snapd from -proposed to see if the fix for
the same issue as bug 1779961 (which is a general randomness issue) also
fixes your scenario.
--
You received this bug notification because you are a
Could you add the output of «journalctl -u snapd» to this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when starting Ubuntu.
To manage notifications about
I believe this may be a different issue to bug 1779961. That bug is
(quote) "Boot stops at "Starting Initial cloud-init job (metadata
service crawler)..."
However in my case boot pauses and alternately displays "Failed to start
snappy daemon, see systemctl status snapd.service for details" and
This may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779961
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when starting Ubuntu.
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
21 matches
Mail list logo
