Insmod error in grub: symbol not found:grub_realidt
I have a dual boot PC with Windows 7 and Ubuntu. I upgraded from 12.04 to 12.10 and then to 13.04 and since then I have not been able to boot because the PC goes into grub rescue with the error "File not found".
I have tried the following steps:
set prefix=(hd0,msdos5)/usr/lib/grub/i386-pc
set root=(hd0,msdos5)
insmod linux
I get error:
symbol not found : 'grub_realidt'.
if I do insmod normal, I get error
symbol not found : 'grub_disk_dev_list'
I have two partitions containing linux file system: (hd0,msdos5) and (hd0,msdos6). They were mountpoints for / and /boot respectively.
I have searched for this error, and found some "solved" threads. But all of them are using Live USB to get in grub prompt. I don't have access to one, and was hoping to be able to solve the issue without a flash drive.
Please help...
Thanks in advance.
boot grub2 dual-boot grubrescue
add a comment |
I have a dual boot PC with Windows 7 and Ubuntu. I upgraded from 12.04 to 12.10 and then to 13.04 and since then I have not been able to boot because the PC goes into grub rescue with the error "File not found".
I have tried the following steps:
set prefix=(hd0,msdos5)/usr/lib/grub/i386-pc
set root=(hd0,msdos5)
insmod linux
I get error:
symbol not found : 'grub_realidt'.
if I do insmod normal, I get error
symbol not found : 'grub_disk_dev_list'
I have two partitions containing linux file system: (hd0,msdos5) and (hd0,msdos6). They were mountpoints for / and /boot respectively.
I have searched for this error, and found some "solved" threads. But all of them are using Live USB to get in grub prompt. I don't have access to one, and was hoping to be able to solve the issue without a flash drive.
Please help...
Thanks in advance.
boot grub2 dual-boot grubrescue
what is shown when you dols (hd0,msdos5)/
andls (hd0,msdos6)/
?
– Rinzwind
Apr 24 '13 at 10:33
ls (hd0,msdos5)/ shows /boot /home vmlinuz initrd.img ls (hd0,msdos6)/ shows /grub lost+found and many generic image files
– stranger_anon
Apr 24 '13 at 10:48
add a comment |
I have a dual boot PC with Windows 7 and Ubuntu. I upgraded from 12.04 to 12.10 and then to 13.04 and since then I have not been able to boot because the PC goes into grub rescue with the error "File not found".
I have tried the following steps:
set prefix=(hd0,msdos5)/usr/lib/grub/i386-pc
set root=(hd0,msdos5)
insmod linux
I get error:
symbol not found : 'grub_realidt'.
if I do insmod normal, I get error
symbol not found : 'grub_disk_dev_list'
I have two partitions containing linux file system: (hd0,msdos5) and (hd0,msdos6). They were mountpoints for / and /boot respectively.
I have searched for this error, and found some "solved" threads. But all of them are using Live USB to get in grub prompt. I don't have access to one, and was hoping to be able to solve the issue without a flash drive.
Please help...
Thanks in advance.
boot grub2 dual-boot grubrescue
I have a dual boot PC with Windows 7 and Ubuntu. I upgraded from 12.04 to 12.10 and then to 13.04 and since then I have not been able to boot because the PC goes into grub rescue with the error "File not found".
I have tried the following steps:
set prefix=(hd0,msdos5)/usr/lib/grub/i386-pc
set root=(hd0,msdos5)
insmod linux
I get error:
symbol not found : 'grub_realidt'.
if I do insmod normal, I get error
symbol not found : 'grub_disk_dev_list'
I have two partitions containing linux file system: (hd0,msdos5) and (hd0,msdos6). They were mountpoints for / and /boot respectively.
I have searched for this error, and found some "solved" threads. But all of them are using Live USB to get in grub prompt. I don't have access to one, and was hoping to be able to solve the issue without a flash drive.
Please help...
Thanks in advance.
boot grub2 dual-boot grubrescue
boot grub2 dual-boot grubrescue
asked Apr 24 '13 at 10:07
stranger_anon
1522517
1522517
what is shown when you dols (hd0,msdos5)/
andls (hd0,msdos6)/
?
– Rinzwind
Apr 24 '13 at 10:33
ls (hd0,msdos5)/ shows /boot /home vmlinuz initrd.img ls (hd0,msdos6)/ shows /grub lost+found and many generic image files
– stranger_anon
Apr 24 '13 at 10:48
add a comment |
what is shown when you dols (hd0,msdos5)/
andls (hd0,msdos6)/
?
– Rinzwind
Apr 24 '13 at 10:33
ls (hd0,msdos5)/ shows /boot /home vmlinuz initrd.img ls (hd0,msdos6)/ shows /grub lost+found and many generic image files
– stranger_anon
Apr 24 '13 at 10:48
what is shown when you do
ls (hd0,msdos5)/
and ls (hd0,msdos6)/
?– Rinzwind
Apr 24 '13 at 10:33
what is shown when you do
ls (hd0,msdos5)/
and ls (hd0,msdos6)/
?– Rinzwind
Apr 24 '13 at 10:33
ls (hd0,msdos5)/ shows /boot /home vmlinuz initrd.img ls (hd0,msdos6)/ shows /grub lost+found and many generic image files
– stranger_anon
Apr 24 '13 at 10:48
ls (hd0,msdos5)/ shows /boot /home vmlinuz initrd.img ls (hd0,msdos6)/ shows /grub lost+found and many generic image files
– stranger_anon
Apr 24 '13 at 10:48
add a comment |
1 Answer
1
active
oldest
votes
From Troubleshooting Preparation it should be possible to fix this from command line. But the commands I found are a bit different than you have in your question. So...
Do a
ls (hd0,msdos5)/
ls (hd0,msdos6)/
If you see
grub
then do aset prefix="(hd0,msdos5)/grub"
where 5 needs to be changed to correct number.
If you see
boot
then do a
set prefix="(hd0,msdos5)/boot/grub"
set root="(hd0,msdos5)"
where 5 needs to be changed to correct number.
After changing prefix you need to do a
insmod normal
normal
and reboot.
set prefix="(hd0,msdos5)/grub" doesn't work since my *.mod files are not present in this directory for some reason. So, insmod gives file not found error.
– stranger_anon
Apr 24 '13 at 10:50
This is the only method I know and I am afraid you will need a live cd...
– Rinzwind
Apr 24 '13 at 11:32
add a comment |
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
});
}
});
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%2faskubuntu.com%2fquestions%2f284898%2finsmod-error-in-grub-symbol-not-foundgrub-realidt%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
From Troubleshooting Preparation it should be possible to fix this from command line. But the commands I found are a bit different than you have in your question. So...
Do a
ls (hd0,msdos5)/
ls (hd0,msdos6)/
If you see
grub
then do aset prefix="(hd0,msdos5)/grub"
where 5 needs to be changed to correct number.
If you see
boot
then do a
set prefix="(hd0,msdos5)/boot/grub"
set root="(hd0,msdos5)"
where 5 needs to be changed to correct number.
After changing prefix you need to do a
insmod normal
normal
and reboot.
set prefix="(hd0,msdos5)/grub" doesn't work since my *.mod files are not present in this directory for some reason. So, insmod gives file not found error.
– stranger_anon
Apr 24 '13 at 10:50
This is the only method I know and I am afraid you will need a live cd...
– Rinzwind
Apr 24 '13 at 11:32
add a comment |
From Troubleshooting Preparation it should be possible to fix this from command line. But the commands I found are a bit different than you have in your question. So...
Do a
ls (hd0,msdos5)/
ls (hd0,msdos6)/
If you see
grub
then do aset prefix="(hd0,msdos5)/grub"
where 5 needs to be changed to correct number.
If you see
boot
then do a
set prefix="(hd0,msdos5)/boot/grub"
set root="(hd0,msdos5)"
where 5 needs to be changed to correct number.
After changing prefix you need to do a
insmod normal
normal
and reboot.
set prefix="(hd0,msdos5)/grub" doesn't work since my *.mod files are not present in this directory for some reason. So, insmod gives file not found error.
– stranger_anon
Apr 24 '13 at 10:50
This is the only method I know and I am afraid you will need a live cd...
– Rinzwind
Apr 24 '13 at 11:32
add a comment |
From Troubleshooting Preparation it should be possible to fix this from command line. But the commands I found are a bit different than you have in your question. So...
Do a
ls (hd0,msdos5)/
ls (hd0,msdos6)/
If you see
grub
then do aset prefix="(hd0,msdos5)/grub"
where 5 needs to be changed to correct number.
If you see
boot
then do a
set prefix="(hd0,msdos5)/boot/grub"
set root="(hd0,msdos5)"
where 5 needs to be changed to correct number.
After changing prefix you need to do a
insmod normal
normal
and reboot.
From Troubleshooting Preparation it should be possible to fix this from command line. But the commands I found are a bit different than you have in your question. So...
Do a
ls (hd0,msdos5)/
ls (hd0,msdos6)/
If you see
grub
then do aset prefix="(hd0,msdos5)/grub"
where 5 needs to be changed to correct number.
If you see
boot
then do a
set prefix="(hd0,msdos5)/boot/grub"
set root="(hd0,msdos5)"
where 5 needs to be changed to correct number.
After changing prefix you need to do a
insmod normal
normal
and reboot.
answered Apr 24 '13 at 10:39
Rinzwind
204k28388523
204k28388523
set prefix="(hd0,msdos5)/grub" doesn't work since my *.mod files are not present in this directory for some reason. So, insmod gives file not found error.
– stranger_anon
Apr 24 '13 at 10:50
This is the only method I know and I am afraid you will need a live cd...
– Rinzwind
Apr 24 '13 at 11:32
add a comment |
set prefix="(hd0,msdos5)/grub" doesn't work since my *.mod files are not present in this directory for some reason. So, insmod gives file not found error.
– stranger_anon
Apr 24 '13 at 10:50
This is the only method I know and I am afraid you will need a live cd...
– Rinzwind
Apr 24 '13 at 11:32
set prefix="(hd0,msdos5)/grub" doesn't work since my *.mod files are not present in this directory for some reason. So, insmod gives file not found error.
– stranger_anon
Apr 24 '13 at 10:50
set prefix="(hd0,msdos5)/grub" doesn't work since my *.mod files are not present in this directory for some reason. So, insmod gives file not found error.
– stranger_anon
Apr 24 '13 at 10:50
This is the only method I know and I am afraid you will need a live cd...
– Rinzwind
Apr 24 '13 at 11:32
This is the only method I know and I am afraid you will need a live cd...
– Rinzwind
Apr 24 '13 at 11:32
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2faskubuntu.com%2fquestions%2f284898%2finsmod-error-in-grub-symbol-not-foundgrub-realidt%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
what is shown when you do
ls (hd0,msdos5)/
andls (hd0,msdos6)/
?– Rinzwind
Apr 24 '13 at 10:33
ls (hd0,msdos5)/ shows /boot /home vmlinuz initrd.img ls (hd0,msdos6)/ shows /grub lost+found and many generic image files
– stranger_anon
Apr 24 '13 at 10:48