EEEPC 900 - Install of EEEBUNTU 4 beta1 - eb4-b1 - FATAL ERROR ..."running grub-install HD0" (95% installed)

[Kristian Fredrik Gron]

Sunday Feb. 14. 2010.

EEEPC 900 CELERON, 1GB RAM, 16GB fixed flashcard with Xandros, 8 GB extra Flashcard attached so i can install EEEBUNTU unto it.
Problem with installing eb4-b1.
http://eeebuntu.org/ (Our new EB4 beta has been released so to download and test it out just.......)

FATAL ERROR ..."running grub-install HD0" (95% installed)

/var/log/syslog could not be retrieved.
/var/log/partman is attached.

I used utorrent and downloaded eb4-b1.
Formatted a Kingston 8GB USB stick and formatted it as instructed to FAT32.
Then is used Vindows Vista with unetbootin-eeebuntu-windows-276.
The eb4-b1.iso file got installed into the USB.
Then i attached USB unto my EEEPC 900 and booted it.
When the eb4-b1 was up and running i chose Install eb4,
followed the instructions as i have done before with EEEBUNTU 3.0.
I always choose to format 100% of the flashcard.
The install procedure worked perfectly well until 95%.
Then i got the FATAL ERROR "running grub-install HD0" and the install process stopped.
I can still use my EEEPC 900 Celeron - from the USB stick and write this text with gedit.
Two times i have tried to install unto the flashcard, but exactly the same problem.

Regards
KFG, Trondheim, Norway.

Crash Report:
--------------------------------------
We're sorry; the installer crashed. Please file a new bug report at https://launchpad.net/ubuntu/+source/ubiquity/+filebug (do not attach your details to any existing bug) and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/syslog and /var/log/partman:

----------
Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 457, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 442, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 245, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 465, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 975, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 2453, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 459, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1810, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1
----------

--------------------------------------

[Monkey (monkey-libre)]

I´ve assigned this bug to the ubiquity package. Thank You for making Ubuntu better.

[obscureflame (frank731tr)]

having the same problem on asus 1005pe

[Kristian Fredrik Gron (kristian-fredrik-gron)]

I found this solution to the EB4 - beta problem, from the development team.
I have not tested it yet, but they tell in forums the problem will be
fixed in the final version.
A well known problem actually but it took me some time to discover it.
:-)

http://forums.eeebuntu.org/viewtopic.php?f=25&t=5056

---------------------------
- On installing, when you get to the summary screen, you need to choose
ADVANCED and select your HD install target. (it was thought that this was
not enough to hold it back any further but will be fixed in final). - or
this will cause GRUB install error.
- For those who are seriously testing the iso, PM me or Paul
(Guitaraholic) and we'll add you to bugzilla. Link is
http://bugs.eeebuntu.org
- If reporting bugs and you know the fix, add that in too.
- Do NOT run update in live before you install, there is a python upgrade
that will break the installer (again it was thought that was not enough to
hold back the beta release).
---------------------------

Regards
K.F.G
Trondheim, Norway.

På Tue, 23 Feb 2010 07:01:56 +0100, skrev obscureflame
<email address hidden>:

> having the same problem on asus 1005pe
>

--
----------------------------------------------------------------
"Yesterday Is History, Tomorrow Is a Mystery, but Today Is a Gift.
That Is Why It Is Called the Present."
----------------------------------------------------------------
http://boinc.berkeley.edu
Donate your computer's idle CPU time to humanitarian non-profit scientific
research projects.
----------------------------------------------------------------

[Kristian Fredrik Gron (kristian-fredrik-gron)]

I discovered the solution to the EB4 - beta problem, from the development
team.
I have not tested it yet, but they tell in forums the problem will be
fixed in the final version.
A well known problem actually but it took me some time to discover it.

http://forums.eeebuntu.org/viewtopic.php?f=25&t=5056

---------------------------
- On installing, when you get to the summary screen, you need to choose
ADVANCED and select your HD install target. (it was thought that this was
not enough to hold it back any further but will be fixed in final). - or
this will cause GRUB install error.
- For those who are seriously testing the iso, PM me or Paul
(Guitaraholic) and we'll add you to bugzilla. Link is
http://bugs.eeebuntu.org
- If reporting bugs and you know the fix, add that in too.
- Do NOT run update in live before you install, there is a python upgrade
that will break the installer (again it was thought that was not enough to
hold back the beta release).
---------------------------

Regards
K.F.G
Trondheim, Norway.

På Mon, 15 Feb 2010 07:52:14 +0100, skrev Monkey <email address hidden>:

> I´ve assigned this bug to the ubiquity package. Thank You for making
> Ubuntu better.
>
> ** Package changed: ubuntu => ubiquity (Ubuntu)
>

--------------------------------------------------
--------------------------------------------------
Bug description:
Sunday Feb. 14. 2010.

EEEPC 900 CELERON, 1GB RAM, 16GB fixed flashcard with Xandros, 8 GB extra
Flashcard attached so i can install EEEBUNTU unto it.
Problem with installing eb4-b1.
http://eeebuntu.org/ (Our new EB4 beta has been released so to
download and test it out just.......)

FATAL ERROR ..."running grub-install HD0" (95% installed)

/var/log/syslog could not be retrieved.
/var/log/partman is attached.

I used utorrent and downloaded eb4-b1.
Formatted a Kingston 8GB USB stick and formatted it as instructed to FAT32.
Then is used Vindows Vista with unetbootin-eeebuntu-windows-276.
The eb4-b1.iso file got installed into the USB.
Then i attached USB unto my EEEPC 900 and booted it.
When the eb4-b1 was up and running i chose Install eb4,
followed the instructions as i have done before with EEEBUNTU 3.0.
I always choose to format 100% of the flashcard.
The install procedure worked perfectly well until 95%.
Then i got the FATAL ERROR "running grub-install HD0" and the install
process stopped.
I can still use my EEEPC 900 Celeron - from the USB stick and write this
text with gedit.
Two times i have tried to install unto the flashcard, but exactly the same
problem.

