[Rear-users] openSuSE 11.4 with dm_crypt pre boot encryption

fuzzy_4711 fuzzy_4711 at gmx.de
Mon Aug 1 13:01:37 CEST 2011


Hi,
I am a total newbie to the rear project.

Nevertheless I studied the documentation available and gave it a try. I
ended up with a 1.11 installation yesterday and a customised
/etc/rear/local.conf which is like that:

OUTPUT=ISO # creates a bootable ISO9660 image on disk as
rear-$(hostname).iso
ISO_DIR=/home/rear
BACKUP=REQUEST_RESTORE


MODULES_LOAD=( dm_mod dm_snapshot sha256_generic dm_cryptc atl1c )

My idea is to write the iso every day via cron and include it in the
regular backup. The ISO should be burned if needed and used to restore
the system. File system backup will be done via backup-manager.

So far so good.

The ISO is being burned pretty well. When I try to restore I get the
following errors in /tmp/rear.log (see below).

I am quite sure my machine setup is causing the trouble and I want to
ask if it is possible to support a setup like mine at all:
Encrypted disk using dm_crypt, installed via YaST.

Thank you for any support.

-fuz

Here is my output for fdisk -l at the systeme to be backuped:
Disk /dev/sda: 400.1 GB, 400088457216 bytes


255 heads, 63 sectors/track, 48641 cylinders, total 781422768 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 512 bytes


I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk identifier: 0x000c1a65





   Device Boot      Start         End      Blocks   Id  System


/dev/sda1   *   285106176   285249535       71680   83  Linux


/dev/sda2       285249536   781422591   248086528   8e  Linux LVM





Disk /dev/mapper/cr_sda4: 254.0 GB, 254039552000 bytes


255 heads, 63 sectors/track, 30885 cylinders, total 496171000 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 512 bytes


I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk identifier: 0x00000000





Disk /dev/mapper/cr_sda4 doesn't contain a valid partition table





Disk /dev/mapper/system-home: 161.1 GB, 161061273600 bytes


255 heads, 63 sectors/track, 19581 cylinders, total 314572800 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/system-home doesn't contain a valid partition table

Disk /dev/mapper/system-root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/system-root doesn't contain a valid partition table

Disk /dev/mapper/system-swap: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/system-swap doesn't contain a valid partition table




This is an extract of /tmp/rear.log
...
Running recreate state
Including recreate/GNU/Linux/09_disable_lvm2_md.sh
Creating directory "/var/lock/lvm"
Finding all volume groups
/dev/dm-0: open failed: No such device or address
/dev/dm-1: open failed: No such device or address
/dev/root: open failed: No such device or address
/dev/dm-3: open failed: No such device or address
No volume groups found
...

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sda unrecognized partition table type
No partitions found
...




More information about the rear-users mailing list