I am having Windows 11 and Ubuntu 22.04 LTS dual boot system. Windows 11 on regular SSD while Ubuntu 22.04 LTS on PCIE NVME SSD. It's Dell XPS 8930 Desktop(2018) where I have made a lot of upgrades and additions. As part of the latest upgrade, I upgraded 512GB PCIE NVME SSD(version 1) to 4 TB PCIE NVME SSD(ver 4.0). I used AOMEI cloning software for this . In the process of upgrading PCIE NVME SSD, I removed the swap partition as it was not being used any more. Disk cloning was successful. After that I just swapped the old PCIE NVME SSD with new PCIE NVME SSD in the desktop.
Dual boot - windows and Linux all booted properly. But the only issue is this check that is there. In the past also I had this check but it was a smaller PCIE NVME SSD but now it is for larger PCIE NVME SSD.
Message is as follows: SGX Launch Control is locked. Support SGX virtualization only. I believe this might be due to the fact that I have enabled virtualization in the BIOS. This message is quick. But after that it's sort of check disk kind of process. Mine PCIE NVME SSD(on which Ubuntu 22.04 LTS is installed is 4TB) so this check disk kind of check is really slowing down the boot process. How I can disable this checkdisk kind of process.
/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p3 during installation
UUID=e6311f73-982f-4037-95ec-23a60032ff67 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p2 during installation
UUID=8DED-981F /boot/efi vfat umask=0077 0 1
# swap was on /dev/nvme0n1p4 during installation
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=e6311f73-982f-4037-95ec-23a60032ff67 ro quiet splash vt.handoff=7
Tried this approach also but no success. Tried this approach also but no success. Here is the video of this issue
I think this could be the potential issue