Regards
KFG, Trondheim, Norway.

Crash Report:
--------------------------------------
We're sorry; the installer crashed. Please file a new bug report at
https://launchpad.net/ubuntu/+source/ubiquity/+filebug (do not attach your
details to any existing bug) and a developer will attend to the problem as
soon as possible. To help the developers understand what went wrong,
include the following detail in your bug report, and attach the files
/var/log/syslog and /var/log/partman:

----------
Traceback (most recent call last):
   File "/usr/lib/ubiquity/bin/ubiquity", line 457, in <m...

[hlee (hmlee)]

eee pc900a ... same problem at 95% (fatal error) .. i got it to work once when in the summary screen .. advanced.. i chose an sd card instead of the target drive ... that worked and rebooted twice ok .. but then i took out the sd card and i got error2 ... even putting it back in still error 2 (no boot) .. i reloaded many times using different combinations .. nothing worked including the recommended "target drive" .. when it did work everything was nice ... except little problems :

anamated gif dont run with default settings .. they are ok if opened with gthumb

there is no support for pps files .. (maybe impress)

if internet access is attempted before wifi is chosen then no wifi stations are found

[hlee (hmlee)]

got it working UB4 !! eeepc900a .. 4gig ssd 1gig ram
i got the fatal error for grub at 95% install... i tried the recommended fix (advanced .. assign boot to target drive) ... that didnt work .. i tried installing to an 8gb external SDHC .. that failed in the same way ... then i loaded UB4 to the internal 4gig ssd but assigned the boot (in advanced for summery screen) to the 8gig SDHC card .. that didnt work at first because the boot was still registered in cmos (F2) to the internal drive ... you can see that by hitting Esc as it is booting .. that gives you a choice of what to boot with .. i chose the SDHD card and everything worked.. i had 1.16 gb left on the internal 4gig drive .. there were two entries on the external card .. 376.52 meg "extended" and 376.49 meg for "linux swap" ... also seen in "system/admin/gparted" was the remainder of the 8gb SD drive (7.4gb) marked as "unknown" .. i formatted that to ext4 and now thats listed on the main screen as 7.6GB file system .. it has a "lost + found" directory but nothing else so far in that partition..

i am new to linux so dont know how to get permission to put things on that drive or if i even need to do that ... i would like to move the email folders to that .. i think i can just reassign the folders to that file system if it will let me .. of course i will have to put duct tape over the SD so it never comes out ... it would also be nice if i can load new programs on that SD card as well.

so this got UB4 install working (nicely too) and gives me some breathing room for hard drive space .. the 8gig SDHC card is a 100x sandisk and it seems to work fast ..

i originally wanted to put several operating systems on different SD cards .. that way i could just plug in whatever i wanted to experiment with while using the intenal drive for data only .. that way the data would be available to all linux versions ... that would be great for experimenting but couldnt get it to work with UB4 so far ...

i cant believe how good UB4 works. they have done a remarkable job. this is just a Beta but i had fewer problems than i had with Win7 ..

[Barry Timm (barry-timmfamily)]

I am also having a fatal error on a fresh install (formated hard drive via installer) on an Asus EEE PC904HA running 2 GB RAM with a 60GB partition for the Linus install.

I'm a novice Linux (trying it out) and had already successfully installed Ubuntu 10.4 on the same netbook earlier this weekend, before I saw the EEE speciic distro here.

Details as follows:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 457, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 442, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 245, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 465, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 975, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 2453, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 459, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1810, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1

[simon (swht)]

Same error report and installation failure on eee PC 701 4G (non-surf).

We're sorry; the installer crashed. Please file a new bug report at https://launchpad.net/ubuntu/+source/ubiquity/+filebug (do not attach your details to any existing bug) and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/syslog and /var/log/partman:

----------
Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 457, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 442, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 245, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 465, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 975, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 2453, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 459, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1810, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1

suggested fix:

http://forums.eeebuntu.org/viewtopic.php?f=25&t=5056

---------------------------
- On installing, when you get to the summary screen, you need to choose
ADVANCED and select your HD install target. (it was thought that this was
not enough to hold it back any further but will be fixed in final). - or
this will cause GRUB install error.
- For those who are seriously testing the iso, PM me or Paul
(Guitaraholic) and we'll add you to bugzilla. Link is
http://bugs.eeebuntu.org
- If reporting bugs and you know the fix, add that in too.
- Do NOT run update in live before you install, there is a python upgrade
that will break the installer (again it was thought that was not enough to
hold back the beta release).

[Bruno Remy (bremy)]

Having the same Bug with a eeePC1000HE, having choosen "ADVANCED" at the beginning of installation.
------------------------------------
Nous sommes désolés, l'installateur a rencontré une erreur. Veuillez signaler ce bogue sur https://launchpad.net/ubuntu/+source/ubiquity/+filebug (n'ajoutez pas vos renseignements à un bogue existant) et un développeur s'occupera du problème le plus rapidement possible. Pour aider le développeur à appréhender le problème, incluez les renseignements suivants dans votre rapport et attachez les fichiers /var/log/syslog et /var/log/partma :
raceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 457, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 442, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 245, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 465, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 975, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 2453, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 459, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1810, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1
--------------------------------------------------

[Simon Quigley (tsimonq2)]

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 with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 521920

and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]