donyorm / weresync Goto Github PK

View Code? Open in Web Editor NEW

213.0 213.0 10.0 446 KB

Clones Linux hard drives incrementally or to a smaller drive

Home Page: https://weresync.readthedocs.io/en/master/

License: Apache License 2.0

Python 99.72% Shell 0.28%

backup clone linux

weresync's People

Contributors

Stargazers

Watchers

Forkers

awesome-python shekkbuilder pqyplzxhgf minimal101 xlotlu bellyfat rastuszhang mmangione kidpixo pla10

weresync's Issues

Exception without proper error message

WereSync Version [0.2]:
Name of Distribution (ex. Ubuntu): lubuntu 16.1
Version of Distribution (ex. 16.04):
Python version (ex. 3.4): 2.7
Gist linking to log file (found in /var/log/weresync):
Expected Behavior:

Actual Behavior:

:~$ weresync -C /dev/sdc /dev/sda
Checking partition validity.
Traceback (most recent call last):
File "/home/the/.local/bin/weresync", line 11, in
sys.exit(main())
File "/home/the/.local/lib/python2.7/site-packages/weresync/interface.py", line 126, in main
mount_points)
File "/home/the/.local/lib/python2.7/site-packages/weresync/interface.py", line 62, in copy_drive
copier.partitions_valid()
File "/home/the/.local/lib/python2.7/site-packages/weresync/device.py", line 618, in partitions_valid
source_parts = self.source.get_partitions()
File "/home/the/.local/lib/python2.7/site-packages/weresync/device.py", line 67, in get_partitions
raise weresync.exception.DeviceError(self.device, "Non-zero exit code", str(error, "utf-8"))
TypeError: str() takes at most 1 argument (2 given)

Other relevant details:

fstab not built properly after copy

Hi @DonyorM when I run weresync disk is copied successfully, but /etc/fstab is left with comments only.

Command line:

weresync -C -L grub2 -E 1 -g 2 --source-mask '{0}p{1}' /dev/nvme0n1 /dev/sda

/etc/fstab from destination disk:


# This file is generated by WereSync. All comments have been copied, but they have not been parsed.
# Any reference to identifiers during installation may be inaccurate.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation

/var/log/weresync/weresync.log

DEBUG - 2023-12-15 17:53:10,449 - weresync.daemon.device - Setting to finished
INFO - 2023-12-15 17:53:10,449 - weresync.daemon.device - Using plugin: grub2
DEBUG - 2023-12-15 17:53:10,848 - parse - format '/dev/nvme0n1p{0}' -> '/dev/nvme0n1p(.+?)'
WARNING - 2023-12-15 17:53:10,874 - weresync.daemon.device - Error copying fstab. Continuing anyway.
DEBUG - 2023-12-15 17:53:10,874 - weresync.daemon.device - Info:
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/weresync/daemon/device.py", line 1677, in make_bootable
    self._copy_fstab(source_mnt, target_mnt, excluded_partitions)
  File "/usr/local/lib/python3.10/dist-packages/weresync/daemon/device.py", line 1451, in _copy_fstab
    raise weresync.exception.DeviceError(
weresync.exception.DeviceError: ('/dev/sda', 'Could not find device /dev/sda2', '')

pip show weresync

Name: WereSync
Version: 1.1.5
Summary: Incrementally clones Linux drives
Home-page: https://github.com/DonyorM/weresync

When I use the same version in another machine copying from /dev/sda to /dev/sdb it works fine. Maybe using source-mask breaks /etc/fstab modification?

Thank you!

NOTE: Both source and destination disk has 2 partitions (So message "'Could not find device /dev/sda2" is strange):

sda           8:0    0 223,6G  0 disk
├─sda1        8:1    0   512M  0 part
└─sda2        8:2    0 223,1G  0 part /media/servidor/c303d4eb-944b-435c-97e8-27d448947bec
nvme0n1     259:0    0 232,9G  0 disk
├─nvme0n1p1 259:1    0   512M  0 part /boot/efi
└─nvme0n1p2 259:2    0 232,4G  0 part /

Remote targets

Since you are using rsync under the hood - any plans to allow remote targets?

GUI Interface

At some point I would like to add a GUI interface to WereSync, so it will be easier to use for the less technically inclined.

It would simply serve as an interface to the copy_files() method in weresync.interface, similar to the main() method.

Command not found error

Hello,
I followed the below process to install weresync on Ubuntu 16.04:

python3 -m venv weresync-env

source weresync-env/bin/activate

pip install weresync

Then, when I run sudo weresync-gui I get sudo: weresync-gui: command not found

Strangely, when I try weresync -h the help text is properly displayed, but when I try
sudo weresync /dev/sdb /dev/sdc I get sudo: weresync: command not found

Any help to troubleshoot would be very much appreciated, as I would love to use this package.

Thank you for your time.

Error with bootloader install with LVM

I'm not entirely sure what is causing this error, but hopefully the traceback will be more useful to someone more familiar with the project.

~$ sudo weresync -C -l maggie-vg -E 1 -g 3 -B 2 /dev/sda /dev/sdb
Checking partition validity.
Checking partition validity.
WARNING - 2018-05-11 18:23:41,483 - weresync.interface - Partition count on two drives different. Invalid.
Partitions invalid!
Copying drive partition table.
WARNING - 2018-05-11 18:23:41,484 - weresync.interface - Drives are incompatible.
Beginning to copy files.
Copying partition 1
Copying partition 2
WARNING - 2018-05-11 18:23:42,465 - weresync.device - Error copying data for partition 3 from device /dev/sda to /dev/sdb.
Finished copying files.
Copying partition root

WARNING - 2018-05-11 18:26:27,530 - weresync.device - Error copying data for partition swap_1 from device maggie--vg to /dev/maggie-vg-copy.
Finished copying files.
Finished copying files.
Making bootable
WARNING - 2018-05-11 18:26:27,710 - weresync.device - Error copying fstab on LVM. Continuing anyway.
Traceback (most recent call last):
  File "/usr/local/bin/weresync", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.5/dist-packages/weresync/interface.py", line 510, in main
    bootloader=args.bootloader, )
  File "/usr/local/lib/python3.5/dist-packages/weresync/interface.py", line 334, in copy_drive
    boot_partition, efi_partition, boot_callback)
  File "/usr/local/lib/python3.5/dist-packages/weresync/device.py", line 1687, in make_bootable
    root_partition, efi_partition)
  File "/usr/local/lib/python3.5/dist-packages/weresync/plugins/weresync_uuid_copy.py", line 52, in install_bootloader
    plugins.translate_uuid(copier, boot_partition, "/", target_mnt)
  File "/usr/local/lib/python3.5/dist-packages/weresync/plugins/__init__.py", line 75, in translate_uuid
    uuid_dict = copier.get_uuid_dict()
  File "/usr/local/lib/python3.5/dist-packages/weresync/device.py", line 870, in get_uuid_dict
    source_vg = parse.parse("/dev/{0}", self.lvm_source.device)[0]
