How to backup with "rpi-clone"?

[kitamura_design]

Hi,

Is there anyone tried to backup moOde OS using with "rpi-clone"?

....
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/etc/python3/K01triggerhappy") failed: Structure needs cleaning (117)
IO error encountered -- skipping file deletion
rsync: symlink "/mnt/clone/etc/ssl/certs/b7a5b843.0" -> "TWCA_Root_Certification_Authority.pem" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/avahi/services/.moode.service.iZmL7J" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/bash_completion.d/.git-prompt.MrtSff" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/bluetooth/.main.conf.cClK3G" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/bluetooth/.proximity.conf.E1qZ79" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/chromium-browser/.default.QiqthJ" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/chromium-browser/customizations/.00-example.Lwn7lv" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.cached_Lat15-Fixed16.psf.gz.ULRbdi" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.cached_UTF-8_del.kmap.gz.JOQos3" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.cached_setup_font.sh.6IwUqO" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.cached_setup_keyboard.sh.LA4wrA" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.cached_setup_terminal.sh.4U4zjm" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.compose.ARMSCII-8.inc.vrF727" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.compose.CP1251.inc.gsubET" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.compose.CP1255.inc.7FSECI" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/etc/console-setup/.compose.CP1256.inc.AhTKjx" failed: Input/output error (5)
rsync: mkstemp "/mnt/clone/usr/lib/arm-linux-gnueabihf/.libglapi.so.0.0.0.uYF5hC" failed: No space left on device (28)
rsync: mkstemp "/mnt/clone/usr/lib/arm-linux-gnueabihf/.libglib-2.0.a.yKEylt" failed: No space left on device (28)
rsync: rename "/mnt/clone/usr/lib/arm-linux-gnueabihf/.libgmpxx.so.4.5.2.rAgFY3" -> "usr/lib/arm-linux-gnueabihf/libgmpxx.so.4.5.2": No space left on device (28)
rsync: rename "/mnt/clone/usr/lib/arm-linux-gnueabihf/.libgnutls.a.ovXb6N" -> "usr/lib/arm-linux-gnueabihf/libgnutls.a": No space left on device (28)
rsync: mkstemp "/mnt/clone/usr/lib/arm-linux-gnueabihf/.libgomp.so.1.0.0.e5MmLj" failed: No space left on device (28)
rsync: mkstemp "/mnt/clone/usr/lib/arm-linux-gnueabihf/.libical.a.0XNf0d" failed: No space left on device (28)
rsync: mkstemp "/mnt/clone/usr/lib/arm-linux-gnueabihf/.libicalss_cxx.so.2.0.0.jXJmDP" failed: No space left on device (28)
rsync: write failed on "/mnt/clone/usr/lib/arm-linux-gnueabihf/libicudata.a": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]

  Mounting /dev/mmcblk0p1 on /mnt/clone/boot
  => rsync /boot/ /mnt/clone/boot  ...

Editing /mnt/clone/boot/cmdline.txt PARTUUID to use 2c3bbc09
Editing /mnt/clone/etc/fstab PARTUUID to use 2c3bbc09
===============================
Done with clone to /dev/mmcblk0
   Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing. 

Hit Enter when ready to unmount the /dev/mmcblk0 partitions ...
  unmounting /mnt/clone/boot
  unmounting /mnt/clone
===============================

[TheOldPresbyope]

@kitamura_design

I don't know anything about rpi-clone and don't wish to, so this is just a comment based on what I see in your output.

Assuming you are running moOde from a uSD card (/dev/mmcblk0), it looks like you tried to clone it to itself.

Code:

....
Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/mmcblk0p2 on /mnt/clone

...

Done with clone to /dev/mmcblk0
  Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

No wonder it ran out of room and starting throwing I/O errors 

Regards,
Kent

[kitamura_design]

@kitamura_design

I don't know anything about rpi-clone and don't wish to, so this is just a comment based on what I see in your output.

Assuming you are running moOde from a uSD card (/dev/mmcblk0), it looks like you tried to clone it to itself.

Code:

....
Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/mmcblk0p2 on /mnt/clone

...

Done with clone to /dev/mmcblk0
  Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

No wonder it ran out of room and starting throwing I/O errors 

Regards,
Kent

Hi Kent,

I am running moOde using with USB boot, and I want to backup to internal uSD card.

Code:

pi@moode:~ $ lsblk
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 /

I am very clear what I am doing

I should unsquash before running rpi-clone?

Thanks,
kitamura_design

[TheOldPresbyope]

@kitamura_design

I don't know anything about rpi-clone and don't wish to, so this is just a comment based on what I see in your output.

Assuming you are running moOde from a uSD card (/dev/mmcblk0), it looks like you tried to clone it to itself.

Code:

....
Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/mmcblk0p2 on /mnt/clone

...

Done with clone to /dev/mmcblk0
  Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

No wonder it ran out of room and starting throwing I/O errors 

Regards,
Kent

Hi Kent,

I am running moOde using with USB boot, and I want to backup to internal uSD card.

Code:

pi@moode:~ $ lsblk
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 /

I am very clear what I am doing

I should unsquash before running rpi-clone?

Thanks,
kitamura_design

