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

    • Chasys Photo 5.41.01 by Razvan Serea Chasys Photo is a suite of image editing applications including a layer-based image editor with adjustment layers, linked layers, timeline and frame-based animation, icon editing, image stacking and comprehensive plug-in support (Chasys Photo Editor), a fast image viewer (Chasys Photo Viewer) and a fast multi-threaded image file converter (Chasys Photo Converter) , with RAW image support in all components. It supports the native file formats of several competitors including Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr, and the whole suite is designed to make effective use of multi-core processors, touch-screens and pen-input devices. Designed under the mantra of “unique, flexible and powerful”, Chasys Photo takes a radically different approach to image editing with the aim of opening up new possibilities for those who dare to be different. Chasys Photo key features: Free-style layering with blending modes Adjustment layers with multiple adjustments per layer Linked layers (a.k.a Linked Smart Objects) Composite, Image List, Frame Animation and Object Animation image modes Animation, both frame-based and object-based (timeline animation) Animation Composer engine Image Stacking for noise reduction, super-resolution, etc. Tablet/Pen-input/Stylus support with pressure control Touch-screen support with gestures including pitch-to-zoom and multi-finger panning Support for the native formats of Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr Support for common formats such as JPEG, animated PNG, animated GIF, TIFF, PICT, WebP, HEIF, DDS, JPEG-2000, JPEG-XR, JPEG-XL, AVI video, etc. Support for the OpenRaster interchange file format and rare formats such as QOI, MNG/JNG and DPX Support for older formats such as PPM/PGM/PBM, PCX/DCX, PCD, TGA, COKE, etc. Comprehensive Camera RAW file support with live adjustment Extensive plug-in support with streamlined SDKs Support for Photoshop Filter Plug-ins (.8BF) Advanced printing and scanning engines PDF document generation Icon and cursor editing, import and export, including Vista-style and Mac-OS icons Screen Capture, including Video Screen Capture with multiple triggering modes Video capture from devices (e.g. TV/Video) Supports multi-core processors, High-DPI displays and Multiple Display setups Integrated File Browser, Bluetooth OBEX and in-built utilities (Calculator, Notepad) Shell integration with thumbnails and conflict detection Unlimited Undo/Redo and Asynchronous Auto-Save, with Just-in-time memory compression to save space Fully re-editable text with advanced styling and effects (TextArt) Full alpha channel through out the workflow with Alpha protection (a.k.a. transparency protection) Multiple language support with user-editable language files and translation assistant (Chasys Photo Language Studio) Anti-aliasing and super-sampling support in tools and paths* Smart-resizing (similar to seam-carving) Best-in-class post-edit heuristics anti-aliasing engine Physical measurement specification with display size detection via EDID Uses the latest CD5 specification with animation and multi-resolution Super-fast internal graphics engine (JpDRAW2) Full UNICODE support in all components Metadata save, restore and scale to imitate vector art Configurable Guides and Grids with Snap-to-Grid Smart-dither to custom palette Asynchronous preview rendering engine Pantone equivalent palettes for PMS 100 to 814-2x Automatic color naming ... and many more! Chasys Photo 5.41.01 changelog: New Features Layered images with multiple pages (Composite/Multi-page) Additional templates to support template-centric workflow New Layer Blend Mode: Inverse Luma Mask Horizon detection in Rotate Transform Cropping option when importing video Orientation options in QR Code Generator plug-in Solved angle ambiguities (CCW versus CW) Internal Improvements Improved graphics engine (JpDRAW2™ v26.05) Improved CD5 codec (v4.10, improved ACSC compression) Improved interpolation when downsizing images Improved motion detection in Video Capture Slightly lower memory usage (RAM is getting expensive!) File Support and Bug Fixes Improved PXZ file support (placeholders, blanks) [bug-fix] Memory leak in flt_JPEG.dll Download: Chasys Photo 5.41.01 | 46.1 MB (Freeware) View: Chasys Photo Home Page | Wikipedia Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • We don't need stars for the word, just use the word "CSAM"
    • If they want to do business in the UK then they can't ignore it. thats why Imgur pulled out of the UK
    • Most of UK Gov are involved in pedophelia and satanic cults/rituals aka epstein mossad agent.
    • Nvidia outs hotfix driver for BSOD, wake from sleep, G-SYNC, Smooth Motion, NV-Failsafe by Sayan Sen Nvidia today rolled out a new hotfix driver in order to fix various issues related to monitors and displays. The company notes G-SYNC-related frame pacing troubles should now be resolved on Ada Lovelace GPUs, ie, RTX 4000 series graphics cards. For anyone not familiar, G-SYNC is Nvidia's in-house proprietary adaptive synchronization tech that syncs the GPU's framerate output with the monitor's refresh rate in order to match them and eliminate screen tearing. On the topic of synchronization, Nvidia claims improved stability when gaming with Vsync or vertical sync on multi-monitor displays. The company also finally fixes a bug wherein displays would fail to wake up from sleep mode. Another bug has been resolved when certain monitors were identified as "NV-Failsafe" since the EDID information was incorrectly read by the GPU. EDID or Extended Display Identification Data of a monitor essentially contains the necessary metadata that lets a GPU understand the features and capabilities of a connected monitor. Ghosting and jittering problems as well as game crashes during the use of the Smooth Motion functionality have also been fixed with this release. Nvidia Smooth Motion feature is a driver-based AI model that delivers a seemingly "smoother" gameplay experience by inferring an additional frame between two rendered frames. Here is the full changelog for the new GeForce hotfix driver 610.52: [Ada] Resolves a frame pacing issue on certain monitors when G-SYNC is enabled Resolved an issue that prevented the EDID from being read on certain monitors causing them to be identified as "NVIDIA NV-Failsafe” Improved gaming stability in multi-monitor configurations when using V-SYNC with DLSS Frame Generation Resolved an issue where certain monitors would not wake from sleep mode [World of Warcraft] Gaming stability improvements Resolved an issue that could cause jittering or ghosting in some DirectX 11 games when Smooth Motion is enabled Resolved an issue that could cause some games to crash when launched with Smooth Motion enabled General stability improvements when the system fails to create a new allocation Others in the feedback thread also point out that the hotfix patches a blue screen of death (BSOD) issue. You can provide your own feedback there too after downloading the new 610.52 driver from Nvidia's official website at this link. Keep in mind that this hotfix is not essential to install unless you are having any or all of these issues. As such you can stay on the latest available GameReady driver version 610.47.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      PsYcHoKiLLa
      219
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      88
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!