Persistent Partitions#
This topic applies only to Linux platforms.
NVIDIA Drive® OS provides persistence across bootburn flashing for user data and metadata partitions. The persistence works by reserving a partition in bootburn that is not written or modified in the flashing process. Due to this effect, the data in this partition is completely unchanged across bootburn flashing. After the filesystem is loaded, the user data partition is mounted on /home, and the persistent metadata is overlayed on /etc.
- Persistent Data Across Flashing
- Why You Require Persistent Data Across Flashing
- Workflow with Persistent Partition
- Methods to Reset Persistent Partition
- Data Migration for Persistent Partitions
- Persistent Partitions FAQ
- How are the persistent partitions defined, and can they be modified?
- How are the persistent partitions picked up at boot time? I don’t see fstab entries or systemd mount units for them.
- Is the root filesystem (RFS) image modified during flashing to enable these partitions?
- How can I reflash an existing ODK so that the persistent partitions are wiped and no longer mounted at boot?
- Can persistent partitions be modified?