Reinstalling Windows with seperate RAID 5 Array


Recommended Posts

Hi all,

I'm in need of little help here as I'm not entirely comfortable with RAID arrays and their foibles.

Currently in my desktop I have:

1x OCZ Vertex 2

5x Samsung 1TB drivers running in RAID5 controlled by:

ASUS P67 Rev 3.1

The Vertex 2 was used as a C drive, with al programs etc running off of it, and the RAID array being used for general storage use.

My Vertex 2 has just totally died, and I've got a Samsung 840 Pro to replace it with.

However I'm wondering what steps I should take when reinstalling the OS?

Should I disconnect the RAID array? Disable it in BIOS and re-enable it after I'm done installing Windows 8 onto the 840?

And finally, I'm assuming that all of my data on the RAID array is still there and secure? My top priority is of course maintaining that data!

Thanks for any help you can offer, I'm happy to provide any more info you may need.

Cheers.

Windows shouldn't touch the array as far as I know? Once the driver loads it should detect there is an existing filesystem on there and do nothing with it.

My guess based on the size variances between the RAID and the "C Drive" - The OS is not configured to be hot swappable and thus re-installing as long as the RAID is running within the same setup - everything should be fine.

Of-course, IF this is not a production enviroment - You could do as you described and simple disable the RAID. Might be over-kill but it is a sure-fire way of making sure nothing happens to the data.

So far I have done nothing regarding install, the 840 is in, and I'm ready to go but a bit worried by these conflicting answers!

Will having them unplugged have any negative effect?

Also, should I have SATA mode set to AHCI or RAID in my BIOS, it was previously set to RAID.

My two options as far as I can tell:

1. SATA Mode to RAID, all drives connected and fresh install on to the 840, or

2. SATA Mode to RAID, RAID array disconnected, and then plugged back in after install.

My priority is protecting the data on the RAID array, formatting and playing around with the C drive is of course now of no concern to me.

I'll be installing Win 8 64 Pro, the same OS as was on there prior to failure, with no other hardware changes.

Thanks for the help so far everyone!

Also, the RAID array is hardware controlled, not software.

Like so:

Unplug the power on the RAID array.

Install Windows. Get into Windows and fully set up.

Power down, replug the power for the RAID array.

Power up, enjoy your raid.

