I have a Cerbo GX device that is unresponsive, other than the LAN leds are on. and the Wifi light flashes orange 3 times about every 5 seconds?
Trying to re-load the Venus OS.
This question was
closed
by
Mike Dorsett for the following reason: The question is answered, right answer was accepted
asked
Cerbo GX Troubleshooting - Venus OS re-install
Have you tried connecting to the internal AP of the GX?
Removing power for 30 seconds or so for a full reset also sometimes helps.
When all else fails, the reset to factory is documented in the manual.
Cerbo access point is not up, is not found with Ethernet connection by victron connect using direct ethernet connection, likewise does not respond to venus.local over same connection, does not claim a dhcp address when connected to the local network.
Looks like a brick. What's the warranty period on these devices?
It appears to be stuck in a boot loop, and not loading new software from SD card....
Connecting to the device serial console, as per https://www.victronenergy.com/live/ccgx:root_access
confirms device is stuck in a boot loop, but can read the SD card.
relevant part of boot log reads:
[ 3.416831] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[ 3.425263] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.10.33-venus-1 #1
[ 3.431953] Hardware name: Allwinner sun7i (A20) Family
[ 3.437201] [<c010d200>] (unwind_backtrace) from [<c010a3b0>] (show_stack+0x10/0x14)
[ 3.444942] [<c010a3b0>] (show_stack) from [<c0656500>] (dump_stack+0x98/0xac)
[ 3.452161] [<c0656500>] (dump_stack) from [<c06541e8>] (panic+0x114/0x30c)
[ 3.459122] [<c06541e8>] (panic) from [<c0901464>] (mount_block_root+0x2c0/0x340)
[ 3.466603] [<c0901464>] (mount_block_root) from [<c09016b0>] (prepare_namespace+0x154/0x190)
[ 3.475123] [<c09016b0>] (prepare_namespace) from [<c0658b00>] (kernel_init+0x8/0x118)
[ 3.483036] [<c0658b00>] (kernel_init) from [<c0100148>] (ret_from_fork+0x14/0x2c)
[ 3.490595] Exception stack(0xc0c4ffb0 to 0xc0c4fff8)
[ 3.495643] ffa0: 00000000 00000000 00000000 00000000
[ 3.503814] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 3.511981] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 3.518601] CPU0: stopping
[ 3.521313] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.33-venus-1 #1
[ 3.528005] Hardware name: Allwinner sun7i (A20) Family
[ 3.533232] [<c010d200>] (unwind_backtrace) from [<c010a3b0>] (show_stack+0x10/0x14)
[ 3.540969] [<c010a3b0>] (show_stack) from [<c0656500>] (dump_stack+0x98/0xac)
[ 3.548187] [<c0656500>] (dump_stack) from [<c010ba54>] (do_handle_IPI+0xf8/0x12c)
[ 3.555752] [<c010ba54>] (do_handle_IPI) from [<c010baa0>] (ipi_handler+0x18/0x20)
[ 3.563320] [<c010baa0>] (ipi_handler) from [<c016c7e8>] (generic_handle_irq+0x34/0x44)
[ 3.571321] [<c016c7e8>] (generic_handle_irq) from [<c016cdec>] (__handle_domain_irq+0x5c/0xb0)
[ 3.580015] [<c016cdec>] (__handle_domain_irq) from [<c03f17f8>] (gic_handle_irq+0x70/0x84)
[ 3.588362] [<c03f17f8>] (gic_handle_irq) from [<c0100b0c>] (__irq_svc+0x6c/0x90)
[ 3.595834] Exception stack(0xc0a01f10 to 0xc0a01f58)
[ 3.600882] 1f00: 00000000 00005cc4 ef79c804 c0118300
[ 3.609053] 1f20: c0a00000 00000000 c0a04f14 c0a04f50 00000000 c094c3e8 00000000 c0a01f70
[ 3.617221] 1f40: c0a03d40 c0a01f60 c01075f8 c01075fc 60000013 ffffffff
[ 3.623835] [<c0100b0c>] (__irq_svc) from [<c01075fc>] (arch_cpu_idle+0x38/0x3c)
[ 3.631228] [<c01075fc>] (arch_cpu_idle) from [<c065f428>] (default_idle_call+0x24/0x34)
[ 3.639316] [<c065f428>] (default_idle_call) from [<c014f088>] (do_idle+0x224/0x250)
[ 3.647058] [<c014f088>] (do_idle) from [<c014f380>] (cpu_startup_entry+0x18/0x1c)
[ 3.654624] [<c014f380>] (cpu_startup_entry) from [<c0900de4>] (start_kernel+0x488/0x4bc)
[ 3.662796] [<c0900de4>] (start_kernel) from [<00000000>] (0x0)
So it looks like the bootstrap code that can read the sd card isn't run. Guess this is probably cos the file system can't mount. Not sure where to go from here.
tried with a .swu file set:
This gives a very different debug output ending with:
[ 3.323236] input: button as /devices/platfo: recovery required on readonly filesystem
[ 3.343698] EXT4-4
[ 3.368596] Please append a correct "root=" boot option; h
[ 3.383835] b301 15556608 mmcblk0p1 518c3ee3-01
[ (179,10)
[ 3.439105] CPU: 0 PID: 1 Comm: swapper/0 Not taintamespace+0x154/0x190)
[ 3.488967] [<c09016b0>] (prepare_name0000000 00000013 00000000
[ 3.532441] CPU1: stopping
[ 3) from [<c010baa0>] (ipi_handler+0x18/0x20)
[ 3.577154] [<c0f50 00000000 c094c3e8 00000000 c0c91fb0
[ 3.631056] 1f80: c0arch_cpu_idle+0x38/0x3c)
[ 3.645061] [<c01075fc>] (arch_cpu_>] (cpu_startup_entry) from [<4010152c>] (0x4010152c)
with a couple of notable warnings (in bold).
How to recover the readonly file system?
To recover a seamingly bricked Cerbo GX or Cerbo GX MK2, follow the procedure explained here:
https://www.victronenergy.com/media/pg/Cerbo_GX/en/reset-to-factory-defaults-and-venus-os-reinstall.html#UUID-f26ec831-f79b-d493-00cb-d37ed8d74a74
(einstein and then .img.zip file)
Is there anything specific that happened or was done before your GX ended up in the state? It would be good for me to know; this doesn’t happen very often.
Thamks @mvader (Victron Energy) , I'll try this again in the morning.
Sorry I don't know what my client has done to this, it was bought directly by them, and has been in a very remote location for a while. Not sure that this ever got on line. It has no record in vrm.
I just installed etcher on the laptop, it causes file conflicts on this pc.
Downloaded several einstein .img.zip
Balena always gives error opening file:Error (0,h.requestMetadata is not a function
The unix disk image writer does write the image to am SD card, but the card is not readable after.
is there a known working solution? i.e. version of source file, disk flasher?
Hi, that is weird, I have used Balena many times; never had an issue.
Have you tried unzipping the file and then opening the .img file with balena?
The other tool that exists is raspberrypi imager.
Sorry for all this trouble!
It's also strange that the Debian disk image writer also finds the same trouble- however, I've used the disk image writer with no trouble on numerous Beaglebone images including a couple of venus images.
After unziping the file - ok - Balena still has the same issue.
However, unzip with Debian archive manager, then it will open ok with either disk image mounter or writer - successfully!! Thanks for the support.
@mvader (Victron Energy) now recovered successfully, thank you.
