Boot new v5 OS with old v2.3 HDD plugged in?

M

MattE

Member
Jan 12, 2018
20
1
8
44
I'm working on installing v5 on a new drive as my old drive running 2.3 seems to be having trouble. I have removed the old drive, and installed v5 on my new drive. Now when I shutdown, connect the old drive to transfer VM images, upon boot up it appears to load the v5 boot loader but the old v2.3 OS install. In my BIOS I only have the new drive enabled as a boot device and I also tried to manually select my new drive for booting. It seems the boot loader scans and detects multiple pve installs and launches the wrong one. How can I go about locking my mount points to the new install?
 
If you only want to transfer data from your old drive, then plug it in, while PVE5 is running, that way you are sure that it booted from the right drive.
 
The only problem I see that could arise is that if both (old and new) are using LVM with the same name of the volume group.
 
The VGs have different VG-UUIDs and should not collide. You can also boot a live cd and rename on the old disk the VG (vgrename pve), as those have the same name and grub selects the wrong one for boot.
 
You must log in or register to reply here.
Top Bottom