ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Moving Win 7 install to your Samsung 950 Pro RAID0
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Moving Win 7 install to your Samsung 950 Pro RAID0

 Post Reply Post Reply
Author
Message
PainterArt View Drop Down
Newbie
Newbie


Joined: 31 Oct 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote PainterArt Quote  Post ReplyReply Direct Link To This Post Topic: Moving Win 7 install to your Samsung 950 Pro RAID0
    Posted: 24 Nov 2015 at 2:59am
How to migrate your Win 7 OS installation to Samsung 950 PRO NVMe RAID

With this instruction you should be able to do a number of derivative how to including setting up a RAID with 950 PRO and getting your computer to recognize it, moving Win 7, 8 or 10 current installations to a 950 PRO RAID or just to a non RAID 950 PRO, or just installing an OS on a 950 PRO RAID.

You can get a pdf of these instructions here: HowtomigrateWin7OSinstallation950PRONVMeRAID.pdf

My Computer hardware details that are pertinent: Asrock Z170 Extreme 7+ motherboard, UEFI bios ver 2, Intel i7 6700K CPU, 2 x 950 PRO NVMe (512 GB) RAID 0, and Win 7 PRO SP1 installation on a Seagate Momentus XT 750 GB harddrive.

Note: Best to upgrade UEFI Bios to the new 2.11 before starting. At the bottom of this, you can read my fingers into desk upgrade of UEFI Bios to ver 2.11 after having already done all this work and have a running Win 7 OS installation on 950 Pro NMVe RAID.

Note: You should be able to do this with a number of motherboards with M.2 slot(s) because what really matters is Intel Rapid Storage Technology (RST) and RAID drivers. My Asrock motherboard does not show the 950 PROs in the UEFI M.2 slots, but more on that later. Also even though I used Win 7 Pro, I see no reason why Win 7 Home or even Vista Ultimate cannot be transferred or installed on 950 PRO singly or in RAID.

I am a big believer in backing up throughout the process either with software or a harddrive duplicator like StarTech USB/eSATA 1:1 SATA Duplicator Dock with UASP, which I used during the process. I should say I went down a few blind allies but below is the direct route.

I am writing this all from memory but I think I got it all right. I tried to write these instructions as detailed as possible so that anyone can do this. I also encourage you to read all the instructions before you start.

Windows installation must be on a GPT harddrive.

If your OS installation is still on a MBR harddrive, to convert your OS to a GPT harddrive is not easy, but doable. Just not the scope of these instructions. You need to create an EFI partition (1st partition about 200MB, Fat32) and build the boot. There are some tutorials out there if you search for Create EFI or Fix EFI. You can also try Macrium Reflect Rescue Disc (which is free) which has a fix EFI boot feature on it if it can locate your OS installation and you have a partition for the EFI at the beginning of your harddrive already set.

Download and Load 950 PRO drivers

After you have successfully installed your 950 PRO(s) into M.2 slots go into your OS. Download and install drivers.
http://www.samsung.com/global/business/semiconductor/minisite/SSD/global/html/support/downloads.html
Direct: http://ssd.samsungsemi.com/ecomobile/ssd/update15.do?fname=/Samsung_NVMExpress_Driver_rev10.zip

There is also the Samsung NVMe driver install manual.

There are links to Samsung NVMe Driver v1.4.7.16 Installer Set.rar, which I used. The link I got mine no longer exists so I cannot vouch for: http://www.win-raid.com/t29f25-Recommended-AHCI-RAID-and-NVMe-Drivers.html that will take you to a mega drive.

You will need to use a zip program like 7-zip to open the rar file.

After the driver installation in Device Manager you will see the Samsung 950 Pro NVMe (s) in under disk drives and the controller in Storage Controller. Later if you make a RAID these drivers will be replaced with Intel Raid 0 Volume SCSI Disk Device and Intel Chipset SATA RAID Controller.

Initializing 950 PRO(s) to GPT

If you open up disk management, you will not see the 950 PRO(s). Open a partition manager. I used MiniTool. You will see the 950 PRO(s) but they need to be initialized to GPT. You do not have to format or create a partition. Close MiniTool.

Open Disk Manager- Right click - Computer in Windows Explorer>Manage from popup menu>Disk Management. You will now see 950 PRO(s) in Disk Management.

Start Intel Rapid Storage Technology (RST)

