i think you will solve my problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/14135
Title:
Grub Install Failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/
getting error: executing 'grub-install/dev/sda' failed
This is a fatal erro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/14135
Title:
Grub Install Failure
To manage notifications about thi
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Opinion
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
** Changed in: grub-installer (Ubuntu)
Status: Confirmed => Incomplete
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
No, this seems not to be working, right now I see the error message:
"Sorry, the program gtk-logout-helper closed unexpectedly". May I
suggest humbly that this is not a user error?
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a m
Ok, take you Windows CD, and format the hard disk. That will do the
trick.
Alternatively, take the Linux CD, boot in life mode, act as if you
wanted to install Linux up to the point where the partition editor shows
up. Enable manual editing, and you can format your hard drive from
there.
Warning:
I suspect that the backup CDs did a Windows restore and not an install.
If you had installed Windows XP, it should have eliminated Grub. There
are ways of restoring the Windows boot process. Have a look at some of
these.
http://www.cyberciti.biz/faq/linux-how-to-uninstall-grub/
http://en.kioskea.n
Thanks for the comment, but I already did that, I installed Windows XP
from the backup CDs and VOILA got the same result: "GRUB loading, error:
unknown filesystem grub rescue> " That is it. As Cameron Diaz said "Now
what?"
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You receive
Ähhmmm well you should never throw your computer away, unless it
starts to smoke...
What you could do is simply install Windows XP from your Windows CD. No
matter what happend to your hard drive, your CD will always work. Make
sure that your computer is set up in a way that it boots from CD fi
I wanted to change from ubuntu 9.10 back to Windows XP and now I do not
even see a command prompt. Do I have to throw the computer away? Thanks
very much.
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Related problem, grub failed to install for me several times, though the
root was /dev/sdc5. Apparently the only valid place for grub would have
been /dev/sdc5 yet the installer didn't display any warnings. After
rebooting the above partition had no boot loader and an otherwise
complete install. I
My 9.10 karmic fails to install grub 2 with every version of the cd
(live cd, alternate) and every architecture. With the live cd it tells
me that grub couldn't have been installed and the system won't boot, but
the windows partition doesn't boot anymore.
I have two hard disks in raid (Motherboard
Yesterday I used netboot install of the Karmic beta-version . Have a
server set up with tftpd and
http://archive.ubuntu.com/ubuntu/dists/karmic/main/installer-i386/current/images/netboot/netboot.tar.gz
.
It's a thin-client with a small flash-thingy inside (512 mb). Installed
the beta on a usb-disk
I have a single 2TB SATA drive. I experienced the same error message as
above although I cant really use most of the suggested workarounds.
My workaround involved manually creating a /boot partition of around
100MB at the beginning of the disk.
Unsure if this is related. Either way, the installer
With 9.04 it seems not possible to reinstall grub by using the livecd if I
don't have a boot partition.
It seems to require a boot partition and a dir only does not install grub
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a mem
With 9.10 alpha 6 I could not install Ubuntu on the second hdd (sdb)
without problems. When rebooting after the installation, I got a Grub
error 15. I could solve it by switching the first and second hdd in the
bios (so sda was switched with sdb).
I had the two partitions on sda configured as "not
By the way, Scott Merrilee's hint above seems to be a cure. Thanks,
Scott!
I think the bigger problem may be that device.map isn't done by UUID.
This issue is most definitely NOT fixed!
** Attachment added: "hardware-summary.txt"
http://launchpadlibrarian.net/27039613/hardware-summary.txt
**
** Attachment added: "partman"
http://launchpadlibrarian.net/27039322/partman
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
OK, I'm having this problem with Jaunty Server AMD64. It worked fine
when I only had scsi hard disks (my CDRom is IDE). When I added an IDE
hard drive and tried to install there, it failed. I'm attaching
everything in /var/log (which, by the way, is painful to recover!)
** Attachment added: "s
Fabulous! Great news and thank you.
Best Regards,
Ron
On Wed, Oct 29, 2008 at 4:12 AM, Evan Dandrea <[EMAIL PROTECTED]> wrote:
> The installer now specifies the GRUB root device by UUID so I'm marking
> this as fixed. If you still experience issues please open a new bug
> report, describe the
The installer now specifies the GRUB root device by UUID so I'm marking
this as fixed. If you still experience issues please open a new bug
report, describe the problem in as great detail as possible, and attach
full installer logs.
Thanks
** Changed in: grub-installer (Ubuntu)
Status: Co
Similar experience here. When attempting to install with a separate
/home partition I cannot under any circumstances get grub to install.
Error 15 all over the place, can't chroot into the installation via live
CD due to "cannot resolve host ubuntu" error, even manually creating all
the files in t
That sounds aweful!! Which part do you mean: the installer, or grub
itself?
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Kenobi,
Yes, UUID support as a patch to GRUB is planned for Ubuntu 8.10.
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I have similar problems: grub installing just doesn't end up with
anything usable.
__
SOLUTION:
can grub and ubuntu be configured as to interprete Disk Labels or UUIDs? It
would be so great if it worked like this:
Where do you want grub to be installed on:
Me wrote:
> I have exactly the same problem with 8.04 RC !!
Interesting! Something happens, because when I tried to install 8.04 (final) on
_same_ computer it was succesful!
Notice: I tried to install 8.04 RC many times before final version and without
success.
--
Grub Install Failure
https://
i have the same problem. i got 10 hdds, all ide, but only 3 of them are
connected to the mainboard, the rest are connected to two promise ultra
ata133tx2 conntroller cards. in setup all drives ar designated as scsi
drives, install completes ok but when i start i get grub 1.5 error 22 or
error 17 (i
flying penguin wrote:
> I got a error window saying "grub-install (hd0) failed. This is a fatal
> error." during my last step
> of installation of ubuntu 7.04 (at 94%) this morning. My PC had 4 NTFS
> partitions and
> I used the "Manual Configure" to instruct the installer to reformat one
> part
Following up on my last post, I was able to manually install GRUB and
uninstall LILO with no ill-effect on the above-mentioned configuration.
So, the problem isn't in the setup or with GRUB, but something going on
during the install, at least in this case.
Where do logs from installs end up? It mi
1 250GB SATA drive. Installing Ubuntu 8.04 Beta Alternate 64bit with
drive formatted using encrypted LVM. Installation crash (red screen box
warning), GRUB would not install. Installed LILO instead.
This might be a serious problem for any user not realizing that they
have an option of installing a
1 ATA and 2 SATA drives. Installing U8.04 alternate 32bit on one of the
SATAs. Installation craches (red warning) when it is reaching the GRUB-
install-step.
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, w
Being a new user and already successfully building 2 PCs, one MythTV
based on Hoary Beta and one server based on Gutsy 7.1, to have this fail
on my main PC is a little disappointing to say the least.
I have 2 SATA drives of 250GB ea with XP on SDA1 and wanted Ubuntu on
SDA2. Don't have the experti
This bug also affects Hardy beta - I have two SATA drives which appear as
sda/b. Ubuntu 6.10 is installed
on sda. When I installed Hardy on sdb, the /boot/grub/menu.lst had the drive
identifiers inverted (hd1,1) in place of (hd0,1) and vice-versa). The MBR was
overwritten and wouldn't boot. I ha
I have been experiencing the exact same issue. In order to complete the
installation, I physically remove and disable the additional "SCSI"
drives, and only then can I install Ubuntu. Then comes the job of
putting everything back in, and thankfully, the first boot then
completes without any issues,
Why exactly is the importance for this set only to High?
It's preventing new users from using Ubuntu!
It should be _at least_ Critical!
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subsc
Based on the error messages I have seen so far I have come to some provisional
conclusions.
1. grub is not comfortable with the ubuntu strategy of using UUID instead of
/dev/hdax.
2. The default grub behaviour of assuming (hd0,0) after the kernel isn't found
tends to hide errors if (hd0,0) is ac
I am too having a similar problem. I have a single SATA disk, and an
existing Windows partition in sda1. I install Ubuntu in sda2, and
everything is fine, except that grub's menu.lst still configures Ubuntu
to boot up from (hd0,0) and root in /dev/hda1. This has been happening
at least since Breezy
i was having a similar problem with booting from a scsi drive. the
solution was to switch off support for INT 13 (LBA) in the SCSI BIOS
(see http://www.gnu.org/software/grub/grub-faq.html#q14)
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification because
I should also add that when I do "Advanced Install" and choose the
correct HD as listed by the GRUB device map, all I'd get is an endless
looping of the word GRUB filling my screen when I boot up the system.
The workaround I found was using Grub4DOS, but I don't like to do that,
I'd prefer installi
You're not really me are you? Because this is just about the EXACT SAME
THING, that's been plaguing me since Feisty. This still is a problem in
Gutsy (Alpha tests were the only thing I've done).
--
Grub Install Failure
https://bugs.launchpad.net/bugs/14135
You received this bug notification bec
We had a live CD installed Ubuntu 7.10 (feitsy) on a SATA (over a
previous dual boot FC6) - succesful (also the booting). But after I
allowed an automatic kernel update grub could not boot Ubuntu, only XP.
The problem was in "/boot/grub/menu.lst" Ubuntu is actually on sda3
(found by inspecting the
I got a error window saying "grub-install (hd0) failed. This is a fatal
error." during my last step of installation of ubuntu 7.04 (at 94%) this
morning. My PC had 4 NTFS partitions and I used the "Manual Configure"
to instruct the installer to reformat one partition to "ext3".
After the failure o
I too echo Ron F's comments.
Ever more frustrated by the inept antics of Gates and Balmer I tried
Linux again... and was immediately reminded of why I abandoned it a few
years ago... Unix is a big hairy mess and putting fancy seats and a
stereo on top doesn't change what's under the hood!
People
Ubuntu Feisty
The Desktop CD fails to install grub. I have a single SCSI disk that
is seen and mounted and files are copied.
Could it be the fault of "Disk Image 7" or "Norton Anti Virus" possibly V2i
disk image protection system installing something to Ring 0?
(Norton Internet security al
I'm with Ron F. I always thought that Linux was way too complicated for
the average computer user. If it won't install, I can't use it.
If there are instructions on what a grub menu is, where it is, what to
use to edit it and how, I don't know where they are. And, in what
system would I edit it
I am a new user, attempting to install Ubuntu on my hard drive for the
first time. The live CD fails to complete, issuing a fatal error when
trying to install grub.
I have a NTFS partiion with Windows XP that boots fine, and a new ext2
partition in which feisty was installed by the Live CD that I
A slightly different wrinkle. I netbooted my laptop to do a feisty
install because there wasn't space on / to do an upgrade. Did an expert
install. When I tried to install grub, it failed. Bottom line was that
I didn't format /boot, and grub was finding the definition of hd0 in
device.map was /
Unfortunately, there isn't anything that can be done to fix this. The
underlying problem is that grub can not automatically determine the
relationship between the linux devices and the bios devices, so you have
to manually configure /boot/grub/menu.lst to indicate those
relationships. The only th
Edgy Eft RC - LIVE CD installer failed installing GRUB to first partition of
1st (and only one) HD (hd0,0).
It works only for MBR (hd0) - so i had to first overwrite MBR with it, boot
into Ubuntu, and from there install it to hd0,0 (BTW grub-installer failed
mentioning corrupted stage1/stage2 as
My cdrom is IDE and all my disks are SATA, there is no reason for the
IDE disk to change the order of the SATA disks. I have two identical
SATA disks, 80G and one 300G. Seems Ubuntu wanted to recognise the
biggest disk as the first one. Once I removed the 300G, installed and
then put back the 300G
** Changed in: grub-installer (Ubuntu)
Status: Unconfirmed => Confirmed
--
Grub Install Failure
https://launchpad.net/bugs/14135
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This can sometimes be caused, as was my case, by device.map in the
/boot/grub directory being incorrect. Causing the drive, which was
(hd2) on the live CD to maybe turn out to be (hd0) on the actual
installation.
My theory is that this is caused by booting of the CD making the boot
order look dif
** Changed in: grub-installer (Ubuntu)
Assignee: Colin Watson => (unassigned)
--
Grub Install Failure
https://launchpad.net/bugs/14135
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have the same Motherboard but my install doesnt work with the
graphical installer, it installs grub onto the wrong hard drive. I have
been using the text installer and manually setting grub to install on
the MBR of hda and it installs but it thinks that my hda drive is really
hd(1,1) instead of h
grub and lilo failed on my ASUS A8N SLI DELUXE. I have 3 disk drives,
80G as sda another identical 80G as sdb and a 300G as sdc, all of them
are seagate disks. Installation of the boot loaders failed till I
removed the 300G. What happend was that the Linux kernel read sda b c in
the correct order,
56 matches
Mail list logo
