Setup of my server:
5 x 2TB samsung and WD discs.
1 x 1TB for operating system.
Mainboard DG45ID
I installed Debian Squeeze on the 1TB disc, everything goes fine. As soon as I attach the 2TB discs the computer boots and just says GRUB with a cursor. If I detach the 2TB discs everything is fine again?
i wiped my entire hard drive that had xp as its only OS. I freshly installed a Windows 7 ultimate and everything went perfectly. I then decided to install 10.4. I split the partitions correctly (i had experience doing this already with my laptop, which has xp/10.4). Ubuntu 10.4 install went flawlessly, except for one thing. Now when i boot up the pc, it goes straight into 10.4. I have tried holding shift during the start up to force the boot menu, and it just shows the Ubuntu 10.4 OS as choices. Any clue what i could do to make Win7 appear in the boot menu?
View 9 Replies View RelatedI'm installing Ubuntu server 10.04 LTS in several machines with identical hardware using clonezilla.Every thing is ok except than wen starting a cloned machine, grub waits the user to make a selection to boot from.The hard disk has 3 partition:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 14 112423+ 83 Linux
/dev/sda2 15 1059 8393962+ 82 Linux swap / Solaris[code].....
how to do to start automaticaly? This is the content of grub configuration file (/boot/grub/grub.cfg)[code]...........
I have Ubuntu 9.10, PuppyLinux431 and Windows XP on a Toshiba laptop. I like Ubuntu, but the speed of PuppyLinux is addictive, so that was my default boot until I upgraded Ubuntu which included an upgrade to Grub2.
My problem: Grub2 doesn't recognise PuppyLinux. Using information from [url] I have made an executable file named 07_Puppy in /etc/grub.d and did update-grub from root. Still no luck. I can boot PuppyLinux from the grub command line using the following commands:
Just before grub displays the boot menu, I think I see a very brief message about a syntax error, but it's gone before I can read it.
Here is the contents of my grub.cfg:
Quote:
Why Grub2 doesn't see Puppy and let me boot it from the menu?
I've just installed the 64 bit edition of 9.10 on my workstation. My raid drivers worked without any custom installation, which is very impressive! I am however having a problem installing grub2. I boot to the live CD, run the install process, resize and partition my free space as an ext4 primary partition with mount point /. Everything installs except grub, so I'm always booting in to windows.This seems to be a bit off as I've never had this occur with dual booting before.
View 9 Replies View RelatedI recently upgraded to 10.04, all went well. Except now Windows 7 does not load. It shows up on the grub menu, but when selected just hangs with blinking cursor?
[code]...
i initilally installed ubuntu 9.10 then installed windows 7 ,then i recovered grub2 using livecd as told in the post [URL] i did "sudo update-grub" and got windows 7 menu entry but when i select that entry windows 7 does not load but the grub2 is reloaded again.
i cant boot to windows 7.
Windows 7 have 100 mb partition "System Reserved" the grub2 points to that partition but still windows 7 not loaded.
sudo fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3c3a81f5
[Code]....
I went through so many post but I haven't found the proper answer yet hope you have an Idea1. Grub2 saves only Linux OS as last selected no Windows OS2.It is possible to boot into a cdrom (drive)?
View 2 Replies View RelatedMy new job requires I use Windows and as such I put a second HDD in my laptop for the purposes of Window/Work The issue is that Windows will not install on this second disc (Windows cannot create partition or install to disc). I got around this by installing Windows to the first disc, then the second then putting Slackware back on the first but then I suffer the "Bootmgr cannot be found, press ctrl + alt + delete to restart".
I am using Lilo and I have never really had an issue dual booting them on the same disc (Admittedly over a year ago) but it is of the utmost important I have them on separate Discs. Has anyone encountered this and/or know a way around?
Ubuntu 10.10 doesn't boot at all. The liveCD only boots once every like 30 attempts, installing from liveCD froze, but the Alternate CD worked and installed ubuntu. Now when I try to boot into it using GRUB, it freezes at the beginning of the boot process.With normal boot it freezes at line: Starting AppArmor profiles Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox.With recovery mode it freezes even before showing me anything
A little kinda like the liveCD, if I try like 30 times, it might manage to boot once in normal mode.That line keeps on repeating, the the xxx.xxx integer changes each time, and this goes on forever.I tried removing my floppy drive, but it didn't help.I tried to boot with fd0=noprobeThe one time it booted, when I restarted, it froze while trying to restart.
Ubuntu 9.10 64bit
Grub2 doesn't have menu.lst. If I want to remove on the booting screen, e.g. Code: Ubuntu, linux 2.6.27-2-generic Ubuntu, linux 2.6.27-2-generic (single-user mode) How to do it?
So, as the title says Windows 7 doesn't show up in GRUB2's selection menu, but it does show my Windows XP professional option that I had before Linux and then reinstalled. After searching very long for the problem in Linux and GRUB2 I decided to boot into XP, witch gave me the option for Windows 7 or older versions of Windows -> so I eventually can boot to it! So here is the real question: How can I make an entry for Windows 7 and for Windows XP? This is because I'd like to use a theme for GRUB and it would be to stupid to make GRUB look nice if I then come to a stupid screen of the Windows loader!
View 9 Replies View RelatedI installed windows 7 after I installed linux. I got grub reinstalled but windows doesnt show up in the grup menu. So I run in linux sudo update-grub, but this doesnt find my windows system.
Here's my fdisk -l
Code:
Device Boot Start End Blocks Id System
/dev/sda1 1 8511 68358144 83 Linux
/dev/sda2 8511 8572 487425 5 Extended
[code]....
I recently installed Ubuntu 9.10 onto my second hard drive, and now I can't boot into Vista (installed on hard drive #1). Grub2 just doesn't seem to be recognizing that there is a Windows Vista installation on the first hard drive.
I followed this guide (with Fabien's changes) because it seemed like they were having the exact same problem. But after rebooting, Vista is still not showing in the GRUB menu. In fact, the GRUB menu doesn't even show up unless I press Shift because it thinks that Ubuntu is the only OS installed on my computer.
My results with boot_info_script:
Code:
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks for (UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd)/boot/grub.
=> Windows is installed in the MBR of /dev/sdb sda1:
[Code]....
When I was installing Ubuntu to HD2 (the 500gb one), I got a peculiar message saying that Windows was installed on it. There wasn't anything on HD2 though, because Windows Vista was most definitely installed on HD1.
However, if I chose to overwrite HD1 with Ubuntu, the message wouldn't come up. It seemed like the installer was confused as to which hard drive actually held my Windows Vista install.
I have installed Lucid Lynx more than a dozen times in the past thirty hours and I've almost got it working with RAID. The current problem is with /dev/md0 not existing when grub2 tries to access it. When I boot from the alternate CD in rescue mode, Ubuntu sees /dev/md0 as a software RAID array and I can access the files accordingly. When I boot from the grub2 bootloader, it sits for a while before spitting out "Gave up waiting for root device" and tossing me into the initramfs shell where I can see that /dev/md0 doesn't (yet) exist. What can I change within grub2's configuration to inspire it to start /dev/md0 before trying to mount it?
View 6 Replies View RelatedWorking on a quad boot system. Two Karmic installs (I find I tend to hork one every once in a while by playing too much, so having a backup around is nice), windows 7, and Snow Leopard. I got everything up and running, except I had Leopard installed instead of snow leopard. At that time, I had the following:
sda1->win 7
sda2->leopard
sda5->karmic 1
sda6->karmic 2
(others for swap / extended / etc)
Grub2 detected everything just fine, made a real nice grub.cfg file and away I went.Now, I've made a change. Snow Leopard required GUID partitions and I had my stuff all set up as MBR and was /not/ about to reformat and start over. So I added a second drive, sdb.
Now, I can boot to that drive independently. Fine.I can boot to sda just fine and go to either Ubuntu install or windows just fine. Great. Grub2 finds Mac OSX on /dev/sdb2. Awesome (sdb1 is a fat32 bootloader for hackintosh reasons). It not only doesn't update grub.cfg, it leaves the old /dev/sda2 listing for my old Leopard install ... whose partition I deleted. It isn't visible anymore.
Code:
> sudo update-grub
Generating grub.cfg ...
Found Debian background: radar.png
[code]....
But nothing after Ubuntu 9.10 on /dev/sda6 shows up in grub.cfg? I'm at a loss. Any ideas how to get it to populate? I'd rather not hack grub.cfg and have to rebuild it by hand every once in a while especially as grub was fine with finding it.
After much struggling with the server (the one referenced in "shifty, shifty drive letters"), I realized that the problem has nothing to do with drive letters at all. The problem is GRUB2, or some way in which it is misconfigured.
To recap:
Ubuntu Server 9.10
/dev/sda solid-state Sandisk (swap)
/dev/sdb1, /dev/sdb2, /dev/sdb3 2 HW RAID0 SCSI (boot, /, tmp)
/dev/sdc - /dev/sdz 24 one-TB SATA drives
I kept getting "device not found" from GRUB2 when trying to boot. The SATA drives are disconnectable from the front of the chassis. So I disconnected each and every one of them and powered the machine up. To my shock, the machine booted into Linux and it was up and running! It seems that when the 24 SATA drives are plugged in, then GRUB2 can NOT see /dev/sdb. Instead, it sees /dev/sda and fifteen of the one-TB drives (and one floppy drive, whatever that is).
I tried deleting /dev/sdc through /dev/sdz from /boot/grub/device.map, but that didn't work. I also tried plugging in only HALF of of the SATA drives. When the system tried to boot in this state, then GRUB2 just hung. I noticed that the blue LEDs on the front of the (plugged-in) SATA drives blinked on and off in sequence, as if GRUB2 was scanning them. I watched this for about 3 minutes before I got impatient.Is there a maximum number of drives in GRUB2? Does GRUB2 hate SCSI if it detects a whiff of SATA? What's going on?
I recently got a netbook and setup as dual boot between win7 starter and 9.10 (64bit). Win 7 starter is not impressive so i want to nuke it and give the space all to my /USR partion. I am comfortable working with Gparted and assume that i can launch using my gparted live usb and delete the windows partion and then resize the /usr partion.
what changes do i need to make w/ Grub2? I would prefer not to see the Grub menu at all and have it load right the main kernel if possible. Also, if this is possible is there a way to get to the Grub menu during boot should i need to select a different kernel?
After installing karmic with Grub2 I am unable to boot into Archlinux partition. Grub2 has removed the last line of the Archlinux boot stanza! It used to read:-
[Code]....
Following the Grub2 tutorials I have tried editing /etc/grub.d/40_custom as follows:-
[Code]....
But no luck. Only way into Archlinux is to get into the edit shell and manually add the missing line and remove other stuff not needed. I have spent hours trying to resolve this issue and I am fairly p----d off
I was yesterday evening experimenting inserting a script into /boot/grub/grub.cfg. Well I broke grub.cfg and had to try to boot from a grub2 prompt.I have separate /boot and / partitions on /dev/sda1 and /dev/sda2 respectively.Working out the correct syntax for the boot to work was a little complicated, so I thought it would be useful to post the correct procedure here, in case anyone else has the same set up that I do (separate /boot and / partitions)At the grub prompt code:
grub> set prefix=(hd0,1)/grub
grub> insmod linux
grub> set root=(hd0,2)
[code].....
I've set up a triple boot system (Ubuntu Karmic, Windows Vista and OSX86 -- a patched OS X which works on a PC) on a Dell 9200 (C2D 2.13 GHz, 4GB RAM, nVidia G210). I sue Grub2 as the bootloader and update-grub picks up OS X and it boots without any problem.
However, although when booting OS X using its own Darwin bootloader, I can apply the boot option "Graphics Mode"="1680x1050x32" to ensure that I get the screen resolution that I want, when OS X boots from Grub2, the only resolution available is 1024x768 which is disappointing. I have tried adding gfxmode=1650x1050x32 to the OS X section of /boot/grub/grub.cfg in Ubuntu but this does nothing.
I'm attempting to triple boot Windows 7, Mac OS X, and Ubuntu 11.04 on non-Mac hardware. Chameleon is my primary bootloader, which is supposed to chainboot into grub2, but all I get when I choose the Linux boot option is a black screen with blinking cursor. If I try to boot Ubuntu while holding shift, I get the word GRUB, followed by a space and a blinking cursor. grub2 is installed to the Ubuntu partition, and attempts to reinstall it there or to the MBR from a LiveCD result in errors. The MBR and GPT partition tables are synchronized. How do I go about making Ubuntu bootable, without breaking my other two operating systems (or at least leaving them recoverable)?
I built a new desktop computer.The goal was to triple boot the system with Windows 7, Mac OS X Snow Leopard, and Ubuntu 11.04. This endeavor has been significantly more complicated than I originally expected, but with the of a forum-goer at InsanelyMac.com, I've managed to get pretty far with a complex installation process. I've attempted to get Ubuntu running using two methods, neither of them achieving what I'm hoping. Both methods follow.
In the first method, I install Mac OS X using a specially designed install CD that boots into the Snow Leopard installation DVD. The disk is partitioned to have a FAT partition, followed by a Mac OS X journaled partition, ending in a second FAT partition. Mac OS is then installed to the second partition. The Windows boot CD is then used to format the first FAT partition as NTFS, which Windows 7 is then installed to.
As I'm sure you know, this installs Windows Boot Manager. Then I boot into OS X using the boot CD mentioned earlier, and install Chameleon, a bootloader specifically designed for Hackintosh systems, and (supposedly) capable of booting into all three operating systems I'm trying to work with. Finally, I divide and reformat the remaining FAT partition into an ext4 partition and a swap partition, and install Ubuntu to that ext4 partition, with the bootloader installed to the same partition. This will break the Windows bootloader, as now the MBR and GPT tables are no longer syncronized. Ubuntu is also unbootable; attempting to chainload into grub2 leaves me at a black screen with a blinking cursor. The former problem is solved by booting into a LiveCD and installing and running gptsync. Windows is now bootable, but Ubuntu remains in 'limbo'.
The second method I attempted is very similar, but deviates in the last few steps. After installing Windows, I instead install Ubuntu 10.04 LTS, as I thought I might have fewer bootloader issues with that distribution (don't ask why; it was a lucky hunch).This breaks Windows Boot Manager, but this time grub2 throws me into the grub> prompt.I can boot into Ubuntu just fine using the set root/linux/initrd/boot commands, but my motherboard's Ethernet port is not detected by the OS, so I can't directly download and run gptsync. Once I do manage to run it, though, Windows is then also repaired.
Unfortunately, since I can't access the Internet, I can't do a distribution upgrade that way. Trying to upgrade from the recent release's LiveCD...well...doesn't upgrade, just overwrites. So I get the same black screen with blinking cursor problem. I've tried reinstalling grub2 through a LiveCD using grub-install both using the --root-directory flag and the chroot method.
System specifications:
Intel Core i7 (LGA1155)
Corsair VENGEANCE 4x4GB DDR3
[code]...
I'm as big a fan of Linux as Linus Torvalds himself but it's things like this that help to keep Linux from becoming mainstream. I mean, how would I ever explain the need for the following procedure to a non-techie type, recent or prospective Ubuntu convert? The following is not a question, as I have finally resolved the issue but is more of a rant, I guess you could say. The reasons that I decided to post it are:
1) To hopefully help someone else experiencing this issue.
2) To point out the need for significant improvement in the area of editing partitions under Ubuntu Linux.
3) To vent my spleen.
[Code]...
I have /dev/sda with Squeeze and Win 7 on it, and /dev/sdb with Squeeze. I've managed to get Grub 2 to boot from /dev/sdb1, but only by disabling /dev/sda from being a boot option in the BIOS. When it is available to boot, and lower priority than /dev/sdb, grub does not recognize the UUIds of the disks. So, I've disabled it for now and can boot from /dev/sdb no problems. Trouble is I cannot get Win7 to boot. Grub prints:
error: no such device: f0903a3a903a081c
error: invalid signature
When I boot into Squeeze and run 'blkid' I can see that:
/dev/sda1: LABEL="System Reserved" UUID="F0903A3A903A081C" TYPE="ntfs"
The Grub entry for Win 7 is:
menuentry "Windows 7 (loader) (on /dev/sda1)" {
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f0903a3a903a081c
chainloader +1
}
I don't understand how Grub 2 cannot recognize the UUIds. Can Grub 2 to be made to work with volume labels or just plain old /dev/... descriptions? Maybe I should give grub-legacy a go.
Trying to get gentoo to play nice with grub2. failing so far. here's what i got in my 40custom file (doens't work):
menuentry "Gentoo-Linux" {
set root (hd0,7)
kernel /boot/kernel-2.6.31-gentoo-r6
initrd=/bin/bb
}
when i run grub-update btw it finds gentoo by itself but doesn't add it to the menu.
I installed Ubuntu9.10 on a USB hard drive attached to my laptop. Laptop has pre-installed XP in the in-built hard-drive. Point to be noted is that my hard-drive is protected via encryption software called Pointsec.
The installation of Ubuntu on the USB hard drive went through fine and I'm able to boot Ubuntu from it.
But now the problem is, GRUB2 fails to detect the Windows XP installation.
Can someone tell me how I can force GRUB2 to boot Windows XP from hd0,0?
The GRUB1 way of configuring /etc/grub/menu.lst does NOT seem to work with GRUB2.
I tend to update stuff slower than most - I'm still using Hardy and I probably won't upgrade to Lucid until June-ish. I wanted to test drive GRUB2 so I upgraded following instructions here:When I chainloaded GRUB2, I got a menu that only contained Ubuntu; my Windows Vista bootloader entry had disappeared. I couldn't find a sample "40_custom" entry to modify when I tried to create an entry for Vista myself. Had no problem booting into Ubuntu and I could still boot Vista from the old menu. Spent about 20 minutes on it, then I gave up and reinstalled legacy GRUB.
View 9 Replies View RelatedI have a Asus EEE PC 1005P which I installed a Command-line system on using the Alternate Installer CD of Ubuntu Lucid Lynx. I do not have (or want) the X Window System installed.
I want to change my console screen resolution (not inside X) to 1024x600. But it isn't reported when I use vbeinfo inside grub2:
Code:
grub> vbeinfo
VBE info: version: 3.0 OEM software rev: 1.0
total memory: 8128 KiB
List of compatible video modes:
[code]....
I'm having an odd dual-boot problem. Briefly, I can't boot Windows XP from its entry on the GRUB2 menu. If I set the disk order in BIOS so that the machine boots off the drive with Windows XP, XP starts normally. However, if I boot off the Ubuntu drive, which brings up the GRUB2 menu, choosing the "Windows 7 loader" option (why it says Windows 7 when there's only Windows XP is another question!) just makes my system reboot.
It appears there's some problem with the way GRUB2 attempts to start Windows XP. I'm also wondering why GRUB2 thinks it sees the Windows 7 loader. There shouldn't be any Windows 7 anything anywhere. I once had a Windows 7 RC install on the same disk as Windows XP, but I wiped the Windows 7 system partition and reallocated its space as just another NTFS partition. FWIW, GRUB2 is installed on the MBR of the disk containing my Ubuntu install. Windows XP has a different drive all to itself.
I upgraded a while back to Windows 7. I run two separate HDDs, with debian on sda and windows on sdb.Everything worked fine, up until i upgraded to windows 7. The installer forced me to unplug sda and make sdb primary. After installing I repositioned the HDDs and was stuck with a "NTLDR is Missing" messageAfter removing the search -fs--uuid tag from grub.cfg, Windows 7 booted for a good 0.5 sec and then rebooted. All that flashed was the "Starting Windows" page. I see similar bugs reported in the launchpad, but nothing that directly parallels this Here's my windows entry in grub.cfg:
Code:
menuentry "Microsoft Windows 7 Ultimate (on /dev/sdb1)" {
insmod ntfs
[code]....