TypeError: 'NoneType' object is not subscriptable

The disk I'm trying to copy looks like this (the default layout created by the Ubuntu 16.04 Server installer):

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: DEBCE901-CC7C-4BEF-9F73-9E0DD685A046

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1050623   1048576   512M EFI System
/dev/sda2  1050624   2050047    999424   488M Linux filesystem
/dev/sda3  2050048 976771071 974721024 464.8G Linux LVM

Running Python 3.5.2 with weresync installed via pip on Ubuntu 16.04.3 (Linux 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux)

Log file is attached.
weresync.log

Supporting more boot setups

Bootloaders are complex things. Right now WereSync only support certain setups of grub. More bootloading setups would be much appreciated.

source hdd won't boot after running weresync

When I tried WereSync to clone my 500GB HDD to a 250GB SSD, neither my new SSD nor my original HDD would boot at all. So I've gone from a working system to a broken one...

Any ideas as to what to try? My original set-up was headless, but attaching to a monitor and booting just leads to a blank screen; the various recovery options don't yield anything, but if I choose Run UEFI Application I can run grubx64.efi and successfully boot the system. But I'm at a loss as to how to make this happen automatically (and I need to switch it back to a headless system...)

Any help gratefully received!

Fresh out of Synaptic: Linux Mint 20 / Ubuntu

sudo weresync-gui

Missing is the weresync-daemon, too

