1 個回答
- 最新
- 最多得票
- 最多評論
0
Found solution. I think aws documentation can be improved (check script and documentation for new nitro systems). Script erroneously return "OK" for NVMe check. In fact nvme driver (e.g. nvme.ko.xz) was present in the OS (modeprobe nvme), but not in initramfs, allowing boot unable to discover and use new nitro based nvme devices.
To add nvme driver in initramfs (available at device discover and mount phase):
echo 'add_drivers+=" nvme "' > /etc/dracut.conf.d/nvme.conf
dracut -f -v
lsinitrd /boot/initramfs-$(uname -r).img | grep nvme.ko
other configuration make instance more robust:
For (ENA):
(optional - network availability in initramfs phase)
echo 'add_drivers+=" ena "' > /etc/dracut.conf.d/ena.conf
dracut -f -v
lsinitrd /boot/initramfs-$(uname -r).img | grep ena.ko
(optional - avoid network device name change between reboot)
add net.ifnames=0 to kernel options (e.g in GRUB_CMDLINE_LINUX inside /etc/default/grub and executing grub2-mkconfig -o /boot/grub2/grub.cfg. OS distribution and version dependent)
(optional - avoid inconsistent disk name)
use UUID instead of device names in /etc/fstab and boot loader (e.g. for GRUB in /boot/grub2/grup.cfg root=UUID=...).
Edited by: Roxyrob on Jul 10, 2020 12:17 PM
Edited by: Roxyrob on Jul 10, 2020 12:31 PM
已回答 4 年前
相關內容
- 已提問 4 小時前
- 已提問 6 個月前
- 已提問 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前