Re: SuSE 10.0 Issue #1
- From: imotgm <imotgm_REM@xxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Mar 2006 18:49:24 GMT
On Tue, 14 Mar 2006 09:17:56 -0800, Jeffrey Drake wrote:
My apologies.
/dev/sda3 / ext3 defaults
1 1
/dev/sda6 /home ext3 acl,user_xattr
1 2
/dev/sda1 /windows/C ntfs
ro,noatime,user,users,gid=users,umask=0002,nls=utf8 0 0
/dev/sda2 /windows/D ntfs
ro,noatime,user,users,gid=users,umask=0002,nls=utf8 0 0
/dev/sda5 swap swap defaults
0 0
grub was installed to sda3, without going to mbr. SuSE of course being
on sda3.
What is on the ATA drive?
This is not an idle question. On my box, I keep all Windows stuff on a
Windows only drive, completely isolated from Linux, which I have on a
number of drives, but physically isolated from Windows.
The Linux drives are hda, and hdc, and the Windows drive is sdb. By
placing grub in the MBR of hda, and setting hda as the boot disk, in
BIOS, I can boot either Linux or Windows, with ease, while not having to
worry about Windows repairs overwriting grub. If I remove the Linux
drives, Windows will boot normally, as it's MBR is untouched by Linux.
Conversely, I can remove the Windows drive, without affecting the Linux
boot process at all.
My drives are in removable drive bay caddies, so I do, in fact, remove
them frequently, and even share them with other machines. While you may
not wish to regularly remove drives, this type of setup is good insurance
against drive failure, where the failure of one drive, or the corruption
of one MBR renders all OSs unbootable. I would suggest that you move the
SUSE installation to the drive on hda, and install grub in the MBR of that
drive, for future safety.
Right now, and to the point, grub, as installed, through menu.lst, sees
sda as (hd1) but having set sda as the boot drive, in BIOS, BIOS sees sda
as (hd0) hence your problem. You could change all the references in
menu.lst from (hd1) to (hd0), or you could leave menu.lst alone, except to
change the Windows stanza to;
title Windows
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
makeactive
chainloader +1
then install grub to the MBR of hda, and set that as the boot disk, in
BIOS. This should enable you to boot either Linux or Windows from grub,
without overwriting your Windows MBR, and without having to jump through
the hoops of making Linux boot from the Windows boot.ini. Grub does a much
better job of handling chainloading than the ntldr/boot.ini combo. Grub,
by design, will boot multiple, and various OSs, including Windows, while
ntldr/boot.ini, by design, was only meant to boot Windows flavors.
If you're in the mood to experiment, try the suggestion to change the
Windows stanza in menu.lst, and install grub to the MBR of hda. Once you
see that Windows, as well as SUSE, can be safely booted from (hd1) you
might want to consider what I said about using separate disks for each,
and moving the SUSE installation to hda.
--
imotgm
"Lost? Lost? I've never been lost... Been a tad confused for a
month or two, but never lost."
.
- References:
- SuSE 10.0 Issue #1
- From: Jeffrey Drake
- Re: SuSE 10.0 Issue #1
- From: imotgm
- Re: SuSE 10.0 Issue #1
- From: Jeffrey Drake
- SuSE 10.0 Issue #1
- Prev by Date: Re: SuSE vs Ubuntuu
- Next by Date: Re: SuSE vs Ubuntuu
- Previous by thread: Re: SuSE 10.0 Issue #1
- Next by thread: Re: SuSE 10.0 Issue #1
- Index(es):
Relevant Pages
|
Loading
