FWIW mine appears to have hung during a hidden (invisible to me) step
where it was attempting to set a MOK. I had to first kill the existing
dpkg, then edit /usr/sbin/update-secureboot-policy to change #!/bin/sh
to #!/bin/bash (I was getting a local variable error), then manually run
Hey folks, just piping in that I am also having this problem. I am on
an encrypted disk, and the build of the kernel modules just hangs.
Please let me know if there is anything I can provide to assist in
debugging.
Note that there appear to be two other related / duplicate bugs: 1769327
and
I'm happy to create a new bug report for this, however before I do I
wanted to follow up here first. I've been working on a bionic VM
template this week and the issue has resurfaced. Client (18.04) reboots
daily at 3:00 a.m., and somewhere between 30 minutes and 2 hours later,
the CIFS mount
That did it for me on Xenial.
root@client:~# uname -a
Linux client 4.4.0-98-generic #121~lp1729337 SMP Thu Nov 2 20:53:20 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
root@client:~# mount | grep share
//server/share on /mnt/share type cifs
FWIW I can confirm that adding sec=ntlmsspi fixed our issue with
4.4.0-98.
root@client:~# mount | grep share
//server/share on /mnt/share type cifs
Confirmed that 4.14-rc7 works fine, no error.
root@cf03:~# uname -a
Linux client 4.14.0-041400rc7-generic #201710292231 SMP Sun Oct 29 22:32:07 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
root@client:~# mount
... snip ...
//server/share on /mnt/share type cifs
Sorry, it doesn't seem to have fixed the issue. I installed the image,
extras, and both headers packages. No cloud or tools (they aren't
installed in our system usually).
root@client:~# uname -a
Linux client 4.4.0-98-generic #121~lp1729337 SMP Wed Nov 1 14:29:16 UTC 2017
x86_64 x86_64 x86_64
@jsalisbury I've got one machine from our cluster that's not been
downgraded so I can do any debugging or provide any additional
information that you might need. Let me know if there's anything I can
do to help.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
We have a cluster of servers that applied a security update overnight
and were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 were fine the night before, and are fine after
downgrading. The only error message CIFS would report, even
