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
mkpart fails with off by one error #1778
Comments
@ritzmann 2018-04-18 01:38:49.260691926 Including layout/prepare/default/250_compare_disks.sh 2018-04-18 01:38:49.263550111 Comparing disks 2018-04-18 01:38:49.314407971 Comparing sdc 2018-04-18 01:38:49.316833419 Device sdc does not exist (manual configuration needed) 2018-04-18 01:38:49.320213737 Switching to manual disk layout configuration ... 2018-04-18 01:39:03.347164368 Including layout/prepare/default/400_autoresize_disks.sh /usr/share/rear/layout/prepare/default/400_autoresize_disks.sh: line 10: backup_file: command not found 2018-04-18 01:39:03.368436066 Total resize of -482927992832B 2018-04-18 01:39:03.371575850 Searching for resizeable partitions on disk /dev/sda (17179869184B) 2018-04-18 01:39:03.384002290 Will not resize partition /dev/sda1. 2018-04-18 01:39:03.405380984 Will resize partition /dev/sda2. 2018-04-18 01:39:03.415167424 Will resize partition /dev/sda5. 2018-04-18 01:39:03.428222714 Resized partition /dev/sda2 from 499849888768B to 8462532616B. 2018-04-18 01:39:03.441723872 Resized partition /dev/sda5 from 499849887744B to 8462532599B. 2018-04-18 01:39:03.452081054 Including layout/prepare/default/420_autoresize_last_partitions.sh 17179869184 256901120 (standard_in) 1: syntax error 0 16922969088 2018-04-18 01:39:03.575701514 Including layout/prepare/default/430_autoresize_all_partitions.sh You are in migration mode and The old layout/prepare/default/400_autoresize_disks.sh Therefore I recommend that you To use our current ReaR upstream GitHub master code Basically "git clone" it into a separated directory and then # git clone https://github.com/rear/rear.git # mv rear rear.github.master # cd rear.github.master # vi etc/rear/local.conf # usr/sbin/rear -D mkbackup Note the relative paths "etc/rear/" and "usr/sbin/". @ritzmann |
Hello @ritzmann, EFI based USB device needs to be formatted with command `rear format -- --efi /dev/<device_name>' So in your case it would be: Also make sure that you are restoring to correct USB device. I happened several times already that ReaR recovery system (source boot USB disk) was overwritten due bad user decision. V. |
@ritzmann UEFI on backed up machine, BIOS in VirtualBox ... Format USB stick: rear -v mkformat /dev/sdl Create rescue image: rear -v mkrescue Boot stick from VirtualBox image with single hard drive attached and run rear restore It seems you also like to migrate from UEFI to BIOS. Bootloader migration is not supported by ReaR, cf. See also |
Sorry for the unnecessary work that I caused. I will clean up my installation as instructed. The UEFI - BIOS mess was of course not intentional either, VirtualBox was just the easiest way to test the restore procedure without messing with my existing setup. I believe I can switch the virtual machine to boot with UEFI in VirtualBox. |
No worries! FYI: For real debugging an issue a log with debug info is needed, Regarding bootloader migration: That bootloader migration is not supported by ReaR The ReaR scripts do not help you to migrate your bootloader. But you can of course manually migrate your bootloader The ReaR recovery system is a rather minimal But by default the ReaR recovery system contains only For example when you like to migrate from one filesystem But via ReaR config variables like COPY_AS_IS, PROGS, I am not at all a bootloader expert but I guess migrating the |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
Latest Git clone, commit dd982eb
(rear -V prints: Relax-and-Recover 2.3 / 2017-12-20)
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
Debian GNU/Linux 8.10 (jessie)
ReaR configuration files ("cat /etc/rear/site.conf" or "cat /etc/rear/local.conf"):
Included in rear.zip
System architecture (x86 compatible or POWER and/or what kind of virtual machine):
amd64, restoration tested with VirtualBox Debian 64 bit machine
Are you using BIOS or UEFI or another way to boot?
UEFI on backed up machine, BIOS in VirtualBox
Brief description of the issue:
Steps to reproduce:
+++ parted -s /dev/sda mkpart ''''logical'''' 256901120B 8719433718B
Error: You requested a partition from 257MB to 8719MB (sectors 501760..17030143).
The closest location we can manage is 257MB to 8719MB (sectors 501760..17030142).
Rear log and disklayout.conf are included in rear.zip.
The text was updated successfully, but these errors were encountered: