February-1st-2020, 10:39 AM
Hello Manuel,
results from the development team are still pending. I looked into the log file myself and I see Docker not starting as well.
I see "unable to configure the Docker daemon with file /etc/docker/daemon.json: EOF" as first indication that something went wrong. Apparently this file is needed but it seems to be empty. The file format is officially explained here https://docs.docker.com/engine/reference...e/dockerd/ and configures the Docker Daemon.
I would expect nobody on the system is ever writing to this file, so I am wondering why it got empty. I guess my team is able to tell me more.
You asked me if an unintended power-off could be the reason. Well, usually in such cases only the file that was written the time of the power-off could get corrupted. But why the daemon.json if nobody is writing to it. And then "EOF" ... End of File, so the file is there, but empty. If a file got corrupt then it is not there and removed by Linux if recognized, but empty ... looks like a systematic problem.
I switched on and off my netPI since I operate it for 3 years nearly daily, I have never had such a problem. And I have not heard it from any customer yet.
The only chance I see right now for you is to recover it with a USB stick.
If you have a revision #2 device (small number "2" in the lower left corner of the bar code label) then the internal SD card can be remove and a binary image be taken with a windows tool for example. This image could be analyzed here. But I expect that we will not get really out what happened here.
Thx
Armin
results from the development team are still pending. I looked into the log file myself and I see Docker not starting as well.
I see "unable to configure the Docker daemon with file /etc/docker/daemon.json: EOF" as first indication that something went wrong. Apparently this file is needed but it seems to be empty. The file format is officially explained here https://docs.docker.com/engine/reference...e/dockerd/ and configures the Docker Daemon.
I would expect nobody on the system is ever writing to this file, so I am wondering why it got empty. I guess my team is able to tell me more.
You asked me if an unintended power-off could be the reason. Well, usually in such cases only the file that was written the time of the power-off could get corrupted. But why the daemon.json if nobody is writing to it. And then "EOF" ... End of File, so the file is there, but empty. If a file got corrupt then it is not there and removed by Linux if recognized, but empty ... looks like a systematic problem.
I switched on and off my netPI since I operate it for 3 years nearly daily, I have never had such a problem. And I have not heard it from any customer yet.
The only chance I see right now for you is to recover it with a USB stick.
If you have a revision #2 device (small number "2" in the lower left corner of the bar code label) then the internal SD card can be remove and a binary image be taken with a windows tool for example. This image could be analyzed here. But I expect that we will not get really out what happened here.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
