So bossman, I realised it kept taking me in a loop for 3 hours, the best fix is I removed the snap, I removed the selinux, and then rebooted the systemctl.
press enter to enter maintainance
this is what I did, and claude helped.
" After following JetsonHacks Chromium fix [Why Chromium Suddenly Broke on Jetson Orin (and How to Bring It Back) - JetsonHacks]
(snapd downgrade), system won’t boot - stuck in emergency mode with:
- Snap mount failures
- SELinux errors preventing systemd services
- “No data available” errors
Root Cause
- Snapd downgrade corrupted snap system state
- SELinux incompatible with Jetson kernel, blocking critical services
Nuclear Solution (Boot from Emergency Mode)
1. Access emergency shell:
bash
# Press Enter at "Press Enter for maintenance"
2. Remove SELinux completely:
bash
apt remove --purge selinux-utils policycoreutils
rm -rf /etc/selinux
3. Remove Snapd completely:
bash
apt remove --purge snapd squashfs-tools
rm -rf /snap /var/snap /var/lib/snapd /var/cache/snapd
rm -f /etc/systemd/system/snap-*.mount
4. Clean systemd:
bash
systemctl daemon-reload
systemctl reboot
Result
- System boots normally
- No more snap apps (Chromium, Firefox snaps gone)
- Install browsers with apt instead:
bash
apt install firefox
# or
apt install chromium-browser
Why This Works
- Jetson kernels lack full SELinux support
- Snapd 2.70+ requires kernel features Jetson doesn’t have
- Regular apt packages work fine without these systems
Prevention
- Don’t downgrade snapd on Jetson
- Use apt packages instead of snaps when possible
- Avoid SELinux on Jetson (use AppArmor if needed)
This gives you a working Jetson without the problematic security layers that break embedded systems."
Hope this helps. I dont know how much this is right but @Kangalow @DaneLLL please suggest this temp fix?