tag:blogger.com,1999:blog-5432566687488141671.post3947170935338528467..comments2024-03-27T21:48:13.424-07:00Comments on Linux Grandma: GRUB2 and chroots, dammit!Valoriehttp://www.blogger.com/profile/08390727972738204487noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-5432566687488141671.post-55536412504043431782011-05-07T16:17:13.646-07:002011-05-07T16:17:13.646-07:00I'm glad to say that KDE has been putting some...I'm glad to say that KDE has been putting some work into this. See http://ksmanis.wordpress.com/2011/05/07/recovering-grub-the-easy-way/ for more details. :-)Valoriehttps://www.blogger.com/profile/08390727972738204487noreply@blogger.comtag:blogger.com,1999:blog-5432566687488141671.post-62578001006517323922010-12-02T18:39:19.223-08:002010-12-02T18:39:19.223-08:00Unfortunately I can't confirm either way, at t...Unfortunately I can't confirm either way, at this late date.Valoriehttps://www.blogger.com/profile/08390727972738204487noreply@blogger.comtag:blogger.com,1999:blog-5432566687488141671.post-73346195506018744272010-11-29T02:14:07.884-08:002010-11-29T02:14:07.884-08:00I was the one who filed the referenced bug report,...I was the one who filed the referenced bug report, and as stated in the bug status it has in fact been fixed. You are experiencing something different (with similar symptoms).<br /><br />That error means that grub wasn't actually installed to the drive you're booting from (more technically, the embedded core.img doesn't match the modules in /boot/grub). This can be caused by many different circumstances. If you could run boot info script as explained here: http://ubuntuforums.org/showthread.php?t=1291280<br />and post the RESULTS.txt along with the output of "debconf-show grub-pc" I can probably tell you what is happening in your case. It's important that you do find the root cause, as running grub-install is only a temporary fix, and without fixing the root cause you will likely get this problem again the next time you do a major upgrade.<br /><br />As for the comment @ https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/comments/20<br /><br />That user, to put it bluntly, has no idea what he is talking about. What he says is the problem is in no way related to bug and shows a fundamental misunderstanding of how bootloaders work.<br /><br />I tried to explain this but eventually gave up as arguing in bug reports is not appropriate or productive. Please don't help spread this misinformation.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5432566687488141671.post-49881428696515363722010-11-28T09:05:04.793-08:002010-11-28T09:05:04.793-08:00Also, simply running 'sudo grub-setup /dev/sda...Also, simply running 'sudo grub-setup /dev/sda' will store up problems for later. The correct fix is 'sudo dpkg-reconfigure grub-pc', and tell it to install to /dev/sda when you get to the relevant dialog.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5432566687488141671.post-15427685826607105042010-11-28T08:58:34.937-08:002010-11-28T08:58:34.937-08:00See my blog post for a full explanation of what...See <a href="http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-06-21-grub2-boot-problems.html" rel="nofollow">my blog post</a> for a full explanation of what's going on here. The bug comment you found is actually a very unhelpful one, from a commenter who has a bee in his bonnet about one particular thing; I've tried to persuade him that he has the wrong end of the stick, but with no luck. <a href="https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/630529" rel="nofollow">Bug 630529</a> is closer to the mark, at least if I'm right in guessing that you were installing from a USB stick.<br /><br />You didn't say what version of Ubuntu you were installing. Perhaps you could contact me by e-mail (cjwatson at ubuntu.com) so that I can make sure I have all the facts straight?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5432566687488141671.post-82665238644784421952010-10-30T04:35:00.058-07:002010-10-30T04:35:00.058-07:00there is another way for solving this using superg...there is another way for solving this using supergrub 2 which is a 1.44 MB download from supergrubdisk website. Burn it to a CD or USB and boot the media supergrub 2 can search and locate the misplaced grub and boot from that so that you are booted to a functioning linux system so that you can fix grub from there.<br />I posted my experience using this in my blog you can find more details there.Jsankarhttps://www.blogger.com/profile/07490096243707160472noreply@blogger.comtag:blogger.com,1999:blog-5432566687488141671.post-43412114130526671162010-10-15T19:48:47.330-07:002010-10-15T19:48:47.330-07:00I've been running Linux since 1995, adminning ...I've been running Linux since 1995, adminning Unix professionally since a few years later, and have used Ubuntu since before the releases went in alphabetical order. And I ran in to the same problem. So don't worry much about inexperience being to blame for this specific thing. :)dannysauerhttps://www.blogger.com/profile/15869815405771212914noreply@blogger.com