Unsolved

1 Rookie

 • 

23 Posts

678

December 29th, 2020 19:00

MD1200 + H810 + 12x4TB - Unexpected Sense Mode Parameters Changed?

We have an R730xd system with an MD1200 Powervault and our sister business has an identical setup. 

On boot we are seeing roughly half the drives report

Controller ID: 1 Unexpected sense: PD
= 00:0:10Mode parameters changed, CDB = 0x88 0x00 0x00 0x00 0x00 0x01 0xd1 0xc0 0xbe 0xaf 0x00 0x00 0x00 0x01 0x00 0x00 , Sense = 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x2a 0x01 0x00 0x00 0x00 0x00

I only see this on boot and it seems to be functioning other than that. I've tried to read the sense data and make sense of it but its beyond me unless someone could help me or knows a good guide. 

Our sister business has also seen the below message, is this something to be concerned about? I believe it's only happening on boot as well.

The PD is the powervault 

Controller ID: 1 Unexpected sense: PD = 49-Invalid field in CDB, CDB = 0x12 0x01 0x80 0x00 0x20 0x00, Sense = 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0b 0x00 0x00 0x00 0x00 0x24 0x00 0x00 0x00 0x00 0x00 0x00

We are using ST4000NM0023 Dell Drives with recently updated GS15 firmware.

Thank You

Pat

 

Moderator

 • 

4.7K Posts

December 30th, 2020 06:00

Hello pcorwin85,

 

I'm sorry see you are getting unexpected sense errors on your storage units.  It's good to see things seem to be working fine otherwise.  Did this start after the hard drive firmware update? Have you done a power cycle since the update?

 

I'd recommend start with these steps:

  • Make sure the controller firmware is up to date
  • Power cycle
  • Run consistency check on the virtual disks
  • Export controller log.

 

 

Dell PERC H810 Adapter firmware release 21.3.5-0002

https://dell.to/2KF0v49

 

In OpenManage Server Administrator run a consistency check on the arrays and pull a controller log for the H810 and check for issues.

 

To run consistency check:

In OMSA: Expand Storage>expand controller H810. Select ‘Virtual Disk’. Choose ‘Check Consistency’ from dropdown and Execute.

 

To get controller log:

In OMSA: expand Storage>select the controller H810. Click Information/Configuration hyper link at top.

Use the ‘Controller Task’ drop down> select Export Log, click Execute and Export on next page.

Log will be in Windows folder with file name LSI_####.log

 

Please let me know how it goes.

1 Rookie

 • 

23 Posts

December 30th, 2020 13:00

Alright I got a copy of the log,

here is the dropbox link https://www.dropbox.com/s/2qlbtg9jbo8fzdm/lsi_1230.log?dl=0

From What Ive read its a mode change requested by the controller? It doesn't appear to cause any issue, our powervault has the dual emm modules and its as a single unit, i forget the term. It has both emm modules connected to the controller and this is the only single thing I can see that pops up.

In addition to the afformentioned sense from the powervault itself.

I found today that this same message happens to our 3rd powervault connected to a client server, there has been no issues with the system since its installation almost a year ago, it just posts this message on boot.

Moderator

 • 

4.7K Posts

December 30th, 2020 14:00

Thank you for the update and the log.  I do see the H810 and the EMM are on the latest firmware.

 

You are correct about the first sense key  6/2a/1 =  mode parameters changed. It doesn't appear to cause any problems.

You could run the hardware diagnostics to give the drives a test:

 

Run diagnostics

Boot to  F11 on Dell Splash screen, selecting  Boot Manager -> System Utilities -> Launch Dell Diagnostics.  Note any error messages and continue testing.

 

The second sense key  5/24/0 sense key is a non-fatal informational message. It means there was an illegal request made due to an invalid field in the command descriptor block (CDB). The drive ignores this.

 

I'm not seeing any drive failures in the log but it only goes back to 12/10/2020. The array does show it is optimal. Since it only logs those sense keys during post and no errors during normal operation you can ignore those.

 

I'd say give the diagnostics a run on one of the setup and if no failures you should be ok.

1 Rookie

 • 

23 Posts

December 31st, 2020 10:00

So far everything seems fine, I did lose two drives the other day but the system had only just been brought online, I'm not surprised, one suddenly reported 39 sector replacements and presumed bad so I replaced it. the other just.... reset a few times and went offline, luckily I have plenty of replacements and its not in service yet anyways. 

These drives all passed the seatools extended tests too.

Top