"Warning: Could not boot" when changing EC2 type on Nitro

0

Hello,

I need to change my EC2 type from t2.medium to t3.medium but when I try it, after enabling ENA, I receive this error :


[ 191.190411] dracut-initqueue[237]: Warning: Could not boot. [ 197.929549] dracut-initqueue[237]: Warning: /dev/disk/by-uuid/be1fac20-759b-49ef-aebe-d81a9d855149 does not exist Starting Dracut Emergency Shell... [ 200.916603] audit_printk_skb: 6 callbacks suppressed Warning: /dev/di[ 200.945686] type=1131 audit(1719406652.904:13): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' sk/by-uuid/be1fac20-759b-49ef-aebe-d81a9d855149 does not exist

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.

dracut:/# dracut:/# ^C dracut:/# "


The fact is that if I return to t2.medium there is no error and boot continue.

I have check on my EC2 machine and see that the disks are ok:


more fstab

/etc/fstab

Created by anaconda on Tue Apr 7 16:11:27 2020

Accessible filesystems, by reference, are maintained under '/dev/disk'

See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info

UUID=be1fac20-759b-49ef-aebe-d81a9d855149 / ext4 defaults,noatime,nodiratime 1 1 UUID=6bfd2255-9232-4aab-9572-98a7842a3418 /boot ext4 defaults,nosuid,noexec,nodev,noatime 1 2 UUID=d0a32815-5bab-4fba-8cd9-e778f95c6931 swap swap defaults 0 0 //172.31.9.223/temp/backup /mi/clever/backup/cifs cifs credentials=/mi/clever/backup/credentials.txt,vers=3.0

./nitrocheck.sh

OK NVMe Module is installed and available on your instance

OK ENA Module with version 2.0.3K is installed and available on your instance

OK fstab file looks fine and does not contain any device names.



Some have any idea or can help me to understand how to resolve this ?

Thanks a lot

Walter

asked 2 months ago158 views
4 Answers
0

I beleive you will need to install the ENA adaptor on the T2 before changing to a T3. I had to do this on a windows box previously https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/resize-limitations.html

You may also need to install the NVMe drivers too

profile picture
EXPERT
answered 2 months ago
profile picture
EXPERT
reviewed 2 months ago
0

Hello,

thanks for your answer!

The problem is that I have run the check and this is the result :


OK NVMe Module is installed and available on your instance

OK ENA Module with version 2.0.3K is installed and available on your instance

OK fstab file looks fine and does not contain any device names.

All seem well and installed...

What can I do ?

Walter

answered 2 months ago
0

Hello,

soome one has some possible solution ?

Thanks

Walter

answered 2 months ago
0

Hi, I think you are getting problem due to t2 and t3 generations are difference as t3 is new generation instnce. Try to verify the ENA again 2.Check the Kernel modules 3.check and modify fstab if needed finally detach volume and reattach it then reboot it

profile picture
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions