linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: cs <cs@networkingnewsletter.org.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: RE: [linux-lvm] won't dual boot: 2 disks and LVM
Date: Wed, 19 Dec 2007 10:25:09 +0000	[thread overview]
Message-ID: <1198059909.3859.21.camel@amd64.local> (raw)
In-Reply-To: <1198059645.4768f07d37201@imp.free.fr>

On Wed, 2007-12-19 at 11:20 +0100, Georges Giralt wrote:
> Selon cs <cs@networkingnewsletter.org.uk>:
> 
> > On Tue, 2007-12-18 at 16:52 -0500, pham_cuong@emc.com wrote:
> > > There is a difference between changing the boot order from the BIOS vs.
> > > [physically] removing the master HD.  Here's why:
> ...............Usefull stuff snipped............
> > > Regards,
> > >
> > > Confucius
> >
> > useful stuff but I'm still unsure why if I change the order in BIOS then
> > (when I had it working a bit) it would start the XP boot sequence (and
> > not the GRUB from master) but then hang indefinitely...
> Hi !
> Let me chime in here as I've faced the same problem you've got.
> My PC has a lot of disks, some of them for Fedora/LVM/mirror install, some of
> them for Mandriva/Ubuntu install and one with Windows XP.
> The problem I encountered came from ...guess what ? Windows XP installation.
> Here is a _short_ HowTo.
> 1) open you PC and let ONLY one disk into it as MASTER (if IDE) and install
> Windows/XP.
> 2) Double check that the Windows/XP boot section specify only this disk.
> 3) Test that you can boot Windows/XP in this particular configuration.
> 4) Return PC hardware as it should be.
> 5) double check that you Linux/LVM config boots fine.
> 6) modify the Grub.conf file to have Windows/XP believe it is on first disk/only
> disk using map() command.
> 7) double check Windows/XP boots fine.
> If you do a Windows/XP install with another configuration than above, you will
> have some references to this configuration in the registry/boot config...etc and
> won't be able to run  XP¨again. Also be sure to wipe clean the Windows/XP disk
> before installation, otherwise, you know what....
> This is just "been there, done that" .... kind of PITA I had.
> And, of course, YMMV.

that does seem the only safe way but I'm still struggling to understand
why!

Thanks, Michael

  reply	other threads:[~2007-12-19 10:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 14:28 [linux-lvm] won't dual boot: 2 disks and LVM michael
     [not found] ` <4768695F.29577.60F3E82@mikes.kuentos.guam.net>
2007-12-18 15:12   ` michael
2007-12-18 18:19 ` Joseph L. Casale
2007-12-18 19:15   ` michael
2007-12-18 19:37     ` Joseph L. Casale
2007-12-18 19:52 ` pham_cuong
2007-12-18 20:09   ` pham_cuong
2007-12-18 20:38   ` cs
2007-12-18 21:52     ` pham_cuong
2007-12-19  9:59       ` cs
2007-12-19 10:20         ` Georges Giralt
2007-12-19 10:25           ` cs [this message]
2007-12-19 14:33             ` pham_cuong
2007-12-19 15:44               ` Georges Giralt
2007-12-19 16:59                 ` pham_cuong
2007-12-19 18:04               ` michael
2007-12-18 23:02 ` Chris Cox
2007-12-19  9:57   ` cs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1198059909.3859.21.camel@amd64.local \
    --to=cs@networkingnewsletter.org.uk \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).