Thanks everyone putty and Windows 11 fixed it with the correct usb driver

Screenshot 2023-11-29 143357.png

Got access to the boot environments now.

I can't get some packages to with with ARM for 23.09 I keep getting completely locked out and having to go back. That fixed it.

@stephenw10 Yes, You are right.

Only few items were left in the partition.

root@:~ # mount /dev/ada0p2 /mnt
root@:~ # ls
.k5login .profile .shrc recover_configxml.sh
root@:~ # cd /mnt
root@:/mnt # ls
.cshrc .profile .rnd .snap .sujournal dev lib libexec sbin usr var
root@:/mnt #

@stephenw10
@steveits
No, It didn't lose power during the update, it just didn't come back online after the update.

I am getting the firmware reinstalled as of this message. no other way of this error sadly other than a full wipe / fresh install

Yup, both those things are true.

The jumper is there in case you end up with a damaged uboot image on the eMMC, you can force it to ignore that and load from SD to recover. If the eMMC is complete blank it should try to load from SD anyway without the jumper.

Steve

@mmmmmmmm Problem solved. Updated to latest virtualbox version...

Problem solved. You need to set "Westmere" or "kvm64" CPU type instead of host passthrough in libvirt/virsh/kvm/qemu configuration file "virsh edit $vmname"

<cpu mode='custom' match='exact' check='none'>
<model fallback='allow'>Westmere</model>
<topology sockets='1' cores='6' threads='2'/>
</cpu>

yes ! good work, Luckily it was only a software problem