Reboot loop after depleted 12V battery Nissan Leaf

Hi all,

Installed my OVMS in March of this year in my Nissan Leaf (2014) and have been using it ever since and was very happy with it's performance.
A few weeks ago I was on vacation for a long time and after about 2-3 weeks the 12V battery of my Leaf was depleted, I didn't know OVMS would drain the battery as this has never been an issue with the original TCU.
Anyway the battery was 10 years old which is ancient on a Leaf, so not bothered getting a new battery. Installed the new bttery and the car came back to life.
But eversince my OVMS has stopped working. today I had some time to get the module out of the car and was able to hook it up to my computer and get PuTTY connected, I was glad to see there was still life in the unit.
Seems like the unit keeps on rebooting every few seconds and this seems to be the problem:

assertion "0 && "fatfs internal error"" failed: file "/home/balzer/esp/esp-idf/components/fatfs/src/vfs_fat.c", line 253, function: fresult_to_errno
abort() was called at PC 0x401364f4 on core 1

Looks like a fs corruption.
What would be the correct procedure to get this fixed?
Is there any way I can save the current config/scripts from the device before performing anything?
I do have some scripts on the device but I don't think I have everything backed up on my servers.
Usually I am very anal about this but somehow I didn't save all the files and config locally.

Any help is appreciated.

