Created attachment 220253 [details]
output of AWS Console "Get instance screenshot"
I have been unable to successfully start the FreeBSD 12 AMI --
AMI id: ami-0cd0a66e446e9fa78
AMI Name: FreeBSD 12.2-RELEASE-amd64-f5af2713-6d84-41f0-95ea-2eaee78f2af4-ami-00be86d9bba30a7b3.4
AMI Location: aws-marketplace/FreeBSD 12.2-RELEASE-amd64-f5af2713-6d84-41f0-95ea-2eaee78f2af4-ami-00be86d9bba30a7b3.4
This is the x86 version of the FreeBSD owned AMI. The ARM version was successful on my first attempt (but I need the x86 architecture)
I am running in the us-west-1 region but I got the same results in the us-east-1 region
I have attached the output of selecting "Get instance screenshot" in the AWS console.
There is no output when selecting "Get system log"
The console status shows "Instance reachability check failed"
I have tried these instance types:
The results were the same in all instance types, with a small exception for t3.medium -- the instance screenshot seemed to be continually re-booting, but never got past the end of the attached screenshot
Can you confirm that the instances are rebooting *repeatedly*? It's normal for FreeBSD to reboot once, since upon booting for the first time it downloads and installs security updates.
What size of root disk are you using?
Are you using an encrypted disk?
Have you tried the non-Marketplace AMIs listed in the release announcement? https://lists.freebsd.org/pipermail/freebsd-announce/2020-October/001993.html
Created attachment 220358 [details]
4 snapshot images in order
series of screenshots showing apparent repeated reboots. Images should be viewed in order *--1 to *--4
I have tried the AMI ami-0e54f016b55b7f6ce for us-west-1 -- I get the same results
I have always used encrypted disks, sizes from 10G to 30G
Thanks, there seems to be an issue with encrypted disks -- this isn't the first report we've had like this.
We're getting the same. Other than using non-encrypted disks, is there a known work around for this?
My workaround is as follows:
1. Launch an instance with an unencrypted disk.
2. Attached an encrypted disk to the instance.
3. Run bsdinstall to set up the encrypted disk with a fresh installation of FreeBSD.
4. Detach both disks from the instance.
5. Attach the encrypted disk to the instance as /dev/sda1 so that the instance boots from the fresh installation.
I personally like this approach because it lets me customize the install rather than use the settings selected in the AMI.
That said, if you like the AMI version, you can probably skip the bsdinstall step and instead just dd from a working unencrypted disk to an attached encrypted disk.
Thank you for your quick response I will try this and confirm asap!