#3433 Issue open: Cannot do backup: "Unsupported partition table 'unknown' on /dev/sdb"¶
Labels: support / question, old version
u4ea75 opened issue at 2025-03-19 11:48:¶
Requesting support or just a question¶
Cannot exclude disk from backup
Platform¶
Linux x64
Output¶
Relax-and-Recover 2.7 / Git
Running rear mkbackup (PID 54431 date 2025-03-19 12:21:43)
Command line options: /home/connadmin/rear/usr/sbin/rear -v -d mkbackup
Using log file: /home/connadmin/rear/var/log/rear/rear-itflowsrv.log
Using build area: /var/tmp/rear.Px7CbCMVxXNYgrU
Setting TMPDIR to ReaR's '/var/tmp/rear.Px7CbCMVxXNYgrU/tmp' (was unset when ReaR was launched)
Running 'init' stage ======================
Running workflow mkbackup on the normal/original system
Running 'prep' stage ======================
Using backup archive '/var/tmp/rear.Px7CbCMVxXNYgrU/outputfs/rear/itflowsrv/20250319.1221/backup.tar.gz'
No 'console=...' setting for recovery system kernel (none in /proc/cmdline)
Found EFI system partition /dev/sda1 on /boot/efi type vfat
Using UEFI Boot Loader for Linux (USING_UEFI_BOOTLOADER=1)
Secure Boot is disabled, not using Secure Boot shim:
SecureBoot disabled
Platform is in Setup Mode
Using autodetected kernel '/boot/vmlinuz-6.8.0-55-generic' as kernel in the recovery system
Cannot write protect USB disk of '/dev/disk/by-label/REAR-000' via ID (no ID found)
File system label of '/dev/disk/by-label/REAR-000' added to WRITE_PROTECTED_FS_LABEL_PATTERNS
Modified ReaR recovery system area after 'prep' stage (/var/tmp/rear.Px7CbCMVxXNYgrU/rootfs contains regular files)
Running 'layout/save' stage ======================
Creating disk layout
Overwriting existing disk layout file /home/connadmin/rear/var/lib/rear/layout/disklayout.conf
ERROR: Unsupported partition table 'unknown' on /dev/sdb (must be one of 'msdos' 'gpt' 'gpt_sync_mbr' 'dasd')
Some latest log messages since the last called script 200_partition_layout.sh:
2025-03-19 12:21:45.225827786 Saving disks and their partitions
Error: Can't have a partition outside the disk!
Error: Can't have a partition outside the disk!
You may use debugscript mode '-D' for full debug messages with 'set -x' output
Aborting due to an error, check /home/connadmin/rear/var/log/rear/rear-itflowsrv.log for details
Exiting rear mkbackup (PID 54431) and its descendant processes ...
Running exit tasks
To remove the build area you may use (with caution): rm -Rf --one-file-system /var/tmp/rear.Px7CbCMVxXNYgrU
Additional information¶
- ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.7 / Git
Ubuntu 24.04.1 LTS
- ReaR configuration files
AUTOEXCLUDE_MULTIPATH=y
AUTOEXCLUDE_DISKS=y
EXCLUDE_RECREATE+=( "fs:/dev/sdb")
-
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
Dell PowerEdge R220 -
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):
Should be a BIOS boot with grub -
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
two hdd on raid 1 -
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
NAME KNAME PKNAME TRAN TYPE FSTYPE LABEL SIZE MOUNTPOIN
/dev/sda /dev/sda sata disk 465.8G
|-/dev/sda1 /dev/sda1 /dev/sda part vfat 1G /boot/efi
|-/dev/sda2 /dev/sda2 /dev/sda part ext4 2G /boot
`-/dev/sda3 /dev/sda3 /dev/sda part LVM2_member 462.7G
`-/dev/mapper/ubuntu--vg-ubuntu--lv /dev/dm-0 /dev/sda3 lvm ext4 100G /
/dev/sdb /dev/sdb sata disk 465.8G
`-/dev/sdb1 /dev/sdb1 /dev/sdb part 465.8G
/dev/sdc /dev/sdc usb disk 28.9G
|-/dev/sdc1 /dev/sdc1 /dev/sdc part 8M
|-/dev/sdc2 /dev/sdc2 /dev/sdc part vfat REAR-EFI 1G
`-/dev/sdc3 /dev/sdc3 /dev/sdc part ext3 REAR-000 27.9G
/dev/sr0 /dev/sr0 sata rom 1024M
I'm unable to do backup, this is the output:
Relax-and-Recover 2.7 / Git
Running rear mkbackup (PID 54431 date 2025-03-19 12:21:43)
Command line options: /home/connadmin/rear/usr/sbin/rear -v -d mkbackup
Using log file: /home/connadmin/rear/var/log/rear/rear-itflowsrv.log
Using build area: /var/tmp/rear.Px7CbCMVxXNYgrU
Setting TMPDIR to ReaR's '/var/tmp/rear.Px7CbCMVxXNYgrU/tmp' (was unset when ReaR was launched)
Running 'init' stage ======================
Running workflow mkbackup on the normal/original system
Running 'prep' stage ======================
Using backup archive '/var/tmp/rear.Px7CbCMVxXNYgrU/outputfs/rear/itflowsrv/20250319.1221/backup.tar.gz'
No 'console=...' setting for recovery system kernel (none in /proc/cmdline)
Found EFI system partition /dev/sda1 on /boot/efi type vfat
Using UEFI Boot Loader for Linux (USING_UEFI_BOOTLOADER=1)
Secure Boot is disabled, not using Secure Boot shim:
SecureBoot disabled
Platform is in Setup Mode
Using autodetected kernel '/boot/vmlinuz-6.8.0-55-generic' as kernel in the recovery system
Cannot write protect USB disk of '/dev/disk/by-label/REAR-000' via ID (no ID found)
File system label of '/dev/disk/by-label/REAR-000' added to WRITE_PROTECTED_FS_LABEL_PATTERNS
Modified ReaR recovery system area after 'prep' stage (/var/tmp/rear.Px7CbCMVxXNYgrU/rootfs contains regular files)
Running 'layout/save' stage ======================
Creating disk layout
Overwriting existing disk layout file /home/connadmin/rear/var/lib/rear/layout/disklayout.conf
ERROR: Unsupported partition table 'unknown' on /dev/sdb (must be one of 'msdos' 'gpt' 'gpt_sync_mbr' 'dasd')
Some latest log messages since the last called script 200_partition_layout.sh:
2025-03-19 12:21:45.225827786 Saving disks and their partitions
Error: Can't have a partition outside the disk!
Error: Can't have a partition outside the disk!
You may use debugscript mode '-D' for full debug messages with 'set -x' output
Aborting due to an error, check /home/connadmin/rear/var/log/rear/rear-itflowsrv.log for details
Exiting rear mkbackup (PID 54431) and its descendant processes ...
Running exit tasks
To remove the build area you may use (with caution): rm -Rf --one-file-system /var/tmp/rear.Px7CbCMVxXNYgrU
jsmeix commented at 2025-03-19 13:21:¶
I think I vaguely remember that we recently had
such kind of issue here at ReaR upstream
ERROR: Unsupported partition table 'unknown' on ... (must be one of 'msdos' 'gpt' 'gpt_sync_mbr' 'dasd')
...
googling for ERROR: Unsupported partition table 'unknown' on
found it:
https://github.com/rear/rear/issues/2995
which is also on Ubuntu 24.04.X LTS
that one is on Ubuntu 20.04.6 LTS and was
reproduced with Ubuntu-Server 20.04.2 LTS, cf.
https://github.com/rear/rear/issues/2995#issuecomment-1598782245
u4ea75 commented at 2025-03-19 13:33:¶
I read that posts before write my one but cannot understand what to do sorry, could u help?
gdha commented at 2025-03-20 08:56:¶
@jsmeix could PR https://github.com/rear/rear/pull/3403 be of any help here?
jsmeix commented at 2025-03-20 09:02:¶
@gdha
I don't know.
I did not find time to investigate the details of those issues.
jsmeix commented at 2025-03-20 09:11:¶
@u4ea75
FYI some generic boilerplate info:
In general I recommend to try out our latest GitHub master code
because the GitHub master code is the only place where we fix things
and if there are issues it helps when you use exactly the code
where we could fix things.
See the "QUICK START GUIDE" and "INSTALLATION" parts on
https://github.com/rear/rear
Additionally / alternatively see the section
"Testing current ReaR upstream GitHub master code" in
https://en.opensuse.org/SDB:Disaster_Recovery
how you can try out our current ReaR GitHub master code
without conflicts with your already installed ReaR version.
In general we at ReaR upstream do not support older ReaR versions.
We at ReaR upstream do not plain reject issues with older ReaR
versions
(e.g. we may answer easy to solve questions also for older ReaR
versions)
but we do not spend much time on issues with older ReaR versions
because
we do not (and cannot) fix issues in released ReaR versions.
Issues in released ReaR versions are not fixed by us (by ReaR
upstream).
Issues in released ReaR versions that got fixed in current ReaR
upstream
GitHub master code might be fixed (if the fix can be backported with
reasonable effort) by the Linux distributor wherefrom you got ReaR.
In particular regarding Ubuntu / Debian:
I am neither a Ubuntu user nor a Debian user.
Currently we at ReaR upstream do not have
an active maintainer for Ubuntu / Debian.
So ReaR support for Ubuntu / Debian
can be only as good as voluntary contributors
who use those Linux distributions contribute
which is much appreciated!
In particular regarding Ubuntu:
It seems Canonical is not sufficiently interested in ReaR
in contrast to Red Hat and SUSE who pay developers
(like me from SUSE and e.g. @pcahyna and @lzaoral from Red Hat)
to contribute to upstream ReaR because Red Hat and SUSE
support ReaR in their enterprise Linux distributions.
[Export of Github issue for rear/rear.]