Traceback (most recent call last):
File "/usr/sbin/weresync-gui", line 11, in
load_entry_point('WereSync==1.0.7', 'gui_scripts', 'weresync-gui')()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 490, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2854, in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2445, in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2451, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/usr/share/weresync/weresync/gui.py", line 18, in
import weresync.plugins as plugins
File "/usr/share/weresync/weresync/plugins/init.py", line 29, in
from distutils.sysconfig import get_python_lib
ModuleNotFoundError: No module named 'distutils.sysconfig'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook
with os.fdopen(os.open(pr_filename,
FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_share_weresync_run-gui.0.crash'

Original exception was:
Traceback (most recent call last):
File "/usr/sbin/weresync-gui", line 11, in
load_entry_point('WereSync==1.0.7', 'gui_scripts', 'weresync-gui')()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 490, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2854, in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2445, in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2451, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/usr/share/weresync/weresync/gui.py", line 18, in
import weresync.plugins as plugins
File "/usr/share/weresync/weresync/plugins/init.py", line 29, in
from distutils.sysconfig import get_python_lib
ModuleNotFoundError: No module named 'distutils.sysconfig'

Python gi module issue

Python = 3.6
OS = Ubuntu 14 LTS

I seem to be able to install Weresync just fine but get this error message when running the application:

Traceback (most recent call last):
  File "/usr/local/bin/weresync", line 11, in <module>
    load_entry_point('WereSync==1.1.5', 'console_scripts', 'weresync')()
  File "/usr/local/lib/python3.6/dist-packages/setuptools-33.1.1-py3.6.egg/pkg_resources/__init__.py", line 561, in load_entry_point
  File "/usr/local/lib/python3.6/dist-packages/setuptools-33.1.1-py3.6.egg/pkg_resources/__init__.py", line 2631, in load_entry_point
  File "/usr/local/lib/python3.6/dist-packages/setuptools-33.1.1-py3.6.egg/pkg_resources/__init__.py", line 2291, in load
  File "/usr/local/lib/python3.6/dist-packages/setuptools-33.1.1-py3.6.egg/pkg_resources/__init__.py", line 2297, in resolve
  File "/usr/local/lib/python3.6/dist-packages/WereSync-1.1.5-py3.6.egg/weresync/interface/cli.py", line 20, in <module>
    import weresync.interface.dbus_client as dbus_client
  File "/usr/local/lib/python3.6/dist-packages/WereSync-1.1.5-py3.6.egg/weresync/interface/dbus_client.py", line 17, in <module>
    from pydbus import SystemBus
  File "/usr/local/lib/python3.6/dist-packages/pydbus-0.6.0-py3.6.egg/pydbus/__init__.py", line 1, in <module>
  File "/usr/local/lib/python3.6/dist-packages/pydbus-0.6.0-py3.6.egg/pydbus/bus.py", line 1, in <module>
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 36, in <module>
    from ._gi import _gobject
ModuleNotFoundError: No module named 'gi._gi'

I need some help figuring out what is going wrong, I've tried reinstalling python3 many times.

Installation with pip not working

Tryng to install with pip python 3.6.7 in ubuntu 18.10 get this error
Downloading https://files.pythonhosted.org/packages/ef/f7/62352a45b181fa28c0dc6a92dc070be82c1353ae64a6092e23f200e4398d/WereSync-1.0.9.tar.gz (157kB)
100% |████████████████████████████████| 163kB 3.0MB/s
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-build-HScKSK/weresync/setup.py", line 66, in
"weresync.resources": [".svg", ".png"] + create_mo_files()
File "/tmp/pip-build-HScKSK/weresync/setup.py", line 19, in create_mo_files
if shutil.which("msgfmt") is None:
AttributeError: 'module' object has no attribute 'which'

DBus.Error.AccessDenied

I installed weresync on my system using: pip3 install weresync

However, when I try to start the weresync-daemon, I get the following error:

peter@peter-DX4831:~$ sudo ~/.local/bin/weresync-daemon
[sudo] password for peter: 
Traceback (most recent call last):
  File "/home/peter/.local/bin/weresync-daemon", line 11, in <module>
    sys.exit(run())
  File "/home/peter/.local/lib/python3.6/site-packages/weresync/daemon/daemon.py", line 37, in run
    with bus.publish("net.manilas.weresync.DriveCopier", DriveCopier()):
  File "/home/peter/.local/lib/python3.6/site-packages/pydbus/publication.py", line 42, in publish
    return Publication(self, bus_name, *objects)
  File "/home/peter/.local/lib/python3.6/site-packages/pydbus/publication.py", line 35, in __init__
    self._at_exit(bus.request_name(bus_name, allow_replacement=allow_replacement, replace=replace).__exit__)
  File "/home/peter/.local/lib/python3.6/site-packages/pydbus/request_name.py", line 29, in request_name
    return NameOwner(self, name, allow_replacement, replace)
  File "/home/peter/.local/lib/python3.6/site-packages/pydbus/request_name.py", line 8, in __init__
    res = bus.dbus.RequestName(name, flags)
  File "/home/peter/.local/lib/python3.6/site-packages/pydbus/proxy_method.py", line 75, in __call__
    0, timeout_to_glib(timeout), None).unpack()
GLib.Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Connection ":1.114" is not allowed to own the service "net.manilas.weresync.DriveCopier" due to security policies in the configuration file (9)

Do you have any suggestions about what I could do to fix this error?

Thanks!
-Peter

PCIe connected NVMe SSDs' partition reading messed up

EDIT: I didn't mask.
Original issue:

After I do:

sudo weresync-daemon & >/dev/null 2>&1
weresync -vg 2 -E 3 /dev/nvme0n1 /dev/sdb

cat /var/log/weresync/weresync.log shows:

DEBUG - 2019-10-12 19:26:15,964 - weresync.utils - Enabling localization
DEBUG - 2019-10-12 19:26:15,965 - weresync.daemon.copier - making object
DEBUG - 2019-10-12 19:26:15,968 - weresync.daemon.daemon - Starting GLib loop
DEBUG - 2019-10-12 19:26:27,233 - weresync.daemon.copier - Daemon starting clone.
WARNING - 2019-10-12 19:26:28,342 - weresync.daemon.device - Error copying data for partition 1 from device /dev/nvme0n1 to /dev/sdb.
DEBUG - 2019-10-12 19:26:28,342 - weresync.daemon.device - Error info.
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 1512, in _copy_files
    source_manager.mount_partition(i, mnt_source)
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/nvme0n1', 'Non-zero exit code. Partition Number: 1', 'mount: /tmp/98224: special device /dev/nvme0n11 does not exist.\n')
WARNING - 2019-10-12 19:26:28,350 - weresync.daemon.device - Error copying data for partition 2 from device /dev/nvme0n1 to /dev/sdb.
DEBUG - 2019-10-12 19:26:28,351 - weresync.daemon.device - Error info.
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 1512, in _copy_files
    source_manager.mount_partition(i, mnt_source)
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/nvme0n1', 'Non-zero exit code. Partition Number: 2', 'mount: /tmp/98224: special device /dev/nvme0n12 does not exist.\n')
WARNING - 2019-10-12 19:26:28,356 - weresync.daemon.device - Error copying data for partition 3 from device /dev/nvme0n1 to /dev/sdb.
DEBUG - 2019-10-12 19:26:28,357 - weresync.daemon.device - Error info.
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 1512, in _copy_files
    source_manager.mount_partition(i, mnt_source)
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/nvme0n1', 'Non-zero exit code. Partition Number: 3', 'mount: /tmp/98224: special device /dev/nvme0n13 does not exist.\n')
INFO - 2019-10-12 19:26:28,357 - weresync.daemon.device - Using plugin: uuid_copy
DEBUG - 2019-10-12 19:26:28,410 - weresync.daemon.device - Failed to mount partition. Info:
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 1346, in _copy_fstab
    source_manager.mount_partition(i, mnt_source)
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/nvme0n1', 'Non-zero exit code. Partition Number: 1', 'mount: /tmp/98224: special device /dev/nvme0n11 does not exist.\n')
DEBUG - 2019-10-12 19:26:28,414 - weresync.daemon.device - Failed to mount partition. Info:
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 1346, in _copy_fstab
    source_manager.mount_partition(i, mnt_source)
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/nvme0n1', 'Non-zero exit code. Partition Number: 2', 'mount: /tmp/98224: special device /dev/nvme0n12 does not exist.\n')
DEBUG - 2019-10-12 19:26:28,418 - weresync.daemon.device - Failed to mount partition. Info:
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 1346, in _copy_fstab
    source_manager.mount_partition(i, mnt_source)
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/nvme0n1', 'Non-zero exit code. Partition Number: 3', 'mount: /tmp/98224: special device /dev/nvme0n13 does not exist.\n')
WARNING - 2019-10-12 19:26:28,876 - weresync.daemon.device - Error copying bootloader.
DEBUG - 2019-10-12 19:26:28,877 - weresync.daemon.device - Info: 
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 1694, in make_bootable
    root_partition, efi_partition)
  File "/usr/lib/python3.7/site-packages/weresync/plugins/weresync_uuid_copy.py", line 54, in install_bootloader
    plugins.translate_uuid(copier, root_partition, "/boot", target_mnt)
  File "/usr/lib/python3.7/site-packages/weresync/plugins/__init__.py", line 56, in translate_uuid
    copier.target.mount_partition(partition, target_mnt)
  File "/usr/lib/python3.7/site-packages/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/sdb', 'Non-zero exit code. Partition Number: 2', 'mount: /tmp/-82531: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error.\n')

