New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
partition resizing #527
Comments
@lesmikesell which version of rear are you using? Did you tried the latest git version too? Was the original |
@jhoekx were you busy with helping Mike? Via the mailing list. |
I briefly checked based on the mailing list conversation, but haven't had the time to investigate deeper... |
The rear version is the rear-1.16.1-1.el5 rpm as packaged in EPEL for Centos 5. I didn't try anything newer. I think the disklayout.conf was right for an exactly-matching destination drive. But the resizing math came out wrong for both a smaller and larger destination. I ended up making it work by obtaining the values from the source disk and editing them into the restore.sh commands with a slightly larger target drive so I don't need help with this particular instance - I'm just reporting a bug in the resizing code. Contributing factors may be that this drive has 3 primary partitions, one of which is /boot. The same system has 2 other drives, each with a single partition and those worked as expected. |
@lesmikesell I guess we can close this issue as it is old? |
Yes, closing. I haven't run into this situation again. |
I'm trying to use rear to convert a Centos5 system to a VM. The
source has 3 primary partitions on /dev/sda:
I've tried both smaller and larger target disks and the restore script
claims that it is resizing the partitions to fit, but parted always
claims that the value for the last partition is 'outside of the
device'. Actually, it only mentions resizing 2 partitions:
(when in fact this target disk is actually bigger) - after failing I have:
And the failing command is:
parted -s /dev/sda mkpart '"primary"' 157840084992B 157840048127B >&2
Excerpts from a debug log below:
The text was updated successfully, but these errors were encountered: