Need help with raid 0 to new system

Sirste

n00b
Joined
Jun 10, 2016
Messages
58
Need help with raid 0 to new system The two ssd drives have Windows 8.0 on them and we're just pulled from a working computer and they should be in tact with no data issues.

Original config
P8Z77-I DELUXE - Overview
With 2x4gb ram and 3770k

New system
ASRock > Z170 Extreme4
With 2x8gb ram and 6700k

So I built the system and set bios to raid and the two drives were seen and all seemed good even the name I labeled it showed up "raidy" ... So went ahead and booted Windows logo pops up starts spinning then some kinda error shows but of course it's insta fast and I cannot read it. Then reboots and tries to fix itself to no avail as always (I have never seen Windows fix itself lol) anywho looking for some help

I will admit only tried a few times and gave up and went to bed

Other things to mention I have another pc working next to it and I'm sure I can also just take that hdd out and plug it into new system to boot up and make any recover USB sticks I need to or Linux etc.

Any questions ask away! Thx


Once I can fully and properly backup all my data off my raid 0 c drive I will then reformat and do the normal procedures I just only had time to backup half the drive before changing parts and there is a slim chance I can plug drives back into original system to restore data I just would have to arrange that with the new buyer local but not the closest!
 
ACHI/n on ACHI settings in BIOSs the same? First thought comes to my mind. Not too familiar with what your doing for trouble shooting cases but every migration i run into the ACHI annoyance.

was it BIOS RAID? IRST RAID or windows RAID? those are the same?

Both drives on the intel SATA ports? Not on the HBA/extra chipset?

Not a cable issue?

Some of the basics i can think of. Maybe a guide exists online about trouble shooting RAID 0 migrations....thats all i got sorry i am not much of a help.
 
One problem is the transfer raid from one PC to another...
and the second problem is to start Windows to a different hardware configuration...

RAID is likely to be OK...
 
ACHI/n on ACHI settings in BIOSs the same? First thought comes to my mind. Not too familiar with what your doing for trouble shooting cases but every migration i run into the ACHI annoyance.

was it BIOS RAID? IRST RAID or windows RAID? those are the same?

Both drives on the intel SATA ports? Not on the HBA/extra chipset?

Not a cable issue?

Some of the basics i can think of. Maybe a guide exists online about trouble shooting RAID 0 migrations....thats all i got sorry i am not much of a help.

One problem is the transfer raid from one PC to another...
and the second problem is to start Windows to a different hardware configuration...

RAID is likely to be OK...


I'll troubleshoot some tonight one problem a friend mentioned is Windows 8 is likely backwards compatible but doesn't recognize this newer chipset being older then the chipset. How I can fix that unsure right now maybe using a newer Windows USB install repair method would work like 8.1 updated or something or maybe 10 not sure.

Method two will be just reformatting new blank hdd with Windows and hoping the raid 0 is recognized and opens fine in Windows that way I can finish copying my data files over to backup drives.

Lastly I'll just reformat and suck it up! Unsure which OS I will use yet so many good and bad things about win10.

Gonna google things up now to see if I can find anything my two buddies said goodluck changing chipset and fact win8 is older then new chip.
 
oh is it an OEM key or retail? I know oem keys can tell you to screw off if hardware is changed.
 
oh is it an OEM key or retail? I know oem keys can tell you to screw off if hardware is changed.
It's oem for now


So update plugged a core 2 quad Windows 8 enterprise sata hdd into the new pc turned off raid in bios and selected ahci and it reconfigured and loaded up no problem.

So the fact that the raid 0 had error issues scares me but of course by default raid 0 = not as simple as just a sata drive. Same OS versions installed.

In Windows it appears one drive shows up and in disk management one drive shows healthy as D and other shows unknown and black bar

Any tips due to these updates almost seems like one drive erased itself somehow which makes almost no sense but before I go erasing everything any other tips for getting that raid0 readable in Windows at least maybe?!
 
I it is an oem key rhat probably the issue
You change hardware it gives you the finger.
 
What's the reason for the SSDs being in RAID 0? After the data is off of them, you might consider getting a new, larger single SSD. 1TB SSDs are dipping below $200 now, and Samsung might be releasing their new line in the first week of July.
 
What's the reason for the SSDs being in RAID 0? After the data is off of them, you might consider getting a new, larger single SSD. 1TB SSDs are dipping below $200 now, and Samsung might be releasing their new line in the first week of July.
does that include 1TB 950 PRO?
 