Start Intel Rapid Storage Technology (RST) (in Programs) if it has not been started.

In it you will not see the 950 PRO(s), but will see any other SSD or hybrid drives. No worries. Go to Help>About>lower right corner, if you have anything less than ver 14.6 time to upgrade RST.
If you need RST 14.6 grab it here: https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver

Also grab the appropriate Info RST f6flp zip file from the page as you may need it to load RST and RAID drivers if your install ends up being different. Unzip burn to CD or USB but I find USB can be unreliable to be recognized in dealing with Win 7 recovery or transfers.

Install RST 14.6. Restart Computer.

Note: If you are not making a RAID you can format your Samsung 950 Pro NMVe and skip the rest of the RAID part of these instructions and go directly to Moving your Win 7 install to your Samsung 950 Pro NMVe RAID down below.

Stop Intel Rapid Storage Technology (RST)

Yes, that is right we are going to stop it after installing it, but will restart it later. Go to Computer Management Window as explained earlier to get to Disk Management.

Services and Applications>Services>find Intel Rapid Storage Technology>right click>Properties> General Tab>Startup type> disable. You do not want RST to start up automatically when windows starts.

Than go lower in the General Tab to Service status and Stop. Stop RST. Close out the Computer Management Windows.

Getting Windows to load Intel RAID drivers on next boot.


Exit all programs in Windows.

Click Start, type regedit in the Start Search box, and then press ENTER.

If you receive the User Account Control dialog box, click Continue.

Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV

In the pane on the right side, right-click Start in the Name column, and then click Modify.

In the Value data box, type 0, and then click OK.

Go to registry subkeys:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\msahci

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor

They should be 0 also but check.

In the pane on the right side, right-click Start in the Name column, and then click Modify.
In the Value data box, type 0, and then click OK

On the File menu, click Exit to close Registry Editor

Restart Computer.

Create the 950 PRO RAID in UEFI

Turn on computer and go into UEFI bios.(delete key)

Go to Advance Tab (may differ in other manufacturer interface)

Got to Storage Configuration> SATA Mode Selection>choose RAID

Selection menu will change below.

In Launch Storage OpROM policy select UEFI only.

Under this in the menu under the M.2 slot(s) that you installed the 950 PRO(s) like M.2_1 RST Pcie Storage Remapping click on and enable mapping.

Save and exit.

Reboot and enter into UEFI bios again.

Got to Advance Tab and you will now see Intel Rapid Storage Technology at the bottom of the first menu. Click on it.

On this page you will create your RAID volume and you will see Samsung 950 Pro NMVe listed along with any other SSDs.

Create a Volume Name.

Select Type of Volume (I went with RAID 0, more on that later.)

Select disks to be in that volume by clicking on Samsung 950 Pro NMVe(s) and choose the ???br>
After choosing the disks to be in your RAID, click the Create RAID button. Your RAID will be created and the name of your RAID will appear on this page as a RAID created.

Exit UEFI and reboot.

Note: Samsung 950 Pro NMVe never show up in the list of SATA and M.2 slots under Storage Configuration. Only under Intel RAID. Also the Asrock UEFI ver 2 uses RST 1.5 and has not been upgraded but that does not matter to set up this RAID with Samsung 950 Pro NMVe. Just as I write this Asrock upgrade their UEFI to ver 2.11 which uses RST 1.6. It does not change anything as far as these instructions and you still cannot see the Samsung 950 Pro NMVe except when building the RAID in UEFI bios.

Ok we are going to enter UEFI again.

Go to Advance Tab>Storage Configuration> Launch Storage OpROM policy > and change it back from UEFI to AHCI. Yes, you read that right.

Go back to Advance Tab menu. You can click on Intel Rapid Storage Technology in the main menu of the Advance Tab and you will see your RAID is still there.

Save and exit.

Installing RAID driver in your Windows 7 Installation


On reboot click F8 and go into safe mode. In Safe mode the Install Device Drivers (new) will start up automatically. It will load the Intel Raid driver and SSD drivers for any SSD you have on your system. Click on the install device balloon to watch the install. Strange the reboot message came up behind my install device window, so move that window, so you can know when to reboot.

Go back into the UEFI on reboot>Go to Advance Tab>Storage Configuration> Launch Storage OpROM policy > and change it back from AHCI to UEFI. Save and Exit.

Reboot and start your Windows 7 install normal.

