New Bios 1102 for Hero available for downloading

[Breimeister]

Does anyone know what ASUS means when they say it improves system stability? My last two bios updates caused my raid drive c: to fail. The bios would not find the second member of my raid set and no way to add it to the set. The only way I can do the bios update is by cloning my drive C: to a removable SATA drive and then cloning it back to a new raid drive created after the bios update.

[HiVizMan]

May I ask how you update your bios? And do you set RAID in bios before you boot to OS for the first time. I have done many a bios flash with RAID systems and the only time I had a problem was when I removed all SATA cables and got the sequence of a RAID 10 wrong.

[Breimeister]

Breimeister wrote:
Does anyone know what ASUS means when they say it improves system stability? My last two bios updates caused my raid drive c: to fail. The bios would not find the second member of my raid set and no way to add it to the set. The only way I can do the bios update is by cloning my drive C: to a removable SATA drive and then cloning it back to a new raid drive created after the bios update.

I have had raid drives even before I switched to ASUS from ABIT with my ASUS M2N32-SLI and I have never had a problem with my raid drives after updating the bios. I have always done it this way:

1. Update the bios
2. Load the bios defaults, set SATA to RAID and reboot
3. If everything goes well, set the bios options to the way I had them.

Instead now I am faced with a screen that tells me that my Stripped Raid drive C: has failed and it only has one member. If I click control-I to enter the raid management utility, there is no way to tell it to add the second drive to this raid set. The only solution I have found is to delete the failed raid drive and then create a new raid set. This of course destroys all the data. The first time this happened to me I spent days re-installing everything from a backup but now I clone my raid drive before the bios update.

I do not know why this is happening to me but maybe it is because my raid drive consists of two Mushkin Chronos Deluxe SSD drives? Both of these drives have the latest firmware from Muskkin.

IF there is someone that has an SSD non-Mushkin raid set and does not have this problem after updating their bios, please let me know.

I just cloned my drive C: and will be updating this new bios. Maybe ASUS has solved this problem, I will let you know.

[HiVizMan]

OK you and I do things exactly the same way. 🙂


Next questions could you please specify the SSD that you are using in this RAID array.

[Breimeister]

HiVizMan wrote:
OK you and I do things exactly the same way. 🙂


Next questions could you please specify the SSD that you are using in this RAID array.

Two Mushkin Chronos Deluxe 240GB with their latest 5.07 firmware.

I just finished with the bios update to 1102 and the same thing happened; guess ASUS did not fix this problem. It is a pain having to clone the drive but that works.

Let me know if you think this problem is caused by the Mushkin SSDs and I will contact them.

[HiVizMan]

SandForce SF-2281 controller on those SSD mate. And there is a compatibility issue with SandForce 2 drivers and Haswell. Nothing further I can do.

[Breimeister]

HiVizMan wrote:
SandForce SF-2281 controller on those SSD mate. And there is a compatibility issue with SandForce 2 drivers and Haswell. Nothing further I can do.

I am sorry to hear that. I just opened a ticket with Mushkin and will let you know what they say. Maybe there is a new beta Sandforce driver out there.

[HiVizMan]

If you do hear something please do let me know too.