Closed bretton closed 3 days ago
This can be closed with #50 however some more tests may be useful
related to #51
With boxes having IPMI, which are most of them apart from the cheap Kimsufi ones, you can load a FreeBSD ISO and install FreeBSD from there. My most recent boxes always a HTML5-based KVM, so no Java shenanigans were required. They don't have a FreeBSD rescue (anymore?), though.
I've tested on a KS-16 OVH machine. I had to replace "mkisofs:mkisofs" by "genisoimage:genisoimage"
Once qemu has booted, I can not ssh -p 1022 msfbsd@... to the machine..
thanks @hpcharles - I'll get an instance and do some testing, then update the script. Could be couple of weeks.
em0
Once qemu has booted, I can not ssh -p 1022 msfbsd@... to the machine..
general diagnostics: is port 1022 open? is there an error message?
Once qemu has booted, I can not ssh -p 1022 msfbsd@... to the machine..
general diagnostics: is port 1022 open? is there an error message?
There is no firewall, no error message
Once qemu has booted, I can not ssh -p 1022 msfbsd@... to the machine..
general diagnostics: is port 1022 open? is there an error message?
There is no firewall, no error message
It ask to accept the new key (sshd works) "The authenticity of host .... an't be established
But fails to identificate with public key : debug1: Trying ... all my public key debug1: No more authentication methods to try. msfbsd@localhost: Permission denied (publickey).
I can confirm that mkisofs:mkisofs
needs replacing with genisoimage:genisoimage
on
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
However it works fine for me when I access mfsbsd on KS-16 host on OVH.
How are you passing in your public key? I'm running ./run.sh http://my.host/keys.txt
where keys.txt
matches an .ssh/authorized_keys
file from a server.
follow up: unattended install completed, but host didn't boot up with reachable network interface. KVM is $40/month and no IPMI. It should pick up correct interface name on firstboot. When I try go back to rescue it says an intervention is underway, limiting my ability to try install again right now. Will pick up in the week as time permits.
update: no change in network reachability with em0
and correctly following exit from rescue / boot from disk process. Might have to get KVM.
for interest sake, KVM is Lantronix Spider
Disks appear to be on a SAN device and won't boot. Tried multiple times. Screenshot attached.
Updated installer script runs fine. There is a delay between creating iso and detecting disks, but everything works to get mfsbsd image running and reachable.
The server actually has 3 disks, and when configured for unattended install with raidz1 then it boots fine
bretton@ns523785:~ $ freebsd-version
14.0-RELEASE
@hpcharles I think we need to try debug your ssh key import. Do you have your id_rsa.pub
accessible via a url?
Test Request: OVH Baremetal servers
https://www.ovhcloud.com/en/bare-metal/
Multiple tiers/ranges of servers with common entry level disk setup of 2 x 2TB or 2 x 512GB SSD:
Linux based rescue system https://docs.ovh.com/gb/en/dedicated/ovh-rescue/