Mounting image failed. Please see server log file for details

/boot dir info:

total 151M
-rw-r–r-- 1 root root 1.2M Jan 19 08:06 abi-4.4.0-112-generic
-rw-r–r-- 1 root root 1.2M Feb 12 19:57 abi-4.4.0-116-generic
-rw-r–r-- 1 root root 1.2M Apr 2 14:05 abi-4.4.0-119-generic
-rw-r–r-- 1 root root 187K Jan 19 08:06 config-4.4.0-112-generic
-rw-r–r-- 1 root root 187K Feb 12 19:57 config-4.4.0-116-generic
-rw-r–r-- 1 root root 187K Apr 2 14:05 config-4.4.0-119-generic
drwxr-xr-x 5 root root 4.0K Apr 4 15:12 grub
-rw-r–r-- 1 root root 39M Mar 1 08:10 initrd.img-4.4.0-112-generic
-rw-r–r-- 1 root root 39M Apr 4 07:06 initrd.img-4.4.0-116-generic
-rw-r–r-- 1 root root 39M Apr 4 15:12 initrd.img-4.4.0-119-generic
-rw-r–r-- 1 root root 179K Jan 28 2016 memtest86+.bin
-rw-r–r-- 1 root root 181K Jan 28 2016 memtest86+.elf
-rw-r–r-- 1 root root 181K Jan 28 2016 memtest86+_multiboot.bin
-rw-r–r-- 1 root root 2.7K Feb 12 19:57 retpoline-4.4.0-116-generic
-rw-r–r-- 1 root root 2.7K Apr 2 14:05 retpoline-4.4.0-119-generic
-rw------- 1 root root 3.8M Jan 19 08:06 System.map-4.4.0-112-generic
-rw------- 1 root root 3.8M Feb 12 19:57 System.map-4.4.0-116-generic
-rw------- 1 root root 3.8M Apr 2 14:05 System.map-4.4.0-119-generic
-rwxr–r-- 1 root root 6.8M Jan 19 08:06 vmlinuz-4.4.0-112-generic
-rwxr–r-- 1 root root 6.9M Feb 12 19:57 vmlinuz-4.4.0-116-generic
-rwxr–r-- 1 root root 6.9M Apr 2 14:05 vmlinuz-4.4.0-119-generic

changed files to 644 from 744 and same error message.
Ran libguestfs-test-tool which ended with:

===== TEST FINISHED OK =====

Cancel that!
At least for now. I had not tried mounting an image after running libguestfs-test-tool.

Also works after reboot.

Thank you very much, indeed.

And… Back to not working. Same error as yesterday.

What kernel version are you running? I have had similar issues where debug mode says mount test is ok (that just means it found guestfs tools installed) but it won’t actually mount the images. If you add the debug environment variables for guestfs tools if should give you some errors pointing to supermin. UrBackup basically mounts the backup image in a supermin jail for system protection. On my systems, if they are running v4.13 kernel, the mainline kernel breaks supermin5 that liguestfs-tools uses.

If you download and compile the newest version of supermin5 and then re-install liguestfs-tools that may get everything working for you again.

This setup is running kernel version Linux 4.4.0 which, I believe, is the latest released to this v.16.04.3 ubuntu. I am planning on upgrading the 18.04 as soon as released. The thing is, when it worked for the first (and, so far, last time) I received a list of files and I even rebooted and could bring up a list of files after mounting the image via the web interface. When I attempted to mount the image the next day (system had not rebooted since successful testing the previous day), mounting failed.

I did not attempt to access any of the listed files. I was only testing by mounting an image.

In order to debug this I had to capture the exact command that urbackupsrv runs when it guestmounts an image.

I just continually ran a ‘ps’ while mounting selecting an image in the web interface to mount. Once I had the guestmount command, I then set the guestmount debug environment variables “export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1” and ran the same command the web interface was trying to run.

That’s what led me to discover the error in supermin which ultimately led me to the patch that fixed supermin for newer kernels.

You could attempt this same process to see if yields any results for why its not mounting.

Server version 2.2.11
Ubuntu 17.10 kernel 4.14.0

Edit: Upgraded kernel to 4.16.3, same result.

Have you tried what I wrote here:

Using the mount helper as root always fixes this problem for me but after a couple of days/updates/restarts (I don’t really know what breaks it) it stops working again.

