# Nano boot error after OS update

**URL:** <https://forums.developer.nvidia.com/t/nano-boot-error-after-os-update/277221>\
**Category:** Jetson Nano\
**Tags:** boot\
**Created:** [December 26, 2023, 4:10pm UTC](https://forums.developer.nvidia.com/t/nano-boot-error-after-os-update/277221 "2023-12-26T16:10:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![oleksiy.tikh](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@oleksiy.tikh](https://forums.developer.nvidia.com/u/oleksiy.tikh)\
**Post date:** [December 26, 2023, 4:10pm UTC](https://forums.developer.nvidia.com/t/nano-boot-error-after-os-update/277221/1 "2023-12-26T16:10:10Z")

</div>

Hi here. Hope you are well!

After i performed  
sudo apt update  
sudo apt apgrade

My nano can’t boot. I see the Following errors in the console (see attachments). Did anybody have the same issue? How to fix?

 ![IMG_20231226_165733_edit_3235789925584898](https://global.discourse-cdn.com/nvidia/original/4X/b/a/7/ba7d6db9d1870189b7c6eb61ad5ad94fe83bdb14.jpeg)  
 ![IMG_20231226_165742_edit_3235781349827607](https://global.discourse-cdn.com/nvidia/original/4X/3/9/c/39c4f6b499f1758f45071fdb6d13685075db428d.jpeg)  
 ![IMG_20231226_165845_edit_3235768650295318](https://global.discourse-cdn.com/nvidia/original/4X/8/a/3/8a325c450b26c40343e89cb36567cae011e554c5.jpeg)

---

<div class="post-metadata">

**Author:** ![DaneLLL](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/danelll/32/14043_2.png) [@DaneLLL](https://forums.developer.nvidia.com/u/DaneLLL)\
**Post date:** [December 27, 2023, 4:21am UTC](https://forums.developer.nvidia.com/t/nano-boot-error-after-os-update/277221/2 "2023-12-27T04:21:09Z")

</div>

Hi,  
We don’t experience this issue. Would see if other users can share experience.

It would be great to re-flash the system to get a clean environment. Would suggest re-flash to Jetpack 4.6.4 through SDKManager.

---

<div class="post-metadata">

**Author:** ![\_Diablo](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@\_Diablo](https://forums.developer.nvidia.com/u/_Diablo)\
**Post date:** [December 28, 2023, 2:24pm UTC](https://forums.developer.nvidia.com/t/nano-boot-error-after-os-update/277221/3 "2023-12-28T14:24:24Z")

</div>

The error proc-sys-fs-binfmt\_mis.mount it’s sudo apt install binfmt-support are present in you system?  
What error returned Sudo systemcl status nvpmodel.service?

---

<div class="post-metadata">

**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\
**Post date:** [December 28, 2023, 8:36pm UTC](https://forums.developer.nvidia.com/t/nano-boot-error-after-os-update/277221/4 "2023-12-28T20:36:19Z")

</div>

I don’t know enough to solve this (I’m doing a lot of guessing here), but if you are using an emulator (such as QEMU), then sometimes the order of installing the qemu-user-static package can change things. I have no idea if this is the problem or not.

Also, note that `nvpmodel.service` is part of the standard NVIDIA installation related to power control. That means it accesses “`/proc`” content for either examining or changing driver settings (each file there is really a driver pretending to be a file, and not a real file on disk). Not having the NVIDIA kernel would result in not having the ability for `nvpmodel.service` to function. This might also be related to device tree since some wiring has multiple possible function, and differs across different carrier boards (e.g., it might work on a dev kit, but fail on a third party carrier board until the correct device tree is used).

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [January 11, 2024, 8:36pm UTC](https://forums.developer.nvidia.com/t/nano-boot-error-after-os-update/277221/5 "2024-01-11T20:36:22Z")

</div>

Closed on January 11, 2024, 8:36pm UTC

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