I Reinstalled Linux Parrot Security 3.9 Kernel Version 4.14.0 86_64 over an installation of Kali 2017.3 (ironically same kernel version of Debian right now) 4.14.0 86_64.
Now I partitioned the HDD fully, Manual like always, /dev/sda1-boot 512M,/dev/sda2-swap 8G,/dev/sda3-/root-25G, /dev/sda4 /home-rest of partion size.
I have 2 HDD's in correct order to boot linux first unless I hit F11 the Linux HDD is in the first SATA cable slot, and I have a separate Windows HDD on the Second SATA cable slot. I prefer not to Dual Boot Windows with Linux on the same HDD.
Normally when I power up I hit F11 for boot options, both HDD's show up and I select accordingly, I use Windows for Gaming, and Linux for everything else.
But now when I hit F11 the old Kali is still in the first option as /dev/sda3 Windows comes up as the second option to boot into (as it has for over a year now with this setup) but Parrot is also coming up on /dev/sda3 (same as Kali which should have been overwritten) I can Select /dev/sda3/Parrot and it works fine. Windows works fine, but if I select the /dev/sda3/Kali (which should have been over-written) it boots into a grub error and I have that grub rescue> prompt.
Lastly, the way I have always cabled this was Linux boots unless I hit F11 and Select Windows HDD, but because I'm getting this Grub Error Grub Rescue> and the last Kali's Grub didn't get removed it seems, I always have to hit F11 now. It’s not like I can't get into my new Parrot OS, built on identical Kernel as Kali now, the Debian 9 just a different repo update method I think. It works fine, I just want my system to be as correct as possible.
What should I do? I seem to have conflicts with /dev/sda3 having a real Distro on it, and another one thinking it does when it does not?