What's the reason for the SSDs being in RAID 0? After the data is off of them, you might consider getting a new, larger single SSD. 1TB SSDs are dipping below $200 now, and Samsung might be releasing their new line in the first week of July.
The whole point of getting the ssds working again in raid 0 is to fully back them up !

I am considering selling the 2x256 and getting a 512 for now don't need a 1tb honestly

Does it make sense to install OS to one 256 and use the second one for all games etc changing all th default paths and stuff

Lastly spent hours redoing this and several methods like it over and over with no avail over and over the same issue presents itself.

https://support.microsoft.com/en-us/kb/927392

Scan os always finds 0 drives
And rebuild bcd never fully works

So almost gave up put an 8.1 USB drive in hit repair and boom new options finally opened there is an explorer option I am now slowly manually backing up the last few files I can think of and will do a fresh install tomorrow unless someone can help me solve this problem. At least now all my data is backed up.

Repairing and scanning log files nothing works Windows always errors and cannot repair itself and all those codes above in link failed to fully work.

Hope this helps narrow down possible issue. I even did a system restore and same exact error problem continued.

It's been so long other then my documents and or downloads what's worth even backing up lol I used to do chrome and Firefox profiles but isn't that all up in the mysterious cloud now?
 
The rumor mill is chattering about a 1TB 960 Pro, and even a 960 EVO line. Wait a couple weeks and see what really happens.
This would be perfect timing thus dropping prices of 850 evos to dirt cheap! Among all competitiors too
 
Samsung released the 850 Pro line (128GB, 256GB, 512GB and 1TB) on or near July 1, 2014, and then released the 2TB 850 Pro and EVO on or near July 6, 2015, so it's reasonable to expect some new SSDs from them in the first week of July 2016.
 
Also tried all of this and looked like all was good till I try rebooting and then got the windows.exe error or missing file


Gonnahttp://www.digitalcitizen.life/command-prompt-fix-issues-your-boot-records

try this next

winload.exe is missing or corrupt: Fix for Windows Vista, 7, 8

Finished transferring most of my files off using explorer in system tools repair mode one more day to troubleshoot then just format it is also a learning experience several people have had exact issues and can't seem to find the full fix write up!
 
today's the last day I will attempt to fix solve etc the problem

As an update I made a win10 USB bootable and tried using that to repair fix to no available but for whatever reason I was able to get into safe mood and with networking but could only install the nic drivers and gave up since drivers don't seem to be the issue booting into Windows is and all the boot files are the problem since half the them keep disappearing even after so called renaming or backing up and following most of those guides I posted above! Thanks
 
Wait up, are you trying to take a pair of RAID0 drives and transfer them to a new motherboard?

To speed things up, if this is the case, stop and just forget it because unless you are damned lucky, and you haven't been so far, this will never work or certainly won't be worth the trouble.

instead, make an image of your RAID0 set and make sure that you'll be able to restore that image later.

Then go into that same system with the RAID set, destroy it, break it apart, get rid of the stripe through the same utility you used to create it.

Now take those drives put them into your new system and rebuild a new RAID0 stripe on your new motherboard.

Now image your RAID0 with your disk image.

This is the approach you should take if you want this to work.

It's not that hard to do, and it won't take much longer than any other shortcut someone has suggested. It's a process, it will work.

Oh, and if BIOS messages are too fast to read, record them with your phone or a better camera if you have it.
 
Wait up, are you trying to take a pair of RAID0 drives and transfer them to a new motherboard?

To speed things up, if this is the case, stop and just forget it because unless you are damned lucky, and you haven't been so far, this will never work or certainly won't be worth the trouble.

instead, make an image of your RAID0 set and make sure that you'll be able to restore that image later.

Then go into that same system with the RAID set, destroy it, break it apart, get rid of the stripe through the same utility you used to create it.

Now take those drives put them into your new system and rebuild a new RAID0 stripe on your new motherboard.

Now image your RAID0 with your disk image.

This is the approach you should take if you want this to work.

It's not that hard to do, and it won't take much longer than any other shortcut someone has suggested. It's a process, it will work.