You will now notice your 950 PRO RAID in your Windows Explorer with whatever name you gave it.
Startup Intel Rapid Storage Technology in Services and Applications reversing what you did earlier when you stopped RST. You also want it to startup automatically or automatic (delayed) for future startups.

Let RST load up and you will see your RAID in it.

This is definitely a place where you want to back up your OS.

Moving your Win 7 install to your Samsung 950 Pro NMVe RAID

Ok I think there are two ways you can do this. You can clone disk with MiniTool or Easus Partition manager. Or you can create an OS system image and load that image on to the RAID in a PreWindows Envirornment or in the Emergency Disk made from your imaging software. You need to create the Emergency Disk with your imaging software in your current OS so that it will hopefully include the Intel RAID Drivers. If your Emergency Disk for whatever reason doesn? include the RAID drivers, you have the RAID drivers on another disk that you made earlier in this instructions and you can load the Intel RAID driver during the startup of the Emergency Disk.

I used Easus Workstation 8.9 which is a paid program to transfer my Win 7 installation to Samsung 950 Pro NMVe RAID. I used this software because it has a system transfer tab that allows you to install drivers if needed in the WinPE. I did not need to do this as the Win PE Emergency disk included the driver and my Samsung 950 Pro NMVe RAID showed up in environment as an option. Another reason it has a place to check where you can optimize for SSD for the transfer on to the NMVe RAID. I do not know if this makes any difference.

My only other bit advice is to unplug the SATA cable on one end of all unnecessary harddrives so that you only have the harddrive your OS image is on, the 950 PRO RAID, and your CD/DVD drive plugged in. It is not necessary to unplug the power on these harddrives. I also plug the harddrive my OS image was on directly to an internal SATA and not through any external harddrive connection.

Now Comes The Cross Your Fingers Moment

After you successful transfer you OS image onto your 950 PRO RAID, do not add any hard drives. Remove your Emergency Disk and the harddrive your image was on so you only have your 950 PRO RAID. Reboot go into UEFI. Under Boot Tab make sure your first boot is the Boot Manager (RAID name that you gave it). Save Exit.

So I tried to start Win 7 normally, and in safe mode and it froze during startup, then I tried Last Known Good Configuration under F8 and I got in.

If you do not get in the after a few tries, a suggestion attach your original harddrive with OS on it. Boot into it by selecting the Boot Manager of that harddrive in the UEFI bios, then use Easy BCD to create an entry for the OS on the RAID. Reboot. Select that new entry that is on the Boot Manager of the original OS harddrive. Try both normal, safe mode, and Last Known Good Configuration. Hopefully you will get in. It will adjust and load any driver need automatically, then you can backup, disconnect the original OS harddrive and attempt to boot in the RAID OS by the RAID boot manager.

Back up like crazy once your Win OS has fully loaded. I also added all harddrives one at a time that I had unplugged while Windows 7 on RAID was live and computer on. You may have to go into Disk Management to change them from Offline to Online or they will automatically load.

After you first get in, all future startups will be normal startup as long as the Boot Manager (Intel 950 PRO RAID) is your first boot.

Initial observation Windows 7 on Samsung 950 Pro NMVe RAID

Boot time and shut down is very fast. Backup time of your OS is really fast. I went from about 2 hours to about 17 minutes. I ran the Windows Experience Index without doing any tweaks on my computer, I got 7.9 for everything but the Intel CPU was 7.8. My bottleneck now, but easy to change.

Microsoft made me reactivate my Windows 7 installation and my Microsoft Office. A bit of a pain as the only thing that changed was the RAID. No other licensed software asked me to reactivate their software.

I plan on upgrading now to Win 10 and have a copy of the Win 7 PRO installation on my RAID in a dual boot situation. May as well since I have no other computer to use the Win 7 software on and you never know when you may need it to go in and fix your running Win 10.

Thoughts on RAIDs and Backing UP

There are no RAIDs that are a backup system!

I ran a Raid 0+1 for years. It worked fine even when a harddrive went bad. Rebuild was easy. Then my motherboard started going bad (maybe my Intel chip) and one day my RAID came back as bad but I could not go into the RAID and fix it using the Intel software. For whatever reason it would not allow me to rebuild even though later I found out that all harddrives in the RAID were good. I did have backups of all pertinent information and data files, so I rebuilt this current computer.

