Home > Error For > Error For Command Inquiry Error Level Informational

Error For Command Inquiry Error Level Informational

Contents

ESX-1271657 19:49:44 05/23/07 Open IPMI improvement for slowness. ESX-2031037 19:47:16 05/23/07 To provide LUN an unique ID Name ESX-1917602 19:47:52 05/23/07 To improve compatibility for Windows NT. Unix Systems Engineer having 7.5 years of Experience in IT industry having steep knowledge and experience in various Unix operating systems like Solaris,Linux, HP-UX and AIX. Fortunately your driver just shrugs them off. get redirected here

You can not post a blank message. Re: SCSI Errors: Solaris 10 x86 on ESX 3.0.1 Texiwill Jun 24, 2008 5:05 AM (in response to ETAVIS_GNS_AG) Hello,Look at your vmkernel logfiles for information. The driver should make the determination as to when to call this function based on the severity of the failure and the severity level that the driver wants to report. Select the HF and install it REMOVING THE PATCH ------------------ 1. https://community.oracle.com/thread/1950114

Error For Command Inquiry Error Level Informational

Re: SCSI Errors: Solaris 10 x86 on ESX 3.0.1 mikepodoherty Jun 24, 2008 5:18 AM (in response to ETAVIS_GNS_AG) What sort of storage are you using? I'm hazarding a guess here, but it looks like something is sending a NULL or zero values that happens to align to the cdb field of your driver code. ESX-1001213 17:02:48 04/24/08 Security update for samba packages. If so, it's a known Oracle issue.

  1. That's 5 years old; that is in no way shape or form "very old" nor "many years".
  2. This entry: scsi_errmsg(devp, pkt, "sd", SCSI_ERR_INFO, bp->b_blkno, err_blkno, sd_cmds, rqsense); Generates: WARNING: /[email protected],f8000000/[email protected],800000/[email protected],0 (sd1): Error for Command: read Error Level: Informational Requested Block: 23936 Error Block: 23936 Vendor: QUANTUM Serial Number:
  3. Everything I have read states it's an optional page; one cannot travel back in time and implement page 0x83 on devices which were made prior to such a specification update.
  4. Re: Daily Messages relating to (invalid field in cdb) 807567 Jun 2, 2010 11:42 PM (in response to 807567) Well, the iostat process is puzzling...it will produce a standard iostat report
  5. Navigate to Settings - Deployment Management tab. 4.
  6. The problem with the rejection is that the Solaris kernel logs this in such a way that it appears as a disk failure to our NOC, which results tickets opened to
  7. severity selects which string is used in the "Error Level:" reporting, according to the following table: Severity Value:String: SCSI_ERR_ALLAll SCSI_ERR_UNKNOWN SCSI_ERR_INFO SCSI_ERR_RECOVERE SCSI_ERR_RETRYABL SCSI_ERR_FATAL blkno is the block number of the
  8. CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization Like Show 0 Likes (0) Actions 4.
  9. sensep may be NULL, in which case no sense key or vendor information is displayed.

ESX-8253547 16:58:35 04/24/08 Security update for gcc packages. drv_name String used by scsi_log(9F). ESX-6657345 20:07:54 05/23/07 iSCSI device failed with check condition ESX-7408807 20:08:37 05/23/07 Hang when booting with one local mirror. ESX-1002096 17:13:36 04/24/08 Qlogic firmware update.

Re: Daily Messages relating to (invalid field in cdb) 807567 Jul 23, 2010 8:32 AM (in response to 807567) Best guess is a application on the host is sending a scsi Error The following messages are being logged in /var/adm/messages every 30 minutes Sep 19 18:24:26 nyriprddb2 scsi: [ID 107833 kern.warning] WARNING: /[email protected],700000/[email protected]/[email protected],0 (sd1): Sep 19 18:24:26 nyriprddb2 Error for Command: inquiry Pretty much all our Fujitsu disks behave like this -- more than just the model shown above (smaller models, etc.). https://community.hpe.com/t5/Storage-Area-Networks-SAN/SAN-Disk-Error-Message-in-Solaris/td-p/4692564 comment:6 follow-ups: ↓ 7 ↓ 8 Changed 4 years ago by koitsu2009 The disk was manufactured in 2007.

