You are not logged in.

#1 2009-01-28 20:56:56

Exitium
Member
From: Helsinki, Finland
Registered: 2008-08-20
Posts: 202

[SOLVED] Grub error 18 - cannot boot to Windows

Earlier today I tried to install Arch 64bit (I had 32bit earlier) with kdemod to test new KDE4.2. However, after installation I could not boot neither Arch nor Windows. Grub appeared, but every single option gave me an error. I can't remember anymore which error it was, but It doesn't matter anymore. I thought I had made a really stupid and basic mistake while installing, I just didn't know what.

I wanted to test KDE4.2 so much so I installed Kubuntu (yeah, this topic is not related to Arch Linux, I hope that somebody can help me though, move this topic to somewhere else if it doesn't belong here smile ). Installation was fine, booting to Kubuntu was fine (and upgrading to KDE4.2 was fine), but booting to Windows was not. It gave me a following error:

Error 18: Selected cylinder exceeds maximum supported by BIOS

I googled a bit and found this: http://wiki.linuxquestions.org/wiki/GRUB#Error_18 I reinstalled Kubuntu using /dev/sdb1 as /boot and /dev/sdb2 as / (/dev/sdb3 is windows and /dev/sdb4 is my game partition, ntfs). Before this I had /dev/sdb1 as / and /dev/sdb2 as swap (now I have no swap at all, my 4GB RAM should be enough). The only difference was that at first grub gave me error 15 (I fixed it with Kubuntu LiveCD). After that - no difference.

I need Windows for playing. That's why it's very important that I can use it. [SOLVED] In addition, I should say that /dev/sda is a separated hard drive which is encrypted with Truecrypt. (I said this because I think that Kubuntu tried to install grub on (hd0)...) When I tried to mount this hard drive with Kubuntu, it couldn't do it. I wanted to test mounting on Windows to check if it is just Kubuntu's problem. If not, I'm fucked because this hard drive contains VERY VERY VERY IMPORTANT files. [/SOLVED]

I really need help, please. If somebody can help me, (s)he is my hero.

Last edited by Exitium (2009-01-29 14:42:32)

Offline

#2 2009-01-28 21:04:38

Exitium
Member
From: Helsinki, Finland
Registered: 2008-08-20
Posts: 202

Re: [SOLVED] Grub error 18 - cannot boot to Windows

Oops, I forgot:

menu.lst:
(Yup, a lot of comments, Ubuntu style)

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default                0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout                10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title               Windows 95/98/NT/2000
# root               (hd0,0)
# makeactive
# chainloader       +1
#
# title               Linux
# root               (hd0,1)
# kernel       /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=504fab5b-7bb6-4b20-af58-83677386de37

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title                Ubuntu 8.10, kernel 2.6.27-11-generic
uuid                504fab5b-7bb6-4b20-af58-83677386de37
kernel                /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro quiet splash 
initrd                /initrd.img-2.6.27-11-generic
quiet

title                Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
uuid                504fab5b-7bb6-4b20-af58-83677386de37
kernel                /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro  single
initrd                /initrd.img-2.6.27-11-generic

title                Ubuntu 8.10, memtest86+
uuid                504fab5b-7bb6-4b20-af58-83677386de37
kernel                /memtest86+.bin
quiet

title                Wintoosa
root                (hd1,2)
savedefault
makeactive
map                (hd0) (hd1)
map                (hd1) (hd0)
chainloader        +1

fdisk -l
(Note: These results are mainly in Finnish. It could be hard to you to read it... But whatever... I'll translate these only if necessary)

Levy /dev/sda: 640.1 Gt, 640135028736 tavua
255 päätä, 63 sektoria/ura, 77825 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0xcc5d88e2

    Laite Käynn     Alku          Loppu    Lohkot   Id  Järjestelmä
/dev/sda1   *      244091      485122  1936074870+  b8  BSDI sivutus
Osion 1 loppu ei ole sylinterin rajalla.
/dev/sda2          176430      394864  1754572509+  43  Tuntematon
Osion 2 loppu ei ole sylinterin rajalla.
/dev/sda3          177329      413105  1893868925   29  Tuntematon
Osion 3 loppu ei ole sylinterin rajalla.
/dev/sda4           57435      309703  2026342066   5c  Priam Edisk
Osion 4 loppu ei ole sylinterin rajalla.

Osiotaulumerkinnät eivät ole levyjärjestyksessä

Levy /dev/sdb: 500.1 Gt, 500107862016 tavua
255 päätä, 63 sektoria/ura, 60801 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0x0007a52a

    Laite Käynn     Alku          Loppu    Lohkot   Id  Järjestelmä
/dev/sdb1               1         128     1028128+  83  Linux
/dev/sdb2             129       13185   104880352+  83  Linux
/dev/sdb3           13186       26239   104856255    7  HPFS/NTFS
/dev/sdb4           26240       60801   277619265    7  HPFS/NTFS

Last edited by Exitium (2009-01-28 21:05:33)

Offline

#3 2009-01-28 21:20:31

deej
Member
Registered: 2008-02-08
Posts: 395

Re: [SOLVED] Grub error 18 - cannot boot to Windows

Earlier today I tried to install Arch 64bit (I had 32bit earlier) with kdemod to test new KDE4.2.

A few questions:

So, 32-bit Arch booted OK ?

You used the exact same partitions to install 64-bit ( Just over-wrote the 32-bit install ) ?

Are either of your drives SATA ?

Deej

Offline

#4 2009-01-29 01:32:17

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: [SOLVED] Grub error 18 - cannot boot to Windows

Perhaps bios needs to be checked to verify the proper HDD boot device....just a thought.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#5 2009-01-29 07:42:06

Exitium
Member
From: Helsinki, Finland
Registered: 2008-08-20
Posts: 202

Re: [SOLVED] Grub error 18 - cannot boot to Windows

deej wrote:

Earlier today I tried to install Arch 64bit (I had 32bit earlier) with kdemod to test new KDE4.2.

A few questions:

So, 32-bit Arch booted OK ?

You used the exact same partitions to install 64-bit ( Just over-wrote the 32-bit install ) ?

Are either of your drives SATA ?

Deej

Yes, yes and yes

lilsirecho wrote:

Perhaps bios needs to be checked to verify the proper HDD boot device....just a thought.

It should be OK.

Offline

#6 2009-01-29 09:04:37

deej
Member
Registered: 2008-02-08
Posts: 395

Re: [SOLVED] Grub error 18 - cannot boot to Windows

The entry in your 'menu.lst' for the windows partition ought to read: root (hd0,0).
Windows *must* be on the first partition to boot. The 'map' entries you have there -
I've never used / come across before... I'll have to investigate those.

I had problems with grub mis-labelling partitions when I ran a SATA drive with
an IDE. Manual editing of the 'menu.lst' was required to get it up and running
properly. Maybe worth a try.

Deej

[EDIT]

OK, I see why you used the 'map' function. It has, however, this rider:

*Caution:* This is effective only if DOS (or Windows) uses BIOS to
access the swapped disks. If that OS uses a special driver for the
disks, this probably won't work.

Much less hassle to put 'doze on the first partition of the first [boot] drive.
Have you tried unplugging your boot-drive and trying to boot the 'doze drive ?

Deej

Last edited by deej (2009-01-29 12:52:46)

Offline

#7 2009-01-29 10:37:07

RabidWolf
Member
From: WI,USA
Registered: 2007-01-20
Posts: 31
Website

Re: [SOLVED] Grub error 18 - cannot boot to Windows

thought I could help, upon further investigation... nope, deej is right, windows "must" be on the first partition, it's sneaky that way

Last edited by RabidWolf (2009-01-29 12:30:51)

Offline

#8 2009-01-29 13:13:08

Exitium
Member
From: Helsinki, Finland
Registered: 2008-08-20
Posts: 202

Re: [SOLVED] Grub error 18 - cannot boot to Windows

RabidWolf wrote:

thought I could help, upon further investigation... nope, deej is right, windows "must" be on the first partition, it's sneaky that way

Why did it work earlier then? It has been as sdb3 for a year now - and there have been a couple of different Linux installations and 2 different Windows installations and no problem.

And is there a nice and fast way to solve this, without reinstalling or waiting damn long time while reordering partitions?

Offline

#9 2009-01-29 14:29:41

Exitium
Member
From: Helsinki, Finland
Registered: 2008-08-20
Posts: 202

Re: [SOLVED] Grub error 18 - cannot boot to Windows

About truecrypt-drive: solved. Thanks to my friend. Yepee. smile

But booting to Windows is still a problem. sad

Edit: FIXED! Problem was that grub was installed on encrypted partition (/dev/sda). When partition was fixed, booting was fixed. However, I had to change (hd1,2) to (hd0,2), even if Windows is located to /dev/sdb3 (this solution did not work before encrypted partition was fixed).

Last edited by Exitium (2009-01-29 14:42:16)

Offline

Board footer

Powered by FluxBB