Grub won't detect Windows 10 on NVME SSD












2















Installed Ubuntu 18.04 alongside Windows 10 a month or 2 ago, but had issues installing and after it installed Grub would never show up at all and I had to choose whether to boot Windows or Ubuntu by changing boot order in UEFI settings. Eventually (today) I was able to get Grub to finally show up (apparently for some absolutely stupid reason a setting got set in /etc/default/grub called GRUB_TIMEOUT_STYLE=hidden which prevents Grub from showing during timeout period unless you hit escape), but it still won't detect Windows 10 and allow me to boot to it. My current drive setup is I have a 128GB SATA SSD that Ubuntu is installed on, a 1TB SATA SSD that I have my Ubuntu Home directory on, a 500GB NVME SSD that Windows 10 is installed on, and a 1TB HDD that I use for bulk storage on my Windows system.
Here is the output when I run sudo update-grub:



ubuntu:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-43-generic
Found initrd image: /boot/initrd.img-4.15.0-43-generic
Found linux image: /boot/vmlinuz-4.15.0-42-generic
Found initrd image: /boot/initrd.img-4.15.0-42-generic
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
Adding boot menu entry for EFI firmware configuration
done


Any help greatly appreciated, thanks.










share|improve this question

























  • The partition sdc1 (I suppose is the boot partition of windows) which kind of partition is?

    – AtomiX84
    Jan 4 at 10:11











  • sdc1 is my 1TB HDD for windows, it does not contain the boot partition. Here are the results of both from fdisk -l pastebin.com/E25dZwWf

    – Gren
    Jan 4 at 18:30













  • The boot partition of windows is stored some were else or is not present at all? If is the second case (not present) that is the reason why grub cannot find it

    – AtomiX84
    Jan 4 at 20:32











  • Shouldn't the boot partition of windows be nvme0n1p1 in that fdisk results? It is marked as boot at least

    – Gren
    Jan 4 at 20:52











  • Ok, I get it, what about you mount that partition and run "sudo os-prober"? It find also windows partito on as well?

    – AtomiX84
    Jan 4 at 21:00
















2















Installed Ubuntu 18.04 alongside Windows 10 a month or 2 ago, but had issues installing and after it installed Grub would never show up at all and I had to choose whether to boot Windows or Ubuntu by changing boot order in UEFI settings. Eventually (today) I was able to get Grub to finally show up (apparently for some absolutely stupid reason a setting got set in /etc/default/grub called GRUB_TIMEOUT_STYLE=hidden which prevents Grub from showing during timeout period unless you hit escape), but it still won't detect Windows 10 and allow me to boot to it. My current drive setup is I have a 128GB SATA SSD that Ubuntu is installed on, a 1TB SATA SSD that I have my Ubuntu Home directory on, a 500GB NVME SSD that Windows 10 is installed on, and a 1TB HDD that I use for bulk storage on my Windows system.
Here is the output when I run sudo update-grub:



ubuntu:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-43-generic
Found initrd image: /boot/initrd.img-4.15.0-43-generic
Found linux image: /boot/vmlinuz-4.15.0-42-generic
Found initrd image: /boot/initrd.img-4.15.0-42-generic
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
Adding boot menu entry for EFI firmware configuration
done


Any help greatly appreciated, thanks.










share|improve this question

























  • The partition sdc1 (I suppose is the boot partition of windows) which kind of partition is?

    – AtomiX84
    Jan 4 at 10:11











  • sdc1 is my 1TB HDD for windows, it does not contain the boot partition. Here are the results of both from fdisk -l pastebin.com/E25dZwWf

    – Gren
    Jan 4 at 18:30













  • The boot partition of windows is stored some were else or is not present at all? If is the second case (not present) that is the reason why grub cannot find it

    – AtomiX84
    Jan 4 at 20:32











  • Shouldn't the boot partition of windows be nvme0n1p1 in that fdisk results? It is marked as boot at least

    – Gren
    Jan 4 at 20:52











  • Ok, I get it, what about you mount that partition and run "sudo os-prober"? It find also windows partito on as well?

    – AtomiX84
    Jan 4 at 21:00














2












2








2








Installed Ubuntu 18.04 alongside Windows 10 a month or 2 ago, but had issues installing and after it installed Grub would never show up at all and I had to choose whether to boot Windows or Ubuntu by changing boot order in UEFI settings. Eventually (today) I was able to get Grub to finally show up (apparently for some absolutely stupid reason a setting got set in /etc/default/grub called GRUB_TIMEOUT_STYLE=hidden which prevents Grub from showing during timeout period unless you hit escape), but it still won't detect Windows 10 and allow me to boot to it. My current drive setup is I have a 128GB SATA SSD that Ubuntu is installed on, a 1TB SATA SSD that I have my Ubuntu Home directory on, a 500GB NVME SSD that Windows 10 is installed on, and a 1TB HDD that I use for bulk storage on my Windows system.
Here is the output when I run sudo update-grub:



