When I do "vfs ls /store" I get 128 lines like the following: -2146205 01-Jan-1970 00:00 ????????.??? After that comes valid content: [DIR] 01-Jan-1980 00:00 ovms_config/ 83 01-Jan-1980 00:00 .htpasswd The config facility appears to be intact. Does the garbage indicate that the /store filesystem is scrogged and needs to be rebuilt? -- Steve
Ouch. Yeah, something threw up on the file system. Do we have fsck included in the build? Greg Stephen Casner wrote:
When I do "vfs ls /store" I get 128 lines like the following:
-2146205 01-Jan-1970 00:00 ????????.???
After that comes valid content:
[DIR] 01-Jan-1980 00:00 ovms_config/ 83 01-Jan-1980 00:00 .htpasswd
The config facility appears to be intact. Does the garbage indicate that the /store filesystem is scrogged and needs to be rebuilt?
-- Steve _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
The filesystem is FAT32, isn't it? fsck would not apply. -- Steve On Thu, 20 Dec 2018, Greg D. wrote:
Ouch. Yeah, something threw up on the file system. Do we have fsck included in the build?
Greg
Stephen Casner wrote:
When I do "vfs ls /store" I get 128 lines like the following:
-2146205 01-Jan-1970 00:00 ????????.???
After that comes valid content:
[DIR] 01-Jan-1980 00:00 ovms_config/ 83 01-Jan-1980 00:00 .htpasswd
The config facility appears to be intact. Does the garbage indicate that the /store filesystem is scrogged and needs to be rebuilt?
-- Steve
I'm thinking of fsck.vfat, specifically. But since your data appears to still be there, probably time to back it up, re-format, and restore. Greg Stephen Casner wrote:
The filesystem is FAT32, isn't it? fsck would not apply.
-- Steve
On Thu, 20 Dec 2018, Greg D. wrote:
Ouch. Yeah, something threw up on the file system. Do we have fsck included in the build?
Greg
Stephen Casner wrote:
When I do "vfs ls /store" I get 128 lines like the following:
-2146205 01-Jan-1970 00:00 ????????.???
After that comes valid content:
[DIR] 01-Jan-1980 00:00 ovms_config/ 83 01-Jan-1980 00:00 .htpasswd
The config facility appears to be intact. Does the garbage indicate that the /store filesystem is scrogged and needs to be rebuilt?
-- Steve
OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
I know that I can use "config backup" to back up the config to SD. Does the re-format step mean "module factory reset"? -- Steve On Thu, 20 Dec 2018, Greg D. wrote:
I'm thinking of fsck.vfat, specifically. But since your data appears to still be there, probably time to back it up, re-format, and restore.
Greg
Yes. You might consider saving the flash partition for further bug analysis before erasing it: https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi... Regards, Michael Am 21.12.18 um 08:10 schrieb Stephen Casner:
I know that I can use "config backup" to back up the config to SD. Does the re-format step mean "module factory reset"?
-- Steve
On Thu, 20 Dec 2018, Greg D. wrote:
I'm thinking of fsck.vfat, specifically. But since your data appears to still be there, probably time to back it up, re-format, and restore.
Greg
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
Michael, I will save the flash partition as you suggest. Also, in your message telling about the addition of the config backup/restore function you said the backup covers the directories "ovms_config" and "events" from "/store". I note that /store also contains a .htpasswd file. Should that also be included, or is it already? -- Steve On Fri, 21 Dec 2018, Michael Balzer wrote:
Yes.
You might consider saving the flash partition for further bug analysis before erasing it: https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi...
Regards, Michael
The .htpasswd file is generated automatically by the webserver from the password config. Regards, Michael Am 21.12.18 um 17:53 schrieb Stephen Casner:
Michael,
I will save the flash partition as you suggest.
Also, in your message telling about the addition of the config backup/restore function you said the backup covers the directories "ovms_config" and "events" from "/store". I note that /store also contains a .htpasswd file. Should that also be included, or is it already?
-- Steve
On Fri, 21 Dec 2018, Michael Balzer wrote:
Yes.
You might consider saving the flash partition for further bug analysis before erasing it: https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi...
Regards, Michael
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
What kind of <path> is expected in "config backup <path>"? I tried "/sd/config-20181221.zip" and "config-20181221.zip" but both resulted in "Error: zip failed: No such file or directory". Manually creating the empty file "/sd/config-20181221.zip" first did not help. -- Steve
Steve, I missed the case of a non-existent "/store/events" directory. I'll fix that now, to backup without updating, do "vfs mkdir /store/events". Regards, Michael Am 22.12.18 um 02:13 schrieb Stephen Casner:
What kind of <path> is expected in "config backup <path>"? I tried "/sd/config-20181221.zip" and "config-20181221.zip" but both resulted in "Error: zip failed: No such file or directory". Manually creating the empty file "/sd/config-20181221.zip" first did not help.
-- Steve _______________________________________________ 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
Michael, Glad you figured that out. I had looked at the code to see if that gave me any hints as to what kind of <path> argument was required, but I could not tell from the code where the error was occurring. I notice that some other commands use <vfspath> for the help string to be more specific. Would that be a good idea for config backup? -- Steve On Sat, 22 Dec 2018, Michael Balzer wrote:
Steve,
I missed the case of a non-existent "/store/events" directory.
I'll fix that now, to backup without updating, do "vfs mkdir /store/events".
Regards, Michael
Am 22.12.18 um 02:13 schrieb Stephen Casner:
What kind of <path> is expected in "config backup <path>"? I tried "/sd/config-20181221.zip" and "config-20181221.zip" but both resulted in "Error: zip failed: No such file or directory". Manually creating the empty file "/sd/config-20181221.zip" first did not help.
-- Steve
On Fri, 21 Dec 2018, Michael Balzer wrote:
You might consider saving the flash partition for further bug analysis before erasing it https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi...
I finally got around to fixing the corrupted /store filesystem on my OVMS v3.0 module. I did save the partition first, as directed by the section of the OVMS v3 Developer Guide to which the reference above points. I also updated the instructions there to add an example of how to mount the saved filesystem on macOS rather than Linux. Looking at the whole filesystem as a raw binary file, I see that the sector at 0x00002000 is all 0xFFs. I don't know if that is what caused the "vfs ls /store" command to show 128 invalid directory entries, but after erasing the flash and rebuilding the /store filesystem and then saving the flash partition to another file on my Mac, there is not a sector of 0xFF like that. Running fsck_msdos on the broken filesystem (as attached on macOS) only shows orphaned clusters, not any invalid directory entries: auge16> fsck_msdos /dev/disk11 ** /dev/rdisk11 ** Phase 1 - Preparing FAT ** Phase 2 - Checking Directories ** Phase 3 - Checking for Orphan Clusters Found orphan cluster(s) Fix? [yn] n Found 25 orphaned clusters 19 files, 800 KiB free (200 clusters) ** Phase 1 - Preparing FAT ** Phase 2 - Checking Directories ** Phase 3 - Checking for Orphan Clusters Found orphan cluster(s) Fix? [yn] n Found 25 orphaned clusters 19 files, 1600 KiB free (400 clusters) ** Phase 1 - Preparing FAT ** Phase 2 - Checking Directories ** Phase 3 - Checking for Orphan Clusters Found orphan cluster(s) Fix? [yn] n Found 25 orphaned clusters 19 files, 2400 KiB free (600 clusters) auge17> -- Steve
participants (3)
-
Greg D. -
Michael Balzer -
Stephen Casner