So for me redundancy in a RAID has very little value, I may as well just have a RAID 0 and backup software that mirrors my RAID in real time or very close to real time to regular disk harddrive. This way in the event of failure, I can just use the mirror to boot into with no down time and also have time to rebuild the RAID replacing whatever went bad. A RAID 0 plus a harddrive mirror gives you all the advantage of the speed of having a RAID and a backup all for just 3 drives. Every RAID beyond 0  and 1 requires more drives and you get no backup.

CMS use to have Bounce Back that worked flawlessly at doing mirroring of a bootable harddisk with OS, but their recent Bounce Back 17 is just a repackaging Novastar backup software which from what I can tell does not have real time mirroring.

I have found two that do Comodo Backup (free) and Backup4All (not free). I have been playing around with Comodo Backup but am still figuring it out and the jury is still out as to whether it will do all of what I need it to do. It definitely has the scheduling to mirror backup in real time. I have not tried Backup4All yet. If you install Comodo Backup and do not want their Cloud Backup which is what they are selling with this free backup software, make sure you unclick cloud backup box during installation.

Imaging is fine but so many image backup software have proprietary imaging files and you have to make sure your Emergency Disk is current with small changes in your system drivers overtime that imaging is too tentative for my liking. I have had image failures so I really do not rely on imaging. Besides disk harddrives are relatively cheap so why have imaging or compression. DriveImage XML is a free imaging software with non-proprietary imaging files, so you can reinstall with a number of different rescue disks or Linux. Also I will mention Yardis (free) which is very easy to use and will backup your files over networks or to another harddrive in system. It can run continuously in the background, it just does not mirror or make a bootable harddrive mirror of your OS.

Note: So after doing all this UEFI bios ver 2.11 came out and I upgraded because I figure it would have Intel RST 14.6. I also wanted to see if the Samsung 950 Pro NMVe would popup in the M.2 slots in the UEFI bios. I thought the upgrade would keep all of my settings as a previous upgrade had. Anyway I was backed up. The upgrade did not keep all my settings. It kept the SATA Mode Selection RAID but the Launch Storage OpROM policy was changed to Legacy only and it looked like my RAID was gone. I changed the Launch Storage OpROM policy back to UEFI only, saved and exited, rebooted, went back into UEFI bios the Intel Rapid Storage Technology menu entry came back, opened it, and my RAID was still there. I changed the Boot Manager back to the RAID and my OS booted with no problem. Also the upgrade changed my UEFI from Advanced to Easy and a few other selections. You are reading this Asrock.

That is all. If people run into problem, or I made a memory error let me know and I will refine the instructions.

Good Luck and Backup Often!

Back to Top
PainterArt View Drop Down
Newbie
Newbie


Joined: 31 Oct 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote PainterArt Quote  Post ReplyReply Direct Link To This Post Posted: 24 Nov 2015 at 3:22am
Could someone with powers to be add RAID to the topic tittle as that got truncated or change the title so that it has RAID in it.
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 15 Jul 2015
Status: Offline
Points: 6336
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 24 Nov 2015 at 5:03am
Wow!

Impressive. Well done there.
< id="kpm_plugin" ="application/x-KPMPlugin">
Nothing here. Move on!

16,441 - https://www.3dmark.com/fs/13030306
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 15 Jul 2015
Status: Offline
Points: 6336
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 24 Nov 2015 at 5:04am
I call Sticky
< id="kpm_plugin" ="application/x-KPMPlugin">
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 5003
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 24 Nov 2015 at 1:23pm
Sticky status in the Media&User's Review forum?

No, unfortunately some people post their technical support questions and technical information posts in the Media&User's Review forum, this forum, where they do not belong. I move threads from this forum to their appropriate location almost daily.

It could be useful in the Technical Support, Intel Motherboards forum, where it belongs and will be moved to. (Fixed the title per request, as much as possible.) I would suggest some editing before making it a sticky. The "... I think I got it right...", and similar statements may not inspire confidence in some readers.

Some comments and questions:

The step where you stop the IRST service from running was done due to a version of IRST older than 14.0 being installed/running, correct? Otherwise, I don't see the point.

It is standard for any BIOS/UEFI update to reset all options to their default values. There are underlying technical reasons for that to be necessary for many options. The UEFI firmware is sourced from AMI, they are the ones that you want listening to you, even if they cannot do what you (and I) wish was possible.

Fortunately, AMI/ASRock has not reset the SATA mode to AHCI with UEFI updates that allow the SATA mode to be retained.

