OMV Restore failing

Whiskeysquirrel · Oct 15th 2023

Hey Folks,

So the SSD where my OMV install lived finally died... Luckily I had a backup taken with the fsarchiver plugin. Unfortunately when I attempt to restore using the stickied instructions it fails... Hoping someone can help me confirm I'm out of luck and should move on with a new install or if there is hope....

One point of confusion is, I thought I had an EFI install and thought I copied those over, but my backup files don't include this, perhaps this is the issue? As a result I start the restore process by formatting my new disk as ms-dos and then restore the partition tables which creates 3 ext4 partitions, and unallocated space. I ignore the gparted msg about expanding.

sdb1 - boot, esp: 512MB

sdb2 - 95.42GB, System?

sdb3 - swap

The next step to restore the FS using fsarchiver restfs fails with the following...

Code

[root@sysrescue ~]# fsarchiver restfs /mnt/backup/HomeAssistant\ Backups/OMV/backup-omv-28-May-2023_00-00-01.fsa id=0,dest=/dev/sdb2 -v
============= extracting filesystem 0 =============
filesys.c#132,devcmp(): Warning: node for device [/dev/sde5] does not exist in /dev/
executing [mke2fs -V]...
command [mke2fs -V] returned 0
executing [mke2fs -V]...
command [mke2fs -V] returned 0
executing [mke2fs  -q  -F  -b 4096  -U bc13a382-864e-48f6-ad86-77ac1385338d  -I 256  -r 1  -O has_journal,ext_attr,resize_inode,dir_index,^sparse_super2,^fast_commit,^orphan_file,filetype,extent,^journal_dev,flex_bg,^meta_bg,^mmp,64bit,^inline_data,^ea_inode,^large_dir,large_file,huge_file,sparse_super,^uninit_bg,dir_nlink,extra_isize,^bigalloc,metadata_csum,^project    /dev/sdb2]...
command [mke2fs  -q  -F  -b 4096  -U bc13a382-864e-48f6-ad86-77ac1385338d  -I 256  -r 1  -O has_journal,ext_attr,resize_inode,dir_index,^sparse_super2,^fast_commit,^orphan_file,filetype,extent,^journal_dev,flex_bg,^meta_bg,^mmp,64bit,^inline_data,^ea_inode,^large_dir,large_file,huge_file,sparse_super,^uninit_bg,dir_nlink,extra_isize,^bigalloc,metadata_csum,^project    /dev/sdb2] returned 0
executing [tune2fs  -o user_xattr,acl  -c 0  -i 0d  /dev/sdb2]...
command [tune2fs  -o user_xattr,acl  -c 0  -i 0d  /dev/sdb2] returned 0
Mount information: []
-[00][  0%][DIR     ] /
-[00][  0%][SYMLINK ] /vmlinuz.old
-[00][  0%][DIR     ] /opt
-[00][  0%][DIR     ] /opt/containerd
-[00][  0%][DIR     ] /opt/containerd/bin
-[00][  0%][DIR     ] /opt/containerd/lib
-[00][  0%][DIR     ] /ssl
-[00][  0%][DIR     ] /usr
-[00][  0%][DIR     ] /usr/share
-[00][  0%][DIR     ] /usr/share/info
-[00][  0%][REGFILEM] /usr/share/info/dir
-[00][  0%][REGFILEM] /usr/share/info/find.info-2.gz
-[00][  0%][REGFILEM] /usr/share/info/gnupg.info.gz
-[00][  0%][REGFILEM] /usr/share/info/gnupg-module-overview.png
-[00][  0%][REGFILEM] /usr/share/info/gzip.info.gz
-[00][  0%][REGFILEM] /usr/share/info/diffutils.info.gz
-[00][  0%][REGFILEM] /usr/share/info/find.info-1.gz
-[00][  0%][REGFILEM] /usr/share/info/gnupg.info-1.gz
-[00][  0%][REGFILEM] /usr/share/info/grub.info-1.gz
-[00][  0%][REGFILEM] /usr/share/info/find.info.gz
-[00][  0%][REGFILEM] /usr/share/info/grub.info-2.gz
-[00][  0%][REGFILEM] /usr/share/info/gnupg-card-architecture.png
-[00][  0%][REGFILEM] /usr/share/info/find-maint.info.gz
-[00][  0%][REGFILEM] /usr/share/info/sed.info.gz
-[00][  0%][REGFILE ] /usr/share/info/coreutils.info.gz
-[00][  0%][DIR     ] /usr/share/debianutils
 
