Community
cancel
Showing results for 
Search instead for 
Did you mean: 
KKomp1
Beginner
1,456 Views

iMR 3008 ROC drops new ST300MP0006 SAS disks on board S2600CW2SR

Hi All,

We have a problem with iMR 3008 ROC Integrated HW RAID controller on board S2600CW2SR. We need to replace failed SAS disk to the new one. After inserting new SEAGATE ST300MP0006 disk into the HOT-swap drive cage the rebuild finish successful but 2-3 days later the RAID controller drop this disk. We have tried it more times (take firmware state offline and rebuild again) but same result (it is working only 2-3 days). We have tried another NEW disk as well (same type) but same result. We have set speed limit to 6Gb/sec but same. It seems there is a firmware problem on this LSI HW Raid controller.

This is a live system we need to fix it. What can we do now? Do you have any suggest?

I have attached the Events Log and Term Log from the LSI card.

The new SAS disk type:

Vendor: SEAGATE

Product: ST300MP0006

Revision: N003

Compliance: SPC-4

Rotation Rate: 15052 rpm

Form Factor: 2.5 inches

Baseboard:

S2600CW2SR

Chassis:

P4304XXMFEN2 (Intel Server Chassis P4304XXMFEN2, Single)

Hot-swap Drive Cage Kit:

FUP4X35S3HSDK (3.5in Hot-swap Drive Cage Kit for P4000 Chassis Family FUP4X35S3HSDK, Single)

iMR 3008 ROC Hardware RAID card:

Product Name: Intel(R) Integrated RAID RS3YC

FW Package Build: 24.21.0-0012

BIOS Version: 6.36.00.0_4.19.08.00_0x06180200

Ctrl-R Version: 5.19-0600

FW Version: 4.680.01-8248

NVDATA Version: 3.1705.01-0002

Boot Block Version: 3.07.00.00-0003

0 Kudos
9 Replies
idata
Community Manager
103 Views

Hello w3host,

 

 

Thank you for contacting Intel(R) Technical Support.

 

 

In an effort to better assist you, can please confirm the following:

 

- Is the on-board RAID controller was working fine before or this issue started from first installation?

 

- What type of RAID ARRAY is the server configuration is running?

 

 

Best regards,

 

 

Jeremiah A.

 

Intel(R) Technical Support
idata
Community Manager
103 Views

Also,

 

- Does the issue started after of before doing firmware update?

 

KKomp1
Beginner
103 Views

"Is the on-board RAID controller was working fine before or this issue started from first installation?"

This server and Raid Controller was working fine for about 2 years with OLD SAS disk. This on-board RAID controller handling 6 disks (three RAID1 virtual disks). One of these RAID1 array had been degraded 2-3 weeks ago because of SAS disk failure that is why we started to replace it.

"What type of RAID ARRAY is the server configuration is running?"

3 x RAID 1 arrays

"Does the issue started after of before doing firmware update?"

Same issue exists before the firmware upgrade. We hoped the firmware upgrade will solve this issue but not.

 

Old firmware with same issue:

Firmware upgrade time: Thu Dec 10 21:53:52 2015

Firmware version 4.260.01-3883

Package version 24.6.0-0030

Some info for this Virtual Disk (Now state is Optimal for 2-3 days):

Number of Virtual Disks: 3

Virtual Drive: 0 (Target Id: 0)

Name :

RAID Level : Primary-1, Secondary-0, RAID Level Qualifier-0

Size : 67.054 GB

Sector Size : 512

Is VD emulated : No

Mirror Data : 67.054 GB

State : Optimal

Strip Size : 64 KB

Number Of Drives : 2

Span Depth : 1

Default Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU

Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU

Default Access Policy: Read/Write

Current Access Policy: Read/Write

Disk Cache Policy : Disk's Default

Encryption Type : None

PI type: No PI

Is VD Cached: No

Number of Spans: 1

Span: 0 - Number of PDs: 2