I'm surprised your RAID 0 volume of PCIe SSDs survived the UEFI update. About two months ago, some ASRock Z170 Extreme7+ users and I began experimenting with RAID 0 arrays of Samsung SM951s. Granted, the SM951s were all AHCI versions, the 950 Pro NVMe. That may make a difference.

We found that simply a UEFI clear was enough to cause the RAID 0 volume to fail, and be non-recoverable. That was even with an empty, non-OS volume. We were using IRST 14.6.

We also discovered performance issues depending upon the RAID 0 stripe size used. But that is really not a part of the purpose of your tutorial.

In my case, my Windows 10 installation was done in full UEFI booting mode, CSM disabled. That is, instead of just setting the Launch Storage OpROM policy to UEFI only.

You did not mention the RST PCIe Remapping options in the paragraph about recovering your RAID 0 array. Did you configure those again to get your RAID 0 array back?

When you say you changed your Boot Manager entry back to RAID, do you mean the entry in the boot order has the prefix "RAID:" followed by either "Intel RAID 0", or possibly "Samsung 950 Pro"?

Or do you have an entry in the boot order that is "Windows Boot Manager"?

I cloned a Windows 10 installation to my RAID 0 volume of SM951s using Macrium Reflect. It worked fine for me. I never tried the Macrium recovery option to recreate my OS installation after the RAID 0 volume failed.

I gave up on using PCIe SSDs in RAID 0 due to performance compromises it has compared to a single drive.



Back to Top
PainterArt View Drop Down
Newbie
Newbie


Joined: 31 Oct 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote PainterArt Quote  Post ReplyReply Direct Link To This Post Posted: 26 Nov 2015 at 5:48am
Originally posted by parsec parsec wrote:

Sticky status in the Media&User's Review forum?

No, unfortunately some people post their technical support questions and technical information posts in the Media&User's Review forum, this forum, where they do not belong. I move threads from this forum to their appropriate location almost daily.


Sorry about that, I did notice the Media&User? Review until you mentioned it as it is not conspicuous where it is. As a new user all I saw was Forum, Intel motherboards, and thought I found the correct spot. You may not be able to do this but if you put your forum labels like Media&User? Review in the box next to the word Forum you would probably not have to move topics almost daily. Almost daily should tell you something. Thank you for the move.

Originally posted by parsec parsec wrote:

It could be useful in the Technical Support, Intel Motherboards forum, where it belongs and will be moved to. (Fixed the title per request, as much as possible.) I would suggest some editing before making it a sticky. The "... I think I got it right...", and similar statements may not inspire confidence in some readers.


Thank you for fixing the title. I state in the original post that my tutorial will probably need more refinement as when I wrote it I was doing it from memory. I did not write all the steps down as I went because I was not sure I would succeed and it was not a straight line process but experimentation with steps that went nowhere. ? think I got it right??is a note of caution because it was refined from memory. So far moving an original Win 7 or OS installation to a RAID of 950 PRO is just n=1. It has to be repeatable, before anyone can be confident. I have no doubts about forming the RAID. Getting a person? original OS installation onto that RAID and working is still finger crossing.

Originally posted by parsec parsec wrote:


Some comments and questions:

The step where you stop the IRST service from running was done due to a version of IRST older than 14.0 being installed/running, correct? Otherwise, I don't see the point.

No I was going from 14.5 to 14.6 IRST. You are probably correct, but I just want to point out that you are changing register values to load Intel RAID drivers and that these drivers show up in IRST. When you have the Intel RAID drivers loaded and there is enough of the appropriate drives to make a RAID the ?reate a RAID??button shows up in the IRST. This may happen without restarting IRST.

Looking back, the other reason I stopped and restarted was that the IRST 14.5 was not showing the 950 PROs and only some other SSD, even though Windows showed them in Disk Management. I installed IRST 14.6 and nothing changed. I thought maybe trying to start restart IRST something would change. It still did not show the singular 950 PROs. It could be possible that once the Intel RAID drivers load and if you enable RAID in the UEFI but did not form a RAID in UEFI, the 950 PROs singly would show in IRST windows interface along with the create RAID button. You could then create the RAID from there. It is not the path I went.

Originally posted by parsec parsec wrote:


