I hate the touchpad on this MSI laptop. It is my least hated option on this laptop. I will NEVER buy another MSI product in the future. It is not solely related to this issue that I make that statement. (the 90 sec)
So I have an NVMe PCIe drive. Seen by fdisk, parted, gparted, fstab, blkid, lsblk, you get the idea, as nvme0n1. OK, so in /etc/fstab:
### first '6' lines are the original fstab for the VSIDO install
### we'll call this section 1.
#proc /proc proc defaults 0 0
#UUID=bda2cbcd-9696-419b-baf4-2e875fc1279a / ext4 defaults,noatime 0 1
#UUID=730da2a3-5aef-4654-908e-865d3ed8f8aa /home ext4 defaults,noatime 0 2
#UUID=efe98bd0-1254-40b4-8378-61811c50da34 swap linux-swap defaults 0 0
#UUID=9E77-1B41 /boot/efi vfat defaults 0 1
### we'll call this section 2.
proc /proc proc defaults 0 1
/dev/nvme0n1p1 /boot/efi vfat defaults 0 1
/dev/nvme0n1p3 / ext4 defaults,noatime 0 1
/dev/nvme0n1p4 /home ext4 defaults,noatime 0 2
/dev/sda1 /media/DATA ntfs-3g defaults,noatime 0 2
/dev/nvme0n1p10 /media/root_manjaro ext4 defaults,noatime 0 1
/dev/nvme0n1p11 /media/home_manjaro ext4 defaults,noatime 0 2
Either way I have the 90 second wait. However, for clarity, here is the general order of events;
Power on, Grub, then the "A start job for dev-x2uuidblahblahblah" happens for 90 seconds. For whatever weird reason, in /etc/fstab when the top lines are uncommented, (called "section 1" above) and the /dev/nvme* are commented, (called "section 2" above) no wireless. The card is seen, (Killer Wireless Qualcom card, ath10k) just no wifi. Haven't tested ethernet.
(this issue resolved itself with the fix described below of adding 'nofail' to /etc/fstab. I no longer believe UUID's are an issue or were an issue. This has happened to as many regular ssd's and hdd's all over the net.) I say this having just booted my laptop into VSIDO with no errors, and all drives present, and accounted for utilizing the UUID's!
Now, as seen above, just as it is, it goes to a emergency mode 'pause' for you to acknowledge that "no, it is not an emergency, or an issue", so press Ctrl-d and it boots to all of VSIDO's glory and finery!
Or type your password to fix any imaginary problems you may be having...
I'm sorry it took so long for me to post about this. I am also grateful to all of you who've taken care of it, so I can come along at last and correct mine! Seriously, to everyone here on the forum, VastOne has been toiling away at this ever since I mentioned it on IRC almost 2 weeks ago. Our one and only dev of VSIDO truly is a "one and only
"!!!! Also thanks to PackRat as well. Wow, also zephyr and anyone else that posts here in support of this non-issue! hehe
I also agree that probably it shouldn't be marked solved...
VastOne, there might also could be a better or more proper name for the thread?