[Ovmsdev] Config store mount failure / reformatting

[Mark Webb-Johnson]

I just updated my test box, and the same thing happened. It had been rock-solid for months.

I (562) ovms_main: Mounting CONFIG...
Initialising OVMS CONFIG within STORE
E (822) config: Error: Cannot open config store directory

Downgraded to 3.1.009, but still can’t mount store.

I’m pretty sure there is something in the new IDF that is corrupting FAT filesystems on flash.

We need to roll-back. I’ve disabled nightly builds until we can resolve this.

> I wonder if there could be a better strategy than immediately formatting the config filesystem on a mount error. Is there any chance the mount fails due to some race condition, i.e. would it make sense to first retry mounting after a short delay?

I’m not seeing a reformat of the flash, just a failure to mount. The reformat option is part of the fat mount option. We can certainly turn it off, or delay/retry it, but it is required for initial boot of a new device.

Regards, Mark.

> On 19 Aug 2018, at 7:23 PM, Michael Balzer <dexter at expeedo.de> wrote:
> 
> I've pulled the latest esp-idf updates, merges, builds and runs without issues. Btw, the idf now includes a CAN driver, may be worth a look.
> 
> On the second app-flashing, this happened:
> …
> Wrote 2399584 bytes (1382879 compressed) at 0x00010000 in 26.1 seconds (effective 736.0 kbit/s)...
> Hash of data verified.
> 
> Leaving...
> Hard resetting via RTS pin...
> …
> I (452) ovms_main: Mounting CONFIG...
> W (722) vfs_fat_spiflash: f_mount failed (13)
> I (722) vfs_fat_spiflash: Formatting FATFS partition, allocation unit size=4096
> I (1152) vfs_fat_spiflash: Mounting again
> Initialising OVMS CONFIG within STORE
> :-(
> 
> The first flash was perfectly OK and I haven't been able to reproduce this afterwards.
> 
> I don't think this is related to idf changes, as we had some reports on lost configs before. Issue #145 also seems to be solved by the new idf, I had no more crashes during reboots.
> 
> I wonder if there could be a better strategy than immediately formatting the config filesystem on a mount error. Is there any chance the mount fails due to some race condition, i.e. would it make sense to first retry mounting after a short delay?
> 
> Regards,
> Michael
> 
> -- 
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180822/62f46bc9/attachment.html>