It is standard for any BIOS/UEFI update to reset all options to their default values. There are underlying technical reasons for that to be necessary for many options. The UEFI firmware is sourced from AMI, they are the ones that you want listening to you, even if they cannot do what you (and I) wish was possible.

So it is standard for a BIOS/UEFI update that people get their RAIDs wiped out? I think not. The main reason I bring up the issue is that if people go forming RAIDs than think they are wiped out by an upgrade of their UEFI and are not told they will be unhappy. It does not wipe out your RAID, but it does put the user in a precarious situation, but more on that later. User should be told that their setting will be changed and they may lose their RAID if they upgrade their UEFI bios. Functionally it is bad that you can make a RAID but then are stuck never upgrading your UEFI bios unless you jump through some hoops or know that it is not wiped out but have to be careful, none of which is spelled out.

Asrock and motherboard manufactures have great influence on the UEFI that are on their motherboards. This why UEFI interfaces can be different from motherboard manufactures even though they source their UEFI firmware from the same source. AMI listens to Asrock and gives them what they want.

They could store user setting and then reapply them after the UEFI bios has been updated. Certainly other bios companies have been able to do this in the past. I remember computer using Phoenix bios where upgrading the bios did not involve resetting my user settings. In as long as I have had RAID and updated my Bios I can never remember having my RAID settings reset.

Originally posted by parsec parsec wrote:


Fortunately, AMI/ASRock has not reset the SATA mode to AHCI with UEFI updates that allow the SATA mode to be retained.


Even if they had changed the SATA mode to AHCI the RAID would not necessarily be wiped out.

Originally posted by parsec parsec wrote:


I'm surprised your RAID 0 volume of PCIe SSDs survived the UEFI update. About two months ago, some ASRock Z170 Extreme7+ users and I began experimenting with RAID 0 arrays of Samsung SM951s. Granted, the SM951s were all AHCI versions, the 950 Pro NVMe. That may make a difference.

We found that simply a UEFI clear was enough to cause the RAID 0 volume to fail, and be non-recoverable. That was even with an empty, non-OS volume. We were using IRST 14.6.

I am not sure what you are saying by a ?EFI clear?? I would not call myself an expert. I am more experienced with cumulative knowledge. I write the following for all that read this so take no offense.

Part of what the UEFI bios does is tell the operating system what is plugged into the motherboard and where things are. In the case of a RAID, the UEFI tells the OS that these drives form a RAID and what RAID they form. The actual RAID information is kept on the GPT or earlier on the MBR. So if the UEFI bios is changed as long as you do not start the OS you can still recover the RAID by changing the UEFI bios back to the settings you used to set up the RAID even up to including the name of the RAID. I was not really that worried about recovering my RAID from the setting change by the UEFI firmware update, but it is precarious in that you cannot make a mistake in resetting the RAID settings in the UEFI bios before starting the OS.

A few years back I was using a motherboard with NVidia RAID drivers. I had a RAID 0+1 and my motherboard went bad. I bought a new motherboard with NVidia RAID capabilities. I do not remember if it was the same motherboard manufacture but I think I upgrade my Intel CPU. Plugged everything in, set the NVidia RAID bios settings exactly like before and recovered the RAID. Admittedly precarious.

Originally posted by parsec parsec wrote:


We also discovered performance issues depending upon the RAID 0 stripe size used. But that is really not a part of the purpose of your tutorial.


Ah, RAID striping size, I used the default Intel 16 striping size which Intel says is optimum for their RAID controller and the RAID 0. I realize there is a lot of debate about this. My opinion and from what I have read and tests I have seen: There is not much speed difference between 16 and 128 stripe size, but a drop off below 16. A stripe size of 16 gives you less wasted storage. Everything is a tradeoff. It depends on your goal and what you use your computer? RAID for. While a stripe size of 16 is not the fastest, it balances speed and storage use optimally. I think this is what Intel concludes when they default to 16. Remember the tests you see on RAID striping are not in normal use tests. I can see if you work a lot with video or work for PIXAR changing the stripe size to 128 would be beneficial to both speed and use of storage space.

Originally posted by parsec parsec wrote:


In my case, my Windows 10 installation was done in full UEFI booting mode, CSM disabled. That is, instead of just setting the Launch Storage OpROM policy to UEFI only.


I have found that CSM does not have to be disabled. In fact on my computer it is enabled. When you change Launch Storage OpROM policy in Storage Configuration it changes in CSM. All other CSM settings do not matter.

Originally posted by parsec parsec wrote:


