[gobolinux-users] mailto:gobolinux-users%40lists.gobolinux.org?Subject=%5Bgobolinux-users%5D%20Grub%20%2B%20SATA%20%3D%20Error%2017%3F&In-Reply-To=49e748a90701020934n1319f257h948614bcb5f03f18%40mail.gmail.com

[Lucas C. Villa Real]

On 1/8/07, molfar <molfar.ua at gmail.com> wrote:
> However the question remains - why was menu.lst generated wrong? To be more
> precise - why didn't grub write over mbr in the first place, and secondly -
>  why didn't it generate proper menu.lst when I set it up manually? I mean -
> now that I recall all the steps I made during installation I still fail to
> see where my possible mistake was (it doesn't mean there wasn't any).
> Still - if it helps you to pinpoint the issue in future - my hdd was
> originally partitioned like this:
> part1 (C:\, NTFS, primary active) (detected as sda1)
> part2 (D:\, NTFS, primary) (detected as sda2)
> ---extended---
> part3 (Linux Swap) (detected as sda5)
> part4 (Ext3, /) (detected as sda6)
>
> When setting it up manually from livecd I did:
> grub> root (hd0,5)
> grub> setup --prefix=/System/Kernel/Boot/grub (hd0)
> grub> quit
>
> Then it happened. Checking the issue as you've advised revealed that
> menu.lst contained wrong path to the kernel:
> ...kernel (hd0,4)/System/Kernel/...
> Booting manually from the command line and then editing menu.lst (to hd0,5)
> saved the day.

That probably is our fault.. could you please post the output for
'fdisk -l'? I'll try to create the same partition layout on a QEMU
image to reproduce/fix the bug.

> P.S. I'm still a noob in *nix universe, so if you consider this to be quite
> a lame issue, please, accept my apologies.

No problem, good to know that your problem is gone now.

-- 
Lucas
powered by /dev/dsp