That's precisely the situation, yes. 32GB EBS volume. So, would either of the following work?
1. Provisioning an encrypted volume at the snapshot size, then extending the size of the volume. 2. Provisioning an unencrypted volume at the desired size. Obviously #1 would be preferable. -----Original Message----- From: Colin Percival <[email protected]> Sent: Thursday, April 1, 2021 6:29 PM To: Connor Sheridan <[email protected]>; [email protected] Subject: Re: FreeBSD 12.2-RELEASE x86_64 EC2 AMIs in us-east-2 not booting On 4/1/21 2:57 PM, Connor Sheridan wrote: > I've attempted to provision x86_64 instances in AWS region us-east-2 from > both the Marketplace AMIs and the specific AMI ID provided by the > 12.2-RELEASE announcement, and they just get stuck in an endless boot loop. > Appears to load the kernel, then reboot instantly. Are there any known > gotchas about provisioning this release or anything I can do to get these > running? There seems to be an issue related to encrypted disks -- possibly specifically related to creating an EBS encrypted volume which is larger than the backing snapshot. Are you using an encrypted disk? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-cloud To unsubscribe, send any mail to "[email protected]"
