環境
vsphere7
Centos8.1
Relax-and-Recover 2.6
rearでフルバックアップisoを作成して、同じスペックの仮想マシンを用意しisoで起動したのですがディスクを認識してくれずリストア出来ません…というかディスクとして認識してくれてない…
予想としては
bootだけうまいこと作成されていない様な出力が見られるからそれが原因かなと…以下抜粋
Did not find /boot/grub2/locale files (minor issue for UEFI ISO boot)
まずはインストール
dnf -y install rear syslinux-extlinux grub2-efi-x64-modules
設定ファイル OUTPUT=ISO OUTPUT_URL=nfs://192.168.1.96/mnt/public BACKUP=NETFS BACKUP_URL=iso:///media/bk/
からの実行
rear -v mkbackup
一応isoファイルは作成されるのですがログを見るとbootがそもそも作れてない?ような感じになってしまっております。
実行時の表示
Relax-and-Recover 2.6 / 2020-06-17 Running rear mkbackup (PID 33300) Using log file: /var/log/rear/rear-localhost.log Running workflow mkbackup on the normal/original system Using backup archive '/tmp/rear.DwWE1msPaWcMdyG/tmp/isofs/media/bk//backup.tar.gz' Using UEFI Boot Loader for Linux (USING_UEFI_BOOTLOADER=1) Using autodetected kernel '/boot/vmlinuz-4.18.0-348.2.1.el8_5.x86_64' as kernel in the recovery system Creating disk layout Using guessed bootloader 'EFI' (found in first bytes on /dev/sda) Verifying that the entries in /var/lib/rear/layout/disklayout.conf are correct ... Creating recovery system root filesystem skeleton layout Skipping 'virbr0': not bound to any physical interface. To log into the recovery system via ssh set up /root/.ssh/authorized_keys or specify SSH_ROOT_PASSWORD Trying to find what to use as UEFI bootloader... Trying to find a 'well known file' to be used as UEFI bootloader... Using '/boot/efi/EFI/centos/grubx64.efi' as UEFI bootloader file Copying logfile /var/log/rear/rear-localhost.log into initramfs as '/tmp/rear-localhost-partial-2021-12-16T11:07:05-05:00.log' Copying files and directories Copying binaries and libraries Copying all kernel modules in /lib/modules/4.18.0-348.2.1.el8_5.x86_64 (MODULES contains 'all_modules') Copying all files in /lib*/firmware/ Broken symlink '/usr/lib/modules/4.18.0-348.2.1.el8_5.x86_64/build' in recovery system because 'readlink' cannot determine its link target Broken symlink '/usr/lib/modules/4.18.0-348.2.1.el8_5.x86_64/source' in recovery system because 'readlink' cannot determine its link target Testing that the recovery system in /tmp/rear.DwWE1msPaWcMdyG/rootfs contains a usable system Creating recovery/rescue system initramfs/initrd initrd.cgz with gzip default compression Created initrd.cgz with gzip default compression (435033640 bytes) in 31 seconds Making backup (using backup method NETFS) Creating tar archive '/tmp/rear.DwWE1msPaWcMdyG/tmp/isofs/media/bk//backup.tar.gz' Archived 2229 MiB [avg 12207 KiB/sec] OK Archived 2229 MiB in 188 seconds [avg 12142 KiB/sec] GRUB2 modules to load: fat part_gpt xfs Did not find /boot/grub2/locale files (minor issue for UEFI ISO boot) Making ISO image Wrote ISO image: /var/lib/rear/output/rear-localhost.iso (2.7G) Copying resulting files to nfs location Saving /var/log/rear/rear-localhost.log as rear-localhost.log to nfs location Copying result files '/var/lib/rear/output/rear-localhost.iso /tmp/rear.DwWE1msPaWcMdyG/tmp/VERSION /tmp/rear.DwWE1msPaWcMdyG/tmp/README /tmp/rear.DwWE1msPaWcMdyG/tmp/rear-localhost.log' to /tmp/rear.DwWE1msPaWcMdyG/outputfs/localhost at nfs location Exiting rear mkbackup (PID 33300) and its descendant processes ... Running exit tasks
宗教上の理由からrearを使わなければいけなくて泣きそうになりながら色々調べているんですが解決できなくて。。。
有識者の方が居ましたらご教授下さい!
回答1件
あなたの回答
tips
プレビュー
バッドをするには、ログインかつ
こちらの条件を満たす必要があります。