__ __ __ __ _____ _ _ _____ _ _ _
| \/ | \ \ / / | __ \ (_) | | / ____| | | | |
| \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | |
| |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | |
| | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | |
|_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
if you need WebShell for Seo everyday contact me on Telegram
Telegram Address : @jackleet
For_More_Tools:
# report about checks being done
if ls -l /sys/block/*/ | grep -q xen ; then
# if some disks are xen related then assume this is a XEN PV VM which boots externally
LogPrint "This looks like a XEN PV system, ignoring boot loader issues"
elif test "$NOBOOTLOADER" ; then
LogPrint "WARNING:
For this system
$OS_VENDOR_VERSION on $ARCH (based on $OS_MASTER_VENDOR_VERSION_ARCH)
there is no code to install a boot loader on the recovered system
or the code that we have failed to install the boot loader correctly.
Please contribute appropriate code to the $PRODUCT project,
see http://relax-and-recover.org/development/
Take a look at the scripts in $SHARE_DIR/finalize - for example
for PC architectures like x86 and x86_64 see the script
$SHARE_DIR/finalize/Linux-i386/660_install_grub2.sh
and for POWER architectures like ppc64le see the script
$SHARE_DIR/finalize/Linux-ppc64le/660_install_grub2.sh
---------------------------------------------------
| IF YOU DO NOT INSTALL A BOOT LOADER MANUALLY, |
| THEN YOUR SYSTEM WILL NOT BE ABLE TO BOOT. |
---------------------------------------------------
You can use 'chroot $TARGET_FS_ROOT bash --login'
to change into the recovered system and
manually install a boot loader therein.
"
fi