Hi, My OVMS v3 prototype appears to have lost it's configuration. It stopped talking to the server a few days ago and power cycling wasn't helping. I had a chance to see what was on the serial console today. The OVMS prompt and command interface is working normally, but there doesn't appear to be anything configured. I'm still using a startup script I wrote before we had the configuration gui, and that doesn't appear to execute at startup. If I do a vfs ls /store then the command line interface hangs and I have to power cycle it to get it back. I don't have the wifi turned on so I don't know if the web interface works after doing this. This behaviour is repeatable, I if I power cycle the module the config is still missing and vfs ls /store still hangs. What is the best way to debug it? Michael appears to have had a similar problem in https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/151 how do I dump the flash to investigate why listing the directory hangs the command line interface?
Tom, I've copied Marks info on retrieving the flash image from this mailing list to the developer manual: https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi... You can also do an fsck run on the image and write back the (hopefully salvaged) image. Regards, Michael Am 12.08.2018 um 00:19 schrieb Tom Parker:
Hi,
My OVMS v3 prototype appears to have lost it's configuration. It stopped talking to the server a few days ago and power cycling wasn't helping. I had a chance to see what was on the serial console today. The OVMS prompt and command interface is working normally, but there doesn't appear to be anything configured. I'm still using a startup script I wrote before we had the configuration gui, and that doesn't appear to execute at startup. If I do a vfs ls /store then the command line interface hangs and I have to power cycle it to get it back. I don't have the wifi turned on so I don't know if the web interface works after doing this.
This behaviour is repeatable, I if I power cycle the module the config is still missing and vfs ls /store still hangs.
What is the best way to debug it? Michael appears to have had a similar problem in https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/151 how do I dump the flash to investigate why listing the directory hangs the command line interface?
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
On 13/08/18 08:52, Michael Balzer wrote:
I've copied Marks info on retrieving the flash image from this mailing list to the developer manual:
https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi...
You can also do an fsck run on the image and write back the (hopefully salvaged) image.
Thanks for fishing that out for me. I found that my flash is badly corrupted. Linux doesn't log an error mounting it, but there is one empty file with a malformed name in the ovms_config directory. fsck.vfat complains about some stuff and renames that file but does not recover the data. Using strings I see that one copy of the configuration is still present so the image is not totally erased but the filesystem has been corrupted. I have a backup (a bunch of commands in a txt file to paste into the console) so I did the full erase and set things up again. It has been operating normally for the 24 hours or so since.
On Fri, 17 Aug 2018, Tom Parker wrote:
I have a backup (a bunch of commands in a txt file to paste into the console) so I did the full erase and set things up again. It has been operating normally for the 24 hours or so since.
You can also create a backup by copying the entire filesystem to another computer using scp if you build the software with CONFIG_OVMS_DEV_CONFIGVFS enabled. -- Steve
participants (3)
-
Michael Balzer -
Stephen Casner -
Tom Parker