Re: Daily Messages relating to (invalid field in cdb) 807567 Jun 2, 2010 10:40 PM (in response to 807567) Hi Michael, Thanks for your reply, I did check the cron and You can not post a blank message. The server is a Sun-Fire V440 running Solaris 9 with c1t0d0 and c1t1d0 hardware raided. Re: Daily Messages relating to (invalid field in cdb) 807567 Jun 2, 2010 11:39 PM (in response to 807567) I managed to obtain some old explorers for the server (from 2007

cmdlist is a mapping table for translating the SCSI command code in pktp to the actual command string. The HF040111900-01 should be visible in the table below. 5. Error For Command Inquiry Error Level Informational ESX-1541239 20:01:35 05/23/07 Updates Emulex Fibre Channel driver. The cmdlist is described in the structure below: struct scsi_key_strings { int key; char *message; }; For a basic SCSI disk, the following list is appropriate: static struct scsi_key_strings

I've seen cases where the SAN "loses" the information about the servers on the LUN and the servers have to be represented. Get More Info ESX-1001693 17:00:39 04/24/08 Security update for openldap packages. ESX-9287937 16:57:04 04/24/08 Fix shutdown panic in mptscsi_2xx driver ESX-8567382 16:57:26 04/24/08 Security update for gdb packages. ESX-1000073 20:15:26 05/23/07 Updated krb5 packages with security fix.

no one of the solaris machines has a iscsi connection. err_blkno is the block number where the error occurred. I am inclined to believe these messages existed since installation of the server. useful reference sensep may be NULL, in which case no sense key or vendor information is displayed.

Re: SCSI Errors: Solaris 10 x86 on ESX 3.0.1 ETAVIS_GNS_AG Jul 4, 2008 12:21 AM (in response to mikepodoherty) its a HP EVA 6100. Same with the vmstat. ESX-6075798 19:50:34 05/23/07 Force vmxnet module to be installed 1st.

LUID lookup via VPD query does not work on these drives.

blkno Requested block number. All rights reserved. decode_fru is expected to return pointer to a char string if decoding possible and NULL if no decoding is possible. Please type your message and try again. 7 Replies Latest reply: Jul 21, 2008 9:14 PM by Colin Neeson SCSI Errors: Solaris 10 x86 on ESX 3.0.1 ETAVIS_GNS_AG Jun 19, 2008

ESX-5885387 19:51:06 05/23/07 RedHat Moderate: gzip security update ESX-5031800 19:51:37 05/23/07 RHSA-2006:0749 tar security update ESX-3199476 19:52:24 05/23/07 VMXNET shutdown may lead to BSOD ESX-9865995 19:53:33 05/23/07 LUNs of MSA Array The cmdlist is described in the structure below: struct scsi_key_strings { int key; char *message; }; For a basic SCSI disk, the following list is appropriate: static struct scsi_key_strings scsi_cmds[] = Or at least I have a hard time remembering a good way to attack such an issue that isn't brute-force in approach: with DTrace on Solaris 10, it's gotten easy to this page Any help will be greatly appreciated.

I will take this up with Fujitsu, as I think that path is better overall compared to adding more quirk-nonsense to smartmontools. I'm afraid I don't know how to verify the TOD chip and if its programmable. Re: Daily Messages relating to (invalid field in cdb) 807567 Jun 3, 2010 2:15 AM (in response to 807567) Perhaps the data passed by the LSI card to scsi inquiry is This will take you to the page which shows the status of the HF on all hosts. 4.

Show 11 replies 1. do you think this messages occures, when the multipahting switches to an other path? ESX-1002972 17:14:55 04/24/08 util-linux security update ESX-1002968 17:15:28 04/24/08 Samba security update ESX-1002964 17:16:03 04/24/08 Perl security update (RHSA-2007:0966-01) ESX-1002963 17:16:39 04/24/08 Patches remote root exploit in OpenPegas ESX-1002962 17:17:10 04/24/08