September-20th-2018, 06:00 PM
Dear Paul,
have you maybe disconnected netPI from power unintended or have you had a power outage or power loss without shutting down netPI via the Web GUI?
What I can definitively say is that Linux caches write accesses to the file system. Imagine you were updating Node-RED by deploying a new flow. This file is definitively cashed ... for some seconds. If then you have a power drop this file could get lost.
Whenever netPI's Linux starts is checks the file system. Broken files will be copied into an internal "lost + found" folder (you can't access to this folder), but they are no more at their original place. This could be a reason why there is no file any more.
Right now I have no explanation why you can't create a file in the container any more.
But how do you get this things working again now? Repowering netPI? Loading the container again?
Thx
Armin
have you maybe disconnected netPI from power unintended or have you had a power outage or power loss without shutting down netPI via the Web GUI?
What I can definitively say is that Linux caches write accesses to the file system. Imagine you were updating Node-RED by deploying a new flow. This file is definitively cashed ... for some seconds. If then you have a power drop this file could get lost.
Whenever netPI's Linux starts is checks the file system. Broken files will be copied into an internal "lost + found" folder (you can't access to this folder), but they are no more at their original place. This could be a reason why there is no file any more.
Right now I have no explanation why you can't create a file in the container any more.
But how do you get this things working again now? Repowering netPI? Loading the container again?
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)