HEXUS.reviews :: The joys of redundancy: XFX's Revo 64

[zed]

I am using on a Win 2k3 server with 3 x 500Gb WD SATA drives - has been running a few weeks and is great value for money. It did however, stop a reboot once - it stopped at the card's BIOS screen and had to be power on and off. Maybe a BIOS upgrade may fix but have not had any other issues and it has only done this once. The server is not heavily used.

[Barkotron]

Also interested in this one as I'd like a completely off-CPU solution: however, I just want RAID1, for now at least. Does this do RAID1 as well? I couldn't find it mentioned anywhere. Surely it does though, right?

[hexusbrowser1]

Hi I bought one of these cards a couple of months ago and have been quite happy with it.

However, recently i noticed that it said a drive 2 was unassigned and that the array was degraded.

Thinking I'd dislodged a cable while doing other things I rebuilt the array and carried on.

However, a few hours later it came up with a red X against drive 0, with (EC: 1).
I backed up everythig and rebooted. On rebooting it just said the drive was unassigned (exclamation mark, and not a red X) and (EC:0) on it so I rebuilt it again.
I have a feeling this happened with the other drive but I hadnt noticed.

These are brand new WD RE2 enterprise class drives and although they could have both failed I think something else is going on. Has anyone else experienced issues like this with their card?
Zed, what WD drives are you using, the same?

I'm thinking of getting a Synology CS407 NAS, putting the disks in there and using a raptor in my desktop.

Cheers,

Tom.

[chuckskull]

Hexusbrowser1 this thread might shed some light on the problems you're having or at least put you in touch people who've had the same experience.

http://forums.hexus.net/news/78203-r...light=XFX+revo

[zed]

Hi I bought one of these cards a couple of months ago and have been quite happy with it.

However, recently i noticed that it said a drive 2 was unassigned and that the array was degraded.

Thinking I'd dislodged a cable while doing other things I rebuilt the array and carried on.

However, a few hours later it came up with a red X against drive 0, with (EC: 1).
I backed up everythig and rebooted. On rebooting it just said the drive was unassigned (exclamation mark, and not a red X) and (EC:0) on it so I rebuilt it again.
I have a feeling this happened with the other drive but I hadnt noticed.

These are brand new WD RE2 enterprise class drives and although they could have both failed I think something else is going on. Has anyone else experienced issues like this with their card?
Zed, what WD drives are you using, the same?

I'm thinking of getting a Synology CS407 NAS, putting the disks in there and using a raptor in my desktop.

Cheers,

Tom.

I'm actually using 3 x 320Gb 16Mb cache WD SATA drives (not 500Gb as I wrote above). I think I got the server version drives WD3200YS and they are so far running fine. These are the RE drives rather than RE2. The locking up on reboot was sorted by a firmware reboot and I also used a normal audio cable to link the HDD activity connector to the Dell SCSI LED input connector so the Hard disk LED light up on the case. Hope that helps.

[hexusbrowser1]

Thanks Chuckskull and Zed,

Having had this card play up already and read through other posts I no longer feel I can trust it.
I'm going to get another couple of WD harddisks (one spare) and put them in the cs407 synology I just bought.

Cheers,

Tom

[Johne]

Guys

I'm currently trying to use a Silicon Image SiI 3114 SATARaid Controller with 3 x 232 maxtor drives and XP will not recognise raid 5. What I would like to know is will vmware esxi work as that is what i'm really interested in doing?