[rear-users] Help migrating Scientific Linux 7.2

James M. Pulver jmp242 at cornell.edu
Tue Aug 23 17:33:30 CEST 2016


I have a Lenovo S30 that I have SL7.2 installed on an SSD, sda. I want 
to try and migrate to a Lenovo P510 that has a NVMe SSD, nvme0n1 I 
believe. I also have a second local SSD that I just plan to physically 
move to the P510.

I've created a REAR backup on the S30, but when I try and restore to the 
P510 I have various partition errors. The current ones I get are in 
marking the initial partition bootable I think, or in creating the 
partitions. It basically says the partition doesn't exist.

REAR seems to select the correct nvme0n1 disk, but is trying to mark 
partition 11 bootable, which isn't a partition that I have, or don't 
have at that point in the recovery.

lsblk of the disk I want to migrate on the S30:
[root at S30 myuser]# lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 238.5G  0 disk
├─sda1            8:1    0   512M  0 part /boot
└─sda2            8:2    0   238G  0 part
   ├─vg-swap     253:0    0     8G  0 lvm  [SWAP]
   ├─vg-sl7      253:1    0    20G  0 lvm  /
   ├─vg-tmp      253:2    0    10G  0 lvm  /tmp
   ├─vg-opt      253:3    0    10G  0 lvm  /opt
   ├─vg-var      253:4    0    10G  0 lvm  /var
   └─vg-images   253:5    0   120G  0 lvm  /mnt/images

disklayout.conf on the S30 for the filesystems I want to migrate:

disk /dev/sda 256060514304 msdos
part /dev/sda 536870912 2097152 primary boot /dev/sda1
part /dev/sda 255521542144 538972160 primary lvm /dev/sda2

lvmdev /dev/vg /dev/sda2 x1wf62-wkqb-2AsV-E8H0-y11f-on0R-HmB1EL 499065512

lvmgrp /dev/vg 4096 60920 249528320

lvmvol /dev/vg tmp 2560 20971520
lvmvol /dev/vg opt 2560 20971520
lvmvol /dev/vg var 2560 20971520
lvmvol /dev/vg swap 2048 16777216
lvmvol /dev/vg sl7 5120 41943040
lvmvol /dev/vg images 30720 251658240
# Filesystems (only ext2,ext3,ext4,vfat,xfs,reiserfs,btrfs are supported).
# Format: fs <device> <mountpoint> <fstype> [uuid=<uuid>] 
[label=<label>] [<attributes>]
fs /dev/mapper/vg-images /mnt/images xfs 
uuid=f800dbeb-1ebf-4fb4-b966-9ff86ba0d611 label= 
options=rw,relatime,attr2,inode64,noquota
fs /dev/mapper/vg-opt /opt xfs uuid=c8b77d97-0027-4e1e-8834-036a2a459be8 
label=  options=rw,relatime,attr2,inode64,noquota
fs /dev/mapper/vg-sl7 / xfs uuid=de411b75-c810-4508-9c48-e8b77cfcfeec 
label=  options=rw,relatime,attr2,inode64,noquota
fs /dev/mapper/vg-tmp /tmp xfs uuid=89b9dc99-9639-4811-bed9-ab36e1f731b6 
label=  options=rw,relatime,attr2,inode64,noquota
fs /dev/mapper/vg-var /var xfs uuid=04c7b4dc-64f4-4ee4-a992-dae698d5eca9 
label=  options=rw,relatime,attr2,inode64,noquota
fs /dev/sda1 /boot xfs uuid=c991f9ad-3c3a-40a7-98d5-df4cbbf6b6c5 label= 
options=rw,relatime,attr2,inode64,noquota
swap /dev/mapper/vg-swap uuid=087fabb0-ca09-4756-9eb9-c96dfc2cb178 label=

Now, I wonder if my problem is ReaR backed up more than just the "system 
drive" sda?
-- 
James Pulver
CLASSE Computer Group
Cornell University


More information about the rear-users mailing list