We changed our privacy policy. Read more.

Hot answers tagged

3

I specifically reactivated my never used account to answer this question, because I was having the same problems last week and felt like other people will too./rant About the actual problem, using the explanation about ssh from Can a Raspberry Pi be used to create a backup of itself? misses a crucial point - rsync does not properly preserve the ownerships (...


3

There is an inherent problem with your live backup approach: you need the entire file system to remain stable during the backup process, otherwise there is no way to guarantee that the backup will correctly work afterwards. One solution is to remount your filesystem read-only during the backup process (pretty much impossible for / on a running system, ...


2

I solved it and thank you goldilocks for your answer. Android Side I installed the app Rsync Wrapper on my Samsung and configured it with the following parameters: Source: /storage/WXYZC-ABCD/DCIM/Camera/ Destination: username@192.168.2.4:~/userS8/ Option: -r --ignore-existing --progress -e "ssh -l username -i /data/user/0/net.letscorp.rsyncwrapper/...


2

The problem is that Windows doesn't automatically host an SSH or Telnet server. You will have to set one up on the Windows machine.


2

Unless your HDDs are powered externally or you have a mod similar to this one, this is most likely due to insufficient power. USB disks consume less power when idle (just spinning), once you actively use them additional motors which move the heads are powered. Most USB HDDs have a rated current between 0.6 and 1 A, and 2 x 0.6 A is already at the limit of ...


2

The method of backing up is irrelevant; it applies to any (tar, rsync, scp, cpio etcetera) form of backup. If you backup a database, and the database changes while you are backing up, you may get a copy that is inconsistent. Serious databases can often be recovered, if you backup the redo-log files last. Shutting down the database ensures that the database ...


1

dd may take quite a while, especially if there's a problem with an sd-card. For these long actions, I generally add status=progress to the dd command line. cp ans dd do very different things. With dd you copy all the "sectors" of the partition, even those that are empty. With cp, you only copy the files. Unless your original and new image are ...


1

The error described in my question/issue above was caused by issues of kernel files located in the boot partition. Originally I only backed up the files on the "os" partition of the Raspberry. So if you update the kernel or parts of the kernel and restore the files on the "os" partition, the kernel files on the "os" partition are not compatible with the ...


1

The instructions you referenced make a copy (of the relevant parts) of the files on the root partition. To make a copy of an OS you ALSO need to copy the files on the boot partition AND the partition table (or be able to re-construct one with the right settings). Your earlier attempt failed because you only restored part of the image. In order to restore ...


1

Most likely a mismatch between /etc/fstab and /boot/cmdline.txt. Other possible errors are a mismatch between the kernel version and modules. The process was designed to BACKUP and RESTORE to the SAME SD CARD - not a new image. It was also written before the adoption of PARTUUID. If you overwrite the boot partition with the contents of that on the old ...


1

The professional OTA updaters include: Mender, rauc, swupdate These are power fail safe, as they do an "A/B" update. Two images: A and B, where A is the current running image stays flashed, until the new B image is confirmed to be flashed in the OTA partition. The following presentation gives a good overview of differences between pushing debugging images, ...


Only top voted, non community-wiki answers of a minimum length are eligible