You did not mention the RST PCIe Remapping options in the paragraph about recovering your RAID 0 array. Did you configure those again to get your RAID 0 array back?


These are some good questions and comments. RST PCIe Remapping settings did not change after the UEFI update. I did not have touch them.

Originally posted by parsec parsec wrote:


When you say you changed your Boot Manager entry back to RAID, do you mean the entry in the boot order has the prefix "RAID:" followed by either "Intel RAID 0", or possibly "Samsung 950 Pro"?

My RAID Boot Manager reads ?ntel 950 PRO RAID?? My RAID? name is 950 PRO RAID without the Intel.

Originally posted by parsec parsec wrote:


Or do you have an entry in the boot order that is "Windows Boot Manager"?

 
I have had this, but most boot manager entries have Boot Manager ?isk identifier?? like HDS5C3030ALA630. I throw around and backup various version of OS disk as I experiment and can have multiple Boot Managers that show up in my boot order. Microsoft may not like all the backups but I do not see how you can experiment safely without them. I always just have one copy I am working on, on one computer. In the end, I when I accomplish getting the Win 7 OS on the 950 PRO RAID, I end up with one OS and a backup copy.

Originally posted by parsec parsec wrote:


I cloned a Windows 10 installation to my RAID 0 volume of SM951s using Macrium Reflect. It worked fine for me. I never tried the Macrium recovery option to recreate my OS installation after the RAID 0 volume failed.


As long as your OS or an OS does not write to drives that are in a RAID when a RAID is broken in your UEFI bios you can recover your RAID by recreating the UFEI settings in bios that you used to originally create the RAID. Macrium recovery options only recovers you EFI boot on a working drive or RAID. It does not recover a RAID. There is software out there that claim they can recover a RAID. I have never used any of them.

Originally posted by parsec parsec wrote:


I gave up on using PCIe SSDs in RAID 0 due to performance compromises it has compared to a single drive.

A link to an article using 950 Pros RAID 0 comparing to a single 950 Pro and other drives using various tests. I suspect he used the default striping size of 16 as he does not mention striping size.

http://www.vortez.net/articles_pages/samsung_950_pro_256gb_raid_review,5.html

Still talking about Win 7 OS what I really notice and find helpful is backup speed. Backing up is a pain, faster backing up makes it more likely. People will back up more often. It will make a continuous mirror backup without notice. I use Thunderbird. Compacting use to take a while, now it takes no time. With computers, we are getting close to instant on from a dead start.

As far as a sticky, it had not occurred to me. It does not matter to me. I was just writing for all the people pulling their hair out moving their information and OS to new technology. These are my people.
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 15 Jul 2015
Status: Offline
Points: 6336
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 26 Nov 2015 at 7:10am
Originally posted by PainterArt PainterArt wrote:

People will back up more often.


More often? Another Ha! That implies they've backed up prior! NOT

Ha! Pardon me if I don't hold my breath waiting for THAT to happen.



If only .......... Geek

< id="kpm_plugin" ="application/x-KPMPlugin">
Back to Top
PainterArt View Drop Down
Newbie
Newbie


Joined: 31 Oct 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote PainterArt Quote  Post ReplyReply Direct Link To This Post Posted: 27 Nov 2015 at 12:43am
Very true observation of human behavior Wardog.

I guess that is another reason to advocate automatic mirroring as a back up strategy. Set it once and let it run.
Back to Top
PainterArt View Drop Down
Newbie
Newbie


Joined: 31 Oct 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote PainterArt Quote  Post ReplyReply Direct Link To This Post Posted: 27 Nov 2015 at 12:51am
I realized when I posted this "A few years back I was using a motherboard with NVidia RAID drivers. I had a RAID 0+1 and my motherboard went bad. I bought a new motherboard with NVidia RAID capabilities. I do not remember if it was the same motherboard manufacture but I think I upgrade my Intel CPU. Plugged everything in, set the NVidia RAID bios settings exactly like before and recovered the RAID. Admittedly precarious. "

I should have added it was a RAID 0+1. I also carefully marked my harddrives  and cables 1-4 so that when I reinserted them into the new motherboard, I made sure they were in the SATA slots in the right order.

This just case someone reads this to help them get out of recovering their RAID and they did not backup.
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 11.06
Copyright ©2001-2018 Web Wiz Ltd.

This page was generated in 0.094 seconds.