Well, you still ran out of room. I have nothing more to offer. Questions about rpi-clone are best answered by the rpi-clone author.

Regards,
Kent

[kitamura_design]

@kitamura_design

I don't know anything about rpi-clone and don't wish to, so this is just a comment based on what I see in your output.

Assuming you are running moOde from a uSD card (/dev/mmcblk0), it looks like you tried to clone it to itself.

Code:

....
Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/mmcblk0p2 on /mnt/clone

...

Done with clone to /dev/mmcblk0
  Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

No wonder it ran out of room and starting throwing I/O errors 

Regards,
Kent

Hi Kent,

I am running moOde using with USB boot, and I want to backup to internal uSD card.

Code:

pi@moode:~ $ lsblk
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 /

I am very clear what I am doing

I should unsquash before running rpi-clone?

Thanks,
kitamura_design

Well, you still ran out of room. I have nothing more to offer. Questions about rpi-clone are best answered by the rpi-clone author.

Regards,
Kent

OK, Mr. moderator, I stop this topic, but I want you to know I just wanted to share everyone the how-to backup moOde smartly.


kitamura

[Tim Curtis]

@kitamura_design

I don't know anything about rpi-clone and don't wish to, so this is just a comment based on what I see in your output.

Assuming you are running moOde from a uSD card (/dev/mmcblk0), it looks like you tried to clone it to itself.

Code:

....
Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/mmcblk0p2 on /mnt/clone

...

Done with clone to /dev/mmcblk0
  Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

No wonder it ran out of room and starting throwing I/O errors 

Regards,
Kent

Hi Kent,

I am running moOde using with USB boot, and I want to backup to internal uSD card.

Code:

pi@moode:~ $ lsblk
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 /

I am very clear what I am doing

I should unsquash before running rpi-clone?

Thanks,
kitamura_design

 
I don't think the squashed file system would matter because it's just a big file, but I don't know how rpi-clone works so can't say for sure.

Is the target uSD card >= in size to the USB stick?

-Tim

[TheOldPresbyope]

@kitamura_design

I don't know anything about rpi-clone and don't wish to, so this is just a comment based on what I see in your output.

Assuming you are running moOde from a uSD card (/dev/mmcblk0), it looks like you tried to clone it to itself.

Code:

....
Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/mmcblk0p2 on /mnt/clone

...

Done with clone to /dev/mmcblk0
  Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

No wonder it ran out of room and starting throwing I/O errors 

Regards,
Kent

Hi Kent,

I am running moOde using with USB boot, and I want to backup to internal uSD card.

Code:

pi@moode:~ $ lsblk
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 /

I am very clear what I am doing

I should unsquash before running rpi-clone?

Thanks,
kitamura_design

Well, you still ran out of room. I have nothing more to offer. Questions about rpi-clone are best answered by the rpi-clone author.

Regards,
Kent

OK, Mr. moderator, I stop this topic, but I want you to know I just wanted to share everyone the how-to backup moOde smartly.


kitamura

I'm sorry if I didn't state my point well or sounded brusque. 

You are having a problem with a software app which is not part of moOde. 

I've now gone out and installed it on one of my moOde players and followed the instructions on the rpi-clone site. It quietly backed up my uSD card to a second uSD card on a USB carrier. As advertised, the second card boots into moOde. There's nothing inherent in moOde which causes rpi-clone to fail. 

Therefore, I think it's reasonable to suggest you contact the rpi-clone developer about your problem.

Regards,
Kent

[Tim Curtis]

Hi Kent,

It does live imaging or some sort of equavalent process?

I'll have to check it out :-)

[kitamura_design]

@kitamura_design

I don't know anything about rpi-clone and don't wish to, so this is just a comment based on what I see in your output.

Assuming you are running moOde from a uSD card (/dev/mmcblk0), it looks like you tried to clone it to itself.

Code:

....
Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/mmcblk0p2 on /mnt/clone

...

Done with clone to /dev/mmcblk0
  Start - 11:38:47    End - 11:48:24    Elapsed Time - 9:37

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

No wonder it ran out of room and starting throwing I/O errors 

Regards,
Kent

Hi Kent,

I am running moOde using with USB boot, and I want to backup to internal uSD card.

Code:

pi@moode:~ $ lsblk
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 /

I am very clear what I am doing

I should unsquash before running rpi-clone?

Thanks,
kitamura_design

Well, you still ran out of room. I have nothing more to offer. Questions about rpi-clone are best answered by the rpi-clone author.

Regards,
Kent

OK, Mr. moderator, I stop this topic, but I want you to know I just wanted to share everyone the how-to backup moOde smartly.


kitamura

I'm sorry if I didn't state my point well or sounded brusque. 

You are having a problem with a software app which is not part of moOde. 

I've now gone out and installed it on one of my moOde players and followed the instructions on the rpi-clone site. It quietly backed up my uSD card to a second uSD card on a USB carrier. As advertised, the second card boots into moOde. There's nothing inherent in moOde which causes rpi-clone to fail. 

Therefore, I think it's reasonable to suggest you contact the rpi-clone developer about your problem.

Regards,
Kent

That's good news, really thank you for your work.
This is 'sharing' what I am saying.

kitamura

[JST1963]

Now, let's all get a beer together…. my threat...