PD: 0 Information

Enclosure Device ID: 62

Slot Number: 4

Drive's position: DiskGroup: 0, Span: 0, Arm: 0

Enclosure position: N/A

Device Id: 26

WWN: 5000C5006C371978

Sequence Number: 2

Media Error Count: 0

Other Error Count: 0

Predictive Failure Count: 0

Last Predictive Failure Event Seq Number: 0

PD Type: SAS

Raw Size: 279.396 GB [0x22ecb25c Sectors]

Non Coerced Size: 278.896 GB [0x22dcb25c Sectors]

Coerced Size: 278.464 GB [0x22cee000 Sectors]

Sector Size: 512

Logical Sector Size: 512

Physical Sector Size: 512

Firmware state: Online, Spun Up

Device Firmware Level: 0008

Shield Counter: 0

Successful diagnostics completion on : N/A

SAS Address(0): 0x5000c5006c371979

SAS Address(1): 0x0

Connected Port Number: 0(path0)

Inquiry Data: SEAGATE ST3300657SS XXXXXXXXXXXX

FDE Capable: Not Capable

FDE Enable: Disable

Secured: Unsecured

Locked: Unlocked

Needs EKM Attention: No

Foreign State: None

Device Speed: 6.0Gb/s

Link Speed: 6.0Gb/s

Media Type: Hard Disk Device

Drive: Not Certified

Drive Temperature :31C (87.80 F)

PI Eligibility: No

Drive is formatted for PI information: No

PI: No PI

Port-0 :

Port status: Active

Port's Linkspeed: 6.0Gb/s

Port-1 :

Port status: Active

Port's Linkspeed: 6.0Gb/s

Drive has flagged a S.M.A.R.T alert : No

PD: 1 Information

Enclosure Device ID: 62

Slot Number: 5

Drive's position: DiskGroup: 0, Span: 0, Arm: 1

Enclosure position: N/A

Device Id: 34

WWN: 5000C5009F7EDBB8

Sequence Number: 18

Media Error Count: 0

Other Error Count: 760

Predictive Failure Count: 0

Last Predictive Failure Event Seq Number: 0

PD Type: SAS

Raw Size: 279.396 GB [0x22ecb25c Sectors]

Non Coerced Size: 278.896 GB [0x22dcb25c Sectors]

Coerced Size: 278.464 GB [0x22cee000 Sectors]

Sector Size: 512

Logical Sector Size: 512

Physical Sector Size: 512

Firmware state: Online, Spun Up

Device Firmware Level: N003

Shield Counter: 0

Successful diagnostics completion on : N/A

SAS Address(0): 0x5000c5009f7edbb9

SAS Address(1): 0x0

Connected Port Number: 1(path0)

Inquiry Data: SEAGATE ST300MP0006 XXXXXXXXXXXX

FDE Capable: Not Capable

FDE Enable: Disable

Secured: Unsecured

Locked: Unlocked

Needs EKM Attention: No

Foreign State: None

Device Speed: 12.0Gb/s

Link Speed: 12.0Gb/s

Media Type: Hard Disk Device

Drive: Not Certified

Drive Temperature :34C (93.20 F)

PI Eligibility: No

Drive is formatted for PI information: No

PI: No PI

Port-0 :

Port status: Active

Port's Linkspeed: 12.0Gb/s

Port-1 :

Port status: Active

Port's Linkspeed: 12.0Gb/s

Drive has flagged a S.M.A.R.T alert : No

idata
Community Manager
103 Views

Hello w3host,

 

 

Thank you for your quick response.

 

 

Looking at your last configuration sent I can see three things:

 

1- The disk you are referring to is not into the drive compatibility list for this server.

 

2- The configuration is showing to link speeds: one for 6GB/s and a second link speed for 12GB/s:

Inquiry Data: SEAGATE ST300MP0006 XXXXXXXXXXXX

Device Speed: 12.0Gb/s

