This is odd...I just received my third M17xR2 (non-i7 920XM model). I moved my two 256GB SSD's (RAID 0 via Intel Option ROM) from my original M17xR2 into this new R2, and went into the BIOS and set it for RAID and enabled the Option ROM display. When I reboot, the Intel Option ROM shows both SSD's status as INCOMPATIBLE, and it doesn't boot. I move them back to the original R2 (Nebula Red one in my sig) and they show up fine and their status is NORMAL.
Both R2's have the same A05 BIOS and the same version of the Intel Option ROM.
What the heck??????![]()
Why can't I just move them? (and, no, I didn't mix them up, HDD0 and HDD1 bays are keyed and you cannot put a drive in the wrong bay when moving them).
Any ideas?
-
DaneGRClose Notebook Virtuoso
It's my understanding that there is an actual raid controller that can be different from one computer to the next even if they are the exact same model/revision. You may need to wipe/format the drives and start from scratch.
-
You should be ok with mirroring the RAIDed partition to an external drive, setting up the RAID as a new RAID with the same specs on your new machine, and then mirror the image back to the drives. TrueImage will work for this.
-
OP, There are two settings you need to change in the BIOS
first
1) RAID mode selection----set this to RAID 0
2) SATA Operation----- set this to RAID.
both are under the advanced tab I believe. After that, then you need to go into the Intel raid controller, create a new RAID volume, select RAID 0 and your stripe size (128K is the default) -
That was my other thought.. maybe he's not using the default stripe size. Other than that.. (shrug) should just work. I just gave him a last resort work-around.
-
I mean, basically, I should be able to just move the two SSD's from one M17x to another and have it boot! The Intel RST Option ROM should pick up the settings. Instead, in the BIOS, for example, the name of the RAID volume shows as "garbage" characters instead of the name I assigned the RAID volume.
I also tried cloning the RAID set to a single drive while in the original Nebula Red M17x (using the esata port for the destination), and my cloning software does not even see the RAID set! That is odd, because I use this software all the time to clone various Intel RAID and non-RAID setups.
Something is amiss, and I haven't figured it out yet. Somehow, I need to get my Windows 7 volume off the original and onto this newest M17x so I can see which one I am going to keep! I dread having to reinstall everything! -
-
Unfortunately, I'm out of town for a week, and left my beloved M17x's home (traveling light with my Z600 this time). I had to overcome some major temptations to lug along the M17x, but I had will power.
Thanks again, and I hope you've found my answer!
Cannot transfer RAID 0 set to new M17xR2
Discussion in 'Alienware 17 and M17x' started by lancorp, Jul 2, 2010.