5.2.20 (failed run)
and the mount never came up.Code: Select all
[ 1.754370] vboxguest: Successfully loaded version 5.2.20 (interface 0x00010004) [ 1.757005] vboxsf: Successfully loaded version 5.2.20 (interface 0x00010004) [ 2.533071] VBoxService 5.2.20 r125813 (verbosity: 0) linux.amd64 (Oct 15 2018 16:24:17) release log 00:00:00.000281 main Log opened 2018-10-21T15:20:07.225851000Z [ 2.533113] 00:00:00.000367 main OS Product: Linux [ 2.533142] 00:00:00.000398 main OS Release: 4.4.0-137-generic [ 2.533166] 00:00:00.000425 main OS Version: #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 [ 2.533196] 00:00:00.000449 main Executable: /opt/VBoxGuestAdditions-5.2.20/sbin/VBoxService 00:00:00.000450 main Process ID: 984 00:00:00.000451 main Package type: LINUX_64BITS_GENERIC [ 2.534719] 00:00:00.001966 main 5.2.20 r125813 started. Verbose level = 0 [ 2.540834] sf_read_super_aux err=-71 [ 2.540933] sf_read_super_aux err=-71 [ 4.228552] FS-Cache: Loaded [ 4.242402] FS-Cache: Netfs 'cifs' registered for caching [ 4.242482] Key type cifs.spnego registered [ 4.242488] Key type cifs.idmap registered [ 4.248306] CIFS VFS: Error connecting to socket. Aborting operation. [ 4.248566] CIFS VFS: cifs_mount failed w/return code = -101 [ 4.253657] CIFS VFS: Error connecting to socket. Aborting operation. [ 4.253746] CIFS VFS: cifs_mount failed w/return code = -101 [ 4.263854] CIFS VFS: Error connecting to socket. Aborting operation. [ 4.264015] CIFS VFS: cifs_mount failed w/return code = -101 [ 4.269199] CIFS VFS: Error connecting to socket. Aborting operation. [ 4.269306] CIFS VFS: cifs_mount failed w/return code = -101 [ 4.314229] CIFS VFS: Error connecting to socket. Aborting operation. [ 4.314560] CIFS VFS: cifs_mount failed w/return code = -101 [ 4.397107] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 4.397381] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
5.2.14 (successful run, with the 5.2.20 GAs still installed)
though the mount was there by the time i looked for it. (edit: I THINK - I could be wrong about that. This is an irrelevant scenario though other than for diagnostic purposes).Code: Select all
[ 3.014231] vboxguest: Successfully loaded version 5.2.20 (interface 0x00010004) [ 3.015495] vboxsf: Successfully loaded version 5.2.20 (interface 0x00010004) [ 3.755233] VBoxService 5.2.20 r125813 (verbosity: 0) linux.amd64 (Oct 15 2018 16:24:17) release log 00:00:00.000086 main Log opened 2018-10-21T15:42:43.439315000Z [ 3.755273] 00:00:00.000152 main OS Product: Linux [ 3.755299] 00:00:00.000181 main OS Release: 4.4.0-137-generic [ 3.755324] 00:00:00.000207 main OS Version: #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 [ 3.755358] 00:00:00.000232 main Executable: /opt/VBoxGuestAdditions-5.2.20/sbin/VBoxService 00:00:00.000233 main Process ID: 983 00:00:00.000234 main Package type: LINUX_64BITS_GENERIC [ 3.757009] 00:00:00.001890 main 5.2.20 r125813 started. Verbose level = 0 [ 3.764704] sf_read_super_aux err=-71 [ 3.765206] sf_read_super_aux err=-71 [ 3.765264] 00:00:00.010130 automount Error: vbsvcAutoMountWorker: Could not mount shared folder 'elements' to '/media/sf_elements': Protocol error (71) [ 5.383665] random: nonblocking pool is initialized [ 5.665780] FS-Cache: Loaded [ 5.679665] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 5.679947] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 5.680985] FS-Cache: Netfs 'cifs' registered for caching [ 5.681159] Key type cifs.spnego registered [ 5.681164] Key type cifs.idmap registered [ 5.687239] CIFS VFS: Error connecting to socket. Aborting operation. [ 5.687317] CIFS VFS: cifs_mount failed w/return code = -101 [ 5.692140] CIFS VFS: Error connecting to socket. Aborting operation. [ 5.692328] CIFS VFS: cifs_mount failed w/return code = -101 [ 5.703537] CIFS VFS: Error connecting to socket. Aborting operation. [ 5.703742] CIFS VFS: cifs_mount failed w/return code = -101
5.2.14 (successful run, with the 5.2.14 GAs reinstalled)
and the mount was there.Code: Select all
[ 3.573519] vboxguest: Successfully loaded version 5.2.14 (interface 0x00010004) [ 3.574962] vboxsf: Successfully loaded version 5.2.14 (interface 0x00010004) [ 4.387001] VBoxService 5.2.14 r123301 (verbosity: 0) linux.amd64 (Jun 29 2018 12:37:51) release log 00:00:00.000064 main Log opened 2018-10-21T15:47:33.053366000Z [ 4.387042] 00:00:00.000131 main OS Product: Linux [ 4.387069] 00:00:00.000160 main OS Release: 4.4.0-137-generic [ 4.387094] 00:00:00.000186 main OS Version: #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 [ 4.387128] 00:00:00.000212 main Executable: /opt/VBoxGuestAdditions-5.2.14/sbin/VBoxService 00:00:00.000213 main Process ID: 1055 00:00:00.000213 main Package type: LINUX_64BITS_GENERIC [ 4.388196] 00:00:00.001278 main 5.2.14 r123301 started. Verbose level = 0 [ 4.394786] sf_read_super_aux err=-71 [ 4.394901] sf_read_super_aux err=-71 [ 4.394961] 00:00:00.008031 automount Error: vbsvcAutoMountWorker: Could not mount shared folder 'elements' to '/media/sf_elements': Protocol error (71) [ 5.772296] random: nonblocking pool is initialized [ 6.098582] FS-Cache: Loaded [ 6.112409] FS-Cache: Netfs 'cifs' registered for caching [ 6.112480] Key type cifs.spnego registered [ 6.112485] Key type cifs.idmap registered
(Ignore the "elements" SF - that's a portable drive. I left the message in the logs because it's a useful checkpoint).
I don't see anything useful in the VB log, but I haven't had coffee yet so I may be a bit slow.
This is just a note / PSA right now: I'll try to find time to look into it later in the week.