# /mnt/legato Empty

**URL:** <https://forum.legato.io/t/mnt-legato-empty/5430>\
**Category:** Legato Application Framework\
**Created:** [September 30, 2020, 7:00pm UTC](https://forum.legato.io/t/mnt-legato-empty/5430 "2020-09-30T19:00:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbeckwith](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/dbeckwith/32/663_2.png) [@dbeckwith](https://forum.legato.io/u/dbeckwith)\
**Post date:** [September 30, 2020, 7:00pm UTC](https://forum.legato.io/t/mnt-legato-empty/5430/1 "2020-09-30T19:00:05Z")

</div>

We just received a unit back from the field that is exhibiting some very strange behavior.

The unit has an empty `/mnt/legato` directory, here is the [log.txt](https://forum.legato.io/uploads/short-url/hhbLuQaBVcgFEgYHOWq9iheajBc.txt) (1.9 MB) The expected version of Legato is in `/mnt/flash/legato`.

What is also very strange is the unit seems to report registration updates to AirVantage in this state but I can’t explain how.

Thoughts,

---

<div class="post-metadata">

**Author:** ![dbeckwith](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/dbeckwith/32/663_2.png) [@dbeckwith](https://forum.legato.io/u/dbeckwith)\
**Post date:** [October 5, 2020, 9:05pm UTC](https://forum.legato.io/t/mnt-legato-empty/5430/2 "2020-10-05T21:05:53Z")

</div>

Any thoughts? I have left the unit in this state incase there is knowledge that can be gained from it. This is the second unit with this issue.

---

<div class="post-metadata">

**Author:** ![mehdiALL1](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mehdiALL1](https://forum.legato.io/u/mehdiALL1)\
**Post date:** [October 20, 2020, 12:26pm UTC](https://forum.legato.io/t/mnt-legato-empty/5430/3 "2020-10-20T12:26:00Z")

</div>

Hello, is the Legato system able to start or not? because, every time you boot, the init scripts will run the start program in /mnt/legato. This program will check to make sure that /mnt/flash/legato (aka /legato) is set up properly before launching /legato/systems/current/bin/supervisor.

---

<div class="post-metadata">

**Author:** ![dbeckwith](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/dbeckwith/32/663_2.png) [@dbeckwith](https://forum.legato.io/u/dbeckwith)\
**Post date:** [October 20, 2020, 5:07pm UTC](https://forum.legato.io/t/mnt-legato-empty/5430/4 "2020-10-20T17:07:50Z")

</div>

No Legato is not able to start at all.

---

<div class="post-metadata">

**Author:** ![mehdiALL1](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mehdiALL1](https://forum.legato.io/u/mehdiALL1)\
**Post date:** [October 21, 2020, 7:42am UTC](https://forum.legato.io/t/mnt-legato-empty/5430/5 "2020-10-21T07:42:25Z")

</div>

Ok, it’s what I expected … in the logs, I can’t see what it is the cause … you need to fill /mnt/legato by flashing the module again.

---

<div class="post-metadata">

**Author:** ![dbeckwith](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/dbeckwith/32/663_2.png) [@dbeckwith](https://forum.legato.io/u/dbeckwith)\
**Post date:** [October 21, 2020, 10:59pm UTC](https://forum.legato.io/t/mnt-legato-empty/5430/6 "2020-10-21T22:59:42Z")

</div>

Any thoughts as to what may have caused this or how to prevent devices from ending up in this state in the feature?

---

<div class="post-metadata">

**Author:** ![mehdiALL1](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mehdiALL1](https://forum.legato.io/u/mehdiALL1)\
**Post date:** [October 27, 2020, 8:17am UTC](https://forum.legato.io/t/mnt-legato-empty/5430/7 "2020-10-27T08:17:35Z")

</div>

if the problem is easily reproducible … I can show you how to permanently store the logs in the module (max 100 MB) …