----- Original Message ----
From: Bean <address@hidden>
To: The development of GRUB 2 <address@hidden>
Sent: Friday, 8 August, 2008 12:10:24 PM
Subject: Re: Windows boot
On Fri, Aug 8, 2008 at 2:22 PM, Viswesh S <
address@hidden> wrote:
>
>
> ----- Original Message ----
> From: Bean <
address@hidden>
> To: The development of GRUB 2 <
address@hidden>
> Sent: Friday, 8 August, 2008 9:13:09 AM
> Subject: Re: Windows boot
>
> On Fri, Aug 8, 2008 at 9:58 AM, Viswesh S <
address@hidden> wrote:
>>
>>
>> ----- Original Message ----
>> From: Javier Martín <
address@hidden>
>> To: The development of GRUB 2 <
address@hidden>
>> Sent: Friday, 8 August, 2008 3:56:35 AM
>> Subject: Re: Windows boot
>>
>> Hi again,
>>
>> 2008/8/7 Viswesh S <
address@hidden>:
>>> Hi,
>>>
>>> I installed ubuntu in the same harddisk(hda) as windows.
>>>
>>> After installing ubuntu, using grub legacy, I was able to log in to
>>> windows,
>>>
using the entries, rootnoverify and chainloader +1.
>>>
>>> But when I install grub2 and then modify the grub.cfg with the following,
>>> statements, it is not working, says ...A disk read error occurred ,Press
>>> Ctrl+Alt+Del .
>>>
>>> This is my grub.cfg
>>>
>>> menuentry "Windows" {
>>> set root=(hd0,3)
>>> chainloader +1
>>>
>>> }
>>>
>>> My windows file sytem is in NTFS and not vfat
>>>
>>> One more thing to check with is, the need of ntfs mod present as part of
>>> grub2.So where exactly that is getting used,though I have tried to load
>>> the
>>> module ntfs and ntfscomp in grub using insmod in grub menu,...but no
>>> positive results.
>> The FS only matters if you try to
access files on the volume, but
>> chainloader just reads raw sectors from disk, so the FS module does
>> not matter: you could have an SFS partition for the sake of it and it
>> would work if the superblock was executable.
>>>
>>> What might be in grub2, which prevents windows to boot.
>> Hmm... you could try booting (hd1) instead of (hd1,1), i.e. Windows'
>> MBR instead of its boot sector directly. I'll be back in town tomorrow
>> night and then I'll be able to look at my own GRUB config file, but
>> Windows has always been a wild beast to master. For the record, my
>> tests were with Windows XP Home in an Athlon X2 and with Windows XP
>> x64 on an Athlon 64. Thus, I don't know if Intel CPUs triple-fault on
>> my code (improbable, because it runs on QEMU) or if Windows Vista
>> (which has a changed boot process) works with
it.
>>
>>
>> Hi,
>>
>> Windows I am trying to boot is Windows Server 2003, but anyway that doesnt
>> matter, as from legacy grub,I am able to boot.This makes it more
>> interesting, as I feel we are missing some small intricacy in grub2 in
>> this
>> case.
>>
>> Let me also have a look.
>
> Hi,
>
> What's the command you use in grub legacy ?
>
> BTW, you should know that device number of grub2 is not the same as
> grub legacy, the first partition is (hd0,1) instead of (hd0,0).
> Anyway, you can use ls to list the current devices.
>
> --
> Bean
> Hi,
>
> The partition number difference I am aware of.That difference was taken into
> account.
>
> In the case of grub legacy,the grub.cfg was in this way.
>
> menuentry "Windows" {
>
>
rootnoverify
> chainloader +1
> }
>
> As windows is in the 3 partition, using ls (hd0,3) I could see windows
> files.
>
> so the grub.cfg
>
> menuentry "Win" {
>
> chainloader (hd0,3)+1
> }
>
> (or)
>
> menuentry "Win" {
> set root=(hd0,3)
> chainloader +1
> }
>
> Tried both the combinations.But not working, getting the message ." A disk
> read Error occurred
>
> Press Ctrl+Alt+Del to restart.
>
> I am not sure whether this is a filesystem issue (ntfs) which grub2 is not
> able to identify as such (or) Grub2 is not able to read the boot sector
> correctly.( As legacy grub was able to boot quite easily the same thing)
>
> I am badly stuck and I dont want to go back to legacy grub
also.
Hi,
I think it's not related to ntfs, chainloader command read the first
sector, it doesn't matter what file system is used.
But I do remember a small issue with chainloader command of grub2, the
partition entry pointed to by %esi is not correct, I wonder if this
have something to do with your problem.
Thanks,let me have a look at the chainloader command in grub2 and in legacy grub.
Could you let me know the issue which you faced in the chainloader command.