Re: M2N-SLI Deluxe - RAID issue?



On Jan 14, 6:45 pm, Paul <nos...@xxxxxxxxxx> wrote:
Christopher wrote:
On Jan 14, 2:40 pm, Fitz <akf...@xxxxxxx> wrote:
Mista Mista (CNorman) wrote:
I've just bought the M2N-SLI Deluxe board and am having trouble
getting the system to recognize the RAID 0 set up I have (two WD 80 GB
drives). Anyone else have similar issues?
I've created the RAID diskette and have followed the instructions/
directions, but when installing Windows, there is no recognized drive
for the system to install the OS to.
Ideas?
Did you enable RAID in the BIOS and create an array?

Fitz

Yeah, enabled RAID in the BIOS on SATA 1 & 2, created a striped array
and set it to boot. The array shows up healthy but isn't found when
trying to install XP! I booted off the XP disc, loaded the RAID driver
from the floppy (F6 when the XP install begins) and when it finally
comes to the install part, it says there aren't any volumes to install
XP on. Only option is to quit the install...

Odd. I've not seen this problem before.

- Christopher

Were the disks previously used for something else ?

I've had to erase a disk in Linux with "dd", before I could get
it to work right in Windows. The whole disk doesn't need to be erased.
Something like:

    dd if=/dev/zero of=/dev/hda count=10000 bs=512

You'd need to verify where the raw hard drive is located, to select
"hda" or whatever the correct name is for the raw drive. I can't
remember whether I did this using my Knoppix or Ubuntu boot CDs.
It was one of the two.

Then you'd go back to the BIOS, and set up the array again.

    Paul- Hide quoted text -

- Show quoted text -

I'm still hammering away at it. I've actually tried another RAID 0 set
that I have working in another computer and it's not booting from
their either. Since my initial posting, I've kept the array, but put
it secondary to a single HD install, just so I can get XP rolling.
Last night I noticed that the array was healthy and noticed by the
NVidia storage manager, but not in the Disk managent section of the
Computer Management snap-in. Also the Device manager is showing that
the RAID array isn't installed... and this is after I've installed
every driver I could squeeze out of the system boards' driver disc.

I'm going to play with it again tonight and see how I fare - just odd.
I've not had trouble like this before with a RAID config.

I'll post again when the computer's in front of me and am making any
headway.
.



Relevant Pages

  • Re: Need help installing OS6 on Dell PowerEdge 2600 with PERC4/Di RAID
    ... > like a fresh install and porting their application and data to the new system. ... PERC4/Di RAID on the motherboard, Dell DLT tape drive, Dell slimline ... PATA connector usable for two PATA drives. ... After downloading drivers from both SCO and Dell to create the ...
    (comp.unix.sco.misc)
  • [Summary] saving disksuite info while rebuilding server
    ... "Caution - If a full install of Solaris is performed, ... make sure you have tape backups of everything. ... I had an old workgroup storage array with six 18G drives formatted RAID5 ...
    (SunManagers)
  • Re: Problems with software RAID on SATA
    ... Connected to this are two 320GB drives ... >>which I want to turn into a RAID1 array. ... >>I'm almost certain it's a problem with initting the RAID arrays at boot. ...
    (Debian-User)
  • Re: RAID newbie...can I have several partitions on a RAID 1 array?
    ... You haven't expounded upon why you think you need raid. ... better backup device rather than buy 2 cheap RAID HBAs. ... RAID array then I would have to replace the mobo with the same one or at ... Lets say, for example, you buy 2 identical model drives, from ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: [PATCH 000 of 5] md: Introduction
    ... "why linux raid isn't Raid really, why it can be worse than plain disk") ... After this, the array ... error is in the filesystem, due to the complex layout of raid5. ... hundreds or 1000s of drives, you've quite high probability that some of them will fail sometimes, or will develop a bad sector etc). ...
    (Linux-Kernel)