Read-only file system for AGX Xavier on Jp4.6.2


I’m trying make a Read-only rootfs on Emmc by overlayroot

I can successfully make it on Xavier NX and Nano

But it failed on AGX Xavier

The step reference here:

Could you help to check why it didn’t work on AGX Xavier?

Hi zax,

Are you using the devkit or custom board for AGX Xavier?
What’s your Jetpack version in use?

It seems the 3-rd party tool and we didn’t verify it before.
What issue do you hit now? Could you share any logs?

Hi KevinFFF,

I tried both custom board and devkit, the result is the same

Jetpack4.6.2 is not work, but Jetpack4.6 is ok just test recently

If there’s any official way to make a read-only rootfs, please help to tell me

The github use ovrlayroot, and the script it actually do the same things as Protecting the Root Filesystem on Ubuntu with Overlayroot

I’ve just referred to the steps in your link and verified it could work for AGX Xavier devkit with JP4.6.4 (L4T R32.7.4).

Please verify with R32.7.4 and share the logs.

1 Like

Hi KevinFFF,

Thanks for help, JP4.6.4 works

But I need your confirm that AGX Xavier can’t work for read-only rootfs on JP4.6.2 to persuade our customer

Could you help to check again on JP4.6.2?

And if possible, please tell me why it is not working


Normally, we would only verify with the latest release. (for R32, it is R32.7.4).

Do you have any requirement for JP4.6.2?
There might be several fixes and update between them.

Is there any release note mention about these?

Could you try to modify the in /etc/fstab from defaults to ro and reboot the board to make rootfs read-only?

Sorry late for reply

After modified the in /etc/fstab from defaults to ro and reboot

The system showed many error message while booting, then stock

I can enter the system through uart debug port

And check the rootfs is ro, but it seems not a good solution
mount.log (2.5 KB)

Since overlayroot would mount your partition at /media/root-ro rather than changing the whole rootfs to read-only as you modified in /etc/fstab.

I would suggest just using the latest R32.7.4 for your use case.


Thanks for help

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.