Re: Active Migration...
Re: Active Migration...
I have been thinking about these concepts since you brought them up, but I
cannot make them fit entirely with what I know of the basic RAID technology.
Unless HP have employed some sort of Software RAID by which you can make
RAID do things it otherwise wouldn't - I am pretty much in the dark here. I
know if you type in "raid" in any search engine you'll get more hits than
you want, it could pay off, a lot of that is good info - I still think you
should e-mail HP tech support. They are nice folks if you address them in
plain and level-headed language, and since you have seen BSOD's, you do have
an issue for them to tackle. Phoning the call-centre will probably be a
waste.
As I have implemented it, the Hard drives show in BIOS setup as two drives.
This is before the driver is read into memory, in the RAID manager I only
see the RAID and in Windows device manager I only see the number of
partitions that I created on the one drive that is the RAID.
Tony. . .
"Seidell23231" <Seidell23231@discussions.microsoft.com> wrote in message
news:8CA3B00F-EFF7-4033-B612-D2DCDBF99BBA@microsoft.com...
> OK, I have the RAID 0 array setup and the Matrix Console Manager says
Status
> is nornal. OK, so if RAID 0 is "Striping" shouldn't it now be writing to
> both HD's?? In Disk Management and Computer, Both HD's are displayed, but
in
> Disk Management both HD's are positioned in line with Disk 0 and Disk 0
shows
> the combined values.
>
> So, if I am copying a huge block of data from my external drive to my C
> drive, shouldn't the status change from NO active migration to YES active
> migration? Additionally, shouldn't the 2nd HD show a value, something,
> anything? It shows 0, NO data displayed............
>
> THOUGHTS???? Joey
>
>
>
> "Tony Sperling" wrote:
>
> > O.K. - the fogs are clearing now - it seems to me that your second
account
> > of your experience is the technologically correct one - that is how I
would
> > expect it to look.
> >
> > This is the trouble with brand-name products - they have completely
> > proprietary ways of doing things their own way. Normally, you cannot
convert
> > a 'Live' system from non-RAID to RAID - so, HP found a way, and now we
have
> > to iron out the wrinkles.
> >
> > Fortunately (for us!) if you have BSOD's doing it the HP way, I think
you
> > should call up, or e-mail their support and have a technician explain
their
> > proprietary philosophy 'en-lieu' these BSOD's. It is hard to make
> > suggestions for something this alien.
> >
> > The only way I can explain the two 'blocks' (as you say) is if they have
> > each disk configured as a separate partition in the RAID set. This would
be
> > odd for a default setup but perfectly in order! Or, if the original
non-RAID
> > partition is not actually converted but sits there serving as a rescue
> > partition, but also, still non-RAID!
> >
> > Gosh, Joey! I really don't know, I have very good experience from HP
> > notebook and printers but I would never buy a brand-name desktop, and
for
> > this very reason. But here you are, and I think you should e-mail their
tech
> > support directly and have them explain this, because this is beyond the
> > normal 'oddities' - this is outright freakish!
> >
> >
> > Tony. . .
> >
> >
> >
> > "Seidell23231" <Seidell23231@discussions.microsoft.com> wrote in message
> > news:39D7821A-AC6E-429D-BA03-33C950A59A90@microsoft.com...
> > > Tony & Carlos,
> > >
> > > OK, here are the results thus far and the problem, if there is one.
The
> > > RAID is down and when I boot up the system it displays the RAID
Controller
> > > and it reports all ok. When I get into the desktop, I went into
> > "Computer"
> > > to see if it was still listing each drive as seperate. It is! I then
> > went
> > > to Disk Management. It has both drives in the Disk 0 slot and the
size
> > > showing is the combination of both. But they are showing as seperate
> > blocks
> > > of space in Disk 0.
> > >
> > > The only problem I see at this stage is what the "Computer" is
displaying.
> > > It should have just one block with both combined, RIGHT?
> > >
> > > Now here is where the BIG difference comes in. If I disregard the
> > > instructions that came with the system, as described in my prior
message
> > and
> > > do it manually, I get a different story. Explaination = I reboot the
PC.
> > > When the RAID Controller screen displays, I press ctl+I and enter the
RAID
> > > Controller menu. Next I Delete the RAID and ALL data. I Reboot and
when
> > the
> > > RAID Controlle display appears I enter the Controller. This time I
Create
> > a
> > > RAID 0. Again, Reboot and insert Disk 1 of the Recovery Disks. The
> > System
> > > goes through the paces as a recovery and loads all data showing Fresh
from
> > > the Factory. The PC Reboots, the RAID Controller displays the RAID 0
and
> > I
> > > reach the Desktop. When I enter the "Computer" only 1 HD id
displayed.
> > NO
> > > mention or indication of a second. I now go into Disk Management,
Disk 0
> > > shows the combined drives, but there is NO block indicating a second
drive
> > > ever existed. Everything looks as it should, drive wise that is.
> > >
> > > However, I was getting a lot of BSOD with this method. Most
referencing
> > > show to do with a POINTER and than does a dump! I have not tried this
> > method
> > > since upgrading to 7.8, so not sure if BSOD are still an issue?
> > >
> > > My QUESTION at this point is this.... I have followed the Directions
as
> > per
> > > HP and built the RAID. So why is there a HD issue, meaning why is the
> > second
> > > drive showing in "Computer" and partially in Disk Management. Can
someone
> > > explain that parrt and is it an issue or not?????
> > >
> > > Thanks! Joey
> > >
> > >
> > >
> > > "Tony Sperling" wrote:
> > >
> > > > I am not quite sure of your current status - I will go through the
> > > > philosophy. . .
> > > >
> > > > First principle:
> > > >
> > > > You define a RAID set as a completely new set of HD's with nothing
on
> > them,
> > > > this is done in the RAID chip's BIOS or the expansion card's BIOS,
if
> > you
> > > > then supply the correct drivers that is compatible with and
supported by
> > > > your OS during the installation of the OS your RAID set will be
> > recognized
> > > > by that OS's installer.
> > > >
> > > > This is where I become uncertain - if you try and convert an
installed
> > > > non-RAID system to a RAID set, then you are going to fail, because
> > > > configuring the RAID will definitely delete all data on all the
disks
> > that
> > > > are being configured as belonging to the RAID.
> > > >
> > > > If you are trying to install an OS to a RAID set that is allready
> > configured
> > > > and has an installed system that is up and running you do not touch
that
> > > > RAID configuration at all! The only requirement is that you supply
the
> > > > driver to the installer that the other OS expects in order to
recognize
> > the
> > > > RAID. The fact that you have configured a RAID and has installed one
> > system
> > > > on to that RAID will not let another OS that you are trying to
install
> > onto
> > > > that same RAID be recognized by the second installer and using the
other
> > > > system's driver!
> > > >
> > > > You have to supply the driver every time. This mean that you can
install
> > a
> > > > Windows system on the RAID and if you have the space you can install
a
> > Linux
> > > > system next to it, and each one can be 32bit or 64bit as you wish if
you
> > > > just make sure that you supply the correct driver for each system
and
> > for
> > > > each new installation, in order for the installer to know there is
HD
> > space
> > > > that it can use! The installer doesn't know about RAIDs, it just
know
> > about
> > > > HD's and the driver makes the RAID visible to the installer and
later to
> > the
> > > > OS as well.
> > > >
> > > > The IDE specification and SCSI and all other specifications have
precise
> > > > definitions of how data is written to and read from each of these
types
> > of
> > > > disks. RAID has no knowledge of IDE or SCSI or anything else except
it's
> > own
> > > > RAID definition. Nothing else in the known universe knows anything
about
> > > > RAID except the RAID and this is why you have to supply the correct
> > driver
> > > > each time.
> > > >
> > > > You may already know all this - I just think it is important that
you
> > don't
> > > > f*ck anything up for yourself at this point, because of a simple
> > > > misconception!
> > > >
> > > >
> > > > Tony. . .
> > > >
> > > >
> > > >
> > > >
> > > > "Seidell23231" <Seidell23231@discussions.microsoft.com> wrote in
message
> > > > news:84CD4939-F7E5-4B02-8DE0-4559FC917D58@microsoft.com...
> > > > > RAID 0 Questions:
> > > > > 1. What reading do you recommend regarding RAID 0? I want to get
> > fully
> > > > > locked in on the RAID world and to do this, I need some sources
> > (Reading
> > > > > wise).
> > > > > 2A. This is a little difficult to explain, but here we go. My PC
has
> > > > RAID
> > > > > 0 & 1 ability. The software side "Intel Matrix Storage Console".
The
> > > > > paperwork that came with the system states this method to use
> > (Obviously
> > > > at
> > > > > this point the OS and drivers and all software is already
installed).
> > > > > However, when I use this method, I do NOT get the HD's combined
> > (Viewing
> > > > that
> > > > > is) in my Computer screen or the Computer Management area), but
the
> > Intel
> > > > > Matrix Storage Console shows and states they are combined. **This
> > deletes
> > > > > everything from the RAID drives!
> > > > > 2B. When I boot up my PC the RAID controller displays that status
of
> > the
> > > > > RAID and all pertinent information. Now if I "DELETE" the RAID
> > created in
> > > > > step 2A and then save and exit and do another Reboot and enter the
> > RAID
> > > > > controller area and CREATE a RAID 0, save and exit. I am than
> > prompted to
> > > > > insert a system disk. I than insert disk 1 of the recovery disks.
> > Once
> > > > all
> > > > > loaded and finally reach the desktop, ALL drives are ONE drive.
NO
> > where
> > > > is
> > > > > there any reference of the 2nd disk! So this is how it is suppose
to
> > look
> > > > > from what I have learned here. Everything works, system is
snappier;
> > > > > HOWEVER, I start getting the BSOD! Where I never got them before
I am
> > > > now!
> > > > > The only deduction I can summorize from this is tha the OS is
Striped,
> > > > > opposed to being on 1 HD in one specific place as in 2A above.
> > > > >
> > > > > I need some thoughts on this and maybe some helpfull pointers on
how
> > to
> > > > > overcome the obstacles as stated in the above questions.
> > > > >
> > > > > Thanks in Advance!! ~~~~ Joey
> > > >
> > > >
> > > >
> >
> >
> >
