EC2 issue when starting: cloud-init-nonet gave up waiting for a network dev

Question

I had an instance running successfully for several years and earlier today it got stuck while running freshclam. I shut the instance down, and changed the instance type to a larger one to be able to update CLAM database faster.  
  
Instance ID: i-05c312353d4c47c7b  
  
But when trying to restart it don't work no more. I'm having a network issue, as well as some issues with mounting ebs volumes.   
  
**The network error:**  
  
```  
cloud-init-nonet waiting 120 seconds for a network device.  
cloud-init-nonet gave up waiting for a network device.  
ci-info: ens5  : 0 .               .               12:da:07:9b:5c:57  
ci-info: lo    : 1 127.0.0.1       255.0.0.0       .  
```  
  
I checked `/etc/network/interfaces` and it's set to auto:  
  
```  
# The loopback network interface  
auto lo  
iface lo inet loopback  
  
# The primary network interface  
auto eth0  
iface eth0 inet dhcp  
```  
  
**EBS volume error:**   
  
```  
The disk drive for /mnt/ebs is not ready yet or not present.  
Continue to wait, or Press S to skip mounting or M for manual recovery  
```  
  
I already tried restoring an image from January and it gives me the same error. I also tried starting a new instance based on the current one image without success.  
  
Would appreciate some tips and guidance on how to find the root cause. Thanks.  
  
Edited by: danielslcosta on Aug 30, 2021 12:16 PM  
  
Edited by: danielslcosta on Aug 30, 2021 12:27 PM

Answer

The issue was caused by me starting the current root device with a T3 instance, instead of a T2 - I was looking to start with a bigger instance to make the CLAM update faster.  
  
After restarting it with a T2 instance, everything worked...

EC2 issue when starting: cloud-init-nonet gave up waiting for a network dev

Relevanter Inhalt