Author Topic: PCLinuxOS doesn't boot after last update (dualbooting with w7 using EasyBCD)  (Read 4283 times)

Offline nixus

  • Full Member
  • ***
  • Posts: 113
In my case # of course ;-)

now I get this:

Code: [Select]
grub> find /boot/grub/stage2
 (hd0,4)

and yes I have a separate boot partition sda1 which I suppose is h0,0.

Would it be correct to do the following. Please check, just to be on the save side :-)

grub> find /boot/grub/stage2                          <Enter>
 (hd0,4)                                   <-- Yours will vary depending on where Linux is installed. Use your results for next command.

grub> root (hd0,4)                             <Enter>
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0)                         <Enter>
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0)"...  15 sectors are embedded.
succeeded
 Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p (hd0,4)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.

grub> quit                                     < Enter>

[root@localhost ~]#

regards,
nixus


That would be the correct procedure if you want the grub on (hd0,4) to be the master grub. If you want the one on (hd0,0) to be the master grub, which is what most people with a boot partition want, you would use that as your root; ie    root (hd0,0)

Did you try;

grub> find /grub/stage2

to see  if the grub on (hd0,0) is recognized?


Just for clarification:

I only have one grub installation in sda5/hd0,4 this is also the PCLOS root partition.
In sda1/h0,0 initially the windows boot loader was installed, which I replaced with the EasyBCD boot loader. The EasyBCD boot loader either boots into win7 or points to grub and boots PCLOS.
So what I am intending to do is to replace the EasyBCD boot loader with the master grub installed in hd0,4.

I posted my menu.lst here (from hd0,4):
http://www.pclinuxos.com/forum/index.php?PHPSESSID=v3n5sl4mkujoltn090d3ikv3g6&topic=95709.msg808532#msg808532

I am not 100% sure if the above does what I am intending to do, and then being able to dual boot win7 and PCLOS.

regards,
nixus

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
nixus:

In this case it really makes no difference, but the fact is you do not have a boot partition; you have a typical Windows installation and a Linux Installation. No dedicated boot partition at all. Saying you have a boot partition, when you do not, only adds confusion to the conversation.

In the Unix/Linux world a boot partition is a separate small partition, typically 100 MB or less, but can be more if needed, that holds copies of all the kernels and initrd images needed to boot all the installed operating systems on the computer, and usually it is placed as the first partition on a hard drive. While Linux itself can boot from any partition it is installed on, older BIOS, and the old LILO boot loader, could only see the first 1024 cylinders of the drive, so on larger drives, with installations above that range, a boot partition was a necessity; ie all Linux kernels had to be found within that range or they couldn't be found at all, so placing them in the (hd0,0) partition insured they could be found and loaded. Once loaded the kernel could see the entire drive, and use / partitions above the 1024 cylinder BIOS/LILO limit.

Newer BIOS, and the Linux boot loaders no longer have this limitation, but boot partitions are still common with muli-booting Linux systems. Though not a necessity anymore, they are good insurance, in that all installations can be booted from two separate locations on the drive; the / partition or the boot partition. Should the kernel or initrd image in one location become corrupt, the system can still be booted using the other copies of the kernel and initrd image in the second location.

All my hard drives have a boot partition and at least one operating system installed, with grub installed to the MBR of each drive. I can therefor designate any of my hard drives as the boot drive, in BIOS,and there will be at least one bootable system available. My master menu.lst for each hard drive has boot stanzas for all of the installations on all of the hard drives, but each drive can actually be used independent of all the others if I wish. Before USB drives became bootable in BIOS, I had all my drives in removable drive bays, so I could pick and choose which to place in any computer at any time and still have a fully bootable system if I only chose to have any one drive present. Now most of my drives are in USB/E-SATA external enclosures so I have the same flexibility on more modern computers.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline nixus

  • Full Member
  • ***
  • Posts: 113