The thing is that NVMe drives use nvme0nXpY versus the normal sdXY, where X is the drive number and Y is the partition number.

So weresync is looking for a partition at nvme011 on my laptop, which of course does not exist.

Centos 7 and XFS

I tried multiple time but i found out that if i use this tool with XFS partitions it fails.
Can you please add the support to it?
There is a big amount of people on the community that are using Google Cloud and there for some reason they are stuck with XFS if they choose Centos as their main VM's

If you need some info about the CentosOS testing i can maybe help, for now i have done this:

I tried to use weresync to copy my /dev/sda disk into /dev/sdb (the external disk with reduced size) and it worked, it creates the partition correctly but i cant boot from that disk.
The only thing that im thinking is that maybe the bootloader (i suppose grub2) is installed in the MBR and that he cant copy that.
(weresync is used for normal systems where you have a partition like /dev/sda1 for the bootloader and /dev/sda2 for the system).

and i also tried the normal way but i think its a XFS problem

-i created a disk of 30gb and attached it to my instance
-i crated a snapshot disk of my original disk (the 40gb one)
-i mounted both in /mnt/big and /mnt/small
-i formatted the small one to replicate the partition of the 40gb one (xfs partition) and then i rsynced.
-i setted the old uuid-label from the original disk to the small one with "xfs_admin -U label-uuid /dev/sdc1" and gived it the "/" root label to make it bootable.

Keep the good work

After installing via pip, the weresync command is still not available.

WereSync Version [0.2]:
Name of Distribution (ex. Ubuntu): Ubuntu
Version of Distribution (ex. 16.04): 16.10
Python version (ex. 3.4):
Gist linking to log file (found in /var/log/weresync):
Expected Behavior:

On typing weresync, see it execute.

Actual Behavior:

zsh: command not found: weresync

Other relevant details:

weresync fails with "Error: /dev/sdb: unrecognised disk label"

WereSync Version [0.2]: 0.2.1
Name of Distribution (ex. Ubuntu): CentOS
Version of Distribution (ex. 16.04): 7
Python version (ex. 3.4): 3.4

Expected Behavior:
This works:

sudo weresync --verbose -C --boot-partition 2 --efi-partition 1 /dev/sda /dev/sdb

/dev/sda is the source 1 TB SSD
/dev/sdb is a brand new 500 GB SSD, just out of the box.

Actual Behavior:

$ sudo pip3 install weresync
Collecting weresync
  Downloading WereSync-0.2.1-py3-none-any.whl (70kB)
    100% |████████████████████████████████| 71kB 1.4MB/s 
Collecting parse>=1.6.6 (from weresync)
  Using cached parse-1.8.0.tar.gz
Installing collected packages: parse, weresync
  Running setup.py install for parse ... done
Successfully installed parse-1.8.0 weresync-0.2.1
You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
$ sudo weresync --verbose -C --boot-partition 2 --efi-partition 1 /dev/sda /dev/sdb
Checking partition validity.
Traceback (most recent call last):
  File "/bin/weresync", line 11, in <module>
    sys.exit(main())
  File "/usr/lib64/python3.4/site-packages/weresync/interface.py", line 217, in main
    mount_points, args.rsync_args)
  File "/usr/lib64/python3.4/site-packages/weresync/interface.py", line 129, in copy_drive
    copier.partitions_valid()
  File "/usr/lib64/python3.4/site-packages/weresync/device.py", line 657, in partitions_valid
    target_parts = self.target.get_partitions()
  File "/usr/lib64/python3.4/site-packages/weresync/device.py", line 69, in get_partitions
    raise weresync.exception.DeviceError(self.device, "Non-zero exit code", str(error, "utf-8"))
