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.

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

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?

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.

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.

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

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!