Oh, and if BIOS messages are too fast to read, record them with your phone or a better camera if you have it.
Thanks for a proper response because yes all fixable routes have failed so far! I will try and make an image of the raid 0 the only problem with this is when I throw in another random hardrive with win8 for example I wasn't able to open the raid0 setup in Windows one drive was showing as not initialized and of course I did not click yes. I will try again because I know raid is still perfectly fine I am able to open it using recovery tools in recovery mode with a usb and apparently safe mode sometimes works lol.

Anyway thanks I will try image method and if not just start over! Lesson learned
 
Did this before for a friend, going from a Gigabyte Z87 to an Asus Z170 board (don't ask which exact model, I don't remember)...here's the easiest logic I thought of, and it worked for me. Clonezilla will be your friend, and assuming you're using motherboard RAID.

Put back both SSDs on the SATA6G slots on your Asus board. Make sure you're in RAID mode. Boot up on to Clonezilla, create an image to another HDD. And make an image out of the RAIDed SSD, and do a image verification.

Next up, plug both SSDs on the board, and just break the RAID, and build again. Boot up on to Clonezilla, and write the same image to the RAIDed SSDs again.

I've only had success transferring RAID0 sets without doing any clone from one motherboard to another if they're either the same make (Asus Z77 to Asus Z87 board), or same generation like Gigabyte Z77 to Asus Z77 of different makers.

EDIT: When I say "make an image", I meant create an image file instead of cloning to HDD.
 
Did this before for a friend, going from a Gigabyte Z87 to an Asus Z170 board (don't ask which exact model, I don't remember)...here's the easiest logic I thought of, and it worked for me. Clonezilla will be your friend, and assuming you're using motherboard RAID.

Put back both SSDs on the SATA6G slots on your Asus board. Make sure you're in RAID mode. Boot up on to Clonezilla, create an image to another HDD. And make an image out of the RAIDed SSD, and do a image verification.

Next up, plug both SSDs on the board, and just break the RAID, and build again. Boot up on to Clonezilla, and write the same image to the RAIDed SSDs again.

I've only had success transferring RAID0 sets without doing any clone from one motherboard to another if they're either the same make (Asus Z77 to Asus Z87 board), or same generation like Gigabyte Z77 to Asus Z77 of different makers.

EDIT: When I say "make an image", I meant create an image file instead of cloning to HDD.
Sounds great I haven't used clonezilla since firebird days but I'm sure I can figure it out I will do this before I give up! And then I suppose install and wipe all older drivers installing newer ones until I become less lazy and just reformat then do a system image backup!

Question how much space do I need the actual size used or total raid
Total raid = 256x2
Total used = much smaller #
 
Well if you got a 1TB HDD somewhere, you should be able to use that. But if you haven't really filled up the whole 512GB (256x2), then even a 500GB HDD will do. You have to create an image and use the sector-copy-thingy-option (don't remember the exact name now) clone to image, because then it will only ready sectors that have data. But to be safe a 1TB is best.

Just to be safe side, which I always do, I make 2 options. Once as an image file on one HDD, and to another HDD as a clone. Just to be on the safe side specially if that spare HDD has been rarely used, and you don't think it's that reliable.

Now....if you have other ideas though, do those first, because my suggestion and instructions involves destroying the RAID structure/build and create a new one on the new motherboard.
 
Well if you got a 1TB HDD somewhere, you should be able to use that. But if you haven't really filled up the whole 512GB (256x2), then even a 500GB HDD will do. You have to create an image and use the sector-copy-thingy-option (don't remember the exact name now) clone to image, because then it will only ready sectors that have data. But to be safe a 1TB is best.

Just to be safe side, which I always do, I make 2 options. Once as an image file on one HDD, and to another HDD as a clone. Just to be on the safe side specially if that spare HDD has been rarely used, and you don't think it's that reliable.

Now....if you have other ideas though, do those first, because my suggestion and instructions involves destroying the RAID structure/build and create a new one on the new motherboard.
Good call I'll try to make 2 backups but at this point borderline ready to say goodbye hah! I'll try it first though
 
Well my suggestion is like the last thing you should try to do when you're "border-line ready to say good-bye", after all, you'll have to destroy the RAID after making an image.
 
I tried clone Zilla as last attempt it for whatever reason couldn't see the raid or just didn't work tried 5 x every option and said f it! Deleted raid wiped drive and installed it on a single ssd! Unsure what I'll do with second ssd plan to sell both I think and get a 512!
 
Back
Top