Request:-  6th May 2007 at 22:52
        I was testing the array recovery process and so I created 
an array and installed. That worked fine so I unplugged 
drive 0 and everything worked as I expected. I then 
formatted the drive and reattached it. When I attempted to 
rebuild the array the BIOS said the disk was too small.

Running tw_cli shows inconsistent results. I have attached 
a log.


Response:- 7th May 2007 at 8:36
        Hi Daniel, 

Kindly contact the Western Digital and make sure the drive firmware is updated and then try the rebuild. Let me know if this helps.

Sincerely,
AMCC Customer Support, 
Tech 6. 



Request:-  12th May 2007 at 20:59
        I've had a look but there's no firmware upgrade for the WD3200YS available.


Response:- 14th May 2007 at 7:4
        Hi Daniel, 

It seems to be drive compatability issue. Can you kindly try a different brand hard drive and rebuild the array. 

Sincerely,
AMCC Customer Support, 
Tech 6.

Request:-  14th May 2007 at 18:8
        I don't have any other 320GB drives available.
I don't see how it can really be a compatibility issue - I created the array just fine with these 2 disks.

I have 5 or so other machines with the same model hard disk in them and they seems to work fine too.


Response:- 14th May 2007 at 20:3
        Hi Daniel, 

Kindly try the rebuild by using ignore ECC errors and let me know if the rebuild works. Kindly check the following KB
http://3ware.com/KB/article.aspx?id=11956

Sincerely,
AMCC Customer Support, 
Tech 6.

Request:-  14th May 2007 at 20:17
        It still fails..
//egbert> /c0/u1 start rebuild disk=0 ignoreECC
Sending rebuild start request to /c0/u1 on 1 disk(s) [0] ... Failed.

(0x0B:0x0036): Replacement drive is too small for rebuild operation


Response:- 15th May 2007 at 7:10
        Hi Daniel, 

This error code denotes the different block size (0x0B:0x0036) Can you try with an another hard disk. 

Sincerely,
AMCC Customer Support, 
Tech 6.

Request:-  15th May 2007 at 16:34
        I will try it tomorrow (I am not at work today), however I think you're missing the point - I made the array with those 2 disks to begin with and there was no problem.

They are identical model disks! They certainly were identical in size when I created the array.


Response:- 15th May 2007 at 20:7
        Hi Daniel, 

There are chances of changes in the disk drive blocks from the identical size disks too. Kindly give a try let me know if this helps.

Sincerely,
AMCC Customer Support, 
Tech 6.

Request:-  16th May 2007 at 22:52
        I tried a fresh disk and it worked.

However I did check the size of the disks - they are identical.

Also, since the disk causing the problem was in the array originally I don't see how it would have magically shrunk.

I suspect that the firmware is getting confused somehow because the disk was once in an array. I will try fully erasing it to see if there is some metadata hiding in it that is being read by mistake.


Response:- 17th May 2007 at 6:40
        Hi Daniel, 

After testing please get back to us with the result.

Thanks

AMCC Customer Support,
Tech 6.

Request:-  22nd May 2007 at 0:18
        It had no effect :(


Response:- 22nd May 2007 at 6:34
        Hi Daniel, 

Then it seems to be a bad drive. 

Sincerely,
AMCC Customer Support, 
Tech 6.

Request:-  18th June 2007 at 19:7
        I am less than impressed with your tardiness in responding to my problem. It is compounded by the fact that your system automatically closes the ticket after 2 weeks of *your* inactivity.



Response:- 18th June 2007 at 20:27
        Hi Daniel,

We are working on this. Still we get the solution to case the case will not be closed. Once this is implemented the cases wont be closed automatically after 2 weeks.

Thanks

AMCC Customer Support,
Tech 6.