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.
After having repaired my Windows it re-wrote MBR where I had had GRUB sector for booting both Linux and Windows. I tried to repair GRUB, run grub-install and it restored GRUB. But then I found that for some unknown reasons my /boot folder didn't have 'vmlinux' and 'initrd.img' (although they must have been there before as I had used GRUB without problems). By then I loaded my RedHat 9.0 from rescue diskette. I copied these files from floppy into boot partition and started the loading process from command line:
At stage 3 it stopped completely. It just didn't see initrd.img. I tried 'find' command but GRUB didn't find it again. I created initrd.img again by 'mkinitrd' but it gave the same result. So far I can't tune my GRUB and am forced to use the rescue diskette. My question is... you must have already guessed it!
I'm feeling this wont help but I will try it, thanks.
I've got a question here - does it matter that my initrd/img file is called like this, without the kernel number like it was before. It still completely strange to me that GRUB shell doesn't see this file whilst it does all other ones.
I have two 80 gig harddrives
on one I have Gentoo and on the other I have Fedora
after installing Gentoo it loaded a new grub.conf file and since
i forgot to write down my settings for booting Fedora I played hell
getting them back (Mostly cause im a complete noob to linux)
But I did get them
My problem was a little bit better cause i'm running two linux des
you have linux and windows problem with that is you can't
boot windows and then open up your old grub.conf file and see your old settings
thats what i did i booted Gentoo then mounted my second harddrive
that had Fedroa on it and was able to view my old grub.conf file
I don't know what kernel you were using but maybe this will help
if your were using this one
Distribution: Home: Fedora Core 1, Mepis RC4, Red Hat 6.2. Work: Fedora Core 1&2, Mandrake 9.0.
Posts: 99
Rep:
I screwed my grub.conf in RH 9 just two days ago, and my home computer became a boat anchor. Luckily I had a copy of Morphix (live cd distro) lying around, so I booted it, mounted hda5 did vi /boot/grub/grub.conf and was able to repair it. Morphix is a great cd rescue for Linux if you need one...
It's not a question of 'grub.conf' file, I do have it and it stopps when proceeding to initrd.img, so it doesn't change a thing.
You can easily boot from a rescue diskette if you set in your BIOS the first boot sequence to Floppy and then boot your system on the hard drive. Thanks for the link, I see there are dozens of live CD linuxes already, I personally use Knoppix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.