How to backup with "rpi-clone"?

[kitamura_design]

Hi Kent,

It does live imaging or some sort of equavalent process?

I'll have to check it out :-)

Hi Tim,

Next, I tried the 'force initialized option (-f, and -f2)'.

...
    -f    - force initialize the destination disk by imaging the booted disk partition structure.  File systems are then synced or imaged.
    -f2    - force initialize only the first 2 partitions to the destination. So a multi partition USB boot can initialize clone back toa 2 partition SD card.
...

.. and shows error massage like as below;

Code:

Syncing file systems (can take a long time)
Syncing mounted partitions:
 Mounting /dev/mmcblk0p2 on /mnt/clone
 => rsync // /mnt/clone with-root-excludes ...rsync: readlink_stat("/mnt/clone/debootstrap") failed: Structure needs cleaning (117)
IO error encountered -- skipping file deletion
rsync: recv_generator: failed to stat "/mnt/clone/bin/bzip2": Structure needs cleaning (117)
rsync: recv_generator: mkdir "/mnt/clone/debootstrap" failed: Structure needs cleaning (117)
*** Skipping any contents from this failed directory ***
rsync: recv_generator: failed to stat "/mnt/clone/etc/memcached.conf": Structure needs cleaning (117)
rsync: recv_generator: failed to stat "/mnt/clone/etc/minidlna.conf": Structure needs cleaning (117)
rsync: recv_generator: failed to stat "/mnt/clone/etc/minidlna.conf.dpkg-dist": Structure needs cleaning (117)
rsync: recv_generator: failed to stat "/mnt/clone/etc/mpd.conf": Structure needs cleaning (117)
rsync: recv_generator: failed to stat "/mnt/clone/etc/passwd": Structure needs cleaning (117)
rsync: delete_file: unlink(etc/alternatives/vi.1.gz/pps/clients/pps-ldisc.ko) failed: Read-only file system (30)
rsync: delete_file: unlink(etc/alternatives/vi.1.gz/pps/clients/pps-gpio.ko) failed: Read-only file system (30)
cannot delete non-empty directory: etc/alternatives/vi.1.gz/pps/clients
rsync: delete_file: rmdir(etc/alternatives/vi.1.gz/pps/clients) failed: Read-only file system (30)

.....

kitamura

I'd post the issue on the rpi-clone Git and mention that you are using a squashed file system for /var/www. The error messages though reference other directories which would suggest some other problem.

-Tim

Hi everyone,

Hi,
rpi-clone worked with option -F on my environment.

[before]

Code:

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda           8:0    1 29.3G  0 disk
├─sda1        8:1    1 43.2M  0 part /boot
└─sda2        8:2    1    3G  0 part /
mmcblk0     179:0    0 14.5G  0 disk
├─mmcblk0p1 179:1    0 43.2M  0 part /media/boot
└─mmcblk0p2 179:2    0 14.4G  0 part

[after]

Code:

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda           8:0    1 29.3G  0 disk
├─sda1        8:1    1 43.2M  0 part /media/boot
└─sda2        8:2    1    3G  0 part /media/rootfs
mmcblk0     179:0    0 14.5G  0 disk
├─mmcblk0p1 179:1    0 43.2M  0 part /boot
└─mmcblk0p2 179:2    0 14.4G  0 part /

The backup moOde on to uSD card booted and running.

FYI,
kitamura