Link Speed: 12.0Gb/s

Port's Linkspeed: 12.0Gb/s

Port-1 :

Port status: Active

Port's Linkspeed: 12.0Gb/s

3- The Raid Arrays are showing two different type of disks:

Inquiry Data: SEAGATE ST3300657SS XXXXXXXXXXXX

 

Inquiry Data: SEAGATE ST300MP0006 XXXXXXXXXXXX

 

 

Can you please check these three factors and confirm?

 

 

Please let me know your results.

 

 

regards,

 

 

Jeremiah A.

 

Intel(R) Technical Support
KKomp1
Beginner
103 Views

Hi Jeremiah,

Thanks for your help.

1. Where can I find disk compatibility list for this server? I have checked now on https://ark.intel.com/products/88276/Intel-Server-Board-S2600CW2SR Intel® Server Board S2600CW2SR Product Specifications page but not found.

2. Yes. Now the link speed of old disk is 6GB/s and link speed of new disk is 12GB/s. Is it not supported? We have set links speed to 6GB/s from storcli.

storcli /cx/phyx set link=<0|1.5|3.0|6.0|12.0>

Phy 1 Information:

SAS Address : 0x5000C5009F7EDBB9

Phy Identifier: 0

Device Type : End Device

Link Speed is : 6.0Gb/s

3. Yes. Now the RAID array contains different type of disks.

Thank You any help and regards,

w3host

idata
Community Manager
103 Views

Hi w3host,

 

 

Thank you for your quick response.

 

 

Yes, the server provides eight-port 12Gbps SAS and 6Gbps SATA interface so it is fine to run the disks at 12GB/s. You can confirm this at the topic: https://www.intel.com/content/dam/support/us/en/documents/server-products/server-boards/S2600CW_TPS_... 3.4.9 Serial Attached SCSI (SAS) Support.

 

 

In order to check the disk compatibility for this server you check the Intel(R) Server Configurator Tool, located https://serverconfigurator.intel.com/exalt/RequestManager?ServletNumber=1&dynamicUser=Y&localinfo=0&... here. Click on Intel Tested Hardware and Operating System List (THOL) Builder.

 

 

Please let me know your results.

 

 

regards,

 

Jeremiah A.

 

Intel(R) Technical Support

 

 

 

 

idata
Community Manager
103 Views

Hello w3host,

 

 

I hope you are doing well today.

 

 

I'm following up with you to see if the information provided helps or still need more assistance from us.

 

 

regards,

 

Jeremiah A,

 

Intel(R) Technical Support
KKomp1
Beginner
103 Views

Hi Jeremiah A,

It seems there is a failed slot in 3.5in Hot-swap Drive Cage Kit (FUP4X35S3HSDK). Maybe it was the first time to replace disk in this cage slot so we are a little surprised and disappointed.

Before the SAS disk has been dropped there was a lot of 6/29/01 unexpected sense in LSI log file (I attached it in first request). Based on the Wiki ( https://en.wikipedia.org/wiki/Key_Code_Qualifier Key Code Qualifier - Wikipedia ) the meaning of this sense is:

Unit Attention - POR occurred

Next sense is 2/04/01: Not Ready - becoming ready

Why?

After that we have checked the S.M.A.R.T info on this disk.

Accumulated start-stop cycles: 342

This server was stopped only one time since this SAS disk has been replaced (NOT 342). So we have moved it to the other slot and we have no problem from that time. As I mentioned earlier we have replaced the SAS disk with new one (same type) into the same slot but NOT resolved this problem. So it is more than a simple contact problem.

Thanks for Your help!

Regards,

w3host

idata
Community Manager
103 Views

Hello w3host,

 

 

Thank you for your information. Based on the same I will go ahead and close this case.

 

 

Thank you for contacting Intel(R) Technical Support

 

 

Best regards,

 

Jeremiah A.

 

Intel(R) Technical Support
Reply