Software :: Update-grub Installing On Ram Disk Instead Of Hda?
May 30, 2009
Trouble shooting a grub install after moving an resizing partitions and install winxp along side a stable Ubuntu 8.04 system.I found that all directions I followed do their thing, however, grub keeps creating menu.lst on the ubuntu ramdisk that is created from the liveCD. I keep thinking it has found the real /boot/grub directory but that is never the one updated.
Just finished installing F14 with RAID1 setup for 2 hdd (SATA''s). Entire drives are mirrored, including SWAP. As I had done in the past, I was planning on installing grub on MBR of 2nd hdd. In prep for this I did the following to locate the grub setup files:
grub> find /grub/stage1 find /grub/stage1 (hd0,1)
[code]....
I was surprised, expected to get (hd0,0) & (hd1,0), not (hd0,1) & (hd1,1)
running "fdisk -l" I get:
Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors Units = sectors of 1 * 512 = 512 bytes
[code]....
MBR is the first 512 bytes of the drive. Each partition has a boot sector. In my case grub stage 1 is on 2nd partition of sda & 2nd partition of sdb. What i dont understand is how grub stage 1 can be on sda2 & sdb2, since I am assuming that sda1 & sdb1 would be the first partitions of the drives & therefore contain the MBR's. Maybe this might be because sda1 & sdb1 are SWAP partitions?
I'm using Debian 4.0 Etch (AMD64) with some programs from the testing area. It was installed on a IDE hard disk, and the troubles started when I changed the disk to a SATA one.My system had two hard disks (hda and hdb) and two optical drives (hdc and hdd).Now, the hard drives are sda and hda, and the optical drives remains as hdc and hdd.After the disk change, it didn't work because all references in menu.lst were still pointing at hda. I changed to sda and everything works fine... until next kernel update.Every time the kernel is updated, grub changes all references to hda, so Linux don't boot until I edit menu.lst. I've also changed /boot/grub/device.map, but it doesn't work.
Is it possible to install GRUB in the MBR of the only bootable disk in the system, but load configuration and images from another disk?Basically I want to install GRUB on /dev/sda, but menu and images will be under /dev/sdb2.Note: /dev/sdb is not bootable.
I'm just slightly confused here, but... what the? Why does installing grub-doc remove BOTH grub-pc, and grub-common? So basically it seems like by installing grub-doc, I have uninstalled grub totally (yes, it is still there as the bootloader, but i have no way of updating it now!) from my system. What's the conflict between grub-doc and grub-pc, such that grub-pc has to be removed?
I have xp/fc8 on an older ide drive and just installed a new sata 1T and planned to put fc10 on it but in the process I killed my fc8 installation. I told the installer that the other disks were off limits but it was somewhat confusing at the bootloader page. So, I suspect that I told it boot off the fc8 disk. If that is the case is there a way to restore the fc8 install by somehow rescuing the /boot partition on the fc8 disk?
I know nothing about this at all. I have never programmed a computer.. I loaned my tower to a friend who put this on ...now i have it back and cant get to my windows 98. all i get each time i boot is ...
GRUB loading ... error:no such disk grub recover>
I have tried ubuntu sec 8.4 recover mode and all i get is unreconized command.. i do not know how to set anything.. i have no disks for this not even the orginal windows recover disk.. is their anything i can do to get win to run as it use to??
If I use the super grub disk I can get to my ubuntu partition otherwise my windows partition boots automatically. I spent over an hour in the community documentation using the live cd to reinstall grub and nothing has fixed it. I think that grub is installed and the windows bootloader is just taking precedence.
I have an old BIOS (only 149 GB detected in 160 GB drive). I have installed very few OS as a result - Windows in first 80 GB , 2 distros (20 GB each) in next 40 MB which is within the 149 GB. On issue of "update-grub" grub seems to detect all OS and generates grub.cfg. But on boot , one distro does not appear in the menu.
I was unaware of the difficulties of installing and booting Ubuntu from the "onboard raid" that the NVIDIA nForce chipsets provide. However, I've managed to get it working reliably with one single caveat:
When update-grub builds the grub.cfg, it refers to all of my partitions as follows:
Code: menuentry 'Ubuntu, with Linux 2.6.35-27-generic' --class ubuntu --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 set root='(/dev/mapper/nvidia_caifaefg,msdos5)'
[Code]...
So I'm guessing that the whole nvidia_blah,msdos5 is because of that. However, it doesn't seem to explain why Grub would THINK that would work and it in fact does not work. That's the biggest source of confusion on my part.
My questions are as follows: First off, because as an IT person I want to know: Why does this sort of change work? What does changing that device name change in GRUB's behavior? Is there a setting in /etc/default/grub that would change the way it's naming these RAID devices? Is there a value for this setting that would give me the device names that work, as explained above?
If there is no setting change I can make in /etc/default/grub, could I add a sed command on to the end of update-grub or can I make a modification to one of the scripts in /etc/grub.d? What sort of change would be recommended? How would I preserve this change through later package upgrades that would possibly rewrite these files?
In sda, I have 4 partitions, and I have windows 7 in one of the extended partitions [not in the primary partition].
In sdb, I have 3 partitions. 2 for storage, and 1 10GB drive for Ubuntu. Again, Ubuntu is not of a primary partition.
I had ubuntu 10.04 running on that for a long time. However, I wanted to reinstall ubuntu and use 10.10.This is what I did EXACTLY:Booted from Ubuntu install CD
Chose advanced istall
Selected sdb3 for Ubuntu
I installed GRUB2 on the SAME partition as Ubuntu aka sdb3 Installed then rebooted
I can boot into Ubuntu fine, but whenever I select Windows 7 bootloader from the GRUB menu, the screen goes black, and my PC reboots.
Boot Info:
Code: Boot Info Script 0.55 dated February 15th, 2010 [code]....
ls: reading directory sda6/: Input/output error
I have tried the testdisk/update-grub method, but it didn't work.
As the title says i updated my system which then needed a reboot. I also installed Mixxx djing software to try it out. So i thought id just restart the system. Usually when i boot into my desktop wireless automatically can connect to my router but not this time, wired only for now... i know theres tons of wireless issue threads but some more experienced users will be able to get straight to the point and run through some diagnostics with me.
after installing Ubuntu on one WD 500 GB hard disk and after making mistake and pasting wrong code into Terminal:my OTHER WD 500 GB hard disk that was also in the system (I guess it was "hd1") - died.The problem must be, I guess, I typed wrong code: "hd1,1" instead of "hd0,0".)500 GB (NTFS) of data was on that other (non-Ubuntu) hard disk, and now I can not access it anymore. While booting, system gives "Hard Disk Error" warning and stops.One again: I installed Ubuntu od one hard disk and at the end of instalation I pasted wrong code for GRUB, giving address of another hard disk. Now that other hard disk has error and will not work
Ran the updater, went to boot to Win7 to use Photoshop and realized that the grub menu was gone. Ubuntu boots by default now. I tried running "sudo update-grub" at a virtual terminal and while it listed the various linux kernels ok, it then got caught in a loop spitting out some crazy looking errors. I rebooted and Ubuntu came up fine. I tried running "sudo update-grub" again from the gnome terminal and it hangs the whole computer for a few minutes and finally gives me this:
I've been trying change the default OS in GRUB. I changed the value for GRUB_DEFAULT in etc/default/grub. However, when I run update-grub, I get the following error:
and I rebooted and grub menu not coming now. I have a dual boot with Win7. Ubuntu 10.04 is installed with WUBI. I can run WIN7 but can't run Ubuntu now.
After certain system-wide changes, like kernels updates, I obtain grub prompt on restart. However, if I put the hard drive into another computer (b), it boots up fine. Since, however, I use the present computer (a) regularly, I only use b to purge and reinstall grub using the chroot method. However, doing so every time is time consuming; and I cannot change anything in the defaults and run update-grub without obtaining a grub prompt on restart. How do I fix this?
I have a sata 320 gb with mandriva linux 2009.1 on it.And it is what curently atached to my cpu. It is shown as 'sda' in the partition table.I also have another 40gb hard disk with windows xp installed on it.It is shown as 'hda' in the partition table . Now what i want to do is attach this 40gb hard disk to my pc and configure grub on my 320gb hard disk('sda') so as to boot windows xp(which is residing on the second hard disk,'hda')Can anyone tell me if what im doing is feasible or not? If it is feasible,can anyone suggest me how to get it working. I know i just need to add 2-3 lines to my grub.conf, but dont know what exactly i need to write.
I had a dual boot (windows 7 + debian), both of them installed in my internal hard disk, with the GRUB in it. I have recently installed a second linux distro (mint), but I put it in an external hard disk. Now the GRUB allows me to boot any of the three operating systems, but I need the external disk to do it. It seems that after the mint installation the GRUB is now working from the external disk (if the external disk is not connected, the machine does not boot.) �Is there a way to change the location of the GRUB, to the internal hard disk of my laptop?
Opensuse 11.4 seems to be creating problems with booting from USB devices. (I have read in a couple places that people are having similar problems.)
Every time I try to boot from a different live USB image, I see a GRUB screen flash and the hard disk starts to boot up. The only live image I have had success with booting was another OpenSuse 11.4, then I got the options to install or run live. I was thinking of just wiping the hard disk and seeing if that made a difference. Can I get into the grub limited command line, can i format from here? Is some other way of installing over the WAN from inside the Suse OS?
I installed Debian squeeze amd64 (using LVM with ext4 for /, /home, and ext2 for /boot). This is on a whole hdd on its own. Before I installed it, I have win7 on it. There is also another hdd with winxp. The dual boot loader is in the hdd. After I installed Debian, grub 1.98 was installed. After reboot, grub says "welcome", and after 10 seconds, it says "error: no such disk". It went on to display the menu with a choice of my debian and MS windows.
There does not seem to be any effect of this "error:no such disk". However, after I chose Debian to boot, gnome comes on, and I typed in the username and password. The screen goes blank for about 30 seconds before my desk top comes on.
I have 2 questions:
1. How do I fix my grub "error:no such disk" message? 2. Is there something wrong with a 30 seconds delay for the desktop to show after typing username and password, and if so, what can be done?
I am dual booting XP and ubuntu, and everytime i want to go to XP through GRUB, and every time a Windows Disk Check apears. How can i stop this? I've set my hard drive partions to 50/50 (20GB on each side)so could that be the problem?
I burned a Fedora ISO onto a CD and I love it. Now, I want to add it as a dual-boot to my hard disk. I divided Drive C into two (formatted) partitions one labeled Linux.During an attemped installation, I was able to find (thru "edit") the partition called "Linux." But one of the next questions threw me: it asked for a "mount point."I have no idea what that means (and yes I have readthe guide onthis site).
ACTUALLY... what I need to do is simply install into a partition I already set up.I don't find an option for that within the Fedora installation menu.I have 20 years of experience with Windows and try to keep up with everything, but Linux is totally new to me, so I don't understand the terminology.I also have been trying to find how to create a dual-boot situation from the hard disk, where XP is still my default (for now, at least).
Okay I want to install Ubuntu Studio but sense the file is 1.7 gigs can I somehowbut half on or a 1/3 on disk the next part on another and so on. If so how?
I am completly new to Linux and managed to download slackware 13.1 iso and burn it to disk 1 and 2.I installed disk 1 and set the laptop up fine but it could not find disk 2. I can burn again but do i need to burn in a certain format or as an iso? also i do not know how to get linux to read a cd or mount it?
We had a server failure this morning because grub was throwing error 15 (file not found). We discovered that the disk had changed names from hd0,0 to hd1,0. Making the appropriate replacements in menu.lst fixed the problem, but I'm still wondering what could have caused the spontaneous name change.
here are some other possibly related tidbits: * the server had been down because of a power loss, but it is behind a UPS so i doubt there is any electrical damage * eth0 also temporarily failed but the system failed over to eth1
My current theory is that when the bios was configuring the hardware the loss of eth0 shuffled around the addresses of the remaining hardware on the pci bus, which somehow caused the hd0/hd1 confusion. The problem is that everything i've read [URL] says that the drive assignment should be based on the way the disk is connected to the motherboard (which in this case didn't change)