Disk wrongly detected as raid

Backup agent for Linux servers and workstations on-premises or in the public cloud

Disk wrongly detected as raid

Veeam Logoby Hejah » Wed Jul 11, 2018 12:31 pm

Hallo,
on one System Veeam wrongly detects /dev/sda as RAID and is therefore not able to backup the disk.

In "Known Issues", there is a problem mentioned, with partitions crated with cfdisk versions older than 2.25.
I don't know with what tool the partitions were created on the system.

Are there more informations about the cfdisk problem and how to detect it and fix it without reinstalling the System?

Or are the other problems known which can cause Veeam to detect a disk as RAID?

I'm using Veeam Agent for Linux FREE v2.0.1.665 on Debian GNU/Linux 9 (stretch).

Code: Select all
lpbcore|     Found matching filter for object [DEV__dev_sda]. Record type: [Include], value: [DEV__dev_sda]
lpbcore|     Device [/dev/sda] has usage type [raid] and will be skipped.
lpbcore|     No matching filters for object [{18bd6f83-2c39-4789-b432-76e6cebc92fd}]
lpbcore|     No matching filters for object [{18bd6f83-2c39-4789-b432-76e6cebc92fd}/o1048576l2995727106048]
lpbcore|     Partition [/dev/sdb1] with index [1] should not be backed up.
lpbcore|     Detecting bootloader on device [/dev/sdb].
lpbcore|       No bootloader detected.
lpbcore|     No bootloader has been detected on device.
lpbcore|     Enumerating LVM volume groups...
lpbcore|       LVM volume group: [pve].
lpbcore|       Enumerating logical volumes for LVM volume group: [pve].
lpbcore|         Found matching filter for object [7tVKDf-QOYf-eoc4-YkXR-jRYU-27Pd-OKFPfy]. Record type: [Include], value: [7tVKDf-QOYf-eoc4-YkXR-jRYU-27Pd-OKFPfy]
lpbcore|         Found matching filter for object [7tVKDf-QOYf-eoc4-YkXR-jRYU-27Pd-OKFPfy/QRMzBr-PVpd-753U-4cRz-uWX6-4XcF-6Lbfkw]. Record type: [Include], value: [7tVKDf-QOYf-eoc4-YkXR-jRYU-27Pd-OKFPfy]
lpbcore|         No matching filters for object [7tVKDf-QOYf-eoc4-YkXR-jRYU-27Pd-OKFPfy/QRMzBr-PVpd-753U-4cRz-uWX6-4XcF-6Lbfkw]
lpbcore|         Logical volume [vm-101-disk-1] with ID [QRMzBr-PVpd-753U-4cRz-uWX6-4XcF-6Lbfkw] should be backed up.
lpbcore|     [1] LVM volume groups were detected.
lpbcore|     LVM volume group [pve] will be backed up.
vmb    |     [SessionLog][error] Unable to backup object: sda(not found).
lpbcore|   Enumerating backup objects. Failed.
lpbcore| BackupJobPerformer: Creating backup. Failed.

NAME                     MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                        8:0    1   952G  0 disk
|-sda1                     8:1    1   285M  0 part /boot
|-sda2                     8:2    1   7.5G  0 part [SWAP]
|-sda3                     8:3    1  46.6G  0 part /
|-sda4                     8:4    1     1K  0 part
`-sda5                     8:5    1 897.7G  0 part
  `-pve-vm--101--disk--1 253:0    0   307G  0 lvm 
sdb                        8:16   1   2.7T  0 disk
`-sdb1                     8:17   1   2.7T  0 part /backup
Hejah
Novice
 
Posts: 3
Liked: never
Joined: Tue Mar 20, 2018 4:08 pm

Re: Disk wrongly detected as raid

Veeam Logoby PTide » Wed Jul 11, 2018 2:45 pm

Hi,

Is that just a simple directly attached drive, or there is anything specific about it?

Also, does the partitions occupy the whole device? My guess is that there might be still older-format RAID superblocks left. For example, v0.9 and v1.0 meta is kept at the end of the device.

Thanks
PTide
Veeam Software
 
Posts: 3996
Liked: 336 times
Joined: Tue May 19, 2015 1:46 pm


Return to Veeam Agent for Linux



Who is online

Users browsing this forum: No registered users and 7 guests