REAR recover failed SLES12SP3 on PowerPC

SUSE Product Topics SLES for POWER
1

Server = 8284 -22A (power8)
OS = SUSE Linux Enterprise server
Version = 12 SP 3
Rear Version = rear-2.5-99.git.0.ef3febb.unknown.changed.ppc64le

**config file /etc/local.conf

OUTPUT=ISO
BACKUP=NETFS
#BACKUP_OPTIONS=“nfsvers=3,nolock”
#BACKUP_URL=file:///tmp/ktm
#OUTPUT_URL=nfs://192.168.130.52/NFS_DIT
BACKUP_URL=nfs://192.168.130.52/NFS_DIT/

#REQUIRED_PROGS=( “${REQUIRED_PROGS[@]}” snapper chattr lsattr )
#COPY_AS_IS=( “${COPY_AS_IS[@]}” /usr/lib/snapper/installation-helper /etc/snapper/config-templates/default )
BACKUP_PROG_INCLUDE=( /srv /var/lib/mailman /tmp /var/lib/libvirt/images /var/opt /var/log /boot/grub2/powerpc-ieee1275 /var/lib/mysql /var/tmp /opt /var/spool /var/lib/pgsql /var/lib/mariadb /usr/local /home /var/lib/machines /var/lib/named /var/cache )
#POST_RECOVERY_SCRIPT=( ‘if snapper --no-dbus -r $TARGET_FS_ROOT get-config | grep -q “^QGROUP.*[0-9]/[0-9]” ; then snapper --no-dbus -r $TARGET_FS_ROOT set-config QGROUP= ; snapper --no-dbus -r $TARGET_FS_ROOT setup-quota && echo snapper setup-quota done || echo snapper setup-quota failed ; else echo snapper setup-quota not used ; fi’ )
#SSH_ROOT_PASSWORD=“root”
#USE_DHCLIENT=“yes”

**error after restore (rear recover)

Confirm restored config files are OK or adapt them as needed

  1. Confirm it is OK to recreate initrd and reinstall bootloader and continue ‘rear recover’
  2. Edit restored etc/fstab (/mnt/local/etc/fstab)
  3. View restored etc/fstab (/mnt/local/etc/fstab)
  4. Use Relax-and-Recover shell and return back to here
  5. Abort ‘rear recover’
    (default ‘1’ timeout 300 seconds)
    1
    User confirmed restored files
    Running mkinitrd…
    Recreated initrd (/sbin/mkinitrd).
    Installing GRUB2 boot loader on PPC64/PPC64LE…
    Determining where to install GRUB2 (no GRUB2_INSTALL_DEVICES specified)
    Cannot install GRUB2 (unable to find a PPC PReP boot partition)
    WARNING:
    For this system
    SUSE_LINUX/12.3 on Linux-ppc64le (based on SUSE/12/ppc64le)
    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 Relax-and-Recover project,
    see http://relax-and-recover.org/development/
    Take a look at the scripts in /usr/share/rear/finalize,
    for example see the scripts
    /usr/share/rear/finalize/Linux-i386/630_install_grub.sh
    /usr/share/rear/finalize/Linux-i386/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 /mnt/local bash --login’
to change into the recovered system.
You should at least mount /proc in the recovered system
e.g. via ‘mount -t proc none /mnt/local/proc’
before you change into the recovered system
and manually install a boot loader therein.

Finished recovering your system. You can explore it under ‘/mnt/local’.
Exiting rear recover (PID 6128) and its descendant processes …
Running exit tasks

2

Hello praditk,

The SLE HA Extension includes the package rear23a which was added to restore SLES on ppc64le -https://scc.suse.com/packages?name=SUSE%20Linux%20Enterprise%20Server&version=12.3&arch=ppc64le&query=rear&module= . Have you tried this?

Mike

3

Hello,

we’ve the same problem using 2.3 as proposed by mfriesenegger.

During recovery the last step :

  1. Confirm it is OK to recreate initrd and reinstall bootloader and continue ‘re ar recover’
  2. Edit restored etc/fstab (/mnt/local/etc/fstab)
  3. View restored etc/fstab (/mnt/local/etc/fstab)
  4. Use Relax-and-Recover shell and return back to here
  5. Abort ‘rear recover’
    (default ‘1’ timeout 300 seconds)
    1
    User confirmed restored files
    Applying disk layout mappings in /var/lib/rear/layout/disk_mappings to certain r estored files…
    The original restored files get saved in var/lib/rear/saved_original_files/ (in /mnt/local)
    Applied disk layout mappings to restored ‘boot/grub2/grub.cfg’ (in /mnt/local)
    Applied disk layout mappings to restored ‘etc/sysconfig/bootloader’ (in /mnt/loc al)
    Applied disk layout mappings to restored ‘etc/fstab’ (in /mnt/local)
    Applied disk layout mappings to restored ‘etc/smartd.conf’ (in /mnt/local)
    Applied disk layout mappings to restored ‘etc/sysconfig/smartmontools’ (in /mnt/ local)
    Applied disk layout mappings to restored ‘etc/security/pam_mount.conf.xml’ (in / mnt/local)
    Patching /etc/default/grub_installdevice: Replacing [/dev/disk/by-id/scsi-360050 7638081001a48000000000001b2-part1] by [/dev/disk/by-id/dm-name-3600507638081001a 4800000000000205-part1]
    /etc/multipath.conf not available in target, creating it…
    Running mkinitrd…
    Recreated initrd (/sbin/mkinitrd).
    PPC PReP Boot partition found: /dev/mapper/3600507638081001a4800000000000205-par t1
    Boot device disk is /dev/mapper/3600507638081001a4800000000000205.
    Limiting bootlist to 5 entries as a maximum…
    Set LPAR bootlist to ‘/dev/sdo /dev/sdk /dev/sdg /dev/sdc /dev/sdm’
    WARNING:
    For this system
    SUSE_LINUX/12.3 on Linux-ppc64le (based on SUSE/12/ppc64le)
    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 Relax-and-Recover project,
    see http://relax-and-recover.org/development/
    Take a look at the scripts in /usr/share/rear/finalize,
    for example see the scripts
    /usr/share/rear/finalize/Linux-i386/210_install_grub.sh
    /usr/share/rear/finalize/Linux-i386/220_install_grub2.sh

| IF YOU DO NOT INSTALL A BOOT LOADER MANUALLY, |

THEN YOUR SYSTEM WILL NOT BE ABLE TO BOOT.

Any idea ?
Manually installing bootloader ? How?

Thank you
Martin