Correct: SSD /sda1 is EOS and SSD /sdb1 is Windoze.
The grub menu is fine but somehow the BIOS seems to get the idea that I don’t have SSDs
And yes, I get the full grub2 menu on a cold start (and Windoze is in that menu as well as EOS). No problem at all with cold starts. And it’s not a problem with Windoze in hibernation mode or some other “quick start” mode. E.g. I can do cold start, load EOS work a bit, do a clean shutdown of EOS. Rins and repeat as many times as I like, but as soon as I do a soft reboot, the BIOS says no!
BTW: I have had this computer so long I had to replace the HDs. I have used EOS ever since the plug was pulled on Antergos. Always dual booted. Never had this problem before.
The ONLY circumstance when the problem occurs is soft rebooting from EOS. Doesn’t happen with Windoze.
When I was setting things up, I used the grub-configuration package. Yes, I also enabled os-prober and did all that stuff.
If you want the long story, it’s as follows:
I used Clonezilla to clone my EOS HD onto my new SSD. Perfect, no problems, could soft reboot to my heart’s content.
Later, I realised that I had to do a clean install of Windoze. Probably a good idea as it was in a mess anyway.
Stupidly, I forgot to unplug my EOS SSD. The Windoze installation goes through several restarts and I realised immediately my egregious mistake. But I didn’t want to pull the cable out in the middle of everything so I waited until the first restart . Too late! Grub had gone, EOS was unbootable.
Following the superb EOS tutorials about UEFI and reading about grub etc I got everything fine and dandy.
Except the above. (Sorry I should have told you all that before but I know people are busy.)
I can live with the problem, it’s a minor irritation but it would be good to know why it only happens with a soft reboot.
Yes, the fast start is disabled. And yes, it’s the latest version of Windows 10. I disabled it because of another warning about encrypted partitons being kept open on restarts. Which is stupid!
Admittedly, there is a bit of magic I don’t understand and well spotted @xircon ! I did check my fstab because I don’t quite get how the UUIDs can be the same if I just clone without somehow referencing the UUIDs to the new disks. If you really want, here is my fstab
No I don’t use Windows boot loader or the BIOS bootloader. I just use grub. And the grub menu is as it always was before I changed my hardware. It gives three options, the third one being sdb1 Windows
Remember, everything is fine and normal except if I choose to reboot from the EOS command line or menu. Only then does the BIOS seem to think there are no disks.