Below the PuTTY output that repeats itself every few seconds:

ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4796
load:0x40078000,len:0
load:0x40078000,len:14896
entry 0x40078d74
I (1136) psram: This chip is ESP32-D0WD
I (1136) spiram: Found 64MBit SPI RAM device
I (1137) spiram: SPI RAM mode: flash 40m sram 40m
I (1140) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
I (1147) cpu_start: Pro cpu up.
I (1151) cpu_start: Application information:
I (1156) cpu_start: Project name:     ovms3
I (1161) cpu_start: App version:      3.3.004-4-gab8f16b7
I (1167) cpu_start: Compile time:     Mar 30 2024 08:08:20
I (1173) cpu_start: ELF file SHA256:  e535c0258e142c2b...
I (1179) cpu_start: ESP-IDF:          v3.3.4-849-g6e214dc335
I (1185) cpu_start: Starting app cpu, entry point is 0x400818d8
I (1178) cpu_start: App cpu up.
I (2063) spiram: SPI SRAM memory test OK
I (2064) heap_init: Initializing. RAM available for dynamic allocation:
I (2064) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (2070) heap_init: At 3FFC1ED8 len 0001E128 (120 KiB): DRAM
I (2076) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (2083) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (2089) heap_init: At 4009CCC8 len 00003338 (12 KiB): IRAM
I (2096) cpu_start: Pro cpu start user code
I (2101) spiram: Adding pool of 4096K of external SPI memory to heap allocator
I (151) ovms_main: Set default logging level for * to INFO
I (151) ovms_main: WATCHDOG already initialized...
I (152) ovms-duktape: Initialising DUKTAPE Registry (1000)
I (158) command: Initialising COMMAND (1010)
I (164) command: Expanding DUKTAPE javascript engine
I (169) boot: Initialising BOOT (1100)
I (173) boot: Boot #1258 reasons for CPU0=12 and CPU1=12
E (179) boot: Early crash #1258 detected
I (184) boot: Reset reason Exception/panic (4)
I (189) events: Initialising EVENTS (1200)
I (194) config: Initialising CONFIG (1400)
I (199) time: Initialising TIME (1500)
I (204) script: Initialising SCRIPTS (1600)
I (208) ovms-duk-http: Installing DUKTAPE HTTP (1710)
I (214) ovms-duk-util: Installing DUKTAPE Utilities (1710)
I (220) ovms-duk-vfs: Installing DUKTAPE VFS (1710)
I (225) metrics: Initialising METRICS (1810)
I (230) metrics: Expanding DUKTAPE javascript engine
I (236) metrics: Persistent metrics serial 1259 using 820 bytes, 66/100 slots used
I (258) notify: Initialising NOTIFICATIONS (1820)
I (260) notify: Registered notification type info
I (260) notify: Registered notification type error
I (264) notify: Registered notification type alert
I (269) notify: Registered notification type data
I (275) notify: Registered notification type stream
I (280) notify: Expanding DUKTAPE javascript engine
I (286) location: Initialising LOCATIONS (1900)
I (293) location: Expanding DUKTAPE javascript engine
I (297) vehicle: Initialising VEHICLE Factory (2000)
I (305) tls: Initialising TLS (3000)
I (307) pcp: Initialising POWER (4000)
I (311) max7317: Initialising MAX7317 EGPIO (4200)
I (317) sdcard: Initialising SD CARD (4400)
I (322) ota: Initialising OTA (4400)
I (327) canformat: Initialising CAN Format Factory (4500)
I (332) canformat-cs11: Registering CAN Format: CS11 (4505)
I (338) canformat-crtd: Registering CAN Format: CRTD (4505)
I (344) canformat-gvret: Registering CAN Format: GVRET (4505)
I (350) canformat-lawicel: Registering CAN Format: LAWICEL (4505)
I (357) canformat-panda: Registering CAN Format: PANDA (4505)
I (364) canformat-pcap: Registering CAN Format: PCAP (4505)
I (370) canformat-raw: Registering CAN Format: RAW (4505)
I (376) can: Initialising CAN (4510)
I (384) dbc-app: Initialising DBC (4520)
I (387) canlog: Initialising CAN logging (4550)
I (390) canlog-monitor: Initialising CAN logging to MONITOR (4560)
I (397) canlog-tcpclient: Initialising CAN logging as TCP client (4560)
I (406) canlog-tcpserver: Initialising CAN logging as TCP server (4560)
I (413) canlog-udpclient: Initialising CAN logging as UDP client (4560)
I (420) canlog-udpserver: Initialising CAN logging as UDP server (4560)
I (428) canlog-vfs: Initialising CAN logging to VFS (4560)
I (433) canplay: Initialising CAN play framework (4570)
I (439) canplay-vfs: Initialising CAN playing from VFS (4580)
I (445) cellular: Initialising CELLULAR (4600)
I (451) cellular-modem-factory: Initialising CELLULAR MODEM Factory (4601)
I (457) cellular-modem-auto: Registering auto-detect modem driver (4650)
I (465) SIM5360: Registering SIM5360 modem driver (4650)
I (471) SIM7000: Registering SIM7000 modem driver (4650)
I (477) SIM7600: Registering SIM7600 modem driver (4650)
I (483) tpms: Initialising TPMS (4700)
I (488) test: Initialising TEST (5000)
I (492) module: Initialising MODULE (5100)
I (497) vfs: Initialising VFS (5200)
I (501) ovms-server: Initialising OVMS Server (6000)
I (506) ovms-server-v2: Initialising OVMS V2 Server (6100)
I (513) ovms-server-v3: Initialising OVMS V3 Server (6200)
I (519) obd2ecu: Initialising OBD2ECU (7000)
I (524) canopen: Initialising CANopen (7000)
I (531) pluginstore: Initialising PLUGINS (7100)
I (535) esp32wifi: Initialising ESP32WIFI (8000)
I (540) ovms-mdns: Initialising MDNS (8100)
I (544) webserver: Initialising WEBSERVER (8200)
I (552) ssh: Initialising SSH (8300)
I (554) powermgmt: Initialising POWERMGMT (8500)
I (560) re: Initialising RE Tools (8800)
I (565) pushover: Initialising Pushover client (8800)
I (570) netmanager: Initialising NETMANAGER (8999)
I (579) v-zeva: Registering Vehicle: ZEVA (9000)
I (580) v-vweup: Registering Vehicle: VW e-Up (9000)
I (585) v-voltampera: Registering Vehicle: Chevrolet Volt/Ampera (9000)
I (593) v-track: Registering Vehicle: TRACK (9000)
I (598) v-toyotarav4ev: Registering Vehicle: Toyota RAV4 EV (9000)
I (605) v-thinkcity: Registering Vehicle: THINK CITY (9000)
I (611) v-teslaroadster: Registering Vehicle: Tesla Roadster (9000)
I (618) v-teslamodels: Registering Vehicle: Tesla Model S (9000)
I (625) v-teslamodel3: Registering Vehicle: Tesla Model 3 (9000)
I (632) v-smarteq: Registering Vehicle: SMART EQ (9000)
I (637) v-smarted: Registering Vehicle: SMART ED (9000)
I (643) v-zoe-ph2-obd: Registering Vehicle: Renault Zoe Ph2 (OBD) (9000)
I (651) v-zoe: Registering Vehicle: Renault Zoe/Kangoo (9000)
I (657) v-twizy: Registering Vehicle: Renault Twizy (9000)
I (663) v-obdii: Registering Vehicle: OBDII (9000)
I (669) v-none: Registering Vehicle: NONE (9000)
I (674) v-nissanleaf: Registering Vehicle: Nissan Leaf (9000)
I (681) v-mitsubishi: Registering Vehicle: Mitsubishi iMiEV, Citroen C-Zero, Peugeot iOn (9000)
I (690) v-minise: Registering Vehicle: Mini Cooper SE (9000)
I (696) v-mgev: Registering Vehicle: MG5 (9000)
I (701) v-mgev: Registering Vehicle: MG ZS EV (UK/EU) (9000)
I (708) v-mgev: Registering Vehicle: MG ZS EV (AU/TH) (9000)
I (714) v-mgev: Registering Vehicle: MG ZS EV (2023-)
I (720) v-mbb250e: Registering Vehicle: MERCEDESB250E (9000)
I (726) v-maxe56: Registering Vehicle: Maxus eDeliver3 (9000)
I (733) v-maxed3: Registering Vehicle: Maxus eDeliver3 (9000)
I (739) v-kiasoulev: Registering Vehicle: Kia Soul EV (9000)
I (745) v-kianiroev: Registering Vehicle: Kia Niro / Hyundai Kona EV (9000)
I (753) v-jaguaripace: Registering Vehicle: Jaguar Ipace (9000)
I (760) v-hyundaivfl: Registering Vehicle: Hyundai Ioniq vFL (9000)
I (767) v-ioniq5: Registering Vehicle: Hyundai Ioniq 5 EV (9000)
I (773) v-fiat500e: Registering Vehicle: FIAT 500e (9000)
I (779) v-demo: Registering Vehicle: DEMO (9000)
I (785) v-dbc: Registering Vehicle: DBC based vehicle (9000)
I (791) v-chevroletc6corvette: Registering Vehicle: Chevrolet C6 Corvette (9000)
I (799) v-cadillacc2cts: Registering Vehicle: Cadillac 2nd gen CTS (9000)
I (806) v-atto3: Registering Vehicle: BYD Atto3 (9000)
I (812) v-boltev: Registering Vehicle: Bolt EV (9000)
I (818) v-bmwi3: Registering Vehicle: BMW i3 (9000)
I (824) version: Initialising Versioning (9900)
I (834) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (0) ovms-duktape: Duktape: Scripting task is running
I (900) ovms_main: Executing on CPU core 0
I (900) ovms_main: Mounting CONFIG...
I (980) ovms_main: Configure logging...
I (990) ovms_main: Registering default configs...
I (990) ovms_main: Starting HOUSEKEEPING...
I (990) housekeeping: Initialising HOUSEKEEPING Framework...
I (990) location: UpdateParkPosition: vehicle is parking @0.000000,0.000000 gpslock=0 satcount=0 hdop=0.0 sq=0 invalid=1
assertion "0 && "fatfs internal error"" failed: file "/home/balzer/esp/esp-idf/components/fatfs/src/vfs_fat.c", line 253, function: fresult_to_errno
abort() was called at PC 0x401364f4 on core 1

ELF file SHA256: e535c0258e142c2b

Backtrace: 0x4008dda6:0x3ffc8850 0x4008e041:0x3ffc8870 0x401364f4:0x3ffc8890 0x402dc70f:0x3ffc88c0 0x402dcfa9:0x3ffc88e0 0x402374a5:0x3ffc8900 0x4000bd9f:0x3ffc8920 0x4008b489:0x3ffc8940 0x40137111:0x3ffc8960 0x40136eb6:0x3ffc89d0 0x40170e51:0x3ffc89f0 0x40170f19:0x3ffc8a50 0x4017042e:0x3ffc8a70 0x4011f1da:0x3ffc8ab0 0x4011f3a9:0x3ffc8ae0 0x4011f490:0x3ffc8b40 0x4011f519:0x3ffc8b80

[OVMS] Current tasks: IDLE0|OVMS Events
Rebooting...