Sorry for any confusion caused. However hd0,0 is at least called boot partition at my HD and is 300 MB in size. w7 is actually installed in hd0,1/sda2. I should have mentioned this. Sorry again.

I have three primary partitions: sda1 (boot partition) sda2 w7 and sda4 with some HP specific tools.
0ne logic partition: with sda5 (linux root), sda6 swap, sda7 (linux home) and sda8,9,10 ntsf data partitions.

I was also a little confused because in the menu.lst windows is listed as hd0,0, which might be because of the EasyBCD boat loader. I don't actually know. That's why I am a bit hesitant to just use grub from hd0,4 as master grub.

regards,
nixus

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Sorry for any confusion caused. However hd0,0 is at least called boot partition at my HD and is 300 MB in size. w7 is actually installed in hd0,1/sda2. I should have mentioned this. Sorry again.

I have three primary partitions: sda1 (boot partition) sda2 w7 and sda4 with some HP specific tools.
0ne logic partition: with sda5 (linux root), sda6 swap, sda7 (linux home) and sda8,9,10 ntsf data partitions.

I was also a little confused because in the menu.lst windows is listed as hd0,0, which might be because of the EasyBCD boat loader. I don't actually know. That's why I am a bit hesitant to just use grub from hd0,4 as master grub.

regards,
nixus

When you are in the process of booting to your Linux installation, and get to the grub boot menu, have you ever tried to use the Windows option? Does it then actually boot your Windows installation? If it does, there should be no problem using it as the primary boot loader installed to the MBR.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline nixus

  • Full Member
  • ***
  • Posts: 113
Selecting the windows option of the grub loader just kicks me back to the EasyBCD boot loader.
Would changing the windows entry in menu.lst from hd0,0 to hd0,1 work?

thanks,
nixus

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Selecting the windows option of the grub loader just kicks me back to the EasyBCD boot loader.
Would changing the windows entry in menu.lst from hd0,0 to hd0,1 work?

thanks,
nixus

The only way to know is to try.

Right now you have EasyBCD handing off to grub to boot Linux. When you choose the Windows option in grub, it hands off to EasyBCD. The way you have things set, that seems to me to be the natural way it should work. When I had a triple boot with Win98, Win2K, and Linux, using grub as the primary boot loader, when Windows was selected, grub handed off to the Win2K boot.ini, where there was a pause as one chose which of the two Win installs to boot. With just a dual boot with Win2K and Linux, There was no hesitation when the boot.ini stage was reached because there was only the one choice.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline nixus

  • Full Member
  • ***
  • Posts: 113
Selecting the windows option of the grub loader just kicks me back to the EasyBCD boot loader.
Would changing the windows entry in menu.lst from hd0,0 to hd0,1 work?

thanks,
nixus

The only way to know is to try.

Right now you have EasyBCD handing off to grub to boot Linux. When you choose the Windows option in grub, it hands off to EasyBCD. The way you have things set, that seems to me to be the natural way it should work. When I had a triple boot with Win98, Win2K, and Linux, using grub as the primary boot loader, when Windows was selected, grub handed off to the Win2K boot.ini, where there was a pause as one chose which of the two Win installs to boot. With just a dual boot with Win2K and Linux, There was no hesitation when the boot.ini stage was reached because there was only the one choice.

Simply changing the windows entry in menu.lst from hd0,0 to hd0,1 doesn't work. I get the same result and it kicks me back to EasyBCD boot loader.
Any further thoughts on that?

I guess I will have to learn a lot more about boot loaders and how to configure them to boot a certain OS, in this case w7  ;-)

regards,
nixus


Offline nixus

  • Full Member
  • ***
  • Posts: 113
Just want to say thank you for all the great input.
Even though I haven't entirely solved my issue, which is only partly true because I can boot into PCLOS without any fuse, I again learnt a lot.
I will dig myself into grub and do some testing and see if I am able configure grub (menu.lst) correctly. Or I'll just wait for the 64-bit version and do a complete reinstall, letting grub handle the boot process.

thanks,
nixus