This is from Oracle support portal:
fmdump -eV reports ereport.io.scsi.cmd.disk.dev.rqs.derr associated with SCSI Mode Select or SCSI Mode Sense commands (Doc ID 1519925.1)
Applies to:
Solaris Operating System - Version 11 and later
Information in this document applies to any platform.
Symptoms
The Fault Manager Daemon (fmd) runs in the background on each Solaris system and receives telemetry information relating to problems detected by the system software, diagnoses these problems, and initiates proactive self-healing activities such as disabling faulty components. Reference the fmd and fmdump man pages for more information.
The following events from the fault management error log are typically triggered by the Fault Manager Daemon disk-transport module:
% sudo fmdump -eV -c ereport.io.scsi.cmd.disk.dev.rqs.derr
TIME CLASS
Dec 26 2012 17:09:27.369690466 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0xc2ded966d3f02c01
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
cna_dev = 0x50db753a0000002d
device-path = /pci@0,0/pci8086,3c04@2/pci1000,3000@0/iport@f/disk@w5000a72b30066ac0,0
devid = id1,sd@n5000a72030066ac0
(end detector)
devid = id1,sd@n5000a72030066ac0
driver-assessment = info
op-code = 0x15
cdb = 0x15 0x11 0x0 0x0 0x20 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x5
asc = 0x26
ascq = 0x0
sense-data = 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0x18 0x0 0x0 0x0 0x0 0x26 0x0 0x0 0x0 0x0 0x0 0x0 0x0
__ttl = 0x1
__tod = 0x50db7597 0x16090762
Jan 02 2013 04:44:01.961151613 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0x9a922c06ff304001
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
cna_dev = 0x50db753a0000018d
device-path = /pci@0,0/pci8086,3c08@3/pci1000,3020@0/iport@40/disk@w5e83a97000003ef3,0
devid = id1,sd@n5e83a97f0f19a1a0
(end detector)
devid = id1,sd@n5e83a97f0f19a1a0
driver-assessment = fail
op-code = 0x1a
cdb = 0x1a 0x0 0x3 0x0 0x24 0x0
pkt-reason = 0x0
pkt-state = 0x37
pkt-stats = 0x0
stat-code = 0x2
key = 0x0
asc = 0xfe
ascq = 0xca
sense-data = 0x40 0x1 0x0 0x0 0xfe 0xca 0xdd 0xba 0xfe 0xca 0xdd 0xba 0xfe 0xca 0xdd 0xba 0xfe 0xca 0xdd 0xba
__ttl = 0x1
__tod = 0x50e40161 0x394a027d
Changes
The following DTrace script was used to identify the trigger of the SCSI MODE SENSE command resulting in error class ereport.io.scsi.cmd.disk.dev.rqs.derr events:
#!/usr/sbin/dtrace -qs
/*
* Identify trigger of modesense resulting in ereport.io.scsi.cmd.disk.dev.rqs.derr fma events.
*
*/
BEGIN
{
printf("Control+C to interrupt\n");
}
fbt:sd:sd_send_scsi_MODE_SENSE:entry
{
printf("%s+%x triggered by:\n", probefunc, arg0);
printf("UID=%d PID=%d PPID=%d CMD=%s\n",
curpsinfo->pr_euid,pid,curpsinfo->pr_ppid,curpsinfo->pr_psargs);
ustack();
stack();
exit(0);
}
Sample output:
% sudo ./modesense.d
Control+C to interrupt
sd_send_scsi_MODE_SENSE+ffffc1c04a178800 triggered by:
UID=0 PID=898 PPID=1 CMD=/usr/lib/fm/fmd/fmd
libc.so.1`syscall+0x13
libc.so.1`__open+0x29
libc.so.1`open+0xc7
libdiskstatus.so.1`disk_status_open+0x4a
disk-transport.so`dt_test_disk+0xae
disk-transport.so`dt_timeout+0xc9
fmd`fmd_module_dispatch+0x207
fmd`fmd_module_start+0x11b
fmd`fmd_thread_start+0x60
libc.so.1`_thrp_setup+0x9d
libc.so.1`_lwp_start
sd`sd_get_physical_geometry+0xbf
sd`sd_tg_getinfo+0x1d3
cmlb`cmlb_resync_geom_caches+0x140
cmlb`cmlb_validate_geometry+0x9a
cmlb`cmlb_validate+0x5b
sd`sd_ready_and_valid+0x249
sd`sdopen+0x28a
genunix`dev_open+0x55
specfs`spec_open+0x606
genunix`fop_open+0x183
genunix`vn_openat+0x736
genunix`copen+0x493
genunix`openat32+0x27
unix`_sys_sysenter_post_swapgs+0x149
Note the CMD=/usr/lib/fm/fmd/fmd, the associated module disk-transport.so, and function dt_test_disk.
% sudo fmadm config | egrep "MODULE|disk-transport"
MODULE VERSION STATUS DESCRIPTION
disk-transport 2.1 active Disk Transport Agent
Cause
A decode of the first error event above:
op-code = 0x15 -> MODE SELECT(6)
stat-code = 0x2 -> CHECK CONDITION
key = 0x5 -> ILLEGAL REQUEST
asc = 0x26 ascq = 0x0 -> INVALID FIELD IN PARAMETER LIST
A decode of the second error event above:
op-code = 0x1a -> MODE SENSE(6)
cdb = 0x1a 0x0 0x3 0x0 0x24 0x0 -> SCSI Mode Page 0x3 -> Format parameters (direct-access devices)
stat-code = 0x2 -> CHECK CONDITION
key = 0x0 -> NO SENSE
As there is no sense, the sense data displayed is a little-endian 0xfe 0xca 0xdd 0xba. Note that a buffer with value of 0xbaddcafe indicates the buffer has been allocated, but is uninitialized.
Support for SCSI Operation Codes 0x15 MODE SELECT(6) and 0x1a MODE SENSE(6) is optional for everything except SEQUENTIAL ACCESS DEVICES, i.e. tape drives.
The SCSI Mode Select command is used to modify device information contained in mode pages in a SCSI target device.
The SCSI Mode Sense command is used to obtain current device information from mode pages in a SCSI target device.
From the SCSI Primary Commands Specification:
If the logical unit does not implement saved mode pages and the SP bit is set to one, then the command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
If an application client issues a MODE SENSE command with a page code or subpage code value not implemented by the logical unit, the command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
If the following is correctly returned in response to an unsupported MODE SELECT or MODE SENSE command, the Fault Manager Daemon should not create an error event:
stat-code = 0x2 -> CHECK CONDITION
key = 0x5 -> ILLEGAL REQUEST
asc = 0x24 ascq = 0x0 -> INVALID FIELD IN CDB
An enhancement was implemented in Solaris 11.3 and higher such that Fault Management Architecture (FMA) now logs an event where the driver assessment is info as an informational report (ireport), not an error report (ereport), such as an ILLEGAL REQUEST associated with a MODE SELECT command.
For SCSI Operation Codes reference
http://www.t10.org/lists/op-num.txt
For SCSI Status Codes reference:
SCSI Status Codes
For SCSI Sense Keys reference:
SCSI Sense Keys
For SCSI ASC/ASCQ Assignments reference:
http://www.t10.org/lists/asc-num.txt
Solution
Contact the disk vendor for updated firmware which complies with the SCSI Primary Commands Specification.