My 19007/4631 is constantly rebooting

My System has been running fine for a couple weeks now. All of sudden I noticed it started rebooting (green light would flash every 6 seconds).

I can put it into into DFU mode fine. I was able to drag and drop the Meshtastic_nRF52_factory_erase_v3_S140_7.3.0.uf2

Then after reboot I go into DFU mode again and drag and drop the
firmware-rak4631-2.5.11.8e2a3e5.uf2

after which it starts rebooting again.

Any assistance would be appreciated.

Logs I was able to capture:
/\ E S H T /\ S T / C

DEBUG | ??:??:?? 2 Filesystem files:
DEBUG | ??:??:?? 2 adafruit (directory)
DEBUG | ??:??:?? 2 bond_prph (directory)
DEBUG | ??:??:?? 2 bond_cntr (directory)
DEBUG | ??:??:?? 2 prefs (directory)
DEBUG | ??:??:?? 2 config.proto (173 Bytes)
DEBUG | ??:??:?? 2 channels.proto (61 Bytes)
DEBUG | ??:??:?? 2 module.proto (115 Bytes)
DEBUG | ??:??:?? 2 db.proto.tmp (26429 Bytes)
DEBUG | ??:??:?? 2 Power::lipoInit lipo sensor is not ready yet
DEBUG | ??:??:?? 2 Using analog input 5 for battery level
INFO | ??:??:?? 2 Scanning for i2c devices…
DEBUG | ??:??:?? 2 Scanning for I2C devices on port 1
INFO | ??:??:?? 2 No I2C devices found
DEBUG | ??:??:?? 2 acc_info = 0
INFO | ??:??:?? 2 S:B:9,2.5.5.e182ae7
INFO | ??:??:?? 2 Build timestamp: 1728125491
DEBUG | ??:??:?? 2 Reset reason: 0x0
DEBUG | ??:??:?? 2 Setting random seed 4140759461
INFO | ??:??:?? 2 Initializing NodeDB
ERROR | ??:??:?? 2 Could not open / read /prefs/db.proto
WARN | ??:??:?? 2 Devicestate 0 is old, discarding
INFO | ??:??:?? 2 Installing default DeviceState
DEBUG | ??:??:?? 2 Initial packet id 660453681
DEBUG | ??:??:?? 2 Partially randomized packet id 149643570
DEBUG | ??:??:?? 2 Using nodenum 0x5ee1db5d
INFO | ??:??:?? 2 Loading /prefs/config.proto
INFO | ??:??:?? 2 Loaded /prefs/config.proto successfully
INFO | ??:??:?? 2 Loaded saved config version 23
INFO | ??:??:?? 2 Loading /prefs/module.proto
INFO | ??:??:?? 2 Loaded /prefs/module.proto successfully
INFO | ??:??:?? 2 Loaded saved moduleConfig version 23
INFO | ??:??:?? 2 Loading /prefs/channels.proto
INFO | ??:??:?? 2 Loaded /prefs/channels.proto successfully
INFO | ??:??:?? 2 Loaded saved channelFile version 23
ERROR | ??:??:?? 2 Could not open / read /oem/oem.proto
DEBUG | ??:??:?? 2 cleanupMeshDB purged 0 entries
DEBUG | ??:??:?? 2 Using nodenum 0x5ee1db5d
INFO | ??:??:?? 2 Adding node to database with 1 nodes and 148084 bytes free!
DEBUG | ??:??:?? 2 Expanding short PSK #1
INFO | ??:??:?? 2 Wanted region 1, using US
INFO | ??:??:?? 2 Saving /prefs/db.proto
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count
ERROR | ??:??:?? 2 LFS assert: block < lfs->cfg->block_count

Ok I think I have it working. The original erase utility in the firmware zip Meshtastic_nRF52_factory_erase_v3_S140_7.3.0.uf2 never prompted me in the terminal to erase NVRAM (not sure if that’s the correct term for where the firmware is written).
I found this utility ‘nrf_erase2.uf2’ which when dropped in in DFU mode brings up a prompt in the serial terminal to perform an erase, after that everything seems to work ok, sort of. I think the the minor issues I see are with the Meshtastic firmware so no reason to mention them on this forum.

I would like to get some clarification on the differences between Meshtastic_nRF52_factory_erase_v3_S140_7.3.0.uf2 and ‘nrf_erase2.uf2’ . I am guessing ‘nrf_erase2.uf2’ is from RAK or the chip maker and Meshtastic_nRF52_factory_erase_v3_S140_7.3.0.uf2 is from Meshtastic. Is that correct?

Also none of this really explains why my device crashed and I had to erase and reinstall. I guess that’s the nature of software/firmware.

Reminds me of the old joke (30 years old really doesn’t apply any more): If Microsoft built cars you would have to pull over every 100 miles and reboot it.