Raid build keeps failing

[beng]

G'day Barrday,
We have just started getting an error that I wonder if it is related.
The scenario is a we have a single Adaptec 5405 card in a Intel SSR212MC2, which has the onboard controller disabled, and 12x Seagate ES.2 1TB drives installed.

The firmware and Bios on the card are 5.2.0 while DSS is 5.0.DB47000000.3178 and the "Driver" is reported as 1.1.5 (2455). Drives are Seagate ES.2 1TB with the "Raid" AN05 firmware.
(But the current Linux driver on the Adaptec site is 1.1.5 (2459)? is this an issue?)

We have had numerous errors and faults with the arrays on the controller and not able to make them "Optimal". The current configuration is all 12 in a Raid6 Array, when the array controller was told to "Verify and Fix" it got to 15% and then sent an alert:
Event Description: Build/Verify failed: controller 1, logical device 1 ("array0") [0x00].
When we investigate further the Agent log states that the drive in Slot 8 has been removed. Which is clearly not the case, after a "rescan" Slot 8's drive returns and it is now "rebuilding" it.
So does this sound like the same issue you are having?
I can't figure out why the controller thinks a drive has been "removed".... to me that is a drive failure, but so far we have lost Slot 11,10,9 and 8, so I doubt it as a true error.

BTW, unrelated we also had the error when we tried to create an iSCSI VMFS, until we created a FS on it first, THEN went and created the VMFS, worked like a charm after that.

So, anyone else using the Adaptec 5805 and finding issues?

Rgds Ben.

[nightmare99]

*** Please ignore me I just reread the post and noticed you already have the AN05 firmware ***

We have just started getting an error that I wonder if it is related.
The scenario is a we have a single Adaptec 5405 card in a Intel SSR212MC2, which has the onboard controller disabled, and 12x Seagate ES.2 1TB drives installed.

This is a bad issue, basically its the HDD's, you need a special firmware called AN05. Seagate have handled this very badly in my opinion I have spoken to thier support on live chat several times and they flat out denied an AN05 firmware existed. I manged to get SN05 out of them (my drives wree on SN04) but after pressing I managed to get AN05, you can get the download links from adatec now here http://ask.adaptec.com/scripts/adapt...i=&p_topview=1. Apparently the ES.2s don't like the Intel IOP used on alot of SAS raid cards, (this includes other makes as well if you check thier drive THOL lists you will see they are listing AN05 firmware as a requirement). Also there is a 4 page thread over on the Seagate forums regarding this issues which is how I found out about it. Alos btw the ES.2 drives aren't on Intel's THOL for the SSR212MC2 so don't ask them for any help as they will just tell you to foxtrot oscar!

[beng]

G'day Nightmare,
Not at all, thanks for the input.
I did know that there were issues with the some SAS/SATA Raid controllers with the ES.2 (didn't know it was specifically the intel IOP though), that's why we went with the Adaptec 5405 which did support the Seagates....
It's amazing, if you read the post it specifies the 2xxx and 5xxx cards need AN05 and the others 3xxx etc need SN05.
Makes a mockery of "Unified" controllers, since the main reason we have stuck with the Adaptecs was because we could then easily shift Arrays from one server to another.

The symptoms are so similar, I wonder if it is possible to have the drives report the AN05 firmware but not actually have it installed.
ie we did the updates, but I wonder if something was screwy with the process.
Nah what are the chances that they don't do a CRC? :-)

Cheers Ben.

[nightmare99]

Do you have a different raid card you can try beng? or I would be interested to know if they work ok using the onboard SAS controller and open-e soft raid. If it doesnt work with the onboard your issue maybe the enclosure.

@Barrday what hard drives are you using?

[beng]

Yep, that is our next plan, but also have problems with the GBE Nics on this machines as well (1% sustained throughput....) yet the hdparm output is 350MB/s, plus it is also "sort of in use.. by the client" so they don't want us to touch it unless we are sure of a fix.
I'd rather not use the onboard, as one of the reasons for this config was to include the separate cards for DRP, ie technically we could switch the card/drives to another box and bring the array back up.....

Rgds Ben