Patching a recover ISO fails

[adrian_vg]

Hi all,

I'm trying to patch a recovery ISO for my WFH workstation, a HP z440 running Kubuntu 22.04 and it's kicking my behind... This has gone so smooth every time before, but not now. This is what I do; based on guide from https://helpcenter.veeam.com/docs/agent ... tml?ver=60.

I've also tried going via the text-GUI with the same results.
Then I downloaded the latest 6.1 build, as I was figuring the 6.0 build was somehow faulty.
I've also done this; https://www.veeam.com/kb4121.

Code: Select all

$ sudo -i
$ cd /root
$ df -h
Filesystem                  Size  Used Avail Use% Mounted on
tmpfs                       6.3G  4.0M  6.3G   1% /run
/dev/mapper/vgkubuntu-root  233G  136G   85G  62% /
tmpfs                        32G   50M   32G   1% /dev/shm
tmpfs                       5.0M  8.0K  5.0M   1% /run/lock
tmpfs                        32G  695M   31G   3% /tmp
/dev/md0                    2.7T  964G  1.7T  37% /home/adrian_vg/RAID0
/dev/sda1                   511M  6.1M  505M   2% /boot/efi
tmpfs                       6.3G  1.6M  6.3G   1% /run/user/1000
tmpfs                       6.3G   68K  6.3G   1% /run/user/0

Location of unpatched ISO-image, freshly downloaded from Veeam-repo.

Code: Select all

$ ll /root
-rw-rw-r-- 1 root root 714080256 dec 18 10:59 veeam-recovery-media-6.1.0.1498_x86_64.iso

Changed permissions to 777 thinking it might have something to do with them.

Code: Select all

$ ll /root/veeam_recovery_iso
drwxrwsrwx  2 root root    4096 dec 18 11:00 veeam_recovery_iso/

"--copy <additional_path>" seems optional according to the guide, so skipping that and only specify where the original ISO-image is and where to put the resulting patched ISO-image.
After the failed procedure, nothing is to be found in the output-folder.

Code: Select all

$ veeamconfig patchiso --efi --input ./veeam-recovery-media-6.1.0.1498_x86_64.iso --output ./veeam_recovery_iso/2023-12-18.veeam-recovery-media-6.1.0.1498_x86_64.iso

Creating custom Veeam Recovery Media...
Not a directory
Failed to remove directory: /tmp/veeam/livecd-{56283af2-6410-403b-a8de-796b20951dbb}/initramfs/lib/modules
Failed to copy modules to directory [/tmp/veeam/livecd-{56283af2-6410-403b-a8de-796b20951dbb}/initramfs]

I'm at a loss here. What can I do?
What is not a directory?
Why does the "wizard" say that the /tmp/veeam/live-cd* can't be removed, when in fact it is?

Any help, tricks, tips or insights are greatly appreciated - thanks!

[rovshan.pashayev]

Hello,

Try to do following:

Code: Select all

mkdir /veeam_recovery_iso
veeamconfig downloadiso --output /veeam_recovery_iso/
ls -l /veeam_recovery_iso #check the content of the directory
veeamconfig patchiso --efi --input /veeam_recovery_iso/veeam-recovery-amd64-6.0.0.iso --output /veeam_recovery_iso/veeam_recovery_iso/2023-12-18.veeam-recovery-amd64-6.0.0.iso

Result should be:

Code: Select all

Creating custom Veeam Recovery Media...
Custom Veeam Recovery Media has been created successfully

Make sure that /tmp has enough space.

Rovshan.

[adrian_vg]

Hello @rovshan.pashayev!

Shouldn't 32 GB be enough?

Filesystem Size Used Avail Use% Mounted on
tmpfs 32G 695M 31G 3% /tmp


Will try again the steps you mention.
Thanks.

[rovshan.pashayev]

Hello,

I would suggest making it (free) space at least equal to the root (/) filesystem.
As a temporary solution, you can attach an external drive, separate, and extend the /tmp directory.

Rovshan.

[adrian_vg]

Nope, failed again.

At no point during the ISO-creation does df say that space is too little - it doesn't fill up at all.
/tmp uses at the most 12% of the 32 GB available.

Code: Select all

root@lanfear2:/veeam_recovery_iso# veeamconfig patchiso --efi --input /veeam_recovery_iso/veeam-recovery-amd64-6.0.0.iso --output /veeam_recovery_iso/veeam_recovery_iso/2023-12-18.veeam-recovery-amd64-6.0.0.iso
Creating custom Veeam Recovery Media...
Not a directory
Failed to remove directory: /tmp/veeam/livecd-{a3c3795e-f7cd-45d4-ba17-dc9db7981977}/initramfs/lib/modules
Failed to copy modules to directory [/tmp/veeam/livecd-{a3c3795e-f7cd-45d4-ba17-dc9db7981977}/initramfs]
root@lanfear2:/veeam_recovery_iso#

