I have been googling like crazy to solve this issue and most of the posted solutions have failed.
I am trying to dual boot an Alienware 17 R3 computer that came with Windows 10 preinstalled on a 1TB HDD. I installed 2 Samsung 950 Pro SSD's and I have previously managed to get Ubuntu 16.04 installed and it dual booted fine.
However, I upgraded the BIOS and that caused serious problems with (only) the Ubuntu installation. First it was a nouveau error and then it dropped me to a shell because it couldn't find the boot drive (I think) I figured that the sanest step was to re-format the SSD's and do a fresh reinstall of Ubuntu 16.04 from a USB.
I have turned off Fast Boot and Secure Boot and have used the UEFI boot with Legacy Option ROM. I cannot recall exactly if Secure Boot was disabled during the initial installation of Ubuntu but I can say with certainty that, as of this moment, Ubuntu (and gparted) do not recognize my SSD drives without Secure Boot being deactivated. With Secure Boot acitvated, I am unable to install to, or even find the SSDs using 'sudo fdisk -l'. As I mentioned previously, I don't think this was the case during the first install (prior to the BIOS update) but I can't be certain.
I am still booted from the USB in UEFI mode and installed in UEFI mode. The installation seemingly went well and advised me to reboot, but the reboot takes me to the grub rescue page ('no such device' then the UUID for the SSD that has the root info).
I tried running boot-repair (several times) but that was ineffective. The latest output can be seen here: http://paste2.org/7LOvctjf
It appears as though this BIOS update has done something to Ubuntu's ability to find/recognize my SSD's, yet it was previously able to do so.
Any help with this matter would be greatly appreciated. I am able to get into Ubuntu via the USB so please let me know what further information is required to resolve this problem.
Thanks in advance for any help you can offer.
p.s. the BIOS update also create a 'nouveau' error but that seems like it has to do with nvidia drivers and is probably unrelated to the larger problem. I only mention it in case it is more meaningful than I believe.