ubuntu:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-43-generic
Found initrd image: /boot/initrd.img-4.15.0-43-generic
Found linux image: /boot/vmlinuz-4.15.0-42-generic
Found initrd image: /boot/initrd.img-4.15.0-42-generic
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
Adding boot menu entry for EFI firmware configuration
done


Any help greatly appreciated, thanks.










share|improve this question
















Installed Ubuntu 18.04 alongside Windows 10 a month or 2 ago, but had issues installing and after it installed Grub would never show up at all and I had to choose whether to boot Windows or Ubuntu by changing boot order in UEFI settings. Eventually (today) I was able to get Grub to finally show up (apparently for some absolutely stupid reason a setting got set in /etc/default/grub called GRUB_TIMEOUT_STYLE=hidden which prevents Grub from showing during timeout period unless you hit escape), but it still won't detect Windows 10 and allow me to boot to it. My current drive setup is I have a 128GB SATA SSD that Ubuntu is installed on, a 1TB SATA SSD that I have my Ubuntu Home directory on, a 500GB NVME SSD that Windows 10 is installed on, and a 1TB HDD that I use for bulk storage on my Windows system.
Here is the output when I run sudo update-grub:



ubuntu:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-43-generic
Found initrd image: /boot/initrd.img-4.15.0-43-generic
Found linux image: /boot/vmlinuz-4.15.0-42-generic
Found initrd image: /boot/initrd.img-4.15.0-42-generic
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
Adding boot menu entry for EFI firmware configuration
done


Any help greatly appreciated, thanks.







boot dual-boot grub2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 4 at 10:09









Kulfy

4,29651342




4,29651342










asked Jan 4 at 10:06









GrenGren

111




111













  • The partition sdc1 (I suppose is the boot partition of windows) which kind of partition is?

    – AtomiX84
    Jan 4 at 10:11











  • sdc1 is my 1TB HDD for windows, it does not contain the boot partition. Here are the results of both from fdisk -l pastebin.com/E25dZwWf

    – Gren
    Jan 4 at 18:30













  • The boot partition of windows is stored some were else or is not present at all? If is the second case (not present) that is the reason why grub cannot find it

    – AtomiX84
    Jan 4 at 20:32











  • Shouldn't the boot partition of windows be nvme0n1p1 in that fdisk results? It is marked as boot at least

    – Gren
    Jan 4 at 20:52











  • Ok, I get it, what about you mount that partition and run "sudo os-prober"? It find also windows partito on as well?

    – AtomiX84
    Jan 4 at 21:00



















  • The partition sdc1 (I suppose is the boot partition of windows) which kind of partition is?

    – AtomiX84
    Jan 4 at 10:11











  • sdc1 is my 1TB HDD for windows, it does not contain the boot partition. Here are the results of both from fdisk -l pastebin.com/E25dZwWf

    – Gren
    Jan 4 at 18:30













  • The boot partition of windows is stored some were else or is not present at all? If is the second case (not present) that is the reason why grub cannot find it

    – AtomiX84
    Jan 4 at 20:32











  • Shouldn't the boot partition of windows be nvme0n1p1 in that fdisk results? It is marked as boot at least

    – Gren
    Jan 4 at 20:52











  • Ok, I get it, what about you mount that partition and run "sudo os-prober"? It find also windows partito on as well?

    – AtomiX84
    Jan 4 at 21:00

















The partition sdc1 (I suppose is the boot partition of windows) which kind of partition is?

– AtomiX84
Jan 4 at 10:11





The partition sdc1 (I suppose is the boot partition of windows) which kind of partition is?

– AtomiX84
Jan 4 at 10:11













sdc1 is my 1TB HDD for windows, it does not contain the boot partition. Here are the results of both from fdisk -l pastebin.com/E25dZwWf

– Gren
Jan 4 at 18:30







sdc1 is my 1TB HDD for windows, it does not contain the boot partition. Here are the results of both from fdisk -l pastebin.com/E25dZwWf

– Gren
Jan 4 at 18:30















The boot partition of windows is stored some were else or is not present at all? If is the second case (not present) that is the reason why grub cannot find it

– AtomiX84
Jan 4 at 20:32





The boot partition of windows is stored some were else or is not present at all? If is the second case (not present) that is the reason why grub cannot find it

– AtomiX84
Jan 4 at 20:32













