A little help for rpi-clone

Hello everybody,

I ask for a little help from the Debian specialists on Octoprint.

The SD card on which my Octoprint was installed being broken, I had to make a complete reinstall. So bad.

Not wanting to make the same mistake twice, I tried to operate an rpi-clone of the new SD but, surprise, I can't find my files.

From what I have saved of Linux knowledge, we can find the disks in dev folder with the label sdx, x representing the reference of the disk (a, b, c, ...).

But in my /dev folder, nothing like that. Here is a copy:

So, could someone tell me where these damn files are located?

In advance, thank you for your precious help.

Kind regards



For those who might be interested, here is the answer given to me on another forum.

The path to the device file that allows access to your SD card is:


mmcblk <=> multi media card block device

Two partitions have been recognized by the system on this SD card
they are accessible by the following paths:


Thanks for your help.

When you plugin a USB microSD card reader, it will appear to the RPi at /dev/sd* where * can be a, b, c, etc. When you execute the rpi-clone script, you specify this /dev/sd* device as the first parameter. It will copy the partitions on the /dev/mmcblk0 device onto partitions it creates on the /dev/sd* device (i.e. the microSD card plugged into the USB microSD card reader).

If the microSD card you are booting the RPi from gets corrupted, you replace it with the microSD card that was written with rpi-clone. Obviously, you will lose any files created between the time that you used rpi-clone and the time that the microSD card failed. While the rpi-clone process takes a while the first time, it uses rsync and subsequent clones are much quicker.

I usually clone my RPi system just before I make any major change like updating the OctoPrint version, hardware changes, and maybe once a month if nothing major has happened. It is also possible to mount the partitions on the cloned microSD card and then copy files from it.


Finally I managed to execute my rpi-clone on my 2 octoprint.
I thought of doing it only once to have a copy of the SD card in case of a crash, but your idea of โ€‹โ€‹doing it once a month or in the event of major changes is excellent especially since it is very easy to do it.
I will apply the same logic.
Thanks for the advice.

Have a good evening

In addition, if you don't change that much on the OS outside of OctoPrint, it has a built in backup and restore option, which will be much faster - and with a couple of plugins you can schedule to backup & upload to cloud/local services as well.

Automatic backups were already scheduled but the SD card having crashed, it did not allow me to restart the system quickly.
I had to do a full reinstall.
In this case, the best practice is a clone of the card.