# Issue: REAR recover error

**URL:** https://forums.suse.com/t/issue-rear-recover-error/41963
**Category:** SUSE Linux Enterprise Server
**Created:** [November 17, 2023, 8:33am UTC](https://forums.suse.com/t/issue-rear-recover-error/41963 "2023-11-17T08:33:17Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![hitrikrtek](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/hitrikrtek/32/10701_2.png) [@hitrikrtek](https://forums.suse.com/u/hitrikrtek)
#### Post date: [November 17, 2023, 8:33am UTC](https://forums.suse.com/t/issue-rear-recover-error/41963/1 "2023-11-17T08:33:17Z")

</div>

This issue is also opened in REAR GitHub: [write\_protected\_candidate\_device called for '/sys/block/nvme0c0n1' but '/dev/nvme0c0n1' is no block device · Issue #3085 · rear/rear · GitHub](https://github.com/rear/rear/issues/3085)

Description of the issue:

write\_protected\_candidate\_device called for ‘/sys/block/nvme0c0n1’ but ‘/dev/nvme0c0n1’ is no block device

- ReaR version (“/usr/sbin/rear -V”): Relax-and-Recover 2.7 / 2022-07-13
- If your ReaR version is not the current version, explain why you can’t upgrade: Latest version with distribution
- OS version (“cat /etc/os-release” or “lsb\_release -a” or “cat /etc/rear/os.conf”):  
NAME=“SLES”  
VERSION=“15-SP5”  
VERSION\_ID=“15.5”  
PRETTY\_NAME=“SUSE Linux Enterprise Server 15 SP5”  
ID=“sles”  
ID\_LIKE=“suse”  
ANSI\_COLOR=“0;32”  
CPE\_NAME=“cpe:/o:suse:sles:15:sp5”
- ReaR configuration files (“cat /etc/rear/local.conf”):  
BACKUP=NETFS  
OUTPUT=ISO  
BACKUP\_URL=nfs://172.17.3.1/rear  
BACKUP\_OPTIONS=  
NETFS\_KEEP\_OLD\_BACKUP\_COPY=yes  
USE\_DHCLIENT=  
MODULES\_LOAD=( )  
#BACKUP\_PROG\_INCLUDE=(“{BACKUP\_PROG\_INCLUDE[@]}” ‘/boot/grub2/i386-pc’ ‘/boot/grub2/x86\_64-efi’ ‘/home’ ‘/opt’ ‘/root’ ‘/srv’ ‘/hana/shared’ ‘/usr’ ‘/var’)  
BACKUP\_PROG\_EXCLUDE=(“{BACKUP\_PROG\_EXCLUDE[@]}” ‘/hana/backup’ ‘/hana/data’ ‘/hana/log’ ‘/hana/shared/HSP/HDB05/backup’ ‘/hana/shared/NSP/HDB50/backup’ ‘/opt/dpsapps/agentsvc/dbs’ ‘/opt/dpsapps/agentsvc/logs’ ‘/tmp’)  
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’)  
REQUIRED\_PROGS=(snapper chattr lsattr ${REQUIRED\_PROGS[@]})  
COPY\_AS\_IS=(/usr/lib/snapper/installation-helper /etc/snapper/config-templates/default ${COPY\_AS\_IS[@]})  
EXCLUDE\_MOUNTPOINTS=(“/mnt”)  
ISO\_MKISOFS\_BIN=/usr/bin/ebiso
- Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):  
DELL PowerEdge R860
- System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):  
x86\_64
- Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):  
BIOS Version 1.5.6  
grub2-x86\_64-efi-2.06-150500.29.8.1
- Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):  
NVMe in RAID configuration

Backplane 1 on Connector 0 of RAID Controller in SL 1  
DeviceDescription Backplane 1 on Connector 0 of RAID Controller in SL 1  
DeviceType PCIeSSDBackPlane  
FirmwareVersion 7.10  
FQDD Enclosure.Internal.0-1:RAID.SL.1-1  
InstanceID Enclosure.Internal.0-1:RAID.SL.1-1  
MediaType Solid State Drive  
PCIExpressGeneration Gen 4  
ProductName BP\_PSV 0:1  
RollupStatus OK  
SlotCount 8  
WiredOrder 1

Backplane 2 on Connector 0 of RAID Controller in SL 4  
DeviceDescription Backplane 2 on Connector 0 of RAID Controller in SL 4  
DeviceType PCIeSSDBackPlane  
FirmwareVersion 7.10  
FQDD Enclosure.Internal.0-2:RAID.SL.4-1  
InstanceID Enclosure.Internal.0-2:RAID.SL.4-1  
MediaType Solid State Drive  
PCIExpressGeneration Gen 4  
ProductName BP\_PSV 0:2  
RollupStatus OK  
SlotCount 8  
WiredOrder 2

- Storage layout (“lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT”):  
NAME KNAME PKNAME TRAN TYPE FSTYPE LABEL SIZE MOUNTPOINT  
/dev/sda /dev/sda disk LVM2\_member 23.3T  
|-/dev/mapper/vghana-lvusrsap /dev/dm-2 /dev/sda lvm xfs 150G /usr/sap  
|-/dev/mapper/vghana-lvdata /dev/dm-3 /dev/sda lvm xfs 6T /hana/data  
|-/dev/mapper/vghana-lvshared /dev/dm-4 /dev/sda lvm xfs 2T /hana/shared  
|-/dev/mapper/vghana-lvlog /dev/dm-5 /dev/sda lvm xfs 4T /hana/log  
'-/dev/mapper/vghana-lvbackup /dev/dm-6 /dev/sda lvm xfs 2T /hana/backup  
/dev/sdb /dev/sdb iscsi disk 100M  
/dev/sdc /dev/sdc iscsi disk 100M  
/dev/sdd /dev/sdd iscsi disk 1G  
/dev/nvme0n1 /dev/nvme0n1 nvme disk 447.1G  
|-/dev/nvme0n1p1 /dev/nvme0n1p1 /dev/nvme0n1 nvme part vfat ESP 250M /boot/efi  
|-/dev/nvme0n1p2 /dev/nvme0n1p2 /dev/nvme0n1 nvme part vfat OS 2G /boot  
'-/dev/nvme0n1p3 /dev/nvme0n1p3 /dev/nvme0n1 nvme part LVM2\_member 444.8G  
|-/dev/mapper/vgroot-root /dev/dm-0 /dev/nvme0n1p3 lvm btrfs 442.8G /var  
'-/dev/mapper/vgroot-swap /dev/dm-1 /dev/nvme0n1p3 lvm swap 2G [SWAP]
- Description of the issue (ideally so that others can reproduce it):  
When running rear recover we get this error:  
[![image](https://user-images.githubusercontent.com/34364792/283724827-90d58584-9a48-4806-91f0-0e8de9f66cef.png)](https://user-images.githubusercontent.com/34364792/283724827-90d58584-9a48-4806-91f0-0e8de9f66cef.png)
- Workaround, if any:  
None