Restor of OMV backup results in non bootable disk

Dear all,

Dear auanasgheps ,

I bought two identical SanDisk 128 GB SSD for my OVM system now. I wanted to use the OMV backup plugin to create a backup of SSD1 and to restore it on SSD2. I used the option fsarchiver because it was recommended in the following link. I wanted to see, if I can restore an existing backup to a blank new drive but the drive, I got was not able to boot-up the system. The BIOS did not recognize the device as bootable. (Hint: My Intel N100 system supports UEFI.)

Link: [How-To] Restore OMV system backup made with openmediavault-backup plugin

Some steps described in the descriptions are not valid in the current version of OMV 7 anymore. So, I slightly adapted my procedure as follows:

Code

# Go to directory, where the backup is stored:
cd <path_to>/omvbackup

# Unmount partitions of the target SSD (if necessary):
sudo umount /dev/sdX1

# Delete existing partition table:
sudo wipefs -a /dev/sdb

# (I have a "virgin" disk now.)

# Restore old partition table to the new disk:
sudo sfdisk /dev/sdX < backup-omv-2024-09-07_10-30-35_2.sfdisk

# Restore system drive:
dd if=backup-omv-2024-09-07_10-30-35.grubparts of=/dev/sdX bs=512

# Unpack UEFI partition:
zstd -d backup-omv-2024-09-07_10-30-35.espdd.zst

# Restore UEFI partition:
dd if=backup-omv-2024-09-07_10-30-35.espdd of=/dev/sdX1 bs=512

# Restore system partition:
fsarchiver restfs backup-omv-2024-09-07_10-30-35.fsa id=0,dest=/dev/sdX2 -v

# Optional: If you want to mount both disks in one system, they should not have the same UUID. You can change it to a random new ID as follows:
sudo e2fsck -f /dev/sdb2
sudo tune2fs -U random /dev/sdb2

# Check the UUID of all disk:
lsblk -f

# Delete unpacked file:
rm backup-omv-2024-09-07_10-30-35.espdd

Weniger anzeigen

These are the steps I have done. No step caused any error message. I just wonder why I don't need to restore any data on partition sdX3.

When I now reboot the system it does not start. Does anybody have any idea what went wrong?

Thank you and regards,

Mic.

I don't want to clone a disk. I want to restore a backup. I just used a 2nd SSD to not to damage my "original" system disk,

I don't unterstand your question "What is sdX3 listed as in lsblk or blkid? If it is swap, then no need to restore any files to it." What do you mean. I cannot boot from the new disk so I cannot chaeck it.

Quote from BernH

Also your comment of wanting to make a backup f form one to the other, you did not say you are trying to test resoreability. It read like you are trying to make a clone for the use of emergency replacement.

Ah yes, yu are right. It is SWAP.

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 119,2G  0 disk
├─sda1        8:1    0   512M  0 part /boot/efi
├─sda2        8:2    0 117,8G  0 part /
└─sda3        8:3    0   977M  0 part [SWAP]

Quote from BernH

Regarding the inability to boot from the 2nd drive I told you that fsarchiver is a file backup utility. It can backup and restore files, but it does not re-create the properties of the partition or the filesystem. For booting that is created during the os install process when grub is installed. If you want to restore a backup made with fsarchiver, you would, as I already said, need to at least have the partitions and created and flagged correctly. The easiest way would be to do just a basic Debian server install on the 2nd drive. Then restore on top of that.

I used the OMV plugin for system backup. There is a fdisk file and a sfdisk file. How to use the files to restore a system?

What is the aim of this OMV plugin if it is not made for restoring a system disk?

Quote from auanasgheps

I will upgrade to OMV7 soon, that's why I don't have a direct feedback.

Maybe you can compare my steps above to check if an update is needed.

Main problem: The target device is not bootable. 🙁