Quote from: PackRat on March 14, 2019, 01:09:39 PM
Also, on my dual boot systems where Windows occupies /dev/sda, the installer has never (5+ installs) written grub to /dev/sdb or /dev/sdc. I always have to reboot and chroot into the system to install grub.
@vastone - in the other thread, you were saying the fstab was blank/incomplete? I interpreted that as an install of the new 2019 build went to completion but an fstab wasn't created. Did you attempt to chroot into the install and attempt to manually create an fstab, or check the partition layout to verify they were created?
So recently, (Last May) this MSI lappy went to the wife and a brand new (almost $200) Win 10 Pro install on it. Now it is mine again. A month ago I did a dual boot as PackRat says above with the same results though a different solution. I also Installed Mint in a different location on the same NVMe drive. This was and is how I am booting into VSIDO currently. The Mint install uses the Ubuntu UEFI grub2 installer. I'm seriously lazy these days and just haven't done the chroot exercise to switch Grub to this (my VSIDO goto) /dev/somewhere/blah. All that to say this, last year when the last ISO's were being released, wasn't there an ongoing issue with this then? A Debian thing?
I think part of this issue is the gpt partitioned disks. Is the installer recognizing the 'gpt' partitioning if it is already 'gpt'? Also, the same holds for the m.2 PCIe SSD's. Probably way tmi. Sorry. All I know is, I have VSIDO back full time!
Nice to see some discussion going on for sure! Hope you are all doing well...