New Build RAID 1 causing windows blue screen crash

rwbil

Reputable
Jul 11, 2014
3
0
4,510
New Build. I7 4790K; Gigabyte Z97 MB. SSD and 2 1TB HDDs, Installed OPS on SSD and every thing boots fine. Initialized the 2 HDD drives but did not create a volume. Went into BIOS and set:

SATA mode selection to RAID
M.2 PCIE SSD RAID Mode – Enabled
SATA Express SRIS capabliltites - Disabled

Went into Intel chipset (CNTRL-I) Selected to create a RAID 1 volume and selected the 2 HDD drives. After it completed it showed:

Disk 0 Non RAID disk This is the SSD which contains the OPS
Disk 1 Member Disk (0)
Disk 2 Member Disk (0)

Rebooted and Windows crashes. I have window 7 home premium so I do not think there is a Mirrow Volume option.

Set everything back to default and windows 7 came up fine.

Do I need to setup as a RAID before installing windows?

Any suggestions?
 
Solution
Interesting comment. If what you really planned was to have a reliable backup system for your HDD, RAID1 is NOT that! It does automatically make two copies of everything put to the HDD, BUT it has major failings as a backup system. Any incorrect data written, either by honest mistake or by malware etc. will instantly write to BOTH halves of the RAID1 array, so there is NO preservation of the "good" data. Power glitches that damage your machine and/or drives likely will damage BOTH, so no safety there, either. Stuff you delete by mistake and then wish to recover is still GONE!

If you want a reliable backup system, a second HDD is a good medium to use, although sometimes it is better if it is larger than the first HDD. That is because a...

Paperdoc

Polypheme
Ambassador
The sequence you used is correct - install Windows on a boot device, then install additional HDD units, then use the RAID management utility to create the RAID array and initialize it. Now what SHOULD happen is that, on the next boot, Windows loads from the C: drive and discovers a new device (the RAID array) and loads the required driver for it. Obviously that is not happening.

Check this, When you boot, go immediately into BIOS Setup and check what device is set as the boot device - usually in some place like Boot Priority Sequence. Most people would set the optical drive as the first device, then the SSD (jn your case) that contains the OS. But be sure that the RAID array and its HDD units are NOT anywhere in the boot device list. I'm thinking that, once you added the HDD units, your BIOS automatically assumed that they would be the first boot device and it can't do that because Windows can't read an empty RAID array. If you make any changes in BIOS Setup, remember to SAVE and EXIT to reboot using the new settings.
 

rwbil

Reputable
Jul 11, 2014
3
0
4,510
I checked the boot sequence and even disabled the RAID from the boot options. Did not make any difference. I set the SSD as 1st in boot process. Played around for another 1hour or so trying different BIOS setting, but nothing worked. I think I might just use a backup program at this point instead of RAID 1
 

Paperdoc

Polypheme
Ambassador
Interesting comment. If what you really planned was to have a reliable backup system for your HDD, RAID1 is NOT that! It does automatically make two copies of everything put to the HDD, BUT it has major failings as a backup system. Any incorrect data written, either by honest mistake or by malware etc. will instantly write to BOTH halves of the RAID1 array, so there is NO preservation of the "good" data. Power glitches that damage your machine and/or drives likely will damage BOTH, so no safety there, either. Stuff you delete by mistake and then wish to recover is still GONE!

If you want a reliable backup system, a second HDD is a good medium to use, although sometimes it is better if it is larger than the first HDD. That is because a good system will make several copies of the data over time and KEEP the old copies in case the error you're trying to recover from is old. However, good backup software will make a single full backup, and then a series of Incremental Backup files (only the recent changes) to save space.

The backup unit really ought to be separate from the computer. Then you connect it to power and the computer only when making (or recovering) a backup - at all other times it is disconnected and safe in a storage space. Ideally, that space is in another location from your computer to guard against flood, fire, etc. I remember the system used by professional server administrators in the place I worked. They did TWO backups regularly - one to an on-site tape unit with tape storage on site for quick access, and a second by high-speed data line to a remote service in another part of the country for safety. I vividly remember when the needed it - when two of the five HDD units in the RAID5 server failed at the same time.

You need good software to make it easy to make and retrieve backup files. And you should learn how to check the backup files to be sure they work to get your data back. (I remember years ago the panic in a university data centre when disaster struck and they found they could not read back their backups tapes! Fortunately, they found a way, but considered themselves lucky.) The most important thing you need is some discipline to DO the backup process regularly and store them properly.

Don't want to discourage, but just to illustrate that even the highly improbable can cause trouble, I heard a story that one corporate data centre in the World Trade Centre's Twin Towers had done it all right up to 9/11 but for one detail - their off-site storage location for backups was in the other tower!
 
Solution