How to backup & restore DRIVE AGX system

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version

Target Operating System

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)

SDK Manager Version

Host Machine Version
native Ubuntu 18.04


We are trying to create backup for our pegasus disk in order to restore it if any issues happen while changing the environment. Since there is no docker support for now, we decided to create a system image for the disk and restore it in case any issues happen.

We managed to successfully create an image from our OS disk (vblkdev0), using dd command as stated in this discussion

I saw many people suggesting to use ./ -r <boardid> <partitionid> , but I couldn’t fine a boardid for pegasus, and I’m not entirely sure that the flashing scripts supports pegasus at all.

Can you please guide us on how to backup/restore our system image on pegasus?


Drive AGX is not using the same method as Jetson AGX Xavier to flash board. There is no
Please do not refer to post on Jetson’s forum for DRIVE OS issue.

Is there a specific way to backup/restore DRIVE AGX boards?

Dear @n.fteiha,
Unfortunately we do not have steps( tested) for restore the image. May I know does it block your devolopment or critical requirement in project?

Hi @SivaRamaKrishnaNV ,

In our system we mainly rely on docker containers that we build that contain all dependencies needed to run it.
As we understood from previous discussions with nvidia representatives is that there is no docker with gpu support available on pegasus right now, we went to the alternative to install all the needed dependencies locally on pegasus and managed to build/run our project.

What’s concerning us right now is that the current state is very fragile where if any developer accessing the pegasus adds/remove mismatching dependencies a chain of dependencies might break, causing failures in build/runtime of our system.

As a result, I can say that it is very critical for our project, to be able to restore the system to a working state at any time anything goes wrong, as without that capability it will make our development lifecycle on pegasus very slow and a much harder process.