Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 have recently installed SuSe linux on my seccond hard drive, therfore i have microsoft on one and linux on the other, until now i have had no problems with grub. but unfortunately i have little experience with the coding...
There is a possibility that the partion that SuSe was on was damaged.
This is the message that i am receiving when i start up my computer.
GNU GRUB version 0.95 (639k lower / 1045696k upper memory)
[Minimal BASH-like line editing is supported. For the first work, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device filename.]
grub>
I receive this almost immediately after my intel screen, through this i am able to enter the bios.
Grub has a find command in the command line. Find your kernel and ramdisk and boot manually
find /boot/vmlinuz
(should return something like (hd0,0))
root (hd?,?)
find /etc/inittab
kernel /boot/vmlinuz root=/dev/hd?? (add 1 to numbering so that hd0,0 would be hda1)
initrd /boot/initrd
boot
(This should enable you to boot, you will then need to check your menu.lst and fix the problem. It will need the same settings as you typed in to boot.)
that seams logical but i think i have deleted the whole linux partion, (this is how my comp is set up i have 2 hard drives the first one is completely microsoft and the first half of the seccond one is un partioned, the other half of the seccond one had the 2 SUSe partions)
Might I suggest that you burn a cd with a live distro (like knoppix) and then use
Code:
fdisk -l /dev/hda
or
fdisk -l /dev/hdb
to see what partitions you have installed on your harddrives. You should then be able to use this information to do what gerardt suggested to allow you to boot. If you have deleted the partition then you could try looking for a partition rescue tool (I'm afraid I don't know any) or re-install if there is nothing important to rescue.
Distribution: Redhat Linux 8 & 9, Fedora Core 2, XP
Posts: 301
Rep:
i had the same problem with Redhat 9...
i had to boot manually everytime i restart the server...
I can't seem to fix the problem for some reason, my grub.conf looks fine, I did this in grub prompt when i logged into the server:
I am not sure but you can try the following-
boot from the linux cd and type at the boot prompt
boot: linux rescue
after it loads the kernel and takes you to the shell prompt type the following set of commands-
sh# chroot /mnt/sysimage
sh# grub -install /dev/hda
sh# exit
sh# exit
the system will reboot and after that the grub will be mounted again.
im also had a trouble with grub. i had erase redhat 9 on my partition with win2k and whaen i boot i see the grub prompt luckily somebody thought me how to boot win2k using grub. my problem is how can i erase grub? ty
Thanks for the help but it came too late i tried using microsoft cd and rewrote partition tables and it went downhill for there.
But i managed to get rid of it and then i got into microsoft setup and deleted both hd's and installed microsoft on the seccond one so i ran a program called eData and just unerased all my files off C: i can gladly say through this experience i have decided to never try to install a linux thing again and ill just stick with good old fun and fixable microsoft.
I probably have less experince than you with Linux installations.You described exactly my situation.I had Windows ME and Suse 9.2 in a dual boot situation.
I then had problems with Suse not booting.I tried the repair procedure but not successfully.
I then decided that since I had Suse on Dvd I would remove the Linux partitions,using 'Partition Magic' from Windows,and then start again.
However when I came to reboot I had the 'Grub' problem that you so accurately described.
My solution was to Boot using an ME boot disc, and then at the prompt type 'Fdisk /mbr' with a space between Fdisk and mbr..
Windows ME then booted correctly and I could the reinstall Suse 9.2 and all in the garden was beutiful again.
If you are using Windows XP get to a command prompt and type 'fixmbr', without the quotes of course.
Yeah that is what i did, but another person told me to enter fixboot and fixmbr, from the xp cd. and my partions were totally screwed on both drives, so, yeah after that i kinda lost control of the situation and said screw it.
Distribution: Redhat Linux 8 & 9, Fedora Core 2, XP
Posts: 301
Rep:
Nowsure about suse but i reckon it's pretty much the same for most linux distros. Always install windows first then linux, if not windows will overwrite the MBR and you won't be able to load Linux again. Of course there are steps to recover linux but when i was a newbie, i'd say screw it as well
Maybe you can google for "linux +xp dualboot" or something like that...
If you use fixboot and fixbmr, you can boot into your windows but not into your linux anymore. To boot into your linux again, I'd say try the linux boot CD method mentioned by gaganjain... I didn't use grub-install though, instead i went to grub prompt and did this (mine's Redhat 9 so grub's in /sbin):
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.