GRUB can't see what os-prober found
There is an HDD and an SSD.
During Lubuntu installation on my HDD, it installed GRUB on HDD and os-prober made a menu entry for the SSD's Windows partition.
But GRUB can't see it on boot:
Error: no such device: 5CD2C8C949DA73C
The menu entry is:
menuentry 'Windows 8 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-5CD2C8C949DA73C' {
insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 5CD2C8C949DA73C
else
search --no-floppy --fs-uuid --set=root 5CD2C8C949DA73C
fi
parttool ${root} hidden-
drivemap -s (hd0) ${root}
chainloader +1
}
Factors to consider:
- This is an MBR system.
- The SSD is inside a caddy.
BIOS recognizes the SSD on POST as my secondary drive:
Fixed Disk 0: HITACHI HTS.........300
Fixed Disk 1: Samsung SSD 850 Evo 120GB
- Every OS and bootable utility including GRUB's os-prober can see the SSD.
- BIOS does not show the SSD in boot options(We're not planning to boot from it.).
Note: Workarounds like "Making the SSD boot-drive" or "Putting the SSD in the primary slot" are not acceptable for various reasons.
UPDATE: Asked about the "various reasons" in the comments: This is a ThinkPad E15. "Making the SSD boot-drive" is simply impossible due to the fact that "BIOS does not show the SSD in boot options" (It's one of the ThinkPads with lack of ultra-bay support, and perhaps because of that, it's designed for not booting a secondary HDD, so despite detecting it on POST as a Fixed Disk, does not show it in boot options. It only trys booting it as a CD-ROM and that doesn't work. Also, one reason for not "Putting the SSD in the primary slot" is, I want shock protection for my HDD but again, this ThinkPad does not support it for a secondary drive according to this site.
linux ubuntu grub
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
|
show 3 more comments
There is an HDD and an SSD.
During Lubuntu installation on my HDD, it installed GRUB on HDD and os-prober made a menu entry for the SSD's Windows partition.
But GRUB can't see it on boot:
Error: no such device: 5CD2C8C949DA73C
The menu entry is:
menuentry 'Windows 8 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-5CD2C8C949DA73C' {
insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 5CD2C8C949DA73C
else
search --no-floppy --fs-uuid --set=root 5CD2C8C949DA73C
fi
parttool ${root} hidden-
drivemap -s (hd0) ${root}
chainloader +1
}
Factors to consider:
- This is an MBR system.
- The SSD is inside a caddy.
BIOS recognizes the SSD on POST as my secondary drive:
Fixed Disk 0: HITACHI HTS.........300
Fixed Disk 1: Samsung SSD 850 Evo 120GB
- Every OS and bootable utility including GRUB's os-prober can see the SSD.
- BIOS does not show the SSD in boot options(We're not planning to boot from it.).
Note: Workarounds like "Making the SSD boot-drive" or "Putting the SSD in the primary slot" are not acceptable for various reasons.
UPDATE: Asked about the "various reasons" in the comments: This is a ThinkPad E15. "Making the SSD boot-drive" is simply impossible due to the fact that "BIOS does not show the SSD in boot options" (It's one of the ThinkPads with lack of ultra-bay support, and perhaps because of that, it's designed for not booting a secondary HDD, so despite detecting it on POST as a Fixed Disk, does not show it in boot options. It only trys booting it as a CD-ROM and that doesn't work. Also, one reason for not "Putting the SSD in the primary slot" is, I want shock protection for my HDD but again, this ThinkPad does not support it for a secondary drive according to this site.
linux ubuntu grub
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
1
And what might those “various reasons” be? Is it perhaps a notebook? Is the SSD on a different storage controller? Is GRUB missing drivers?
– Daniel B
Jun 11 '17 at 20:03
@DanielB The post is updated with "various reasons". Of course it's a laptop(I did mentionThe SSD is inside a caddy). I had never heard of GRUB drivers. I searched for how to install drivers for GRUB, but couldn't find anything. Could you please point me in the right direction? Also, I'm looking forward to try FreeBSD boot loader from TrueOS on this. Thanks.
– Small Boy
Jun 12 '17 at 7:39
1
GRUB of course also needs drivers to access disks, just like any other OS. If supported, it can also use INT13 (legacy BIOS access). Try accessing the GRUB command line. Uselsto list disks. Try before and after executinginsmod ahci.
– Daniel B
Jun 12 '17 at 8:15
@DanielB Before issuinginsmod ahci, typinglsdisplayed(hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos1)and after it, it displayed(ahci1) (ahci1,msdos1) (ahci0) (ahci0,msdos7) (ahci0,msdos6) (ahci0,msdos5) (ahci0,msdos1). Clearly, the SSD and it's only partition are recognized besides the HDD and it's partitions. Now what should I do? I tried booting the menu but GRUB complained:Error: There is no 'hd0,msdos7' diskand repeated it 5 times! Thanks for the help :)
– Small Boy
Jun 12 '17 at 23:54
1
I expect (hd*) (which is implemented using INT13) is disabled in grub once you load the AHCI module. As AHCI is the specific hardware, if you talk to it directly and then later ask the bios to talk to it using INT13, then I would anticipate conflict.
– sourcejedi
Jun 17 '17 at 19:14
|
show 3 more comments
There is an HDD and an SSD.
During Lubuntu installation on my HDD, it installed GRUB on HDD and os-prober made a menu entry for the SSD's Windows partition.
But GRUB can't see it on boot:
Error: no such device: 5CD2C8C949DA73C
The menu entry is:
menuentry 'Windows 8 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-5CD2C8C949DA73C' {
insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 5CD2C8C949DA73C
else
search --no-floppy --fs-uuid --set=root 5CD2C8C949DA73C
fi
parttool ${root} hidden-
drivemap -s (hd0) ${root}
chainloader +1
}
Factors to consider:
- This is an MBR system.
- The SSD is inside a caddy.
BIOS recognizes the SSD on POST as my secondary drive:
Fixed Disk 0: HITACHI HTS.........300
Fixed Disk 1: Samsung SSD 850 Evo 120GB
- Every OS and bootable utility including GRUB's os-prober can see the SSD.
- BIOS does not show the SSD in boot options(We're not planning to boot from it.).
Note: Workarounds like "Making the SSD boot-drive" or "Putting the SSD in the primary slot" are not acceptable for various reasons.
UPDATE: Asked about the "various reasons" in the comments: This is a ThinkPad E15. "Making the SSD boot-drive" is simply impossible due to the fact that "BIOS does not show the SSD in boot options" (It's one of the ThinkPads with lack of ultra-bay support, and perhaps because of that, it's designed for not booting a secondary HDD, so despite detecting it on POST as a Fixed Disk, does not show it in boot options. It only trys booting it as a CD-ROM and that doesn't work. Also, one reason for not "Putting the SSD in the primary slot" is, I want shock protection for my HDD but again, this ThinkPad does not support it for a secondary drive according to this site.
linux ubuntu grub
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
There is an HDD and an SSD.
During Lubuntu installation on my HDD, it installed GRUB on HDD and os-prober made a menu entry for the SSD's Windows partition.
But GRUB can't see it on boot:
Error: no such device: 5CD2C8C949DA73C
The menu entry is:
menuentry 'Windows 8 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-5CD2C8C949DA73C' {
insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 5CD2C8C949DA73C
else
search --no-floppy --fs-uuid --set=root 5CD2C8C949DA73C
fi
parttool ${root} hidden-
drivemap -s (hd0) ${root}
chainloader +1
}
Factors to consider:
- This is an MBR system.
- The SSD is inside a caddy.
BIOS recognizes the SSD on POST as my secondary drive:
Fixed Disk 0: HITACHI HTS.........300
Fixed Disk 1: Samsung SSD 850 Evo 120GB
- Every OS and bootable utility including GRUB's os-prober can see the SSD.
- BIOS does not show the SSD in boot options(We're not planning to boot from it.).
Note: Workarounds like "Making the SSD boot-drive" or "Putting the SSD in the primary slot" are not acceptable for various reasons.
UPDATE: Asked about the "various reasons" in the comments: This is a ThinkPad E15. "Making the SSD boot-drive" is simply impossible due to the fact that "BIOS does not show the SSD in boot options" (It's one of the ThinkPads with lack of ultra-bay support, and perhaps because of that, it's designed for not booting a secondary HDD, so despite detecting it on POST as a Fixed Disk, does not show it in boot options. It only trys booting it as a CD-ROM and that doesn't work. Also, one reason for not "Putting the SSD in the primary slot" is, I want shock protection for my HDD but again, this ThinkPad does not support it for a secondary drive according to this site.
linux ubuntu grub
linux ubuntu grub
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
edited Jun 12 '17 at 7:47
Small Boy
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
asked Jun 9 '17 at 23:27
Small BoySmall Boy
5110
5110
1
And what might those “various reasons” be? Is it perhaps a notebook? Is the SSD on a different storage controller? Is GRUB missing drivers?
– Daniel B
Jun 11 '17 at 20:03
@DanielB The post is updated with "various reasons". Of course it's a laptop(I did mentionThe SSD is inside a caddy). I had never heard of GRUB drivers. I searched for how to install drivers for GRUB, but couldn't find anything. Could you please point me in the right direction? Also, I'm looking forward to try FreeBSD boot loader from TrueOS on this. Thanks.
– Small Boy
Jun 12 '17 at 7:39
1
GRUB of course also needs drivers to access disks, just like any other OS. If supported, it can also use INT13 (legacy BIOS access). Try accessing the GRUB command line. Uselsto list disks. Try before and after executinginsmod ahci.
– Daniel B
Jun 12 '17 at 8:15
@DanielB Before issuinginsmod ahci, typinglsdisplayed(hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos1)and after it, it displayed(ahci1) (ahci1,msdos1) (ahci0) (ahci0,msdos7) (ahci0,msdos6) (ahci0,msdos5) (ahci0,msdos1). Clearly, the SSD and it's only partition are recognized besides the HDD and it's partitions. Now what should I do? I tried booting the menu but GRUB complained:Error: There is no 'hd0,msdos7' diskand repeated it 5 times! Thanks for the help :)
– Small Boy
Jun 12 '17 at 23:54
1
I expect (hd*) (which is implemented using INT13) is disabled in grub once you load the AHCI module. As AHCI is the specific hardware, if you talk to it directly and then later ask the bios to talk to it using INT13, then I would anticipate conflict.
– sourcejedi
Jun 17 '17 at 19:14
|
show 3 more comments
1
And what might those “various reasons” be? Is it perhaps a notebook? Is the SSD on a different storage controller? Is GRUB missing drivers?
– Daniel B
Jun 11 '17 at 20:03
@DanielB The post is updated with "various reasons". Of course it's a laptop(I did mentionThe SSD is inside a caddy). I had never heard of GRUB drivers. I searched for how to install drivers for GRUB, but couldn't find anything. Could you please point me in the right direction? Also, I'm looking forward to try FreeBSD boot loader from TrueOS on this. Thanks.
– Small Boy
Jun 12 '17 at 7:39
1
GRUB of course also needs drivers to access disks, just like any other OS. If supported, it can also use INT13 (legacy BIOS access). Try accessing the GRUB command line. Uselsto list disks. Try before and after executinginsmod ahci.
– Daniel B
Jun 12 '17 at 8:15
@DanielB Before issuinginsmod ahci, typinglsdisplayed(hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos1)and after it, it displayed(ahci1) (ahci1,msdos1) (ahci0) (ahci0,msdos7) (ahci0,msdos6) (ahci0,msdos5) (ahci0,msdos1). Clearly, the SSD and it's only partition are recognized besides the HDD and it's partitions. Now what should I do? I tried booting the menu but GRUB complained:Error: There is no 'hd0,msdos7' diskand repeated it 5 times! Thanks for the help :)
– Small Boy
Jun 12 '17 at 23:54
1
I expect (hd*) (which is implemented using INT13) is disabled in grub once you load the AHCI module. As AHCI is the specific hardware, if you talk to it directly and then later ask the bios to talk to it using INT13, then I would anticipate conflict.
– sourcejedi
Jun 17 '17 at 19:14
1
1
And what might those “various reasons” be? Is it perhaps a notebook? Is the SSD on a different storage controller? Is GRUB missing drivers?
– Daniel B
Jun 11 '17 at 20:03
And what might those “various reasons” be? Is it perhaps a notebook? Is the SSD on a different storage controller? Is GRUB missing drivers?
– Daniel B
Jun 11 '17 at 20:03
@DanielB The post is updated with "various reasons". Of course it's a laptop(I did mention
The SSD is inside a caddy). I had never heard of GRUB drivers. I searched for how to install drivers for GRUB, but couldn't find anything. Could you please point me in the right direction? Also, I'm looking forward to try FreeBSD boot loader from TrueOS on this. Thanks.– Small Boy
Jun 12 '17 at 7:39
@DanielB The post is updated with "various reasons". Of course it's a laptop(I did mention
The SSD is inside a caddy). I had never heard of GRUB drivers. I searched for how to install drivers for GRUB, but couldn't find anything. Could you please point me in the right direction? Also, I'm looking forward to try FreeBSD boot loader from TrueOS on this. Thanks.– Small Boy
Jun 12 '17 at 7:39
1
1
GRUB of course also needs drivers to access disks, just like any other OS. If supported, it can also use INT13 (legacy BIOS access). Try accessing the GRUB command line. Use
ls to list disks. Try before and after executing insmod ahci.– Daniel B
Jun 12 '17 at 8:15
GRUB of course also needs drivers to access disks, just like any other OS. If supported, it can also use INT13 (legacy BIOS access). Try accessing the GRUB command line. Use
ls to list disks. Try before and after executing insmod ahci.– Daniel B
Jun 12 '17 at 8:15
@DanielB Before issuing
insmod ahci, typing ls displayed (hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos1) and after it, it displayed (ahci1) (ahci1,msdos1) (ahci0) (ahci0,msdos7) (ahci0,msdos6) (ahci0,msdos5) (ahci0,msdos1). Clearly, the SSD and it's only partition are recognized besides the HDD and it's partitions. Now what should I do? I tried booting the menu but GRUB complained: Error: There is no 'hd0,msdos7' disk and repeated it 5 times! Thanks for the help :)– Small Boy
Jun 12 '17 at 23:54
@DanielB Before issuing
insmod ahci, typing ls displayed (hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos1) and after it, it displayed (ahci1) (ahci1,msdos1) (ahci0) (ahci0,msdos7) (ahci0,msdos6) (ahci0,msdos5) (ahci0,msdos1). Clearly, the SSD and it's only partition are recognized besides the HDD and it's partitions. Now what should I do? I tried booting the menu but GRUB complained: Error: There is no 'hd0,msdos7' disk and repeated it 5 times! Thanks for the help :)– Small Boy
Jun 12 '17 at 23:54
1
1
I expect (hd*) (which is implemented using INT13) is disabled in grub once you load the AHCI module. As AHCI is the specific hardware, if you talk to it directly and then later ask the bios to talk to it using INT13, then I would anticipate conflict.
– sourcejedi
Jun 17 '17 at 19:14
I expect (hd*) (which is implemented using INT13) is disabled in grub once you load the AHCI module. As AHCI is the specific hardware, if you talk to it directly and then later ask the bios to talk to it using INT13, then I would anticipate conflict.
– sourcejedi
Jun 17 '17 at 19:14
|
show 3 more comments
1 Answer
1
active
oldest
votes
I put the SSD in the primary slot (because of giving up) but then I discovered that the HDD Shock Protection feature works when the HDD is in the secondary slot as well!
That is, the information that this site had gave me was incorrect and resulted in so much time being wasted. So let's try things more than relying on some info.
A few days ago I found out that the primary slot has 3.0 GB/s bandwidth and the secondary slot has 1.5 GB/s. So putting the SSD in the secondary slot would really be a miss.
edited Jan 29 at 7:50
Pang
599611
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1217809%2fgrub-cant-see-what-os-prober-found%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
I put the SSD in the primary slot (because of giving up) but then I discovered that the HDD Shock Protection feature works when the HDD is in the secondary slot as well!
That is, the information that this site had gave me was incorrect and resulted in so much time being wasted. So let's try things more than relying on some info.
A few days ago I found out that the primary slot has 3.0 GB/s bandwidth and the secondary slot has 1.5 GB/s. So putting the SSD in the secondary slot would really be a miss.
edited Jan 29 at 7:50
Pang
599611
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
add a comment |
I put the SSD in the primary slot (because of giving up) but then I discovered that the HDD Shock Protection feature works when the HDD is in the secondary slot as well!
That is, the information that this site had gave me was incorrect and resulted in so much time being wasted. So let's try things more than relying on some info.
A few days ago I found out that the primary slot has 3.0 GB/s bandwidth and the secondary slot has 1.5 GB/s. So putting the SSD in the secondary slot would really be a miss.
edited Jan 29 at 7:50
Pang
599611
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
add a comment |
I put the SSD in the primary slot (because of giving up) but then I discovered that the HDD Shock Protection feature works when the HDD is in the secondary slot as well!
That is, the information that this site had gave me was incorrect and resulted in so much time being wasted. So let's try things more than relying on some info.
A few days ago I found out that the primary slot has 3.0 GB/s bandwidth and the secondary slot has 1.5 GB/s. So putting the SSD in the secondary slot would really be a miss.
edited Jan 29 at 7:50
Pang
599611
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
I put the SSD in the primary slot (because of giving up) but then I discovered that the HDD Shock Protection feature works when the HDD is in the secondary slot as well!
That is, the information that this site had gave me was incorrect and resulted in so much time being wasted. So let's try things more than relying on some info.
A few days ago I found out that the primary slot has 3.0 GB/s bandwidth and the secondary slot has 1.5 GB/s. So putting the SSD in the secondary slot would really be a miss.
edited Jan 29 at 7:50
Pang
599611
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
edited Jan 29 at 7:50
Pang
599611
edited Jan 29 at 7:50
Pang
599611
edited Jan 29 at 7:50
Pang
599611
599611
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
answered Sep 25 '17 at 7:50
Small BoySmall Boy
5110
5110
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1217809%2fgrub-cant-see-what-os-prober-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
1
And what might those “various reasons” be? Is it perhaps a notebook? Is the SSD on a different storage controller? Is GRUB missing drivers?
– Daniel B
Jun 11 '17 at 20:03
@DanielB The post is updated with "various reasons". Of course it's a laptop(I did mention
The SSD is inside a caddy). I had never heard of GRUB drivers. I searched for how to install drivers for GRUB, but couldn't find anything. Could you please point me in the right direction? Also, I'm looking forward to try FreeBSD boot loader from TrueOS on this. Thanks.– Small Boy
Jun 12 '17 at 7:39
1
GRUB of course also needs drivers to access disks, just like any other OS. If supported, it can also use INT13 (legacy BIOS access). Try accessing the GRUB command line. Use
lsto list disks. Try before and after executinginsmod ahci.– Daniel B
Jun 12 '17 at 8:15
@DanielB Before issuing
insmod ahci, typinglsdisplayed(hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos1)and after it, it displayed(ahci1) (ahci1,msdos1) (ahci0) (ahci0,msdos7) (ahci0,msdos6) (ahci0,msdos5) (ahci0,msdos1). Clearly, the SSD and it's only partition are recognized besides the HDD and it's partitions. Now what should I do? I tried booting the menu but GRUB complained:Error: There is no 'hd0,msdos7' diskand repeated it 5 times! Thanks for the help :)– Small Boy
Jun 12 '17 at 23:54
1
I expect (hd*) (which is implemented using INT13) is disabled in grub once you load the AHCI module. As AHCI is the specific hardware, if you talk to it directly and then later ask the bios to talk to it using INT13, then I would anticipate conflict.
– sourcejedi
Jun 17 '17 at 19:14