Trouble using mondo for Proxmox nodes...

I'm using mondo (apart in P2V migration ;-) to do bare metal restore
for my Proxmox-VE node.

Proxmox is, for the mondo point of view, simply a debian jessie with a
custom kernel, mostly from Ubuntu.

I've noted that sometime mondo fail on that node, and seems related to
kernel upgade: eg, if i upgrade the system (and the kernel), and i
DON'T reboot, mondo fail creating the boot image:

 [...]
 INFO: Call GetInitrdFilesystemToUse() with parameter /boot/vmlinuz-4.4.35-1-pve to get filesystem to use for initrd.
 INFO: GetInitrdFilesystemToUse(): called with parameter: /boot/vmlinuz-4.4.35-1-pve
 INFO: Found a non gzip compressed kernel /boot/vmlinuz-4.4.35-1-pve
 INFO: GetInitrdFilesystemToUse(): gzip magic found at lvOffset 18356.
 INFO: GetInitrdFilesystemToUse(): Filesytem to use for initial ram disk is initramfs.
 INFO: Creating a gzip'ed cpio (AKA initramfs) initrd image...
 INFO: MakeBootInitFile finished without error.
 INFO: Copying /var/tmp/mondo/scratch/mondo.scratch.68lY9S/images/*.gz to /var/tmp/mondo/mondo.tmp.Ilf69x/target/images
 INFO: Copying /boot/vmlinuz-4.4.35-1-pve to /var/tmp/mondo/mondo.tmp.Ilf69x/target/vmlinuz
 INFO: Copying /var/tmp/mondo/mondo.tmp.Ilf69x/initrd.img to /var/tmp/mondo/mondo.tmp.Ilf69x/target/initrd.img
 ----------- syslinux's conf --------------
 [...]
 ------------------------------------------
 INFO: Creating a 109252 KB empty file for boot device of the ISO image
 INFO: Creating a vfat filesystem on /var/tmp/mondo/mondo.tmp.Ilf69x/mindi-bootroot.img
 mkfs.fat 3.0.27 (2014-11-12)
 INFO: Mounting /var/tmp/mondo/mondo.tmp.Ilf69x/mindi-bootroot.img on /var/tmp/mondo/mondo.tmp.Ilf69x/mpt
 mount: wrong fs type, bad option, bad superblock on /dev/loop0,
        missing codepage or helper program, or other error
 
        In some cases useful info is found in syslog - try
        dmesg | tail or so.
 ERROR: Unable to mount /var/tmp/mondo/mondo.tmp.Ilf69x/mindi-bootroot.img on /var/tmp/mondo/mondo.tmp.Ilf69x/mpt
 INFO: Mindi 3.0.2-r3578 is exiting
 INFO: End date : sab  1 apr 2017, 06.58.14, CEST

on kernel/system log i got:

 Apr  1 06:54:11 capitanamerica kernel: [9204594.307868] msdos: disagrees about version of symbol module_layout
 Apr  1 06:54:11 capitanamerica systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 3763 (df)
 Apr  1 06:54:11 capitanamerica systemd[1]: Mounting Arbitrary Executable File Formats File System...
 Apr  1 06:54:11 capitanamerica mount[3764]: mount: unknown filesystem type 'binfmt_misc'
 Apr  1 06:54:11 capitanamerica kernel: [9204594.573979] binfmt_misc: disagrees about version of symbol module_layout
 Apr  1 06:54:11 capitanamerica systemd[1]: proc-sys-fs-binfmt_misc.mount mount process exited, code=exited status=32
 Apr  1 06:54:11 capitanamerica systemd[1]: Failed to mount Arbitrary Executable File Formats File System.
 Apr  1 06:54:11 capitanamerica systemd[1]: Unit proc-sys-fs-binfmt_misc.mount entered failed state.
 Apr  1 06:54:12 capitanamerica systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 3832 (df)
 Apr  1 06:54:12 capitanamerica systemd[1]: Mounting Arbitrary Executable File Formats File System...
 Apr  1 06:54:12 capitanamerica mount[3833]: mount: unknown filesystem type 'binfmt_misc'
 Apr  1 06:54:12 capitanamerica kernel: [9204595.109652] binfmt_misc: disagrees about version of symbol module_layout
 Apr  1 06:54:12 capitanamerica systemd[1]: proc-sys-fs-binfmt_misc.mount mount process exited, code=exited status=32
 Apr  1 06:54:12 capitanamerica systemd[1]: Failed to mount Arbitrary Executable File Formats File System.
 Apr  1 06:54:12 capitanamerica systemd[1]: Unit proc-sys-fs-binfmt_misc.mount entered failed state.
 Apr  1 06:54:44 capitanamerica systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 9441 (df)
 Apr  1 06:54:44 capitanamerica systemd[1]: Mounting Arbitrary Executable File Formats File System...
 Apr  1 06:54:44 capitanamerica mount[9442]: mount: unknown filesystem type 'binfmt_misc'
 Apr  1 06:54:44 capitanamerica systemd[1]: proc-sys-fs-binfmt_misc.mount mount process exited, code=exited status=32
 Apr  1 06:54:44 capitanamerica kernel: [9204627.654564] binfmt_misc: disagrees about version of symbol module_layout
 Apr  1 06:54:44 capitanamerica systemd[1]: Failed to mount Arbitrary Executable File Formats File System.
 Apr  1 06:54:44 capitanamerica systemd[1]: Unit proc-sys-fs-binfmt_misc.mount entered failed state.
 Apr  1 06:54:46 capitanamerica kernel: [9204629.590616] isofs: disagrees about version of symbol module_layout
 Apr  1 06:54:46 capitanamerica kernel: [9204629.595308] linear: disagrees about version of symbol module_layout
 Apr  1 06:54:46 capitanamerica kernel: [9204629.598771] raid0: disagrees about version of symbol module_layout
 Apr  1 06:54:46 capitanamerica kernel: [9204629.611858] raid6_pq: disagrees about version of symbol module_layout
 Apr  1 06:55:01 capitanamerica CRON[16774]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
 Apr  1 06:55:59 capitanamerica systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 9400 (mindi)
 Apr  1 06:55:59 capitanamerica systemd[1]: Mounting Arbitrary Executable File Formats File System...
 Apr  1 06:55:59 capitanamerica mount[6409]: mount: unknown filesystem type 'binfmt_misc'
 Apr  1 06:55:59 capitanamerica systemd[1]: proc-sys-fs-binfmt_misc.mount mount process exited, code=exited status=32
 Apr  1 06:55:59 capitanamerica systemd[1]: Failed to mount Arbitrary Executable File Formats File System.
 Apr  1 06:55:59 capitanamerica kernel: [9204702.259916] binfmt_misc: disagrees about version of symbol module_layout
 Apr  1 06:55:59 capitanamerica systemd[1]: Unit proc-sys-fs-binfmt_misc.mount entered failed state.
 Apr  1 06:55:59 capitanamerica systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 9400 (mindi)
 Apr  1 06:55:59 capitanamerica systemd[1]: Mounting Arbitrary Executable File Formats File System...
 Apr  1 06:55:59 capitanamerica kernel: [9204702.264524] binfmt_misc: disagrees about version of symbol module_layout
 Apr  1 06:55:59 capitanamerica mount[6413]: mount: unknown filesystem type 'binfmt_misc'
 Apr  1 06:55:59 capitanamerica systemd[1]: proc-sys-fs-binfmt_misc.mount mount process exited, code=exited status=32
 Apr  1 06:55:59 capitanamerica systemd[1]: Failed to mount Arbitrary Executable File Formats File System.
 Apr  1 06:55:59 capitanamerica systemd[1]: Unit proc-sys-fs-binfmt_misc.mount entered failed state.
 Apr  1 06:56:52 capitanamerica kernel: [9204755.312764] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
 Apr  1 06:56:52 capitanamerica kernel: [9204755.322133] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
 Apr  1 06:58:14 capitanamerica kernel: [9204838.056149] nls_iso8859_1: disagrees about version of symbol module_layout
 Apr  1 06:58:14 capitanamerica kernel: [9204838.056303] FAT-fs (loop0): IO charset iso8859-1 not found


My supposition is correct?
There's some way to prevent/fix that, without rebooting teh server?

Thanks.

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''          http://www.lanostrafamiglia.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
    http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot