Hi,
I have an Ubuntu 18.04 installation on a two hard disk computer along with a windows 10.
HDD 1 -> Windows 10
HDD 2 -> Windows 10 and Ubuntu 18.04
After boot, snapd related systems fail:
systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● snapd.seeded.service loaded failed failed Wait until snapd is fully seeded
● snapd.service loaded failed failed Snappy daemon
● snapd.socket loaded failed failed Socket activation for snappy daemon
snap version
snap 2.38+18.04
snapd unavailable
series -
uname -a & systemd-detect-virt
[1] 18682
Linux canbolat-Alienware-17-R5 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[1] + 18682 done uname -a
none
These are the logs:
journalctl -u snapd.service
– Reboot –
6月 09 10:44:15 canbolat-Alienware-17-R5 systemd[1]: Starting Snappy daemon…
6月 09 10:44:25 canbolat-Alienware-17-R5 snapd[1479]: AppArmor status: apparmor is enabled and all features are available
6月 09 10:44:26 canbolat-Alienware-17-R5 snapd[1479]: cannot run daemon: cannot determine core refresh time: lstat /snap/core/current: no such file or directory
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: snapd.service: Failed with result ‘exit-code’.
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: Failed to start Snappy daemon.
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: snapd.service: Triggering OnFailure= dependencies.
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: Stopped Snappy daemon.
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: Starting Snappy daemon…
6月 09 10:44:26 canbolat-Alienware-17-R5 snapd[1750]: AppArmor status: apparmor is enabled and all features are available
6月 09 10:44:26 canbolat-Alienware-17-R5 snapd[1750]: cannot run daemon: cannot determine core refresh time: lstat /snap/core/current: no such file or directory
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: snapd.service: Failed with result ‘exit-code’.
6月 09 10:44:26 canbolat-Alienware-17-R5 systemd[1]: Failed to start Snappy daemon.
As the logs say, /snap/core/current does not exist. I found a /snap/core18/current but not sure linking that to /snap/core/current would solve it.
Anny suggestions?