Changing grub loader to another hdd

[markovski]

I have two HDD`s. On the first i have installed Windows, on the second PCLOS. When i installed linux, set the grub loader to master boot from the windows HDD.
So now the Grub is installed on the Windows HDD. How to change it to the linux HDD?

[Old-Polack]

I have two HDD`s. On the first i have installed Windows, on the second PCLOS. When i installed linux, set the grub loader to master boot from the windows HDD.
So now the Grub is installed on the Windows HDD. How to change it to the linux HDD?

http://www.pclinuxos.com/forum/index.php/topic,62786.msg508062.html#msg508062

[markovski]

Ive done that what you posted, grub loader now shows without the fancy graphics(the pcolos image).
There are entries but none of them work like they should. This is the menu.lst in the Linux hdd:

Code:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd1,0)/boot/gfxmenu
default 0

title linux
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=10efa168-2ab9-42d5-9fef-$
initrd (hd1,0)/boot/initrd.img

title linux-nonfb
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=10efa168-2ab9-42d5$
initrd (hd1,0)/boot/initrd.img

title failsafe
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=10efa168-2ab9-42d5-9f$
initrd (hd1,0)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

hd0 is windows, and hd1 is linux

[Bald Brick]

Waiting for the return of O-P I couldn't help noticing that all the lines in your menu.lst are cut off at 80 characters. That can't be intentional.

[shrinivas]

I suggest that using Windows installation disk, repair the windows boot so that only windows bootloader is on first HDD (hd0)
Then using the PClinuxOs CD/DVD, redo the MBR and install the bootloader into the root of the Linux installation, it automatically recognizes the Windows installation. In the bootloader setup, specify that you will be booting from the HD1.
Then in the BIOS, set it to boot from from the second hard disk (HD1) where PClinuxOs is installed.
That way, both Windows an Linux are safe from each other.

[markovski]

I suggest that using Windows installation disk, repair the windows boot so that only windows bootloader is on first HDD (hd0)
Then using the PClinuxOs CD/DVD, redo the MBR and install the bootloader into the root of the Linux installation, it automatically recognizes the Windows installation. In the bootloader setup, specify that you will be booting from the HD1.
Then in the BIOS, set it to boot from from the second hard disk (HD1) where PClinuxOs is installed.
That way, both Windows an Linux are safe from each other.

The windows repair didnt worked. The boot loader is still in HD0.

OK how to delete the current grubs and install it again in hd1?

[Old-Polack]

Ive done that what you posted, grub loader now shows without the fancy graphics(the pcolos image).
There are entries but none of them work like they should. This is the menu.lst in the Linux hdd:

Code:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd1,0)/boot/gfxmenu
default 0

title linux
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=10efa168-2ab9-42d5-9fef-$
initrd (hd1,0)/boot/initrd.img

title linux-nonfb
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=10efa168-2ab9-42d5$
initrd (hd1,0)/boot/initrd.img

title failsafe
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=10efa168-2ab9-42d5-9f$
initrd (hd1,0)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

hd0 is windows, and hd1 is linux

Not any more. When a drive becomes the boot drive, it becomes (hd0). From the system's viewpoint, that is the definition of "boot drive."

Your /boot/grub/menu.lst must be edited so each instance of (hd1,0) becomes (hd0,0) for all the Linux entries, while the Windows stanza needs to become;

title windows
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
makeactive
chainloader +1

The menu.lst file must be edited as root, so the changes can be saved. With these changes, and the Linux drive set as the boot drive both OS should then boot properly.

[markovski]

Ive done that what you posted, grub loader now shows without the fancy graphics(the pcolos image).
There are entries but none of them work like they should. This is the menu.lst in the Linux hdd:

Code:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd1,0)/boot/gfxmenu
default 0

title linux
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=10efa168-2ab9-42d5-9fef-$
initrd (hd1,0)/boot/initrd.img

title linux-nonfb
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=10efa168-2ab9-42d5$
initrd (hd1,0)/boot/initrd.img

title failsafe
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=10efa168-2ab9-42d5-9f$
initrd (hd1,0)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

hd0 is windows, and hd1 is linux

Not any more. When a drive becomes the boot drive, it becomes (hd0). From the system's viewpoint, that is the definition of "boot drive."

Your /boot/grub/menu.lst must be edited so each instance of (hd1,0) becomes (hd0,0) for all the Linux entries, while the Windows stanza needs to become;

title windows
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
makeactive
chainloader +1

The menu.lst file must be edited as root, so the changes can be saved. With these changes, and the Linux drive set as the boot drive both OS should then boot properly.

Well i didnt knew that, tnx for this now it works. I also changed the gfxmenu to hd0, to give me the fancy image. The linux now works, but the windows doesent. I will try to add the maps

Edit- It worked perfectly thanks OP

[Old-Polack]

Well i didnt knew that, tnx for this now it works. I also changed the gfxmenu to hd0, to give me the fancy image. The linux now works, but the windows doesent. I will try to add the maps

Edit- It worked perfectly thanks OP

Was there ever any doubt? 

[uncleV]

Have a little doubt but...
... worked here too, thank you.