[adrian_vg]

Hello,

I would suggest making it (free) space at least equal to the root (/) filesystem.
As a temporary solution, you can attach an external drive, separate, and extend the /tmp directory.

Rovshan.

Woah!
Okay, I'll try that.

Seems weird that it'd need that much space though.
You sure about that?

[rovshan.pashayev]

Hello,

Use "while" or "watch" CLI tools in the new terminal, to monitor /tmp or root(/) (assuming /tmp is sub directrory) space sizes, during patchiso.

Rovshan.

[adrian_vg]

Yupp, that's what I already do. That's how I can tell the 32 GB /tmp wasn't gettting full.

Anyway, extended /tmp to use an 458G external disk.
Will try the patching again in a sec.

[adrian_vg]

Heh, it worked!

Code: Select all

root@lanfear2:/veeam_recovery_iso# veeamconfig patchiso --efi --input /veeam_recovery_iso/veeam-recovery-amd64-6.0.0.iso --output /veeam_recovery_iso/veeam_recovery_iso/2023-12-18.veeam-recovery-amd64-6.0.0.iso
Creating custom Veeam Recovery Media...
Custom Veeam Recovery Media has been created successfully

But this is totally bonkers!
If a 32 GB /tmp isn't enough, how much space is actually needed to patch the ISO?

[rovshan.pashayev]

Hello,

I am glad that we found solution for you.
Regarding /tmp space size, it depends on root(/) filesystem.

Rovshan

[adrian_vg]

Yeah, my apologies - thanks for the assistance! I greatly appreciate the help!

Now, may I ask how the /tmp space depends on the rootfs?
I realise it's not the scope of this support-forum, but may I ask for a hint for further research?

As seen below, my rootfs is a 250 GB SSD-device and / uses it all via lvm.
Some time ago I decided to use a portion of my RAM for tmpfs (/tmp) to speed things up.
I have 64 GB RAM, so figured a 32 GB /tmp would do nicely, since I was rarely using much of the 64 GB RAM anyway...
I don't recall exactly how big the previous /tmp was, but I believe it was smaller than 32 GB.

Code: Select all

Filesystem                  Size  Used Avail Use% Mounted on
/dev/mapper/vgkubuntu-root  233G  138G   84G  63% /
tmpfs                        32G  8.5M   32G   1% /tmp

[rovshan.pashayev]

Hello,

Thank you for detailed information.
We will look into that.

Rovshan.

[rovshan.pashayev]

Hello Adrian,

I kindly request that you submit a support case along with the logs pertaining to the issue you faced. This will greatly assist in conducting a more thorough analysis.

Thank you,
Rovshan

[adrian_vg]

Hello @rovshan.pashayev,
I'll see if I can find the relevant logs.

[starsystem]

I ran into this issue creating recovery media on an openSUSE Tumbleweed Linux client. My /tmp is 16G tmpfs as well. The entire recovery media process from start to finish consumed <6G of space so it theoretically should have been fine.

After seeing the response here that it's looking for a /tmp with the same space as / I decided that I didn't want to take that route of adding storage to /tmp and expanding it.

What worked for me is that I noticed within /tmp it uses a folder named veeam. I removed that directory and replaced it with a symlink to a temporary /veeam directory I made outside of /tmp. This allowed the recovery media to be created successfully.

[adrian_vg]

A symlink works?

That's actually quite brilliant, and I wish I'd thought of that as well!
Thanks @starsystem!

[rovshan.pashayev]

Hello @adrian_vg

Could you please provide an update on whether you were able to find any logs related to the initial issue?

[adrian_vg]

@rovshan.pashayev

Sorry, I forgot about that.
Looking into it now.

[adrian_vg]

@rovshan.pashayev

Actually, how do I submit a support case?
I must enter a business email and this is a problem I have on WFH computer I use with Veeam Baclup agent for linux, so no company involved per se...

[adrian_vg]

I ran into this issue creating recovery media on an openSUSE Tumbleweed Linux client. My /tmp is 16G tmpfs as well. The entire recovery media process from start to finish consumed <6G of space so it theoretically should have been fine.

After seeing the response here that it's looking for a /tmp with the same space as / I decided that I didn't want to take that route of adding storage to /tmp and expanding it.

What worked for me is that I noticed within /tmp it uses a folder named veeam. I removed that directory and replaced it with a symlink to a temporary /veeam directory I made outside of /tmp. This allowed the recovery media to be created successfully.

This worked like a charm, thanks!