Re: installation puzzle
- From: Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 18 Jan 2007 18:57:55 GMT
In message <%bCrh.2466$jG1.82@trnddc04>
"Ben Crain" <bcrain@xxxxxxxxxxx> wrote:
I finally decide to try Linux -- via the distribution that comes with the
book "Suse Linux 10 Unleashed" (by Michael McCallister). My current setup:
running Windows XP, with two hard drives in a RAID configuration, and also a
separate third hard drive (or, really, second hard drive, since the two RAID
drives are functionally just one). I try to install Linux from the DVD that
comes with the book, and soon get an error message that says something like
(I paraphrase): "A harddrive is detected with a RAID configuration which
the BIOS says is a hardware RAID but it's really a software RAID". (I
swear, that's what the message said!) "If you install Linux on that
harddrive it will destroy the RAID".
But I was planning to install Linux on the separate harddrive which has no
RAID configuration, so I just ignored that message and proceeded. By
selecting "Custom Partionining", or whatever it was called, I got to the
point of being able to designate that Linux would be installed on my second,
separate, non-RAID-infested harddrive. It then began the base installation,
which seemed to proceed smoothly. According to the book, after the base
installation it would proceed to the task of "Creating the root User". But,
what actually happened: it acted as though the computer were being
re-booted, and showed the Suse installation setup screen once again (though
this time with more colors). But not for long: while I was staring at it
trying to figure out what was going on, that screen vanished and WinXP
booted normally. I then removed the Linux DVD and rebooted, and it just
goes directly to WinXP, which operates normally. Except it can't access
that second drive, which, according to PartitionMagic, has indeed been
formatted for Linux.
But the book says (pg 36): "If YaST detects the presence of another
operating system, it will ask whether you want to replace that OS with SUSE
Linux or dual boot both." Yes, I do want to dual boot, but it never asked
me that. Perhaps it would have after the base installation, but instead it
re-booted itself into Windows.
I did try installing anew, and everything proceeded as above (with the same
error messages about RAID), until at some point in the base installation the
entire system froze. No mouse movement, no nothing. So I shut down the pc
and gave up on this installation. Any ideas?
I'm no expert. However, based on what I've read, the way it arranges
dual boot is that it replaces the Windows "startup" on the primary
drive with one which launches Grub. Grub is automatically configured
to offer a choice between Liunux and Windows.
Now this means altering the MBR of the primary drive, which it has
already decided is a RAID configuration it doesn't know how to touch.
I'm not surprised it hasn't altered the boot setting.
I *think* there is a way to make the Windows boot loader offer Linux -
it will involve editing BOOT.INI, but I don't know the details. That
would be an alternative for you.
Alan
--
Alan Adams, from Northamptonshire
alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.
- References:
- installation puzzle
- From: Ben Crain
- installation puzzle
- Prev by Date: Re: how to turn off beep sound on console mode?
- Next by Date: Re: Ubuntu Linux books and Unix book question
- Previous by thread: Re: installation puzzle
- Next by thread: mdadm raid array boot by it's UUID in GRUB
- Index(es):
Relevant Pages
|
