Physical server. B&R

[noah]

Hello, nice to meet you.

As a test, a backup recovery was performed on a physical server environment.
and, Backup succeeded normally with an active full backup.
But, I booted a server from the same vendor(other model) using the rescue media and the restore was successful and the server booted. After selecting the Linux kernel, it stops at Reached target basic system.

boot mode is uefi mode

[HannesK]

Hello,

it stops at Reached target basic system.

can you describe a bit more what that means? Single user mode?

boot mode is uefi mode

on source and target? or are we talking about BIOS to UEFI restores?

in any case: what is the support case number for the problem? What did Veeam support say about the issue?

Thanks,
Hannes

[noah]

So how should we proceed?
The same goes for creating a boot image in uefi mode.
The boot mode of the source is uefi and the boot mode of the target is also uefi.

[noah]

can you describe a bit more what that means? Single user mode?



Message after selecting kernel version in Linux

Code: Select all

==========================================
dracut-initqueue[]: Warning: dracut initqueue timeout - starting timeout scripts
dracut-initqueue[]: Warning: dracut initqueue timeout - starting timeout scripts
dracut-initqueue[]: Warning: dracut initqueue timeout - starting timeout scripts
dracut-initqueue[]: Warning: dracut initqueue timeout - starting timeout scripts
dracut-initqueue[]: Warning: Could not boot

After that it enters dracut mode.

on source and target? or are we talking about BIOS to UEFI restores?

The same goes for creating a boot image in uefi mode.
The boot mode of the source is uefi and the boot mode of the target is also uefi.

[PTide]

Hi,

Since you've mentioned that you restored to another model, it looks like your initramfs might be missing some drivers that are required to mount your storage.

Therefore, I need you to answer the following questions:

1. Is there anything else after dracut-initqueue[]: Warning: Could not boot string?

I would expect a message like Warning: /dev/vgroot/root does not exist or some UUID.

2. Do you have LVM configured in place?


Also I'd suggest you to take a look at this KB article. It contains a brief explanation of the issue (which I think you've encountered), and steps to fix that.

Thanks!