[rear-users] Recovery fails on creating disklayout

Roth, Markus Markus.Roth at bechtle.com
Fri Oct 25 08:32:21 CEST 2013


Hello,

I want to recover a RHEL4 system. Backup with rear on a cifs share was successful. I boot the test system (identical hardware) with the rescue ISO. The recover process stops at generating the disklayout.

Log file:
------------------------------------------
+++ Print 'Creating partitions for disk /dev/sda (msdos)'
+++ test 1
+++ echo -e 'Creating partitions for disk /dev/sda (msdos)'
+++ parted -s /dev/sda mklabel msdos
+++ parted -s /dev/sda mkpart primary 0 5671
+++ parted -s /dev/sda set 1 boot on
+++ parted -s /dev/sda mkpart primary 5671 53599
+++ parted -s /dev/sda mkpart primary 53599 101527
+++ parted -s /dev/sda set /dev/sda3 on
Error: Expecting a partition number.
2013-10-25 08:21:19 An error occured during layout recreation.
2013-10-25 08:22:03 User selected: 6) Abort Relax-and-Recover
2013-10-25 08:22:03 Error detected during restore.
2013-10-25 08:22:03 Restoring backup of /var/lib/rear/layout/disklayout.conf
2013-10-25 08:22:03 ERROR: There was an error restoring the system layout. See /var/log/rear/rear-daytona2.log for details.
----------------------------------------------------------------------------------


The disklayout looks as follows:

#disk /dev/hda 4294965248
disk /dev/sda 291999055872 msdos
part /dev/sda 5946845184 32256 primary boot /dev/sda1
part /dev/sda 50256460800 5946877440 primary none /dev/sda2
part /dev/sda 50256460800 56203338240 primary  /dev/sda3
part /dev/sda 1024 106459799040 primary  /dev/sda4
part /dev/sda 10075935744 106459831296 logical  /dev/sda5
part /dev/sda 5946845184 116535799296 logical  /dev/sda6
part /dev/sda 11852596224 122482676736 logical  /dev/sda7
part /dev/sda 11720991744 134335305216 logical  /dev/sda8
fs /dev/sda1 / ext3 uuid=8f3bc4f0-d605-4029-8cf2-c8fff9dfb95b label= blocksize=4096 reserved_blocks=4% max_mounts=27 check_interval=180d bytes_per_inode=8177 options=rw
fs /dev/sda6 /root2 ext3 uuid=<none> label= blocksize=4096 reserved_blocks=4% max_mounts=25 check_interval=180d bytes_per_inode=8177 options=rw,noexec,nosuid,nodev,noatime
fs /dev/sda5 /var ext3 uuid=79293447-713d-48e9-be5f-dfe2a680e623 label= blocksize=4096 reserved_blocks=4% max_mounts=37 check_interval=180d bytes_per_inode=8187 options=rw,noexec,nosuid,nodev,noatime
fs /dev/sda2 /opt/avaya ext3 uuid=78f75f71-8e71-403e-a98d-798b6212641d label= blocksize=4096 reserved_blocks=4% max_mounts=31 check_interval=180d bytes_per_inode=8179 options=rw
fs /dev/sda3 /opt/dbase ext3 uuid=58b70eff-daf0-4ab0-9fca-e9f31999970b label= blocksize=4096 reserved_blocks=4% max_mounts=25 check_interval=180d bytes_per_inode=8179 options=rw
fs /dev/sda8 /DVD_OPS ext3 uuid=dd8dd625-1c8d-4ed9-83f8-2ba60fe287d3 label= blocksize=4096 reserved_blocks=4% max_mounts=32 check_interval=180d bytes_per_inode=8177 options=rw
swap /dev/sda7 uuid= label=


fdisk -l on the original system looks:

Disk /dev/sda: 291.9 GB, 291999055872 bytes
255 heads, 63 sectors/track, 35500 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         723     5807466   83  Linux
/dev/sda2             724        6833    49078575   83  Linux
/dev/sda3            6834       12943    49078575   83  Linux
/dev/sda4           12944       35500   181189102+   5  Extended
/dev/sda5           12944       14168     9839781   83  Linux
/dev/sda6           14169       14891     5807466   83  Linux
/dev/sda7           14892       16332    11574801   82  Linux swap
/dev/sda8           16333       17757    11446281   83  Linux


Has anybody a hint why the creation of the extended partition /dev/sd4 fails?

regards,
Markus



More information about the rear-users mailing list