• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Raid Problem

J

JLambCWU

Junior Member
So I had a processor burn up and dropped a new one in today. The system wouldn't just boot, so I went into the BIOS to make sure the boot was set to the RAID 0 array I had setup and working before my old processor quit. Trying to just let windows start without going into the BIOS keeps posting "A Disk Read Error Occurred."

Is there something I have to select to make sure it can see the RAID 0 I had working before? Maybe there is a simple fix to this?

As a side note, I tried looking in the BIOS and hitting Ctrl+S and F4 to see if the RAID was still working, but pressing those doesn't do anything. The boot just continues and comes up with the "A Disk Read Error Occurred" again. So I can't get into the RAID setup or anything per the motherboard manual.

I'm trying to get it to work without reinstalling windows, but not sure where to go from here. Any help would be appreciated!

Computer info
I have an ASUS P5AD2-E with 2 37 gig raptors in a RAID 0 configuration.

Thanks
Justin
 
Welcome to the Forums 🙂 Check an easy thing first: if your keyboard is a PS/2 type (round plug) and you had your rig apart for the CPU swap, then confirm that the keyboard is plugged into the purple PS/2 port and not the green one.
 
Yeah, didn't have it apart, I can navigate the bios, it just won't open the RAID setup with Ctrl+S or F4. I flashed the bios about 6 months ago to update to a newer version. Could that have messed up the RAID setup access? The RAID and everything has been working since, but haven't even looked at the RAID setup part since I first built the computer over a year ago.

Thanks
Justin
 
Is the controller still in RAID mode for sure? If the main BIOS reverted to default settings as a consequence of your CPU frying, then it might not be in RAID mode anymore. You could go into the motherboard BIOS and check that, if you haven't already done so.
 
Thanks for getting my mind working. I figured at least part of it out and got it working again!

I'll post what I found in case it helps someone else out. In the BIOS main window under "Main," the top of the window says "IDE configuration"

Under that I had "Configure SATA as RAID" selected, but below that it says "Onboard Serial ATA BOOTROM," and that had been disabled. I don't know whether my old CPU frying caused it to be disabled, or dropping the new CPU in reset it, but it just had to be re'enabled. So I enabled that, rebooted and it works. My old RAID is there and Windows loads normally now.

Thanks for getting me to check again. I sure do appreciate the help!

Thanks
Justin
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top