Recovering a RAID 0 array on different hardware (good drives!)

[bhendin]

So I'm trying to recover my brother's data from an ASUS UX51V laptop.
Brilliantly this laptop was shipped with 2 ADATA XM11 SSD drives configured in a RAID 0 array.
I believe the RAID was configured via Intel Rapid Storage (aka Intel Matrix).
This laptop is no longer able to boot due to a motherboard/power issue.

The cost to replace the motherboard or for ASUS to provide data recovery are both relatively expensive and I would like to get this data back on my own.

Further complicating things is that the XM11 drives are not even a standard SATA/mSATA/m.2 connector format, but rather a proprietary 18 pin connection.
I am able to purchase special adapters to convert these drives to SATA drives. I should then be able to plug them in via SATA or (more likely due to the resources I will have at the site) via SATA/USB enclosure.

I have seen some RAID recovery softwares like these:
http://www.ufsexplorer.com/download_stdrr.php
https://www.runtime.org/raid.htm
and others.

I'm wondering if anyone has experience doing a RAID recovery like this using software from SATA drives. I might have difficulty on-site having access to install them as internal SATA and may only be able to use them via a USB enclosure.

Any thoughts, advice, experiences?

Thanks.

 

[drtweak]

With windows 10 that isn't as true anymore. I have swapped hard drives with Windows 10, without issue, many times.

Win 10 is better than previous versions, but its still a crapshoot.
I've seen it work, I've seen it fail.

Yea mainly just depends on how new the chipset it. Everything I have done it was are stuff that for the most part have been out before 10 lol

 

[Marco Zingaro]

Hi guys,

I'm reviving an old thread because I'm also the lucky owner of a ASUS UX51VZ-XH71 and I've started experiencing an odd recurring BSOD issue about a week ago (after using the laptop for 6 years = proud). After every BSOD crash, the computer reboots and a DOS screen comes up with Intel Rapid Storage Technology complaining that both RAID0 volumes are failed, and then reboots again saying "media test failure check cable, pxe m0f exiting pxe rom" (presumably, not finding the boot drive)

But it's rather oddly intermittent: yesterday I used my laptop normally for 10 hours straight, no issue ... today, as soon as I boot it up it crashes, then again after 5 min reboot ... now it's been running for a few hours... the point is, it's intermittent enough that I'm rather skeptical about a definite hardware failure, it acts more like a loose connection (even though the connectors look great from an inexperienced visual inspection...)

Another weird issue is that when I open it up and unhook the memory and SSD drives and put them back in, then turn it on -- the screen stays black, nothing happens. When I then disconnect the memory, I get that old "media test check cable" error, so I'm more inclined to suspect the RAM than the SSD. If I jam a little piece of foam under the memory chip, it seems to boot up normally again -- I hoped maybe that'd be a longer-term bandaid -- but the problem unfortunately recurred today.

So -- the question is -- what diagnostics tools do I have at my disposal to diagnose the health of two ADATA XM11 SSD drives configured in a Intel Rapid Storage RAID 0 array? Just to make sure my SSDs are ok? The ADATA SSD Toolbox just gives me an error "No available SATA disk! Try using a Windows AHCI driver for SATA controllers" and quits. And the Intel SSD Toolbox won't let me run a diagnostic scan on the RAID 0 volume (must be run on a RAID member) and it's greyed out when I select the 256 GB SSD (I guess because it's an ADATA and not an Intel SSD?)

I ran the windows memory diagnostics tool and it reported no errors.

Thanks.

 

[USAFRet]

Hi guys,

I'm reviving an old thread because I'm also the lucky owner of a ASUS UX51VZ-XH71 and I've started experiencing an odd recurring BSOD issue about a week ago (after using the laptop for 6 years = proud).

1. Please start a new thread for your particular situation.
2. Please start a comprehensive backup routine. Now. The very next thing you do after reading this.
3. See #2.