weresync.exception.DeviceError: ('/dev/sdb', 'Non-zero exit code', 'Error: /dev/sdb: unrecognised disk label\n')
$ sudo parted -s /dev/sdb p
Error: /dev/sdb: unrecognised disk label
Model: Samsung SSD 850 EVO 500G (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

This fixed the problem: $ sudo parted /dev/sdb --script -- mklabel gpt but I would have expected weresync to do this for me.

Can't launch in Manjaro/KDE plasma

No luck trying to run weresync.

Operating System: Manjaro Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 5.15.89-1-MANJARO (64-bit)
Graphics Platform: X11

Weresync 1.1.5-1,  installed with pamac.

Atttempts to launch via launcher results in a brief flicker, but no running weresync.

Command line throws an error:

$ weresync 
Traceback (most recent call last):
File "/usr/bin/weresync", line 33, in <module>
sys.exit(load_entry_point('WereSync==1.1.5', 'console_scripts', 'weresync')())
File "/usr/bin/weresync", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/usr/lib/python3.10/site-packages/weresync/interface/cli.py", line 20, in <module>
import weresync.interface.dbus_client as dbus_client
File "/usr/lib/python3.10/site-packages/weresync/interface/dbus_client.py", line 17, in <module>
from pydbus import SystemBus

And weresync-gui asks for root password before the error:

$ weresync-gui
/usr/bin/pkexec
Job for weresync.service failed because the control process exited with error code.
See "systemctl status weresync.service" and "journalctl -xeu weresync.service" for details.
Gtk-Message: 01:01:57.782: Failed to load module "appmenu-gtk-module"
Traceback (most recent call last):
File "/usr/bin/weresync-gui-only", line 33, in <module>
sys.exit(load_entry_point('WereSync==1.1.5', 'gui_scripts', 'weresync-gui')())
File "/usr/bin/weresync-gui-only", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/usr/lib/python3.10/site-packages/weresync/interface/gui.py", line 33, in <module>
import weresync.interface.dbus_client as dbus_client
File "/usr/lib/python3.10/site-packages/weresync/interface/dbus_client.py", line 17, in <module>
from pydbus import SystemBus
ModuleNotFoundError: No module named 'pydbus'
/usr/bin/pkexec

A directory /var/log/weresync/ does not exist here (crash too early to write it?).

Kernel log shows 31.01.23 01:01 audit type=1130 audit(1675123317.588:1312): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=weresync comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'for every attempt (different time stamps, of course).

Error on launching fresh install (via Manjaro Add/Remove Apps gui)

Installed through Manjaro's Add/Remove App gui.

When running on terminal:

weresync
Traceback (most recent call last):
  File "/home/myara/.local/bin/weresync", line 5, in <module>
    from weresync.interface.cli import main
  File "/usr/lib/python3.9/site-packages/weresync/interface/cli.py", line 20, in <module>
    import weresync.interface.dbus_client as dbus_client
  File "/usr/lib/python3.9/site-packages/weresync/interface/dbus_client.py", line 17, in <module>
    from pydbus import SystemBus
ModuleNotFoundError: No module named 'pydbus'

Tried to re-intall python's dbus, like:
pip install dbus-python
dbus installed ok, but weresync launch error still happens.
Any suggestions?

Failed to connect to dbus service. Is it running?

I installed weresync on Ubuntu 20.04 Server using pip3 install weresync.
Then I ran sudo weresync-daemon & >/dev/null 2>&1 which returns:

[1] 16114

running it again returns:

[2] 16133 Traceback (most recent call last): File "/usr/local/bin/weresync-daemon", line 11, in <module> load_entry_point('WereSync==1.1.5', 'console_scripts', 'weresync-daemon')() File "/usr/local/lib/python3.8/dist-packages/WereSync-1.1.5-py3.8.egg/weresync/daemon/daemon.py", line 37, in run with bus.publish("net.manilas.weresync.DriveCopier", DriveCopier()): File "/usr/local/lib/python3.8/dist-packages/pydbus-0.6.0-py3.8.egg/pydbus/publication.py", line 42, in publish return Publication(self, bus_name, *objects) File "/usr/local/lib/python3.8/dist-packages/pydbus-0.6.0-py3.8.egg/pydbus/publication.py", line 35, in __init__ self._at_exit(bus.request_name(bus_name, allow_replacement=allow_replacement, replace=replace).__exit__) File "/usr/local/lib/python3.8/dist-packages/pydbus-0.6.0-py3.8.egg/pydbus/request_name.py", line 29, in request_name return NameOwner(self, name, allow_replacement, replace) File "/usr/local/lib/python3.8/dist-packages/pydbus-0.6.0-py3.8.egg/pydbus/request_name.py", line 13, in __init__ raise RuntimeError("name already exists on the bus") RuntimeError: name already exists on the bus

I just can't get this to work without being thrown some sort of error no matter what I do. Is this even still under development or some sort of supervision? Please help!

Cannot target /dev/nvme0n1 but /dev/sd? seems to work fine.

$ sudo weresync -v /dev/sdb /dev/nvme0n1 -g2 -B1 -E1
Beginning to copy files.
WARNING - 2018-10-31 10:42:20,846 - weresync.device - Error copying data for partition 1 from device /dev/sdb to /dev/nvme0n1.
WARNING - 2018-10-31 10:42:20,853 - weresync.device - Error copying data for partition 2 from device /dev/sdb to /dev/nvme0n1.
Finished copying files.
Finished copying files.
Making bootable
INFO - 2018-10-31 10:42:20,853 - weresync.device - Using plugin: uuid_copy
WARNING - 2018-10-31 10:42:20,892 - weresync.device - Error copying fstab. Continuing anyway.
WARNING - 2018-10-31 10:42:20,897 - weresync.device - Error copying bootloader.
All done, enjoy your drive!

Does it matter that nvme0n1 uses p1 and p2 as drive identifiers and not 1 or 2?
Like /dev/nvme0n1p1 instead of say /dev/sd?1

Error: Can't have a partition outside the disk!

I'm trying to shrink a 200 GB boot disk (43GB of this disk is used) to a 50 GB disk on GCP. So I attached a 50 GB additional disk and ran weresync -C -L grub2 -g 1 /dev/sda /dev/sdb. But I'm getting this error upon running the weresync command.

weresync -C -L grub2 -g 1 /dev/sda /dev/sdb

Traceback (most recent call last):
  File "/usr/local/bin/weresync", line 11, in <module>
    load_entry_point('WereSync==1.1.5', 'console_scripts', 'weresync')()
  File "/usr/local/lib64/python3.6/site-packages/weresync/interface/cli.py", line 255, in main
    lvm_target, args.bootloader)
  File "/usr/local/lib/python3.6/site-packages/pydbus/proxy_method.py", line 75, in __call__
    0, timeout_to_glib(timeout), None).unpack()
