So it's been a few days and I still can not connect to my new HVM instance with EC2 running Ubuntu 16. For reference, I am trying to upgrade our server from an m3 instance running Ubuntu 16, to a C5 instance running Ubuntu 16. For almost every method I've tried, I am able to get to the point where I stop my new C5 instance, detach all volumes, and attach the newly updated source volume as
/dev/sda1, but then when I go to connect to the instance, I always end up timing out. Amazon's status check also fails, as it says the instance is unreachable. However, the system log shows no issues when starting up.
I've tried doing everything in this post. I've tried this post as well. I've looked on other sites, and have given this and this a try. I've even tried both the ec2 command line tools method, and converting an AMI from the ec2 console (online), however I either cannot launch a C5 instance with the converted AMI, or the instance will stop and fail (in the case of conversion via command line).
The only thing I can really think of that might be causing it, is the naming convention for the partitions on the C5 instance. Every single guide I've seen uses
xvda/xvdf/xvdg. I could be wrong, but I do not have these partitions or disks, and instead have
nvme0n1p1, (the new HVM root),
nvme1n1p1. When I tried the HVM / source / target disk method, I had
nvme1n1 (target -- where everything should end up), and
nvme2n1/nvme2n1p1 (source -- where everything was from, on m3). I found this Amazon post about nvme so I don't think this should be an issue, as I'm just using the correct disk / partition when using
/mnt/, ie. I call
mkdir -p /mnt/target && mount /dev/nvme1n1 /mnt/target instead of
mkdir -p /mnt/target && mount /dev/xvdf /mnt/target, but nothing so far has worked. My instance becomes unreachable the moment I attach the
So, is there something that I'm missing when doing these with a disk named
nvme*? Is there any other information or debug things I can provide to help understand the issue?