Even if I am wrong (and I'm not) this is the safest way to do it, and if anyone has objections to this idea other than it's a waste of time, feel free to pipe up.

I lost a RAID array to the issue I described. I made a topic on this forum, but I can't find it (might have been trimmed?). I lost my Windows install to a USB3 driver issue that corrupted the install. Reinstalled with the RAID array driver present. It read my disks, and then overwrote parts of the drive setting up an install (due to not finding a file system). Just like what we are talking about here.

I'm legitimately asking people to pipe up if I am wrong.

  On 19/01/2013 at 18:16, WA7ER said:

2. SATA Mode to RAID, RAID array disconnected, and then plugged back in after install.

That will work and you can also make sure the SATA ports are connected back in the same order but thats not really important for a working array.

Disconnecting the array first because installing the OS on another drive with SATA set to RAID insures windows don't installs the OS boot on the array with windows on the other drive.

Excellent, all done following articuno's instructions, here's my steps so far:

Unplugged all drives.

Installed Win 8 with just the SSD connected, fully updated through Windows Update, and installed all drivers etc from the ASUS download page

Replugged all drives in exactly the same order, booted into Intel RST and seen the following: http://i.imgur.com/inf769z.jpg Which all looks good, so my data is still sat there.

However when I boot into Windows I do not see the array as a drive, and neither do I see the disks in Device Manager, is there something I need to do for Windows to 'Discover' them?

if the data on the array is life and death data, disconnect them while installing windows, reboot, enable the array/controller and let W8 load up drivers for the new controller/raid array and off you go.

I leave my RAID0 array enabled any time I reformat, but its just game data n cache, user files are on my NAS.

in device manager, do you see the RAID controller? if not re-run Scan for hardware changes from the Action menu.

you should see something similar to below (but 5 RAID5 devices)

devmgr.jpg

  On 19/01/2013 at 21:25, WA7ER said:

Excellent, all done following articuno's instructions, here's my steps so far:

Unplugged all drives.

Installed Win 8 with just the SSD connected, fully updated through Windows Update, and installed all drivers etc from the ASUS download page

Replugged all drives in exactly the same order, booted into Intel RST and seen the following: http://i.imgur.com/inf769z.jpg Which all looks good, so my data is still sat there.

However when I boot into Windows I do not see the array as a drive, and neither do I see the disks in Device Manager, is there something I need to do for Windows to 'Discover' them?

  On 19/01/2013 at 21:25, WA7ER said:

Excellent, all done following articuno's instructions, here's my steps so far:

Unplugged all drives.

Installed Win 8 with just the SSD connected, fully updated through Windows Update, and installed all drivers etc from the ASUS download page

Replugged all drives in exactly the same order, booted into Intel RST and seen the following: http://i.imgur.com/inf769z.jpg Which all looks good, so my data is still sat there.

However when I boot into Windows I do not see the array as a drive, and neither do I see the disks in Device Manager, is there something I need to do for Windows to 'Discover' them?

Go into Disk Manager and see if they are there, they might be 'offline' or need a drive letter assigning to the array.

  On 19/01/2013 at 21:31, Mando said:

if the data on the array is life and death data, disconnect them while installing windows, reboot, enable the array/controller and let W8 load up drivers for the new controller/raid array and off you go.

I leave my RAID0 array enabled any time I reformat, but its just game data n cache, user files are on my NAS.

People don't really need to do this, he could of easily just left the driver part out of it and installed Windows 8 to the new SSD then installed the drivers. As long as he isn't booting off the RAID array itself, it's fine. You only need to install the drivers during setup if your going to install to the array itself.

  On 19/01/2013 at 21:36, Tony. said:

Go into Disk Manager and see if they are there, they might be 'offline' or need a drive letter assigning to the array.

People don't really need to do this, he could of easily just left the driver part out of it and installed Windows 8 to the new SSD then installed the drivers. As long as he isn't booting off the RAID array itself, it's fine. You only need to install the drivers during setup if your going to install to the array itself.

Sorry should have been a bit more precise, I didn't mean in windows install start up, I meant if he had controller disabled in bios before installing W8. Once W8 was fully installed and he rebooted n enabled it.

I personally would have left it all enabled and let W8 setup see it in initial install time, what I always do on my own rig and exactly what I do with LUN mapped drives on SAN arrays presented as RAID volumes on rebuilds of servers. Never been an issue yet.

the raid config data is held and owned by the controller, same with the volumes in the raid container, windows will read it form that and not mess it up.

Indeed, I didn't install any drivers during Win 8 installation, allowed it to do it's regular thing seeing as I only had the one drive enabled.

I have the latest Intel RAID drivers installed, and also the latest Marvell SASA controller drivers, I'm a bit perplexed as to why it's not just appearing as I had anticipated!

(This is my first build using RAID in case you couldn't guess :p)

Indeed, in BIOS I see the 5 separate individual drives, in Intel RST I see the complete array, is there another time during boot I should see the array listed?

Here are the only two screens I see during the actual boot process:

http://i.imgur.com/OxysUeV.jpg

http://i.imgur.com/ySBdKxW.jpg

"Unplugged all drives.

Installed Win 8 with just the SSD connected"

So you booted the computer and powered on the array controller with ALL the drives unplugged - don't you think the array controller might notice that it booted up and all its disk were offline? I am quite sure it would mark them OFFLINE when that happens, and your array is not valid any longer.

Now you should be able to go into the controller and get them back online again.. But there would of been no freaking reason to unplug them in the first place.. You might do that with single drives if you your not sure you could tell which one is which on an install. But I would be pretty sure you could tell the difference between a SSD and a raid 5 array to which one you wanted to install too.

Good luck - its quite possible you blew up the array when you unplug all its drive and then boot the controller -- what do you think its going to think happened to its disks??

  • Like 1

I doubt it blew up lol - you might of meant this as a dramatic way of saying uninitialized. It can take quite some time for the re-initialization process to complete. If I pull a hot swappable disk on one of the older units - it could take up to 3 hours before the new one is back online. A flashing light indicates the drives status.

The controller should be able to re-init off of the disks based on the fact it's identified them as being disk members.

It ought just read the damn thing in theory. I've done it before with Intel controllers.

At the very worst it might require a resync.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • So is Ubuntu and Fedora (with GNOME). It's a welcome move and those that need X11 can easily install as pointed out in the article it but that won't stop a loud minority from whining of course. Funny but It will actually be easier to install X11 on Ubuntu then enable Flatpak support/Flathub and use them.
    • End of an era? Kubuntu is removing default support for X11 in new installs by David Uzondu X11, the old window system whose days have long felt numbered, just saw another one of its major supporters head for the exit. Kubuntu has decided to follow its parent distro's lead, making its next release, version 25.10, a Wayland-only affair for fresh installs. It seems many Linux developers see Wayland as the future. Just recently, Linux Mint started working to improve support for the protocol in Cinnamon, tackling lingering issues with keyboard layouts and input methods. You can even see the progress in KDE's development, where an upgrade to Wayland PiP is planned for KDE Plasma 6.5. So what's the logic behind dropping a session that, for the most part, still works? According to Kubuntu's Rik Mills, the team wants to "rip off this sticking plaster" now, in an interim release, rather than ###### off a lot of people by doing it in the next Long-Term Support version, 26.04. The developers feel that maintaining code for the aging X11 system holds back progress on security and new features that Wayland can enable more easily. Plus, supporting two separate display servers is a massive undertaking. Of course, this change might have some people worried, but relax; all is not lost if you still need the old session. If you're running hardware that acts up, like some older NVIDIA cards, or who relies on an ancient application that doesn't play nicely with the XWayland compatibility layer, you can still get your familiar session back. Just enter the following command in your terminal: sudo apt install plasma-session-x11 Once that command finishes, the X11 session will appear as an option on the login screen, so you can carry on as before. As OMGUbuntu notes, not everyone in the Ubuntu family is following its lead just yet. Other official flavors like Xubuntu, Ubuntu Budgie, and Ubuntu Cinnamon are expected to keep offering an X11 session on their default installs for this cycle.
    • Mangohud hasn't been built into "Steam Deck", it has been built into SteamOS. I understand that your goal is to try and praise MS for a simple feature that everyone else has, but we are comparing OS vs OS. Hardware does not have anything "built-in". Software does. Like it or not, SteamOS has it "built-in". And it is far superior to XBOX game bar's information.
    • Please don't inject yourself into a discussion you did not read or understand what was said. No where did I say Windows was hard to use. I knew when seen two notifications with your handle the replies they were going to be a waste of time to read.
    • Exactly. The UI feels a lot snappier when animations are disabled. I think I might actually give it a try for a while, I'm liking it so far.
  • Recent Achievements

    • First Post
      Johnny Mrkvička earned a badge
      First Post
    • Week One Done
      viraltui earned a badge
      Week One Done
    • One Month Later
      serfegyed earned a badge
      One Month Later
    • Dedicated
      firey earned a badge
      Dedicated
    • Dedicated
      fettermanj earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      648
    2. 2
      Michael Scrip
      222
    3. 3
      ATLien_0
      220
    4. 4
      Xenon
      144
    5. 5
      Steven P.
      142
  • Tell a friend

    Love Neowin? Tell a friend!