GLib.Error: g-io-error-quark: GDBus.Error:unknown.DeviceError: ('/dev/sdb', 'Non-zero exit code', "Error: Can't have a partition outside the disk!\nModel: Google PersistentDisk (scsi)\nDisk /dev/sdb: 53.7GB\nSector size (logical/physical): 512B/4096B\nPartition Table: unknown\nDisk Flags: \n") (36)

The partition size created by weresync is greater than the disk size.

 sudo fdisk -l -u /dev/sdb

Disk /dev/sdb: 53.7 GB, 53687091200 bytes, 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048   105737510    52867731+  83  Linux

I followed the instruction in this article.

Can anyone help?

No translation file found for domain: 'weresync'

Hi there -- this looks like a great project. I haven't been able to get it running on Ubuntu 16.04 MATE amd64 or armhf. After installing either from pip or from the github I get the following output:

guygma@baggins:~/repos/github.com/clones/weresync$ weresync -h
Traceback (most recent call last):
  File "/usr/local/bin/weresync", line 9, in <module>
    load_entry_point('WereSync==1.0.4', 'console_scripts', 'weresync')()
  File "/usr/local/lib/python3.5/dist-packages/WereSync-1.0.4-py3.5.egg/weresync/interface.py", line 352, in main
    enable_localization()
  File "/usr/local/lib/python3.5/dist-packages/WereSync-1.0.4-py3.5.egg/weresync/interface.py", line 45, in enable_localization
    languages=LANGUAGES)
  File "/usr/lib/python3.5/gettext.py", line 432, in translation
    raise OSError(ENOENT, 'No translation file found for domain', domain)
FileNotFoundError: [Errno 2] No translation file found for domain: 'weresync'

Is this a known issue? I am using Python 3.5

AttributeError: 'module' object has no attribute 'which'

hi all, when I want to install this package I got this error:

$ pip install weresync
Collecting weresync
  Downloading WereSync-1.0.7.tar.gz (157kB)
    100% |████████████████████████████████| 163kB 487kB/s
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/pq/k8mwc5cx6d77wp3nd60m_l8h0000gn/T/pip-build-5M0DNi/weresync/setup.py", line 66, in <module>
        "weresync.resources": ["*.svg", "*.png"] + create_mo_files()
      File "/private/var/folders/pq/k8mwc5cx6d77wp3nd60m_l8h0000gn/T/pip-build-5M0DNi/weresync/setup.py", line 19, in create_mo_files
        if shutil.which("msgfmt") is None:
    AttributeError: 'module' object has no attribute 'which'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/pq/k8mwc5cx6d77wp3nd60m_l8h0000gn/T/pip-build-5M0DNi/weresync/

how I can fix it? I'm running macos X.

How to make an incremental full disk backup?

Just to make it easier to get started with this, how do I make an incremental full disk backup of a running live disk, with no deduplication, so that the backup disk can replace the source disk in the case of failure? I want to set a cron job so that it keeps the backup disk incrementally updated once a day. Thanks.

Failed to connect to dbus service.

ENV
OS : Google cloud Centos7

When i used sudo weresync -C --grub-partition 1 /dev/sda /dev/sdb, the command fails.

output error
Failed to connect to dbus service. Is it running?

But dbus service status is active(running).

How can i solve this problem?

RFE: Support simple partition table to lvm copying

Expected Behavior:
weresync --lvm source destination
Actual Behavior:
It does not exist
Other relevant details:
Create a vg and then the lv

Thank you

Failed to wipe signatures on logical volume

Hi !!

I am trying to clone a drive to an smaller SSD with enough free space using the command line since the gui version seem's to work for 2 hours but then errors out saying it cannot start the cloning process. Now trying to use the command line but I get this error right after the partition table is copied:

Partition Table Copying: |████████████████████████████████████████████████████████████| 100.0% Traceback (most recent call last): File "/usr/local/bin/weresync", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.10/site-packages/weresync/interface/cli.py", line 250, in main result = dbus_client.copy_drive( File "/usr/lib/python3.10/site-packages/pydbus/proxy_method.py", line 102, in __call__ raise error File "/usr/lib/python3.10/site-packages/pydbus/proxy_method.py", line 97, in __call__ result = instance._bus.con.call_sync(*call_args) gi.repository.GLib.GError: g-io-error-quark: GDBus.Error:unknown.DeviceError: ('/dev/fedora_localhost-live-copy', 'Error creating new logical volume.', 'WARNING: ext4 signature detected on /dev/fedora_localhost-live-copy/home00 at offset 1080. Wipe it? [y/n]: [n]\n Aborted wiping of ext4.\n 1 existing signature left on the device.\n Failed to wipe signatures on logical volume fedora_localhost-live-copy/home00.\n Aborting. Failed to wipe start of new LV.\n') (36)

There seem's it got a "wipe it?" command but it automatically awnsers no.

the command i am using is like this:
weresync -C -l fedora_localhost-live -E 1 -B 2 /dev/sdb /dev/sdc

I'm on Fedora 35, let me know if you need more infos/logs then what's up here.

Thanks a lot for your help.

sly

The -S rsync option would be a useful default

It would be useful to add the rsync -S option as one of the default rsync options to more efficiently copy sparse files to avoid potentially running out of disk space when cloning to smaller disks. This issue happened the first time I used this utility. The sparse file causing the issue was Docker's devicemapper file.

local variable 'table_type' referenced before assigment

