OS: SuSE 10.0 Other OS: Win95 Disk: One EIDE Partitions: hda1 Win95 hda2 Linux Swap hda3 SuSE 10 This was originally a Win95 system but I shrank the FAT32 to 500+Mb and installed SuSE. Everything worked fine but I wanted to be sure no one booted Win95 so I used the YaST Boot Loader module to delete the Win95 section. Now I want to put it back and have managed to get to the point it says "Grub Loading Stage 2". Then several messages flash by and it goes back to the menu. Questions: 1. Does grub log these messages anywhere? Where? 2. Alternatively, can it be forced to halt instead of continuing? BTW, the Windows section of menu.lst is: unhide (hd0,0) rootnoverify (hd0,0) chainloader +1 makeactive boot from the "info grub" section on DOS/Windows. Thank you, Lucky Leavell
On Thursday 02 February 2006 23:33, Lucky Leavell wrote:
BTW, the Windows section of menu.lst is:
unhide (hd0,0) rootnoverify (hd0,0) chainloader +1 makeactive boot
from the "info grub" section on DOS/Windows.
The chainloader +1 command starts the whole boot process so it never sees the remaining two statements. Put the makeactive prior to the chainloader and delete the boot. Not needed. That at least may help.
** Reply to message from Bruce Marshall <bmarsh@bmarsh.com> on Fri, 03 Feb 2006 08:47:21 -0500
BTW, the Windows section of menu.lst is:
unhide (hd0,0) rootnoverify (hd0,0) chainloader +1 makeactive boot
from the "info grub" section on DOS/Windows.
The chainloader +1 command starts the whole boot process so it never sees the remaining two statements. Put the makeactive prior to the chainloader and delete the boot. Not needed.
That at least may help.
I dual boot all the time and I only have 2 lines for Windows in /boot/grub/menu.lst title Windows chainloader (hd0,0)+1 Ed Harrison, Linux User # 199533 SuSE10.0, Kernel 2.6.15 PolarBar Mailer 1.26
On Fri, 3 Feb 2006, Ed Harrison wrote:
** Reply to message from Bruce Marshall <bmarsh@bmarsh.com> on Fri, 03 Feb 2006 08:47:21 -0500
I dual boot all the time and I only have 2 lines for Windows in /boot/grub/menu.lst
title Windows chainloader (hd0,0)+1
This is what YaST created when we first tried to put it back but only resulted in a blank blue screen I am thinking of taking the installation CDs over there (25+ miles away) and doing a system check/repair. It worked fine until I deleted the Windows section and then tried to put it back. Thank you, Lucky
On 03/02/06 20:31, Lucky Leavell wrote:
On Fri, 3 Feb 2006, Ed Harrison wrote:
** Reply to message from Bruce Marshall <bmarsh@bmarsh.com> on Fri, 03 Feb 2006 08:47:21 -0500
I dual boot all the time and I only have 2 lines for Windows in /boot/grub/menu.lst
title Windows chainloader (hd0,0)+1
This is what YaST created when we first tried to put it back but only resulted in a blank blue screen
I am thinking of taking the installation CDs over there (25+ miles away) and doing a system check/repair. It worked fine until I deleted the Windows section and then tried to put it back.
Run "fdisk -l /dev/hda" and see if there is a * in the "boot" column for the hda1 line. If not, then you need a "makeactive" command in the grub menu entry. This must be put between the "rootnoverify" and "chainloader" commands.
On Sun, 5 Feb 2006, Darryl Gregorash wrote:
On 03/02/06 20:31, Lucky Leavell wrote:
and doing a system check/repair. It worked fine until I deleted the Windows section and then tried to put it back.
Run "fdisk -l /dev/hda" and see if there is a * in the "boot" column for the hda1 line. If not, then you need a "makeactive" command in the grub menu entry. This must be put between the "rootnoverify" and "chainloader" commands.
/dev/hda1 is active but fdisk shows the type as "b"? I did a system repair and the fstab section for /dev/hda1 (the Win 95 FAT32 partition) as removed (actually marked Ignore). The boot loader part removed then all references to the Windows section. It would appear that my removing the Windows section from grub (via YaST) somehow damaged the Windows partition such that it can no longer boot. (Is this possible?) (I thought I was simply removing that section of menu.lst and nothing more serious BUT Windows is rather fragile! Methinks I have two or three options: 1. Run Repair again, replacing the original MBR 2. Try switching to LILO 3. Start over reinstalling from scratch and then SuSE (changing partition sizes in the process) Comments or Suggestions? Thank you, Lucky
participants (4)
-
Bruce Marshall -
Darryl Gregorash -
Ed Harrison -
Lucky Leavell