-[00][  9%][SYMLINK ] /srv/dev-disk-by-label-WD8TB/config/letsencrypt/live/npm-2/privkey.pem
-[00][  9%][DIR     ] /srv/dev-disk-by-label-WD8TB/config/letsencrypt/live/npm-1
-[00][  9%][SYMLINK ] /srv/dev-disk-by-label-WD8TB/config/letsencrypt/live/npm-1/fullchain.pem
-[00][  9%][SYMLINK ] /srv/dev-disk-by-label-WD8TB/config/letsencrypt/live/npm-1/chain.pem
-[00][  9%][SYMLINK ] /srv/dev-disk-by-label-WD8TB/config/letsencrypt/live/npm-1/cert.pem
-[00][  9%][SYMLINK ] /srv/dev-disk-by-label-WD8TB/config/letsencrypt/live/npm-1/privkey.pem
-[00][  9%][DIR     ] /srv/dev-disk-by-label-WD8TB/downloads
-[00][  9%][DIR     ] /srv/dev-disk-by-label-WD8TB/downloads/complete
-[00][  9%][DIR     ] /srv/dev-disk-by-label-WD8TB/downloads/incomplete
-[00][ 14%][REGFILE ] /srv/dev-disk-by-label-WD8TB/downloads/incomplete/video.mkv.part
[errno=22, Invalid argument]: archreader.c#507,archreader_read_block(): cannot read block (finalsize=513954) failed
oper_restore.c#802,extractar_restore_obj_regfile_unique(): queue_dequeue_block()=-5=FSAERR_ENDOFFILE for file(/srv/dev-disk-by-label-WD8TB/downloads/incomplete/video.mkv.part) failed
oper_restore.c#849,extractar_restore_obj_regfile_unique(): queue_dequeue_header() failed: cannot read footer dico
oper_restore.c#879,extractar_restore_obj_regfile_unique(): removing /tmp/fsa/20231015-131327-0008d078-00/srv/dev-disk-by-label-WD8TB/downloads/incomplete/video.mkv.part
oper_restore.c#996,extractar_extract_read_objects(): queue_check_next_item() failed: cannot read object from archive

Display More

Appreciate any help!... hope I can avoid a lot of pain... Otherwise how do folks feel about USB installs and just keeping a cloned USB handy? That seems like an easy approach.

chente · Oct 15th 2023

An easy way to do this, if you can't solve it any other way, is to do a clean installation of OMV and restore the copy of fsarchiver over that installation. You get rid of grub issues etc.

BlueCoffee · Oct 15th 2023

I could never restore my backup from the backup plugin after my SSD died. Had to start over again. Hope you have more luck than I did.

edit= and I tried the way chente is saying. never worked

macom · Oct 15th 2023

This might help

Post

How to restore OMV 4.X from backup-plugin to system SSD

My hardware setup is

- CPU x64
- RAID6 with 7 disks (yes, I will change to snapraid)
- SSD with operating system OMV4 connected to SATA port
- backup flash USB option (if SSD does not work, I plug in usb and restart)
- The BIOS boot order should be setup so that it boots firstly from the USB slot and secondly from the normal OMV disk. That way, if no USB is connected, the system will boot the normal operating system. But with USB connected it will boot the emergency option first. This comes in handy…

bvrulez

Jan 19th 2019

chente · Oct 15th 2023

Quote from BlueCoffee

never worked

Why didn't it work for you? I did it without problems a few months ago. What went wrong for you?

BlueCoffee · Oct 15th 2023

Quote from chente

Why didn't it work for you? I did it without problems a few months ago. What went wrong for you?

I think to backup was corrupted slowly over time when the main drive was failing I have a new setup now in case this happens again.

chente · Oct 15th 2023

Quote from BlueCoffee

I think to backup was corrupted slowly over time when the main drive was failing

That makes sense, yes.

Whiskeysquirrel · Oct 15th 2023

Fresh install and using fsarchiver to restore the filesystem actually went much further which was surprising given the original read error... from 9% to 36%, but still ultimately failed with a FSAERR_ENDOFFILE and cannot read object from archive error...

dumb question... Do I need to have my other media/app drives connected when doing this? I see a lot of references to Symlinks during the fsarchiver restore and those files live on other disks not attached at the moment...

Unless there are other ideas, If I scrap everything and go with a USB install are there any tips? e.g.: UEFI vs Legacy, flashmem plugin etc?

chente · Oct 15th 2023

Quote from Whiskeysquirrel

Fresh install and using fsarchiver to restore the filesystem actually went much further which was surprising given the original read error... from 9% to 36%, but still ultimately failed with a FSAERR_ENDOFFILE and cannot read object from archive error...

If you can't read that file it's of no use to you, you'll have to do a fresh install I guess.

Quote from Whiskeysquirrel

dumb question... Do I need to have my other media/app drives connected when doing this? I see a lot of references to Symlinks during the fsarchiver restore and those files live on other disks not attached at the moment...

It should not be necessary, once the system is restored you can connect them and everything will return to normal. Having them connected during this process could lead to errors and data loss that you can avoid by disconnecting those drives.

Quote from Whiskeysquirrel

Unless there are other ideas, If I scrap everything and go with a USB install are there any tips? e.g.: UEFI vs Legacy, flashmem plugin etc?

As long as the motherboard allows it, choose Legacy, uefi only causes headaches and problems. You need the flashmemory plugin if you are installing on a pendrive or SD card. If you install on an SSD it will also be beneficial but to a lesser extent.

OMV Restore failing

macom Oct 15th 2023

Participate now!

Similar Threads

Time To Replace Drives

openmediavault-nut 6.0.1-1 failing after update from openmediavault all 6.1.1-1 to openmediavault all 6.1.2-1

Tags