Hello,
I am just trying to use weresync-gui to clone a running drive (and weresync) because it looks to me very interesting like Carbon Copy Cloner on mac. .
I am under ubuntu 17.10 on disk sde,
I have installed Ubuntu 17.04 on sdc (thinking it would help cloning).
Running weresync-gui with: source: /dev/sde to destination: /dev/sdc

with Bootloader UUID Copy checked ,and root partition 2 :
But I got the following error :
Error starting clone : local variable 'table_type' referenced before assigment.
Idem if I run from terminal with : sudo weresync -C /dev/sde /dev/sdc
I am far for being an expert . So
Please can someone tell me what this means and ... may be the 'solution'.
Dominique

"Error creating logical volume group" during LVM clone

I'm trying to clone a 250GB HDD to a 240GB SSD on Ubuntu Server 18.04. Pretty standard partition layout I think:

$ lsblk -l
NAME                  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0                   7:0    0    89M  1 loop /snap/core/[redacted]
loop1                   7:1    0  89.1M  1 loop /snap/core/[redacted]
sda                     8:0    0 232.9G  0 disk
sda1                    8:1    0   512M  0 part /boot/efi
sda2                    8:2    0     1G  0 part /boot
sda3                    8:3    0 231.4G  0 part
sdb                     8:16   0 223.6G  0 disk
ubuntu--vg-ubuntu--lv 253:0    0    50G  0 lvm  /
ubuntu--vg-lv--0      253:1    0 181.4G  0 lvm  /home

Note that I had some trouble installing with pip, perhaps this is what you mean on the release page. I opted to use the provided .deb. Here is what I've issued:

sudo apt install python3-pydbus
wget https://github.com/DonyorM/weresync/releases/download/v1.1.5/weresync-doc_1.1.5-1_all.deb
sudo dpkg -i weresync-doc_1.1.5-1_all.deb
sudo apt install -f

sudo weresync-daemon > /dev/null 2>&1 &
weresync -C -l ubuntu-vg -B2 -E1 /dev/sda /dev/sdb

I get the following error message:

Partition Table Copying: |████████████████████████████████████████████████████████████| 100.0%
Traceback (most recent call last):
  File "/usr/bin/weresync", line 11, in <module>
    load_entry_point('WereSync==1.1.5', 'console_scripts', 'weresync')()
  File "/usr/share/weresync/weresync/interface/cli.py", line 255, in main
    lvm_target, args.bootloader)
  File "/home/radu/.local/lib/python3.6/site-packages/pydbus/proxy_method.py", line 75, in __call__
    0, timeout_to_glib(timeout), None).unpack()
GLib.Error: g-io-error-quark: GDBus.Error:unknown.DeviceError: ('/dev/sdb', 'Error creating logical volume group.', "  No command with matching syntax recognised.  Run 'vgcreate --help' for more information.\n  Correct command syntax is:\n  vgcreate VG_new PV ...\n\n") (36)

and the log:

DEBUG - 2019-10-28 02:10:48,615 - weresync.daemon.copier - Daemon starting clone.
DEBUG - 2019-10-28 02:10:48,988 - weresync.daemon.device - Partition 3 couldn't be mounted. Bad FS type
Traceback (most recent call last):
  File "/usr/share/weresync/weresync/daemon/device.py", line 1303, in partitions_valid
    i) > target_manager.get_partition_size(i):
  File "/usr/share/weresync/weresync/daemon/device.py", line 332, in get_partition_used
    return int(self._get_general_info(partition_num)[2])
  File "/usr/share/weresync/weresync/daemon/device.py", line 299, in _get_general_info
    self.mount_partition(partition_num, MOUNT_POINT)
  File "/usr/share/weresync/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/sda', 'Non-zero exit code. Partition Number: 3', "mount: /mnt: unknown filesystem type 'LVM2_member'.\n")
INFO - 2019-10-28 02:10:48,989 - weresync.daemon.copier - Drives are compatible
ERROR - 2019-10-28 02:10:49,132 - pydbus.registration - Exception while handling net.manilas.weresync.DriveCopier.CopyDrive()
Traceback (most recent call last):
  File "/home/radu/.local/lib/python3.6/site-packages/pydbus/registration.py", line 81, in call_method
    result = method(*parameters, **kwargs)
  File "/usr/share/weresync/weresync/daemon/copier.py", line 297, in CopyDrive
    target_manager)
  File "/usr/share/weresync/weresync/daemon/copier.py", line 70, in create_new_vg_if_not_exists
    "Error creating logical volume group.")
  File "/usr/share/weresync/weresync/utils.py", line 64, in run_proc
    raise DeviceError(target, error, output)
weresync.exception.DeviceError: ('/dev/sdb', 'Error creating logical volume group.', "  No command with matching syntax recognised.  Run 'vgcreate --help' for more information.\n  Correct command syntax is:\n  vgcreate VG_new PV ...\n\n")

Edit: I was specifying the volume group wrong I believe but errors persist:

$ sudo weresync -v -C -l /dev/ubuntu-vg/ -B2 -E1 /dev/sda /dev/sdb
Partition Table Copying: |████████████████████████████████████████████████████████████| 100.0%
Copying Partition 1.0: |████████████████████████████████████████████████████████████| 100.0%
Copying Partition 2.0: |████████████████████████████████████████████████████████████| 100.0%
Copying Partition 3.0: |------------------------------------------------------------| 0.0%
Some error copying partition 3.0. Probably fine, but see logs.
Bootloader installed
All done, enjoy your drive!

and the logs:

