Problem after BIOS reset

jamesw1008

Reputable
Oct 27, 2015
4
0
4,510
I have an Asus M4A77TD and AMD Phenom II X6 1055T. No overclocking or other adjustments had been made to the BIOS (other than disk setup). I ran into an issue with my RAID setup and wanted to change over to a single SSD, so I reset the BIOS to wipe out the configuration. That worked fine, but the mobo won't run for much longer than 5 minutes without crashing. Everything ran stable for years before the BIOS reset. What might the reset have changed that would make the system crash? As an attempt to get the system working, I flashed the latest BIOS, with no change - still crashes. Any tips would be much appreciated.
 
well raid 0 you will need to reinstall unlike mirrored aray raid 0 puts bits and pieces of data between the 2 drives

''RAID 0 (also known as a stripe set or striped volume) splits ("stripes") data evenly across two or more disks, without parity information, redundancy, or fault tolerance. Since RAID 0 provides no fault tolerance or redundancy, the failure of one drive will cause the entire array to fail; as a result of having data striped across all disks, the failure will result in total data loss. This configuration is typically implemented having speed as the intended goal.[2][3] RAID 0 is normally used to increase performance, although it can also be used as a way to create a large logical volume out of two or more physical disks.[4]''

https://en.wikipedia.org/wiki/Standard_RAID_levels
 
just to add before you ''break'' the raid 0 you clone the array to a single disk or backup first then break the array to a single drive and re clone that witch is now total single data

you had to take the scattered data between the 2 raid 0 drives and unify it to another hard drive or what ever backup media


I guess I said all that right ??
 

jamesw1008

Reputable
Oct 27, 2015
4
0
4,510
I'm just going to abandon RAID altogether and go with a single SSD. I can get the SSD connected and recognized but can't get the system to stay up long enough to reinstall the OS. There must have been a setting in the BIOS that changed with the reset that is causing the problem, but I can't figure out what it is.
 
copied from the web [if it helps any]

Here's how I did it (Windows 7, Intel ICH10r Raid 0 -> non raid)
1. make sure raid volume size is less than that of a single physical drive
- use "shrink volume" in disk manager if possible, or, get a larger drive
2. create image backup (windows backup is fine)
- quickest when done to a sata hard drive, I have an hot swap slot and just slide them in
3. remove the drives that make up the Raid 0 pair and set them aside
- just in case something goes very wrong, you can always go back by putting them back in
4. Leave Backup drive connected but Disconnect all other drives (just in case)
5. Put in new drive(s) to replace Raid 0 pair (one or more)
6. boot from recovery disk (or installation disk)
7. Recovery will find your latest image backup and suggest that you restore from it
- do that, windows will boot after the restore is complete
8. Shutdown and reconnect other drives
9. Boot up & readjust volume sizes, rename, associate drive letters as required
- note that primary boot drive volume size will be smaller than physical drive capacity if you followed step 1, if not you probably never got to this step
- use "extend volume" in disk manager
10. in my case search indexer re-indexed everything (took a while)
11. Backup once you're sure things look good

There can be some other quirks depending on your configuration (there were for me). I left BIOS configured for RAID as well.

Bottom line: no need to reinstall unless you have other motivations to do so.


thing is when you do raid 0 just count on total loss that's all there is to it overall - for me I use raid 0 for things I cant loose but my time all my games or programs are retail disks so if I loose the array big deal just rebuild and reinstall the game and the os just time is all I loose

now things like photos movies important stuff that's not so easy to get back will never see a raid 0

as winki says above ''without parity information, redundancy, or fault tolerance. Since RAID 0 provides no fault tolerance or redundancy, the failure of one drive will cause the entire array to fail;''

when you broke the array bad drive or not still the same as a failed drive unless you put it back to raid 0 and start backing it up to save your data

that's all there is to it
 

jamesw1008

Reputable
Oct 27, 2015
4
0
4,510
Thanks for all the tips on RAID, I appreciate it. I'm still trying to sort out the basic problem with the BIOS with the motherboard crashing. Any ideas on what might have changed in a BIOS reset that would make it crash?
 
well I see some say about this

'', the new system would not work because the hard drive has been changed and the system will not be able to find the hard drive from Registry when startup. ''

https://social.technet.microsoft.com/Forums/windows/en-US/235c664a-c2e0-4f82-9412-e0d4b57d883e/using-windows-restore-from-raid0-to-nonraid

or this

''
9.Open ‘Device Manager’ and look for your RAID driver. Uninstall it. You should be prompted to reboot.


10.Enter your Mainboard BIOS setup, Change the sata controller mode from RAID to SATA (you could try AHCI but if it wont boot you will need to follow one of the many guides on enabling AHCI).

http://superuser.com/questions/396642/how-do-i-clone-a-raid-0-array-to-a-single-disk


like I say you see why raid -0- is just performance mode and not good for much after that ? that's why I say if something goes wrong with it just call it a goner


I do hope the best outcome but been there done that , learned