Shouldn't the boot partition of windows be nvme0n1p1 in that fdisk results? It is marked as boot at least

– Gren
Jan 4 at 20:52





Shouldn't the boot partition of windows be nvme0n1p1 in that fdisk results? It is marked as boot at least

– Gren
Jan 4 at 20:52













Ok, I get it, what about you mount that partition and run "sudo os-prober"? It find also windows partito on as well?

– AtomiX84
Jan 4 at 21:00





Ok, I get it, what about you mount that partition and run "sudo os-prober"? It find also windows partito on as well?

– AtomiX84
Jan 4 at 21:00










1 Answer
1






active

oldest

votes


















0














Apologies, it seems I expected too much from Microsoft. Even though I installed Windows within the last year and just expected it installed as UEFI, it was installed as BIOS and Ubuntu was installed as UEFI. Just converted Windows to UEFI and it seems to work fine.






share|improve this answer
























  • lol, that is nothing about expectation, anyway, sure both system use UEFI, bot of the disks had dos partition table and as far as I remember UEFI require GPT partition table, anyway important is you resolve, about your answer i think is much better to say your troubleshoot steps and action taken to fix the issues, like this others folling in same situation can find this question useful

    – AtomiX84
    Jan 5 at 14:52











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1106860%2fgrub-wont-detect-windows-10-on-nvme-ssd%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Apologies, it seems I expected too much from Microsoft. Even though I installed Windows within the last year and just expected it installed as UEFI, it was installed as BIOS and Ubuntu was installed as UEFI. Just converted Windows to UEFI and it seems to work fine.






share|improve this answer
























  • lol, that is nothing about expectation, anyway, sure both system use UEFI, bot of the disks had dos partition table and as far as I remember UEFI require GPT partition table, anyway important is you resolve, about your answer i think is much better to say your troubleshoot steps and action taken to fix the issues, like this others folling in same situation can find this question useful

    – AtomiX84
    Jan 5 at 14:52
















0














Apologies, it seems I expected too much from Microsoft. Even though I installed Windows within the last year and just expected it installed as UEFI, it was installed as BIOS and Ubuntu was installed as UEFI. Just converted Windows to UEFI and it seems to work fine.






share|improve this answer
























  • lol, that is nothing about expectation, anyway, sure both system use UEFI, bot of the disks had dos partition table and as far as I remember UEFI require GPT partition table, anyway important is you resolve, about your answer i think is much better to say your troubleshoot steps and action taken to fix the issues, like this others folling in same situation can find this question useful

    – AtomiX84
    Jan 5 at 14:52














0












0








0







Apologies, it seems I expected too much from Microsoft. Even though I installed Windows within the last year and just expected it installed as UEFI, it was installed as BIOS and Ubuntu was installed as UEFI. Just converted Windows to UEFI and it seems to work fine.






share|improve this answer













Apologies, it seems I expected too much from Microsoft. Even though I installed Windows within the last year and just expected it installed as UEFI, it was installed as BIOS and Ubuntu was installed as UEFI. Just converted Windows to UEFI and it seems to work fine.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 5 at 6:12









GrenGren

111




111













  • lol, that is nothing about expectation, anyway, sure both system use UEFI, bot of the disks had dos partition table and as far as I remember UEFI require GPT partition table, anyway important is you resolve, about your answer i think is much better to say your troubleshoot steps and action taken to fix the issues, like this others folling in same situation can find this question useful

    – AtomiX84
    Jan 5 at 14:52



















  • lol, that is nothing about expectation, anyway, sure both system use UEFI, bot of the disks had dos partition table and as far as I remember UEFI require GPT partition table, anyway important is you resolve, about your answer i think is much better to say your troubleshoot steps and action taken to fix the issues, like this others folling in same situation can find this question useful

    – AtomiX84
    Jan 5 at 14:52

















lol, that is nothing about expectation, anyway, sure both system use UEFI, bot of the disks had dos partition table and as far as I remember UEFI require GPT partition table, anyway important is you resolve, about your answer i think is much better to say your troubleshoot steps and action taken to fix the issues, like this others folling in same situation can find this question useful

– AtomiX84
Jan 5 at 14:52





lol, that is nothing about expectation, anyway, sure both system use UEFI, bot of the disks had dos partition table and as far as I remember UEFI require GPT partition table, anyway important is you resolve, about your answer i think is much better to say your troubleshoot steps and action taken to fix the issues, like this others folling in same situation can find this question useful

– AtomiX84
Jan 5 at 14:52


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1106860%2fgrub-wont-detect-windows-10-on-nvme-ssd%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Ellipse (mathématiques)

Quarter-circle Tiles

Mont Emei