DEBUG - 2019-10-28 04:44:06,767 - weresync.daemon.copier - Daemon starting clone.
DEBUG - 2019-10-28 04:44:07,274 - weresync.daemon.device - Partition 3 couldn't be mounted. Bad FS type
Traceback (most recent call last):
  File "/usr/share/weresync/weresync/daemon/device.py", line 1303, in partitions_valid
    i) > target_manager.get_partition_size(i):
  File "/usr/share/weresync/weresync/daemon/device.py", line 332, in get_partition_used
    return int(self._get_general_info(partition_num)[2])
  File "/usr/share/weresync/weresync/daemon/device.py", line 299, in _get_general_info
    self.mount_partition(partition_num, MOUNT_POINT)
  File "/usr/share/weresync/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/sda', 'Non-zero exit code. Partition Number: 3', "mount: /mnt: unknown filesystem type 'LVM2_member'.\n")
INFO - 2019-10-28 04:44:07,275 - weresync.daemon.copier - Drives are compatible
DEBUG - 2019-10-28 04:44:07,434 - weresync.daemon.copier - PVs in LVM:
INFO - 2019-10-28 04:44:07,457 - weresync.daemon.copier - Drives are compatible
INFO - 2019-10-28 04:44:07,576 - weresync.daemon.device - Starting rsync process for partition /dev/sda.
DEBUG - 2019-10-28 04:44:07,576 - weresync.daemon.device - Arguments = rsync -aAXxH --delete --exclude=/dev/* --exclude=/proc/* --exclude=/sys/* --exclude=/tmp/* --exclude=/run/* --exclude=/mnt/* --exclude=/media/* --exclude=/lost+found --exclude=/home/*/.gvfs /boot/efi/ /tmp/-33610 --info=progress2
DEBUG - 2019-10-28 04:44:07,596 - weresync.daemon.device - Errors for partition 1:

DEBUG - 2019-10-28 04:44:07,596 - weresync.daemon.device - Setting to finished
INFO - 2019-10-28 04:44:07,646 - weresync.daemon.device - Starting rsync process for partition /dev/sda.
DEBUG - 2019-10-28 04:44:07,646 - weresync.daemon.device - Arguments = rsync -aAXxH --delete --exclude=/dev/* --exclude=/proc/* --exclude=/sys/* --exclude=/tmp/* --exclude=/run/* --exclude=/mnt/* --exclude=/media/* --exclude=/lost+found --exclude=/home/*/.gvfs /boot/ /tmp/-33610 --info=progress2
DEBUG - 2019-10-28 04:44:07,934 - weresync.daemon.device - Errors for partition 2:

rsync: write failed on "/tmp/-33610/vmlinuz-4.15.0-66-generic": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]

DEBUG - 2019-10-28 04:44:07,934 - weresync.daemon.device - Setting to finished
WARNING - 2019-10-28 04:44:07,993 - weresync.daemon.device - Error copying data for partition 3 from device /dev/sda to /dev/sdb.
DEBUG - 2019-10-28 04:44:07,993 - weresync.daemon.device - Error info.
Traceback (most recent call last):
  File "/usr/share/weresync/weresync/daemon/device.py", line 1512, in _copy_files
    source_manager.mount_partition(i, mnt_source)
  File "/usr/share/weresync/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/sda', 'Non-zero exit code. Partition Number: 3', "mount: /tmp/80420: unknown filesystem type 'LVM2_member'.\n")
INFO - 2019-10-28 04:44:08,006 - weresync.daemon.device - Using plugin: uuid_copy
DEBUG - 2019-10-28 04:44:08,093 - weresync.daemon.device - Failed to mount partition. Info:
Traceback (most recent call last):
  File "/usr/share/weresync/weresync/daemon/device.py", line 1346, in _copy_fstab
    source_manager.mount_partition(i, mnt_source)
  File "/usr/share/weresync/weresync/daemon/device.py", line 175, in mount_partition
    partition_num), str(output, "utf-8"))
weresync.exception.DeviceError: ('/dev/sda', 'Non-zero exit code. Partition Number: 3', "mount: /tmp/80420: unknown filesystem type 'LVM2_member'.\n")
DEBUG - 2019-10-28 04:44:08,232 - parse - format '/dev/{0}' -> '/dev/(.+?)'
DEBUG - 2019-10-28 04:44:08,233 - parse - format '/dev/{0}' -> '/dev/(.+?)'
DEBUG - 2019-10-28 04:44:08,249 - weresync.daemon.device - UUID Dict: {[redacted]}

Google unable to boot after weresync completes.

Hey there, I'm not able to get Google VM to boot after completing the sync from a 1TB to 200GB disk. There's plenty of room (only using about 45GB), but there are some odd messages that popup when I'm completing the migration.

Creating new GPT entries. The operation has completed successfully. Checking partition validity. weresync.interface - Partition count on two drives different. Invalid. Partitions invalid! Copying drive partition table. weresync.interface - Drives are incompatible. The operation has completed successfully. weresync.device - Invalid filesystem type found. Partition 14 not formatted. Beginning to copy files. weresync.device - Error copying data for partition 14 from device /dev/sda to /dev/sdb. Copying partition 15 Copying partition 1

Arch Linux Feedback

Hey,

Just to want to give some feedback about Arch Linux, so everything went smoothly, i just have to install some packages (like rsync gptfdisk sgdisk parted).

Since i use systemd boot it give me an error in the end (but related to grub), and in order to complete the switch from my hdd to sdd i just change the PARTUUID number in my boot entries.

Just want to thank you for making this software, it saves me a huge amount of time ❤️

PS : Not really an issue, so you can close it if you want.

donyorm / weresync Goto Github PK

weresync's People

Contributors

Stargazers

Watchers

Forkers

weresync's Issues

Recommend Projects

Recommend Topics

Recommend Org