can't boot / Can't find "boot config"?

Hi,
i have a problem where i don't know what to do.

Its a virtual server at Hetzner.
They announced to change the "network model".
To do this i should change networkconfig to DHCP, poweroff server, update "network model", power on server.
It allready was on DHCP so i only did the "network model".

But now it won't boot.

I have console access.

It says:

Booting from Hard Disk...
/boot/config: (smiley symbol?)

FreeBSD/x86 boot
Default: zroot/ROOT/....
boot:
/
Can't fint (smiley symbol)


I feel overwhelmed with this.
What should i do?
 

Attachments

  • a.png
    a.png
    17.7 KB · Views: 29
Changing some network related setting on the VM has nothing to do with the system not booting. So it looks like you may have accidentally changed something else too?
 
Thanks for you answer!
I would tend to say "i changed nothing".
I have absolutely no clou what it could be.
Do i have any options at this "boot:"-prompt?
 
Did you perhaps change UEFI boot to BIOS (aka CSM) boot? Because this looks like the MBR boot prompt. And what happens if you just press 'enter'?
 
I don't know how i could change UEFI. Its a virtual server.
When i press enter the process starts again and ends with the "boot:"-prompt.
I can start the system with a freebsd-rescue-iso-image.
But since i don't know whats broken, i don't know what to do.
 
I can start the system with a freebsd-rescue-iso-image.
But since i don't know whats broken, i don't know what to do.
If you can boot the rescue, you can at least have a look at the partitioning of the disk ( gpart show), that might provide additional clues. If it's MBR vs. GPT, or if there is an efi partition or not.

The prompt looks like it came from boot2: https://docs.freebsd.org/en/books/handbook/boot/#boot-boot1

Did you perhaps, before you shutdown the system, upgrade the boot pool? But forgot to update the bootloader too? Maybe you did this some time ago but haven't rebooted yet, and so never encountered the boot issue. But with the shutdown (to change that network setting) it now fails to boot?
 
(edit: ignore my comment for now, SirDice presents better suggestions here).

How did you install this critter and more importantly: how do you keep it up to date? Is this all installed using binary packages or did you build stuff yourself (maybe also the kernel and/or base system)?

Because a change in the external network stack is definitely not a reason why the system wouldn't boot anymore. Stall during boot perhaps, but that's it.
 
Is "network model" a setting in the web control panel for your VM?

I bet they changed something in boot_config and its stalled.

Don't you have a backdoor web shell like VIRSH?
 
Phishfry The "network model" is some setting on the vm-server as i understand.
I contacted support and they did reset it for test, but the boot problem persistet.
From there they are "unable to give further support"

I'm in the rescue (14.1) and gpart says its gpt.

If i now import the zpool.

zpool import -N -R /mnt zroot
zfs mount zroot/ROOT/default

could i then run something like:

gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0
 

Attachments

  • c.png
    c.png
    15.1 KB · Views: 17
Its running again. :)

I imported the zpool
mounted it
chrooted into it
mounted /dev
gpart bootcode
AHA
gpart recover
gpart bootcode
exit, umount, reboot

all ok.

Thanks for the tips and for holding my hand.
And thanks to FreeBSD for beeing such a cool robust system!
 
Back
Top