Jay_E
February 20th, 2013, 10:44 AM
Greetings.
I installed Ubuntu 12.04-2 from a DVD
(ubuntu-12.04.2-desktop-amd64.iso)
The DVD booted OK.
After the install - where it said it was finished and it was time to boot from the Hard Drive, grub failed.
It said something like (I didn't write it down at the time.):
Grub Rescue > Ubuntu 12.04-2 fail boot
I started to reading the posts and suspected an UEFI problem.
For general background, I read:
http://www.zdnet.com/ubuntu-linux-adopts-new-uefi-boot-problem-approach-7000004648/
and
https://help.ubuntu.com/community/UEFI
Anyway. I'm stumped.
This is a new system. It never had any windows on it.
I am trying to get an Radeon HD 7750 to work and have installed both
Debian 6.06 and ubuntu-12.10-desktop-amd64.iso
Both of these booted OK. I had wiped all partitions out and started over each time.
Then I tried Ubuntu 12.04-2 in a dual boot with the Debian -
by taking the install option to install Ubuntu side-by-side with Debian.
That did not work. I *really* wish I had written the exact error message.
It was along the lines that grub could not find the partition.
So I wiped all partitions and started over with the Ubuntu 12.04-2 install.
This time I used the easy install method so I could go eat dinner without answering a lot of install questions.
This is where I get the Grub Fail message.
the Ubuntu 12.04-2 did not have a Rescue option in the menu,
just ( paraphrase)
- try it
- install it
- memory test
I tried the "Try it" option to see if I could fix it.
No Go. That version of GParted said it needed 'gpart'.
I couldn't get gpart.
After reading more posts, I tried to boot with BIOS set with full UEFI enabled.
Got a new error message this time:
The current BIOS setting do [sic] not fully support the boot device.
Click OK to enter the BIOS setup.
Go to Advanced > Boot > CSM Parameters and adjust the CSM
(Compatibility Support Module) settings to enable the boot device.
OK. did this.
Changed Launch CSM
From: Enabled
To: Disabled
The Bios screen had these explanations:
[Enabled] : For better compatibility, enable the CSM to fully support the
non-UEFI driver add-on devices or the Windows UEFI mode.
[Disabled] : Disable the CSM to fully support the Windows Security Update and Security Boot.
OK. I'm confused. But no matter. Try something and see if it works....
Saved the settings and tried to boot the HD.
A new error!
A different BIOS display..
Here is the info written from the screen... :-)
American Megatrends
AMIBIOS (C) 2012 American Megatrends, Inc.
ASUS Sabretooth 990FX R2.0.ACPI BIOS Revision 0906
CPU AMD FX(tm) -8150 Eight-core processor .....
....
The VGA card is not supported by the UEFI driver.
CSM (...) settings have been changed for better compatibility
Just great. :-(
Then the option to procede, or go back and change the settings.
I tried to procede.
That went to the 1st message about adjusting the CSM to enable the boot device.
OK. I'm writing this down so I won't have to go back; do it over to answer a question later - of what I did try.
OK.
Rest CSM back to auto.
[This BIOS is labelled ASUS UEFI mBIOS Utility - EZ Mode (or Advanced mode)
Launch CSM: Enabled
{Then 4 more settings show up.}
I set these to:
Boot Device Control : UEFI and Legacy OpRom
Boot from Network devices : Legacy OpRom first
Boot from Storage Devices : Both, UEFI first
Boot from PVIe/PCI Expansion Devices : UEFI driver first
save and reboot.
{insert a drum roll while I go get a beer.] :popcorn:
A different error message.
Grub loading
Welcome to GRUB!
error: invalid arch independent ELF magic.
Entering rescue mode...
grub rescue>
Beer in hand I went googling for grub rescue commands.
Ah-hah. Another post said:
"Sometimes, when you change the partition layout of your HD, the number of the partition which contains GRUB2 changes. Let's assume we installed GRUB2 from (hd0,7) or /dev/sda7, which is a logical partition inside an extended partition. Then we deleted /dev/sda5 and /dev/sda6, our /dev/sda7 became /dev/sda5. Now when the "MBR part" is looking for the rest of the program, it can't find it in (hd0,7) since such partition doesn't exist anymore. In this case, instead of showing the usual GRUB2 menu, you are being dropped to some sort of command line which is called GRUB rescue."
YES - So isn't Ubuntu supposed to RE install the MBR and Grub when it runs?
Is this the problem??
Here is the posting:
https://bbs.archlinux.org/viewtopic.php?id=85603
Still. This isn't the message that I started off with - so I will try another UEFI setting.:roll:
Boot Device Control : UEFI and Legacy OpRom
Boot from Network devices : Legacy OpRom first
Boot from Storage Devices : Ignore
Boot from PVIe/PCI Expansion Devices : Legacy OpRom driver first
and another link about the commands..
(hd0) (hd0,1) (hd1) (hd1,1) This list is showing that there are two physical hard drives (hd0 and hd1) and each hard drive has a single partition on it (hd0,1 and hd1,1). Where legacy Grub counted partitions from #0, Grub2 counts partitions from #1. Another important thing to note is that the order in which Grub2 names the drives does not necessarily correspond with the drive device assignments in Linux. So the first linux drive /dev/sda is not necessarily (hd0). You can figure out which drive is which though, by ‘mounting’ them and checking. The Grub2 root command ‘mounts’ the volume. Note that you want to mount the partition, not the drive. So if I issue the command [I]root (hd0,1) to mount the partition on the first drive, Grub2 responds with:
......
above from:
http://planetstephanie.net/2009/05/27/grub2-rescue-mode/
Yikes!
also the 'help' and the 'root' commands did not work. ](*,)
Maybe that is the problem.
But first, try a reboot with the altered settings:
Get the ELF magic again.
Go back to factory settings...
and I saw a comment in the above post:
You can avoid all of these problems if you have free space at the start of your disk, or create a bios_grub partition of > 31kb.
http://grub.enbug.org/BIOS_Boot_Partition
(http://grub.enbug.org/BIOS_Boot_Partition)
[sic - a bad link]
Maybe that is the problem.
But first, try a reboot with the altered settings:
Get the ELF magic again.
Go back to factory settings...
I will load up a system rescue disk, run GPARTED add the blank spaces on the front of the disks and reload.
Will end this post and give results tomorrow/later today.
In the meantime, anybody have a suggestion?
(Or want to go out for a beer?)
Jay
I installed Ubuntu 12.04-2 from a DVD
(ubuntu-12.04.2-desktop-amd64.iso)
The DVD booted OK.
After the install - where it said it was finished and it was time to boot from the Hard Drive, grub failed.
It said something like (I didn't write it down at the time.):
Grub Rescue > Ubuntu 12.04-2 fail boot
I started to reading the posts and suspected an UEFI problem.
For general background, I read:
http://www.zdnet.com/ubuntu-linux-adopts-new-uefi-boot-problem-approach-7000004648/
and
https://help.ubuntu.com/community/UEFI
Anyway. I'm stumped.
This is a new system. It never had any windows on it.
I am trying to get an Radeon HD 7750 to work and have installed both
Debian 6.06 and ubuntu-12.10-desktop-amd64.iso
Both of these booted OK. I had wiped all partitions out and started over each time.
Then I tried Ubuntu 12.04-2 in a dual boot with the Debian -
by taking the install option to install Ubuntu side-by-side with Debian.
That did not work. I *really* wish I had written the exact error message.
It was along the lines that grub could not find the partition.
So I wiped all partitions and started over with the Ubuntu 12.04-2 install.
This time I used the easy install method so I could go eat dinner without answering a lot of install questions.
This is where I get the Grub Fail message.
the Ubuntu 12.04-2 did not have a Rescue option in the menu,
just ( paraphrase)
- try it
- install it
- memory test
I tried the "Try it" option to see if I could fix it.
No Go. That version of GParted said it needed 'gpart'.
I couldn't get gpart.
After reading more posts, I tried to boot with BIOS set with full UEFI enabled.
Got a new error message this time:
The current BIOS setting do [sic] not fully support the boot device.
Click OK to enter the BIOS setup.
Go to Advanced > Boot > CSM Parameters and adjust the CSM
(Compatibility Support Module) settings to enable the boot device.
OK. did this.
Changed Launch CSM
From: Enabled
To: Disabled
The Bios screen had these explanations:
[Enabled] : For better compatibility, enable the CSM to fully support the
non-UEFI driver add-on devices or the Windows UEFI mode.
[Disabled] : Disable the CSM to fully support the Windows Security Update and Security Boot.
OK. I'm confused. But no matter. Try something and see if it works....
Saved the settings and tried to boot the HD.
A new error!
A different BIOS display..
Here is the info written from the screen... :-)
American Megatrends
AMIBIOS (C) 2012 American Megatrends, Inc.
ASUS Sabretooth 990FX R2.0.ACPI BIOS Revision 0906
CPU AMD FX(tm) -8150 Eight-core processor .....
....
The VGA card is not supported by the UEFI driver.
CSM (...) settings have been changed for better compatibility
Just great. :-(
Then the option to procede, or go back and change the settings.
I tried to procede.
That went to the 1st message about adjusting the CSM to enable the boot device.
OK. I'm writing this down so I won't have to go back; do it over to answer a question later - of what I did try.
OK.
Rest CSM back to auto.
[This BIOS is labelled ASUS UEFI mBIOS Utility - EZ Mode (or Advanced mode)
Launch CSM: Enabled
{Then 4 more settings show up.}
I set these to:
Boot Device Control : UEFI and Legacy OpRom
Boot from Network devices : Legacy OpRom first
Boot from Storage Devices : Both, UEFI first
Boot from PVIe/PCI Expansion Devices : UEFI driver first
save and reboot.
{insert a drum roll while I go get a beer.] :popcorn:
A different error message.
Grub loading
Welcome to GRUB!
error: invalid arch independent ELF magic.
Entering rescue mode...
grub rescue>
Beer in hand I went googling for grub rescue commands.
Ah-hah. Another post said:
"Sometimes, when you change the partition layout of your HD, the number of the partition which contains GRUB2 changes. Let's assume we installed GRUB2 from (hd0,7) or /dev/sda7, which is a logical partition inside an extended partition. Then we deleted /dev/sda5 and /dev/sda6, our /dev/sda7 became /dev/sda5. Now when the "MBR part" is looking for the rest of the program, it can't find it in (hd0,7) since such partition doesn't exist anymore. In this case, instead of showing the usual GRUB2 menu, you are being dropped to some sort of command line which is called GRUB rescue."
YES - So isn't Ubuntu supposed to RE install the MBR and Grub when it runs?
Is this the problem??
Here is the posting:
https://bbs.archlinux.org/viewtopic.php?id=85603
Still. This isn't the message that I started off with - so I will try another UEFI setting.:roll:
Boot Device Control : UEFI and Legacy OpRom
Boot from Network devices : Legacy OpRom first
Boot from Storage Devices : Ignore
Boot from PVIe/PCI Expansion Devices : Legacy OpRom driver first
and another link about the commands..
(hd0) (hd0,1) (hd1) (hd1,1) This list is showing that there are two physical hard drives (hd0 and hd1) and each hard drive has a single partition on it (hd0,1 and hd1,1). Where legacy Grub counted partitions from #0, Grub2 counts partitions from #1. Another important thing to note is that the order in which Grub2 names the drives does not necessarily correspond with the drive device assignments in Linux. So the first linux drive /dev/sda is not necessarily (hd0). You can figure out which drive is which though, by ‘mounting’ them and checking. The Grub2 root command ‘mounts’ the volume. Note that you want to mount the partition, not the drive. So if I issue the command [I]root (hd0,1) to mount the partition on the first drive, Grub2 responds with:
......
above from:
http://planetstephanie.net/2009/05/27/grub2-rescue-mode/
Yikes!
also the 'help' and the 'root' commands did not work. ](*,)
Maybe that is the problem.
But first, try a reboot with the altered settings:
Get the ELF magic again.
Go back to factory settings...
and I saw a comment in the above post:
You can avoid all of these problems if you have free space at the start of your disk, or create a bios_grub partition of > 31kb.
http://grub.enbug.org/BIOS_Boot_Partition
(http://grub.enbug.org/BIOS_Boot_Partition)
[sic - a bad link]
Maybe that is the problem.
But first, try a reboot with the altered settings:
Get the ELF magic again.
Go back to factory settings...
I will load up a system rescue disk, run GPARTED add the blank spaces on the front of the disks and reload.
Will end this post and give results tomorrow/later today.
In the meantime, anybody have a suggestion?
(Or want to go out for a beer?)
Jay