Would be good to find out why it works after mounting as root so I could at least have a script run at startup to make sure that it works automatically.

1 Like

Your solution works!

P.S. No need to mount as urbackup, mounting as root is sufficient.

@DrRSatzteil
Now the mounting error has reappeared.
The server has not rebooted, and the urbackup service has not been restarted.

Yes this is kind of annoying. Still happens to me as well. Please let me know if you find out what’s causing this. For now I decided to not look deeper into it as long as I know how to fix this when I need this feature.

Any solution?
Now I run on Ubuntu 18.04, urBackup 2.2.11.
I trying to mount raw on btrfs.
Error:
Mounting image failed. Please see server log file for details.
Guestmount… libguestfs: error: /usr/bin/supermin exited with error status 1. To see full error messages you may need to enable debugging. Do: export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 and run the command again. For further information, read: http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs You can also run 'libguestfs-test-tool' and post the complete output into a bug report or message to the libguestfs mailing list.

@artyomtsybulkin I ended up switching to ext4, and now it works.

I switched to btrfs because need RAW images >2Tb. On ext4 it not applicable. Maybe it works on ZFS?

So far there have been two causes:

  • Newer kernel with older supermin causing a supermin boot problems. Should cause libguestfs-test-tool to fail. Make sure supermin is up to date and your kernel is distribution supported. If not complain about it on the distribution bug tracker.
  • Ubuntu kernel image permission problems (“for security reasons, won’t fix” https://bugs.launchpad.net/fuel/+bug/1467579). Newer UrBackup servers should fix those automatically. See my post here for how to discover Mounting image failed. Please see server log file for details

To debug change the user urbackup to have a login shell login as urbackup (su urbackup) then run export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1; urbackup_mount_helper mount clientname XXX_Image_C Image_C_XXXX.raw

1 Like

Does this issue solved?

I have the same problem.

Debug export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 didn’t give any information.
Only: libguestfs: error: /usr/bin/supermin exited with error status 1.

I saw many topics, try them all and didn’t find a solution.

Mounting from urbackup user doesn’t work, then mounting from root (works fine), and after that mounting from urbackup starts working too but only for a while.

#### run as urbackup
# su urbackup -s /bin/bash

#### enable debug
$ export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1

#### mount .raw image from urbackup user
$ urbackup_mount_helper mount win7_vm210_2 200620-1954_Image_C Image_C_200620-1954.raw
Guestmount...
libguestfs: error: /usr/bin/supermin exited with error status 1.
To see full error messages you may need to enable debugging.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libgue    stfs.org/guestfs-faq.1.html#debugging-libguestfs
    You can also run 'libguestfs-test-tool' and post the *complete* output
    into a bug report or message to the libguestfs mailing list.

$ libguestfs-test-tool
...
===== TEST FINISHED OK =====

$ exit


#### run as root
#### mount .raw image from root user - works fine!
# urbackup_mount_helper mount win7_vm210_2 200620-1954_Image_C Image_C_200620-1954.raw
Guestmount...

#### umount
# urbackup_mount_helper umount win7_vm210_2 200620-1954_Image_C Image_C_200620-1954.raw
Mountpoint: /media/BACKUP/urbackup/win7_vm210_2/200620-1954_Image_C_mnt
Guestunmount...

#### run as urbackup
#### mount again .raw image from urbackup user
# su urbackup -s /bin/bash

 #### mount .raw image from urbackup user
$ urbackup_mount_helper mount win7_vm210_2 200620-1954_Image_C Image_C_200620-1954.raw
Guestmount...
   ### Now it works fine but only for a while.

Environment: UrBackup Server 2.4.12, Debian 10, btrfs storage.

For some reason it seems to work for me now pretty reliable even though I did not change anything (of course a lot of possible relevant components have been updated in the meantime).

What happens on my instance now is that it takes a while to mount from the webinterface and then lets me know that mounting failed. However this is not true as I can see the mounted image when I go back to the backup list and then select the same image backup again.

After mount image from root from cli, for some time mount from web interface starts working too.

Some times it mounts without errors.
But sometimes same like you lets me know that mounting failed. However this is not true as I can see the mounted image when I go back to the backup list and then select the same image backup again.

Detailly I wrote about it here:

Nice work with your detailed bug report!

I never had the issue that the web interface becomes unreachable though but I can reproduce the mount failure you are describing at the end of your report.

Thanks! I hope developers will fix these issues with mount image backups.