CentOS 5 :: Boot Stuck At Initrd After Reinstalling GRUB?
May 7, 2009
I am using CentOS 5.2 with GRUB booting a software RAID configuration. The first disk is md0 and is mirrored across sda1 and sdb1.I manually re-installed grub using grub-install and the machine will no longer boot off of the HD. The grub menu comes up, I can select my kernel the machine then jumps to loading the initrd and hangs.It will go no further. I have a live DVD that can boot from the HD. If I use that to first boot from the DVD, then specifiy the HD, it shows the same grub menu and then the machine boots fine w/o the initrd hang.I have tried re-installing grub but not been able to get the machine to work again w/o the DVD.
I'm running Debian testing and after a recent software update, suddenly I can no longer boot into my single Linux kernel image anymore. I did look at the software update before I did it and I don't believe that it removed any software packages. When I try to boot into my linux 2.6.26-1-amd64 image, I get the following message from grub:"error: unknown command `initrd'"..The same error appears if I try to boot into single-user mode. I have a Windows XP partition on the same hard disk and I am still able to boot into that from grub. I've searched the net and haven't really found my same problem replicated anywhere. I would imagine that the problem is just that somehow the initrd package got removed in my last software update, but again I don't recall seeing any software that the update planned to remove.
Any thoughts on how I would go about fixing this problem? Since I'm unable to get into Linux at all, I imagine I'll have to use a LiveCD to get in and fix the problem, but I don't know where to begin looking.
I have installed vmlinuz and initrd.gz (squeeze) in /boot/newinstallation and added to Grub the lines:titleNova Instalaçãoroot(hd0,0)kernel/boot/newinstall/vmlinuzinitrd/newinstall/initrd.gzNevertheless, when I choose this option at the grub, it begins to start the kernel vmlinuz and thus restart the system. The installed Debian Lenny boots in a normal way.
I had Windows XP Pro 32 bit and CentOS 5.4 installed on my Dell M6400 laptop and life was wonderful. Until I had to reinstall Windows. In the process, I reformated the C: partition of the drive where the Windows operating system was installed. I was careful NOT to reformat anything else. Now I cannot boot CentOS. The drive that has both the Windows and CentOS still shows the same partitions as were there before I reinstalled Windows, namely:
NTFS (C:) 171.82 GB /boot 102 MB (F:) 60.96 GB
is where my CentOS partition has all of my linux data and apps. I assume /boot should be the boot partition for CentOS I use Acronis OS Selector to show the partitions to boot. Now CentOS doesn't show as an option even if I go through the process of trying to detect a CentOS boot partition using OS Selector. I have researched this in the forums but have not found anything that was of help. There was a thread from someone who had trouble booting Ubuntu on a system with Windows Vista and CentOS but I did not see anything there that looked like it would help in my situation.
I lost power during my Ubuntu update and when I powered back up ubuntu was broken. Now the stupid bit. My hdd was partitioned into 3 bits, vista os, data, and ubuntu. In vista I deleted the ubuntu part and merged it with the data part. Now when I power up my computer it goes straight to a black screen that says... error : no such partition.
grub rescue> I have looked through the forums for an answer to my problem but to no avail. When I put the ubuntu live cd in and turn back on itjust goes to the same screen. I'm a novice to the world of computers and need any help you can offer.
After my last update in my ubuntu, I had a problem. (As almost everytime that I update it) When I select to boot ubuntu, it doesn't work.It shows something like:"GNU GRUB version 1.97"beta 4[ Minimal BASH-like line editing is supported.For the first word, TAB lists possible command completions.Anywhere else TAB lists possible device/file completions] sh:grub> "And I don't know how to make it work.I tried to follow this tutorial:[URL]I got an error message saying that the file couldn't be found. And if I skip it, when I type "boot" the system reboots and comes to the same place I was before. I've also tried to set another partitions like
I was dual-booting XP and Ubuntu 10.10 for a while, but as I never used Ubuntu it was just taking up space, so I figured I'd get rid of it. I used a partitioning tool from inside XP to remove the Ubuntu partition, forgetting that I used GRUB2 every time I booted to select which OS to load. Now when I start my computer I get stuck at the "grub rescue>" screen.After searching for solutions to this problem all of them said to either use the Windows XP CD to fix the Master Boot Record or reinstall Ubuntu, but I dont have my XP CD and there isnt enough room on my hard drive anymore for a Ubuntu install. Is there anything else I can do to fix this?
I accidently deleted my ubuntu partition, and when boot I get this message:GRUB loading.error:unknown filesystemgrub rescue>I can't get into my bios options either... I just see the MSI splash screen and it cuts right to this error message.
I am familiar with linux and have done some managing of servers before. I just tried to install centos 5.5 on a server, but after booting the screen was blank and my monitor said vga mode not supported. I found online to press ctrl+alt+F1, which allows me to see the rest of the boot commands. Then after I was able to see the boot commands it says enabling /etc/fstab swap, but never says ok or gets past that part.
This is a standard install, just like I've done dozens of times before.
Plain vanilla, just installed.
When I boot, I get to the splash screen and it doesn't go into the default selection.
Could this be a Hardware thingy? The reason I ask is because I've had this issue happening with 5.2 on the same machine. I just formatted it completely and installed a fresh 5.3 i386 on it and I get the same behavior.
[root@server ~]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that
I have used CentOS for a while and have never run into this issue. I searched all over and didn't see a similar issue anywhere, I did an install of CentOS as a server (no GUI) with only the base. Partition is /boot ext3, size of 100MB. The rest of the drive is partitioned as / with ext3. This is being done on a CompactFlash card of 32GB in size. The BIOS sees it as an IDE drive.
When the install completes and the system reboots, the grub stops at the grub> prompt. There is no menu for OS options. If I do the following commands: grub>root (hd0,0) grub>kernel /vmlinuz-2.6.18-194.el5 root=LABEL=/ grub>initrd /initrd-2.6.18-194.el5.img grub>boot
When I compile a custom kernel with this command: make-kpkg --initrd kernel_image kernel_headers and then install the .deb, there's no initrd in /boot and I have to create it manually. I've thought that the --initrd option should take care about this, but somehow it doesn't.
It behaves like this for about two years at least (since I've compiled my first kernel). Of course, it's no big deal to create it manually, I was just wondering whether do I do anything wrong or whether should I fill a bug report..
I run alot of Linux running in memory. Mainly by PXE booting a kernel and the entire OS as the "initrd" file.
I have a RHEL6 image running as a VirtualBox guest and the entire OS (minimal) is contained withing 1GB of disk. I wan't to boot the entire /dev/sda1 "/" (its the only partition on the drive, no swap) as the initrd file and run everything from memory. But grub won't let me. So before I try and re-invent the wheel I thought to post here first.
Details. RHEL 6 as guest in VIrtual BOX. configured with 3Gb memory. HD is single partition and known as /dev/sda1.
But the grub windows just freezes. Apparently it doesn't like the fact that I've referenced the entire partition (hd0,0) as the initrd. Any thoughts? Or any better boot loader like SYSLINUX?
BTW, I am not worried about the /etc/fstab mentioning /dev/sda1 at this point, I have a fix for that already. I would like to see grub load up the partition as an initrd.
I had 9.04, then upgraded to 9.10. After screwing it up, it won't boot. Is it possible to just reinstall Ubuntu using the CD? Cause then I would get GRUB 2. I installed kde-desktop, then it failed to boot (I selected KDM) and that somehow screwed it up.
I wasn't thinking at the time, but after I installed Ubuntu 9.10, I installed Xp. Did it the wrong way around, is there anyway to get grub going again, without reinstalling Ubuntu?
I had Ubuntu 10.10 installed on an HP G72 laptop, and I wish to reinstall Win 7. I loaded from the recovery disks that I made before installing Ubuntu and all went fine. At the end, I need to restart. When restarting, I am getting the GRUB rescue prompt with "unknown filesystem." It surprises me that GRUB is still there. How can I get rid of it so I can boot windows?
So I have 2 ide hdds but whenever they are both connected, grub gets stuck at GRUB loading stage 1.5. how can I resolve this problem? both are Maxtors with ext4 fs. primary is 20 gb and secondary 80 gb. Jumpers are set to cable select. Boot order in bios is correct. (primary first, secondary isn't in the list at all)
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
I just upgraded by box from Fedora Core 9 to Centos 5.2. Finally!I have a 500GB SATA drive, it's partitioned into three equal size slices, hda1 through 3. The old Fedora was on hda1, I installed the new Centos on hda3. I instructed the installer to write the MBR to /dev/hda, not /dev/hda3. Fdisk says I have sector 0 unused.First, the system wouldn't boot - it just looped through the BIOS, rebooting over and over again. The BIOS sees the disk, but it never loaded Grub. I tried re-running grub-install /dev/hda, and not I get a Grub Error 17 after stage 1.5 loads.
I can boot from rescue OK, the grub.conf man menu.lst look fine, it's pointing to "root (hd0,2)". It's either the BIOS that can't find the MBR, or the MBR can't find Grub.When I looked at the disk with fdisk after the install, hda1 was still marked bootable, hda3 was not, so I swapped bootable flags but that has not made a difference. I also appended the new grub to the old grub thinking I could get the MBR (if it is there) to load the old grub and thence find the new Centos, but that didn't work either.Mobo is an old Shuttle AK35.Any ideas? Did I mess up by not telling the system to put the MBR on /dev/hda3? Is there a way to fix this without reinstalling?
Ive installed centos freebsd and mandriva but i want to manage grub from my centos and y create successfully a boot load for freebds. But for mandriva it just doesnt work... so how can a create a boot load entry for mandriva from grub centos?
3 partitions (in order): Windows 7, CentOS and shared data partition.
I need to increase the size of the Windows 7 partition (c:windowswinsxs seems to be something not easily remedied).
GParted didn't work in moving things around (bad sector) so I wiped out its partition (# 2 out of 3) and I was able to increase the size of the Windows 7 partition (I can reinstall CentOS easily and not much work lost).
Except ... no more grub menu (unsurprising). This incantation does allow me to boot into Windows 7.
Is there any way of rebuilding the grub menu short of reinstalling CentOS (5.5)?
My Windows installation had a problem and I had to reinstall Windows. The problem now is that I need to get grub back so that I can boot into Fedora. I'm using a Fedora 11 LiveCD I had sitting around. Here are the results of the command most of the way down the first page:
Quote:
Disk /dev/sda: 250.0 GB, 250059350016 bytes 240 heads, 63 sectors/track, 32301 cylinders Units = cylinders of 15120 * 512 = 7741440 bytes Disk identifier: 0x000f09ab
[Code].....
I'm tempted to try the grub-install command quoted near the end of the thread, but I don't want to do anything that will hose the system.
I recently had to reinstall Windows XP and as usual it destroyed my grub setup. I have done this before, so I simply booted from a live CD and typed this in the terminal:
Now, the problem with it this time is that in the past in these situations I had only Ubuntu Feisty and Windows XP installed on my machine. But I have installed Ubuntu 9.04 on a separate partition (retaining the old 7.04 installation separately) since I last had to reinstall XP. Doing the above procedure restores my grub sttings to my pre-9.04 installation (i.e. I only get Ubuntu 7.04 and Windows XP in the grub menu).
I have triple boot machine Windows 7 + Ubuntu + Mac OS X in a single HDD.
Windows 7 -- /dev/sda1 Ubuntu 10.10 -- /dev/sda2 (In same Partition grub 2.0) Mac Snow Leopard -- /dev/sda3
I have installed GRUB 2.0 in same partition where current ubuntu is installed ie /dev/sda2 and basically Windwos Boot manager is installed within MBR.. & I have added GRUB 2.0 and Mac OSX entry into windows boot manger with some freeware from windows 7. So practically when I start my computer First Windows Boot manager comes up and asks me which OS to start first. I set up this type of installation with the thought that when grub 2.0 is not installed within MBR, I can format the whole /dev/sda2 partition without any difficulty and reinstalled any future release distro of ubuntu. So is it practically possible? If I format /dev/sda2 and reinstall new ubuntu release there.. Old grub won't affect the installation of new one.
