Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had been using Xubuntu 9.10 successfully for some time. Recently, however, I tried to boot Xubuntu, and instead of reaching the login screen, a "GRUB" interface appeared.
The title was "GNU GRUB VERSION 1.97~beta4"
Below that, there were a few instructions describing the use of the Tab key and a blank command line interface beginning with "sh:grub7".
Before this started occurring, my computer would turn on and then display a menu to choose the OS. If I selected Xubuntu, a few lines would flash by, and the login screen would appear. My computer is a Dell XPS M1530 laptop. The operating systems installed are Windows Vista Ultimate and Xubuntu 9.10. The Xubuntu was installed using a Wubi installation.
As far as I remember, I did not make any changes that may have caused this. The only significant event that did occur was a power outage, but my computer was not plugged in nor on at this time.
If everything works normally, how would I boot Wubi Xubuntu from the GRUB interface? Are there any other solutions to this problem?
I can't give too much advice, but when the grub menu comes up, hit e and look at the boot settings, this might just be a case of an update gone wrong, in there make sure that your boot options look as they should something like:
I tried pressing 'e' at every stage and screen of turning on my computer, but it had no effect. I don't seem to be reaching a GRUB menu, just an interface.
Pressing 'set' in the command line of the GRUB interface listed some information, including a "kernel: hd0,3".
I tried entering "boot hd0,3" and was told that no kernel existed.
Follow the grub2 link above - then go to the link in post 2 of that reference. It is quite a detailed article - and at the end has some troubleshooting notes.
I have no experience with wubi, so can't help you there.
Last edited by syg00; 05-24-2010 at 10:39 PM.
Reason: Deleted comment - hadn't read post closely enough
To boot using grub2 ubuntu from the grub command line
Quote:
root (hd0,1)
linux /vmlinuz root=/dev/sda?
initrd /initrd.img
boot
I don't know what drive or partition your ubuntu is on but start from zero for drives and start from one for partition for the numbering in the root line ( maybe root (hd0,3)) and replace the ? (maybe sda3) with the actual partition number, should allow you to boot into your ubuntu installation then you can reinstall grub.
Last edited by colorpurple21859; 05-25-2010 at 09:35 AM.
i encountered the same problem, when i hit the e it says record fail=1 if [ -n ${have_grubenv} ]; then save_env recordfail; fi set quite=1
insmod ext2
set root =(hd0, 1)
search --no floppy --fs-uuid --set 1574800c-0386-45f9-a627-449a559d\0ea
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=1574800c-0386-45f9-a\
627-449a599d70ea ro quite splash
initrd /boot,initrd.img-2.6.31-14-generic
i've read your reply, and it has different root=UUID number, is it neccessary to change to the one that you replied to the other? then after, what will i do?
thank you so much. hope you will help me with my problem. thanks
I've looked through the article for all references to Wubi.
I tried
Code:
set root=(loop0)
linux /vmlinuz root=/dev/sda3 loop=/ubuntu/disks/root.disk ro
initrd /initrd.img
boot
as suggested in the article, but I always get something like "no disk found" after the second command is entered.
When I enter ls, I get the drives (hd0), (hd0,1), (hd0,2), (hd0,3), and (hd0,5). I've tried sda, sda1, sda2, sda3, and sda5, but I always get the same response.
Are there any other suggestions? This is Xubuntu on a Wubi installation.
If I do choose to reinstall Xubuntu, is there anything I could do to prevent this issue from reoccurring?
My suggestion is to not use wubi. I saw a reference from a Ubuntu dev that wubi would be dropped - issues with grub2 IIRC.
I did try and find it later, but couldn't - maybe they changed their mind. I generally use dual boot, but if I have to use virtualisation on Windoze (which I do a fair bit) I use VirtualBox and install Linux (and OpenSolaris) there.
most ubuntu distros use grub2 with gfxmode so instead of pressing E for edit....press ESCape to escape graphical mode and enter text mode....then press E to edit
2) they have a nasty habit of using hiddenmenu as well.
this is best solved by using a live cd to mount your /boot partition using root powers
Then part 1 test.... just edit /boot/grub/grub.cfg to put a # in front of hiddenmenu....report if you don't see one pls
reboot and if that works....search each file of /etc/default/grub or /etc/grub.d
I do not use Ubuntu so am only guessing
Cannot understand why it worked ok without alteration unless it was an update/upgrade problem, especially if done on the gui.
Perhaps, boot into a live ubuntu, drop to init 1, 'umount' the relevant partition,run fsck, then reboot and use the (still inserted) to boot from the first hard drive- providing that is where you linux is. Otherwise, after running fsck, remove that disk and use System rescue disk or supergrub to reinstall the MBR. This is only a suggestion.
I'm beginning to think that I wont be able to recover my system. I'll reinstall it using a proper partition instead of Wubi. Is there any way at all to get my files back? In Windows Explorer, I can find the folder that Wubi created. I assume that all my files are somehow contained in the "install" folder, which only contains one file: a large .fuse_hidden0000000400000001 file.
yeah well looks like its more of a wubi issue than a grub2 issue. I re-read syg00 post on grub2 and wubi.
IMHO you have only windows installed to the partition....then your windows bootloader has an option to boot a single file on the windows partition that is a "virtual" linux http://linux.about.com/od/dist/gr/dstwubi.htm
The problem is....grub2 is NOT installed in MBR or in the partition boot record so normal command modes will fail IMHO.
2) I don't blame you for being conservative and trying out linux. Instead of wubi can I suggest you download the windows version of virutualbox and then you can boot up windows...open virtualbox....install any linux distro you like into it....and play with it?
3) other suggestions depending on your risk profile....get rid of windows....install linux....install linux virtualbox and run windows from that if you need something?
b) wipe the drive with a linux cd....partition it for real....install windows....into partition 1 = c.....install linux into partition 2 ....partition 3 is windows swapfile and partition 4 is linux swap.....assuming you have a msdos partition table and not GPT
When linux installs....install grub2 into MBR and let it chainload to your windows bootloader.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.