GRUB geom error after install of suse 9.1

Posted on 2006-11-22
Medium Priority
Last Modified: 2013-12-15
I am trying to install suse 9.1 on a Dell inspiron lap top. This computer has Windows xp already installed. During the install I only had enough space for the minimal graphical system (probably an indication that something was wrong since it has a 120G hard drive that is mostly empty). I tried the install anyway and it went smoothly until the reboot. Then I immediately  got "GRUB geom error". I can boot from the installation CD. Yast gives me the message "it appears this machine already has Linux .. ". Then I take the option "Boot installed system" and it boots ok.

I cannot get into windows at all. If I use the windows installation CD and try the recovery console, I get the message "The path or file specified is not valid C:\>" . It does not seem to "see" the hard drive at all.  

At this point I would be happy just to get Windows xp running again, and re-try the linux installation at a later date. I was just installing linux to learn about it and don't know much about it yet.
Question by:morgan_dg
  • 3
  • 2
LVL 14

Expert Comment

ID: 18000930
did you try the windows installation cd and attempt to FIX MBR as an option.  

Linux installs grub on the Master Boot Record (MBR) which would have been earlier occupied by the Windows info.  Try that once.  Normally, it is advisable to have different partitions and loading windows and linux on different partitions makes the system work trouble free between the OS.  if you had single partition and have gone ahead with the Linux installation, well you only can reinstall windows all over again.

good luck

Author Comment

ID: 18003772
I did load Linux on a different partition. Here is the partition table:

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1           6       48163+  de  Dell Utility
/dev/hda2   *           7       14001   112414837+   7  HPFS/NTFS
/dev/hda3           14002       14409     3277260   db  CP/M / CTOS / ...
/dev/hda4           14410       14592     1469947+   f  W95 Ext'd (LBA)
/dev/hda5           14410       14440      248976   82  Linux swap
/dev/hda6           14441       14592     1220908+  83  Linux

I've tried using the windows recovery console, but it can't find the hard drive. I tried running fixmbr anyway, but I still get the same error when the system is rebooted.
LVL 14

Assisted Solution

ygoutham earned 1500 total points
ID: 18018227
it seems that you did not have a separate partition when you tried to install suse and went in to install suse in available free space and linux has created its own partition tables overwriting the windows tables.

you might want to look at some utility to mount NTFS partitions so that the data stored in them can be recovered.

it is always GOOD to have a separate partition CREATED in windows and then install linux in that free partition if you intend to use windows AND linux from the same box.  installing linux in available free space always creates this problem.
LVL 14

Accepted Solution

ygoutham earned 1500 total points
ID: 18018251

gives you an idea to mount the NTFS partition in your case it is


and take the data.  if it is any critical data that you want backed up first, then consider doing so first before doing further damage.  once that is done, then get back to reinstalling windows or something so that you can have a comfortable working windows machine.

do not partition entire 120 GB as a single disk. consider multiple partitions and then pick any one of the smaller areas to install suse. you can already see that you would be quite well off with  a lesser partion size of about 10 GB space which gives ample play area for suse.

RECOVER data first and then do anything ahead.

Author Comment

ID: 18041116
Success! I repartitioned the disk. First I deleted the Linux partitions and the I shrunk the windows partition ( I don't know why this wouldn't work on the original install). Then I reinstalled Linux. I was able to create a large Linux partition (plus a Linux swap partition).  Now everything works perfectly.  I can boot both windows and Linux.

My guess is that the geom error was because the original Linux partition too high in memory for the bios to access. Thanks for the helpful suggestions ygoutham.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
I have written articles previously comparing SARDU and YUMI.  I also included a couple of lines about Easy2boot (easy2boot.com).  I have now been using, and enjoying easy2boot as my sole multiboot utility for some years and realize that it deserves …
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Suggested Courses
Course of the Month15 days, 19 hours left to enroll

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question