Recovery Media cannot mount backup-hd

[Hermann]

Hi,

I'm running Linux Mint 17.3 Cinnamon and Veeam Linux Agent 2.0.
My Western Digital Book 2 TB works fine with it, is auto-mounted, saves Veeam images and can restore files from veeam images under Linux Mint.

But the recovery cd 2.0 does neither auto-mount this hd nor it can manually be mounted.
Error: Child execution failed, exit code 16.

As the hd contains older veeam images made with veeam Linux Agent 1.0 I tried also the older recovery cd 1.0.
Same problem, different error:
Volume cannot be mounted, is already mounted or is busy, exit code 32.

Then I plugged in other hd (containing other data, no veeam images).
Veeam recovery auto-mount it and offers its partitions for backup-selection.

How can I find out what the problem is - what means "child execution failed" when I try to manually mount a local disk?
Any suggestions?

Thanks in advance

[ManOrs]

Hi,
how is the disk formatted?
(i mean both as partition scheme and filesystem)

Regards,
manuel

[Hermann]

Grazie per il riposto!

/dev/sdb1: LABEL="My-Book-S" UUID="793430245E121963" TYPE="ntfs"
/dev/sdb2: LABEL="S-Linux-Backups" UUID="ea35fe38-2581-4a58-ada6-018e809e6796" TYPE="ext4"

created by gparted and it says: partitiontable msdos

Saluti

[PTide]

Hi Hermann,

I'd like to ask a couple of clarifying questions:

But the recovery cd 2.0 does neither auto-mount this hd nor it can manually be mounted.
Error: Child execution failed, exit code 16.

So, even if you drop to shell of the recovery media (both v1 and v2) and try to use mount command on either of the partitions (ntfs or ext4) it gives you code 16 error, is that correct?

Then I plugged in other hd (containing other data, no veeam images).
Veeam recovery auto-mount it and offers its partitions for backup-selection.

This makes me wondering what are the differences between those two drives. Could you tell us?

Thanks

[Hermann]

Hi,

thanks for picking up my problem.

No, I got error code 16 (child execution failed, exit code 16. Mount failed) in menue "select backup location", then "mount local disk" and selecting there sda2

When I go to shell 'blkid' shows me all drives and all partitions, to my surprise drives are numbered a and c, not a and b.

/dev/nvme0n1: PTUUID="...." PTTYPE="dos"
/dev/nvme0n1p1:................................UUID="....."....TYPE="ext4".............................(Linux Mint 17.3)
/dev/sr0:.......LABEL="ISOIMAGE".......UUID=".....",...TPYE="iso9660" PTUUID="...." PTTYPE="dos"
/dev/sda1 .......
/dev/sda2: LABEL="S-Linux-Bckp"...UUID="......." TYPE="ext4"..............................(veeam images)
/dev/sdc1: LABEL="My-Book-T".......UUID="......." TYPE="ntfs"................................(media)

None of them can manually be mounted:
mkdir /media/veeam
mount /dev/sda2 /media/veeam
results in "mount: /dev/sda2 is already mounted or /media/veeam busy"
Same result for sdc1.

BUT when exit shell to the main menue, and 'restore volumes', then auto-mounted are shown:

Name..type.mount point
sda......usb /media/Live-CD qt.............blkid said sr0 !
sdc1....usb /media/My-Book-T.............(ntfs)

My attempt "mount local disk" in menue "select backup location" offers "select local disk":

Device.............size.........filesystem
sda2................175G........ext4........................(veeam-images)
nvme0n1p1:....................ext4........................(Linux Mint 17.3)

and selecting there sda2 shows "child execution failed, exit code 16. Mount failed".

No, I got no idea what could be the difference between the 2 drives.
Both WD My-Book 2 TB, formatted by gparted.
What further information could be useful to find the difference and error reaseon?

[PTide]

I think that you should contact our support team directly so they can investigate. Once you do please post your case ID.
Btw, does 'mount' command show sda2 as mounted?

Thanks