This problem is for my parents computer, I have a 40 GB HDD and an 80 GB HDD the 80 has Win 7 (TM) and the 40 has Xubuntu 9.04. I upgraded Grub to grub 2 and got that all sorted out but when ever I select " Windows Vista (loader)" from the grub 2 menu it says " invalad signature". How would I fix this?
View 3 RepliesI am planning to move my main OS from Windows to Ubuntu (Yeah I am that impressed) but I wish to move windows to my current smaller hard drive until I find all ubuntu replacement programs i can use then eventually eject the windows drive. The problem is has we all know who dual-boot you have to install windows first before ubuntu as the windows mbr is when grub is stored and gets wiped when you install windows.
It must be possible to add windows as secondary OS while keeping / or reinstating grub must it not it surely (eg on 10.4LTS release it would be ok, but if i installed windows vista or 7 on my secondary hardisk it would destroy grub).
I installed karmic, then damn small linux - the DSL's loader would not recognize my xubntu automatically, so I got GRUB 1.97 on xubuntu and it recognized my DSL and added it to the menu with 3 alternative resolution options.
Now, xubuntu starts fine, but when I start DSL in any of the modes, I get the following output:
1. 'vga=normal is deprecated use gfxpayload=text before linux command' comes up in the same font as GRUB menu is displayed - but only for a split second, I had to video it to read it!
2. Uncompressing linux... ok, booting the kernel - similarly, disappears before you can read it, and the computer reboots.
Below are my /etc/default/grub and /boot/grub/grub.cfg.
Does all that mean I want to edit /boot/grub/grub.cfg even though I apparently must not?
NB I have some problems with my hard drive, I have to fdisk it a lot but that's probably because my laptop has a dead BIOS battery - I'm having to fdisk it every time I boot up etc. I'm a bit lost with this to be honest! Anyway, please forget the hard drive note unless you seriously suspect it's at fault for GRUB problems.
Code:
Code:
I'm not consistently able to boot into Ubuntu Lucid on my new dual boot (w/ Win7) setup. Machine is a Dell XPS 1645 laptop. Usually it takes 1-3 tries of hard shut down and restart before the OS starts up. Boot info script results are below. Windows starts up fine everytime. What I usually get is this: Dell startup screen, then Grub2 menu, then after selecting Linux kernal a blinking cursor at upper left of monitor and it just hangs.
View 9 Replies View RelatedI want to set up grub for a dual boot system of xp and vista. The thing is that I have vista installed and would have to install it ance again after setting up XP in order to use the microsoft bootloader. And secondly I slowly want to get into linux...
This is how I tried it: I have four partitions on my HD and want to install the Bootloader on /dev/sda3. I started up the ubuntu live cd, mounted partition3, opened the console and tried this command line which I found in a tutorial
grub-install --root-directory=/media/hda3 --recheck /dev/hda However I get the following error message:
mkdir: cannot create directory '/media/hda3/boot': No such file or directory
I've been all afternoon trying to install Ubuntu Lucid on my fakeRAID 0 configured (2) HDDs and am unable to set GRUB up. The fake RAID setup is provided by Intel Matrix Storage Manager, it is correctly enabled and the BIOS is also correctly set up -- in fact, I've managed to install Windows 7 with no significant hitch. After struggling with partioning the drives (had to follow advice I found on a very helpful guide online [0]), creating the filesystems AND getting Ubuntu's installer to actually do what it is supposed to do, I now cannot seem to set GRUB up. My system, as it stands, is unbootable at all; via live CD only.
This is how the RAID0 dev is partitioned:
Code:
# fdisk -l /dev/mapper/isw_ecdeiihbfi_Volume0
Disk /dev/mapper/isw_ecdeiihbfi_Volume0: 1000.2 GB, 1000210694144 bytes
255 heads, 63 sectors/track, 121602 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disk identifier: 0x6634b2b5 .....
i am trying to change the boot order on the GRUB menu so that the countdown automatically starts on an older kernel. From what i can see all the solutions on the web want me to edit the /boot/grub/menu.lst file. The problem is that i don't have one. Someone also mentioned that if i don't have a menu.lst file then i should look for the grub.conf file. I don't have on of those either. The closest thing in /boot/grub is grub.cfg but that looks nothing like the descriptions i have heard of /boot/grub/menu.lst file
View 5 Replies View Relatedwe have an oracle application server on red hat 4.6 upon booting it comes up with error: attempting boot from hard drive (c GRUB)
View 2 Replies View RelatedI'm running Karmic Server with GRUB2 on a Dell XPS 420. Everything was running fine until I changed 2 BIOS settings in an attempt to make my Virtual Box guests run faster. I turned on SpeedStep and Virtualization, rebooted, and I was slapped in the face with a grub error 15. I can't, in my wildest dreams, imagine how these two settings could cause a problem for GRUB, but they have. To make matters worse, I've set my server up to use Luks encrypted LVMs on soft-RAID. From what I can gather, it seems my only hope is to reinstall GRUB. So, I've tried to follow the Live CD instructions outlined in the following article (adding the necessary steps to mount my RAID volumes and LVMs). [URL]
If I try mounting the root lvm as 'dev/vg-root' on /mnt and the boot partition as 'dev/md0' on /mnt/boot, when I try to run the command $sudo grub-install --root-directory=/mnt/ /dev/md0, I get an errors: grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: error: Embedding is not possible, but this is required when the root device is on a RAID array or LVM volume.
Somewhere in my troubleshooting, I also tried mounting the root lvm as 'dev/mapper/vg-root'. This results in the grub-install error: $sudo grub-install --root-directory=/mnt/ /dev/md0 Invalid device 'dev/md0'
Obviously, neither case fixes the problem. I've been searching and troubleshooting for several hours this evening, and I must have my system operational by Monday morning. That means if I don't have a solution by pretty early tomorrow morning...I'm screwed. A full rebuild will by my only option.
I am busy to do some tests using the Adaptec 1430sa hardware raid controler .I started the setup by generating the raid 1 aray and it worked ok .I did the regular setup of Cent Os 5.5 64 bits all worked ok but the system do not boot .When I start the box it enter the minimal grub screen .I tried to install a first time on the MBR like suggested and how it need to be done for soft raid setup .nd I tried to install it on the first cluster from the boot sequence like possible on second choice
View 2 Replies View RelatedHere is a thought experiment:
1. Copy vmlinuz and initrd.img from isolinux subdir into /boot
2. Adjust grub.conf to boot to that kernel
3. Reboot to setup
4. Format /boot (actually '/' ) during "fresh install"
5. Proceed with the installation-over-network
I see two possible outcomes:
1. The setup fails to reformat the drive, because it is "in use" by boot kernel
2. The partition is not "in use" and the installation succeeds
Why? Old cluster with broken CD-drives, lacking USB, and no separate /boot partition.
I installed 11.04 after Windows 7. when the GRUB boot menu starts up there is an option for Win 7 boot but it will not boot windows. When that option is selected the screen changes colour for 2 seconds and then reverts to the GRUB menu. Ubuntu boots fine.I downloaded the Boot Info Script and ran it, the results are
Code:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================[code].....
after doing an upgrade to 10.4 and updating grub I get this message. how do I address this
[Code]...
I've been using Linux for over a decade, so no need to worry about the obvious. I'm positive that I have my partitions/install correct. What has me baffled is that Fedora 14, which uses GRUB 0.97 (GRUB legacy) - boots Windows flawlessly every single time on the same hardware, but Ubuntu's (or the upstream Debian's) GRUB legacy do not - even though they are based on the same upstream code from the GNU Savannah servers.
No matter what I've tried I cannot get the Debian or Ubuntu version of GRUB/GRUB-legacy to boot any recent Windows 64 beyond XP (Vista or 7). All that it does is resets the computer when Windows attempts to boot, without an error. GRUB is notoriously difficult to compile, so before I try to compile code from RedHat's archives - any thoughts,experiences, similar issues - whatever?
I got ubuntu 10.04 lucid lynx along with windows (dual boot) and using Grub. On my computer, I have my C:/ (programs) and D:/ (data). I've never used my D:/ before that day that I've lost my windows partition on my grub menu. I usually use my D:/ with windows. The first time I used my D:/ to store data with linux, I lost my windows option in my grub menu. I'm not sure what I did wrong but I do want to restore my windows option in my grub menu.
After "fdisk -l",
I checked in /boot/grub and there is no menu.lst to modify. how I can get back my windows option in my grub menu ?
The first is I seem to have 3 GRUB installs. So whilst I update the one from my live session, the change does not appear in the boot up menu. I had installed 10.10 from a CD into a different partition (sda6), but that will not boot, so I have just deleted this and done another grub install and update. The kernel I am using has just been updated from 10.04 to 10.10 too, and it is this that I use and the Grub I have been working on (sda5).
[Code]...
I updated yesterday and now when I start my laptop it goes in to grub rescue mode. I have booted from a 'live cd' and thought I could repair grub from there. In gparted however the partition with ubuntu (sda1) is seen as unknown file system, in terminal when I list the partition table it shows up as FAT16 type. When I try a grub-install it gives this error message:
[Code]....
I have 2 hard disks. sda,sdb
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.
So my computer has ubuntu 9.10 installed 1st and I want to install win 7 in a separate partition. Basically, ubuntu 1st, win 7 later so far from what I learned from search results, grub 2 have problem with win 7 installed later and what was recommended was install win 7 before ubuntu. how ever I do not have the time to start over again because there are too many things to back up or install again. can I simply revert grub 2 to grub 1 again and resolve the problem?
View 7 Replies View RelatedI am running 10.04 and when I installed Nvidia 3d driver the fonts in a non GUI terminal ie. contol-alt-F2 are very large. I used to be able to alter the font size in /boot/grub/menu.lst but cannot do the same in /boot/grub/grub.cfg.
View 6 Replies View RelatedI was wondering, how much hassle would it be to setup a PXE boot so I can boot a machine from the network.
View 9 Replies View RelatedMy problem is this, I decided to try Pardus since I had the disk space available and learned that it never created a entry for Ubuntu 9.10 64-Bit. I have tried many different boot options and have only gotten it to show the first black and white bootsplash but never can continue to boot. Is there a option I am forgetting to add via Pardus's GRUB editor or is it something else?
View 3 Replies View RelatedI'm trying to take my current windows7 (x64) setup and make it into a dual-boot setup with slackware 13.0 (x32) and am hitting a brickwall. I guess I would like to know if I can salvage the situation without formating my windows drive. I fully intend to, but I had hoped to not do it this month. I'd like to get dual boot going so I can master it and acquire all the files/drivers I'll want and then format and do it 100% right next time.
Currently I have windows setup on a 3x 500gb Raid0 onboard array which itself has been flawless. After I shrunk my current partition size to give me about 25gb of free space I proceeded to setup Linux, and I was unable to perform the cfdisk portion for partitioning the array for Linux.
I tried using cfdisk:
/dev/hdx (a1-a3,b1-b3)
/dev/sdx (a1-a3,b1-b3)
I even attempted to locate with: cat proc/partition and tried using cfdisk on every device it located. It always said it was either an unknown partition table and should I start at zero, or bad partition. I was of course too concerned over my windows setup (which has almost 1tb of stuff I have not backed up) to go any further into the unknown.
PS: I have used Slackware before, back at 8.1, 10, and even a very brief interlude at 12.0, this is my first attempt on this computer however with 13.0, it is currently running fine on my laptop and my PS3 (Laptop is even dual booting 7/Slack13. Albeit without raid)
Phenom 9850
M2N-SLI Deluxe (Nvidia AM2)
4x1gb of 1066 kingston hyperX
3x500gb WD Caviar Black Sata2 3.0
I was installing sqeeze i386 on my laptop VOSTRO 1400 and got this the 'grub-pc' package failed to install into /target/. without the GRUB boot loader, the installed system will not boot.
View 3 Replies View Relatedsince i have installed the nvidia drivers i have lost the graphical boot and just had a bar at the bottom of the screen instead. i tried to get the graphical screen back by adding vga=795 to my /boot/grub/grub.conf but when i rebooted not only did i not get the graphical boot or the toolbar at bottom.
i got list of all the drivers and services it is starting with ok next to it. i have also since doing this lost the bit when restarting or shutting down getting the words restarting or shutting down and just get blank screen with flashing cursor. i removed the vga=795 and i still get the list of drivers/services loading.
how do i get the quiet option back. i have checked /boot/grub/grub.conf and it has the quiet in it.i have also tried running update-grub but get message command not found. i have attached the grub.conf file
I've been running openSuse 11.2 for a while on my notebook.Today I turned it off at work and came home. When I tried to turn it on, it boots, shows a black screen written 'GRUB' and then NOTHING. It doesn't complete the boot process.
View 9 Replies View RelatedI've got myself the curious situation where, when I boot the system, I can get grub to start, but it always drops to the prompt.
I can run:configfile /grub/menu.lst
and this brings up the menu with no problems, and from there I can boot the system to either linux or windows. What I don't understand is why it wont go to the menu in the first place?As far as I can tell, grub/Kubuntu got confused when installing, as each of the hd#,# settings in the menu.lst have needed tweaking to let the system boot. (e.g. windows is actually hd0, but the original install had it at hd2. Likewise linux is on hd1, but the menu.lst had it at hd0). I've happily tweaked these to make the system boot, but would appreciate any help in convincing grub to actually load the menu without me having to use the prompt.
A failed upgrade, from disk images, of Fedora 10 to 11 resulted in no GRUB bootloader main menu appearing on bootup (no WIN, no LINUX choices from which to boot). I am booted directly into the GRUB command shell...so, no WIN, no LINUX, nothing. And my understanding of GRUB shell commands is very low.I have 2 hard disks, WIN on the first, LINUX on the second. I believe GRUB Bootloader is on the first disk.Sadly, I have no external install media.An old grub.conf hardcopy indicates that root =/dev/sdb2, root (hd1,0), kernel /vmlinuz....olderversion...(relative to /boot),initrd /initrd...olderversion... (relative to boot). and WINDOWS on (hd0,1), with chainloader +1
I need to somehow get past this grub shell, and re-install/re-instate the grub bootloader, so it can boot normally.What grub command(s) must I use? I've played around with the commands, but with no success.I worry that if I can't resolve this, the whole machine may be useless.
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
I started another thread about this to get help booting into openSUSE after Fedora rewrote my bootloader and deleted all other entries. I managed to fix it but I never did find out why the following commands caused my system to boot to the grub shell instead of the grub menu.
Code:
grub
root (hd0,3)
setup (hd0)
quit
reboot
Can anyone explain to me why these commands caused my system to boot directly to a grub shell? It's as if there were no /boot/grub/menu.lst files for it to use, but after I got everything back to normal, the files were still there.
If it helps, this is how the drive was setup before and now, except Fedora was on /dev/sda4 and has since been deleted.
Code:
Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 263 13316 104856255 83 Linux
/dev/sda3 * 13317 14621 10482412+ 83 Linux