BIOS can't read disk after using HPT 3520 controller

[NLight95]

The Highpoint 3520 controller I just purchased I now have to part with because I had to pay for my friend's funeral (I'm still grieving from that). The problem that I'm having is getting my on-board ICH9 to recognize my drives after RAIDing them on the HPT 3520. I've used WD Diagnostics to write zeros to the drives (in this case, two WD7500AAKS) but the ICH9 still doesn't recognize them. When I have them connected to the ICH9 the BIOS just gives an error when trying to read the drives at POST. The drives read fine when connected to the 3520.

I'd like to re-initialize these drives so I can use them with my on-board ICH9 without having to pay WD to do it. If I would have know the 3520 had such issues I never would have purchased it.

[NapalmV5]

you did a quick write? if so, try a full write

i did full write on 4 x wd6400aaks and all 4 are detected on areca/onboard mobo controllers

[NLight95]

you did a quick write? if so, try a full write

i did full write on 4 x wd6400aaks and all 4 are detected on areca/onboard mobo controllers

Yes, I tried a quick write but that didn't take. I will try the full write to see if that makes a difference.

[NLight95]

Even writing zeros to the drives using a FULL ERASE didn't work. The ICH9 of my Maximus Formula still can't see the drives.

Any other suggestions?

[NapalmV5]

theres nothing else to do @ drives

update to latest mobo bios

try the drives on other mobos.. other controllers

[XS Janus]

This isn't maybe PUIS related, that NapalmV5 was talking about in his recent thread?

[NapalmV5]

nlight, what rr3520 bios are you @ ?

[NLight95]

nlight, what rr3520 bios are you @ ?

To wrap this thread up, no matter what I tried the WD7500AAKS drives were unusable after RAIDing them on the 3520 (the Seagate 320s were fine). So I had to RMA the drives back to WD which they replaced. I will no longer consider purchasing any Highpoint controller unless they resolve this issue.