Menu
▾
▴
Re: [smartmontools-support] Update 490258-290694082 - RE: SmartCtl LSI FW logs -wait for response from smartmontool
|
From: Chanda Y. (cyadaval) <cya...@ci...> - 2013-10-23 18:36:01
|
I haven't heard from smartmon folks. CC'ing smartmontools-support. thanks. chanda From: Satriya, Erni [mailto:Ern...@ls...] Sent: Wednesday, October 23, 2013 11:28 AM To: Chanda Yadavalli (cyadaval); Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Rose, Grant; Pierce, Mark; Cook, Harold E; Alex Samorukov (ml...@os...); Christian Franke (Chr...@t-...) Subject: RE: Update 490258-290694082 - RE: SmartCtl LSI FW logs -wait for response from smartmontool Hi Chanda, Alex, Christian, Any feedback on Lai-Ying’s inquiry below? Thanks, -Erni From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...] Sent: Monday, October 14, 2013 2:04 PM To: Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark; Cook, Harold E; Alex Samorukov (ml...@os...<mailto:ml...@os...>); Christian Franke (Chr...@t-...<mailto:Chr...@t-...>) Subject: RE: Update 490258-290694082 - RE: SmartCtl LSI FW logs -wait for response from smartmontool Adding smartmontools folks, Alex and Christian. From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Monday, October 14, 2013 1:50 PM To: Chanda Yadavalli (cyadaval); Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark; Cook, Harold E Subject: RE: Update 490258-290694082 - RE: SmartCtl LSI FW logs -wait for response from smartmontool Hi Chanda, How does SmartCtl handle the drive does not support/enable “Smart”? Should that be check before issuing any Smart command? Please see Identify Device Data as I listed below. Thanks, Lai-Ying From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...] Sent: Monday, October 14, 2013 1:42 PM To: Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark; Cook, Harold E Subject: RE: Update 490258-290694082 - RE: SmartCtl LSI FW logs -wait for response from smartmontool Hello Lai, Here's the response from smartmontools support – see in bold below. thanks. chanda -----Original Message----- From: Alex Samorukov [mailto:ml...@os...] Sent: Monday, October 14, 2013 1:37 PM To: Chanda Yadavalli (cyadaval); Christian Franke Cc: sma...@li...<mailto:sma...@li...> Subject: Re: [smartmontools-support] smartctl health check fails On 10/14/2013 09:56 PM, Chanda Yadavalli (cyadaval) wrote: > Hello Alex and Christian, > > We did some experiments where we commented out the SMART STATUS check > in both JBOD and RAID modes. In JBOD mode, we use: > "smartctl -H /dev/sdb", and in RAID mode, we use "smartctl -H /dev/sdb -d megaraid,4". > > In the first case, we get back rc=0 and in the second case, rc=4. > > LSI says they retun same error status in both cases, but smartctl > seems to report it differently. In JBOD mode controller exporting all devices to FS as normal disk devs, so megaraid IOCTL based API is not in use at all. It is great that LSI trying to deal with this, my requests were [silently] ignored. I would recommend them to look on the code, e.g. @ http://sourceforge.net/p/smartmontools/code/HEAD/tree/trunk/smartmontools/os_linux.cpp#l865 . If they can provide a patch to get the SMART health status (or some reference code to do this) i would be happy to add patch to the product. But from my personal point of view problem is in the firmware SAT layer. From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Monday, October 14, 2013 12:48 PM To: Chanda Yadavalli (cyadaval); Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark; Cook, Harold E Subject: Update 490258-290694082 - RE: SmartCtl LSI FW logs -wait for response from smartmontool Hi Chanda, Yes, please do. We need to understand the different status on the same command to the same PD between JBOD mode or member of RAID volume. Thanks, Lai-Ying From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...] Sent: Monday, October 14, 2013 12:25 PM To: Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark; Cook, Harold E Subject: RE: SmartCtl LSI FW logs Lai, Is it ok to forward your response to smartmontool support? thanks. chanda From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Thursday, October 10, 2013 4:26 PM To: Chanda Yadavalli (cyadaval); Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark; Cook, Harold E Subject: RE: SmartCtl LSI FW logs Hi Arvind and Chanda, Firmware returned the same error status from the drive on 0xda Smart command for both JBOD and RAID modes. 0x2d (45.) - MFI_STAT_SCSI_DONE_WITH_ERROR SmartCtl may report the status differently between JBOD and RAID. Further investigation on error status is due to the drive does not support Smart. Please refer to Identify Device data. Commands and feature sets supported Word 82: bit 0 : 1 = The SMART feature set is supported Word 84: bit 0 : 1 = SMART error logging is supported bit 1 : 1 = The SMART self-test is supported Commands and feature sets supported or enabled Word 85: bit 0 : 1 = The SMART feature set is enabled Word 87: bit 0 : 1 = SMART error logging is supported bit 1 : 1 = SMART self-test supported -------------------------------------------------- LINUX_JBOD_smartctl.log: === START OF READ SMART DATA SECTION === REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK Input: FR=0xda, SC=...., LL=...., LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 [ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ] scsi_status=0x2, host_status=0x0, driver_status=0x8 info=0x1 duration=72 milliseconds resid=0 >>> Sense buffer, len=22: 00 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 10 00 4f 00 c2 40 50 status=2: [desc] sense_key=1 asc=0 ascq=1d Values from ATA Return Descriptor are: 00 09 0c 00 00 00 00 00 00 00 4f 00 c2 40 50 [Duration: 0.072s] Output: ERR=0x00, SC=0x00, LL=0x00, LM=0x4f, LH=0xc2, DEV=0x40, STS=0x50 REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK returned 0 SMART overall-health self-assessment test result: PASSED LINUX_smartctl_da.log === START OF READ SMART DATA SECTION === REPORT-IOCTL: Device=/dev/sda Command=SMART STATUS CHECK Input: FR=0xda, SC=...., LL=...., LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 [ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ] sat_device::ata_pass_through: scsi_pass_through() failed, errno=5 [megasas_cmd result: 1.4 = 0/45] [Duration: 0.076s] REPORT-IOCTL: Device=/dev/sda Command=SMART STATUS CHECK returned -1 errno=5 [megasas_cmd result: 1.4 = 0/45] SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. LSIFW_JBOD_smartctl.log 10/10/13 21:08:21: MfiCmdIssue: mf=c05aaa00, cmdId=1, ctx=16, mfa=7716d400, cmd=4, mfiFlags=0x22 10/10/13 21:08:21: CMD_PCI: cmd=03, cmdId=1, nsg=0, pd=04, timeout=0, cdb= 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 10/10/13 21:08:21: DCDB at 7716d400 done: ss= 2sd=72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 4f 10/10/13 21:08:21: DONE: id=1, status=2d 10/10/13 21:08:21: MfiCmdDone(cmdId=1, status=2d extStatus=2) LSIFW_smartctl_send_da.log 10/10/13 17:41:33: MfiCmdIssue: mf=c05aaa00, cmdId=2, ctx=a, mfa=77171400, cmd=4, mfiFlags=0x0 10/10/13 17:41:33: CMD_PCI: cmd=03, cmdId=2, nsg=0, pd=04, timeout=0, cdb= 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 10/10/13 17:41:33: DCDB at 77171400 done: ss= 2sd=72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 4f 10/10/13 17:41:33: DONE: id=2, status=2d 10/10/13 17:41:33: MfiCmdDone(cmdId=2, status=2d extStatus=2) Thanks, Lai-Ying From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...] Sent: Thursday, October 10, 2013 3:12 PM To: Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark Subject: RE: SmartCtl LSI FW logs Here it is. Please note that in JBOD mode, we don't use the "-d megaraid,x" option. thanks. chanda From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Thursday, October 10, 2013 1:56 PM To: Chanda Yadavalli (cyadaval); Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark Subject: RE: SmartCtl LSI FW logs Hi Chanda, Can you please send the firmware log with JBOD mode also? Thanks, Lai-Ying From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...] Sent: Thursday, October 10, 2013 11:51 AM To: Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Satriya, Erni; Rose, Grant; Pierce, Mark Subject: RE: SmartCtl LSI FW logs Lai, We're running Linux 3.10.4. The command passes in JBOD mode, no issues there. I'm now sending the logs in RAID mode, both Linux-side and FW-side logs. As you can see, the SMART STATUS command is now being sent to the FW and it returns failure. [cyadaval@nuo-swvm-02 ~]$ grep "cdb=" LSIFW_smartctl_send_da.log 10/10/13 17:41:32: CMD_PCI: cmd=03, cmdId=2, nsg=1, pd=04, timeout=0, cdb= 12 00 00 00 24 00 10/10/13 17:41:32: CMD_PCI: cmd=03, cmdId=2, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 10/10/13 17:41:32: CMD_PCI: cmd=03, cmdId=2, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 10/10/13 17:41:33: CMD_PCI: cmd=03, cmdId=2, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 d0 00 01 00 00 00 4f 00 c2 00 b0 00 10/10/13 17:41:33: CMD_PCI: cmd=03, cmdId=2, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 d1 00 01 00 01 00 4f 00 c2 00 b0 00 10/10/13 17:41:33: CMD_PCI: cmd=03, cmdId=2, nsg=0, pd=04, timeout=0, cdb= 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 === START OF READ SMART DATA SECTION === REPORT-IOCTL: Device=/dev/sda Command=SMART STATUS CHECK Input: FR=0xda, SC=...., LL=...., LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 [ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ] sat_device::ata_pass_through: scsi_pass_through() failed, errno=5 [megasas_cmd result: 1.4 = 0/45] [Duration: 0.076s] REPORT-IOCTL: Device=/dev/sda Command=SMART STATUS CHECK returned -1 errno=5 [megasas_cmd result: 1.4 = 0/45] SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. So, MEGASAS_IOC_FIRMWARE returns cmd_status = 45 thanks. chanda From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Wednesday, October 09, 2013 11:09 PM To: Arvind Krishnan (arvikris) Cc: Chanda Yadavalli (cyadaval); Satriya, Erni; Rose, Grant; Pierce, Mark Subject: Re: SmartCtl LSI FW logs Do you have this FW log with pcidebug turn on? I can check if the status returned from controller FW. Otherwise, I don't know what is status 45. Do you get this status only in Raid mode and not in JBOD mode? On Oct 9, 2013, at 7:18 PM, "Arvind Krishnan (arvikris)" <arv...@ci...<mailto:arv...@ci...>> wrote: Lai-Ying, We checked with the smartctl developers and determined that smartctl doesn’t issue this particular command when talking to a LSI MR controller (due to issues). The driver is not filtering commands. However, when we actually issued the command, the status returned was 45. Can you please look into what that means? Thanks. --Arvind From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Wednesday, October 09, 2013 7:13 PM To: Arvind Krishnan (arvikris) Cc: Chanda Yadavalli (cyadaval); Satriya, Erni; Rose, Grant; Pierce, Mark Subject: Re: SmartCtl LSI FW logs I don't think so, since I saw the other pass through commands. I will double check with the driver developer tomorrow. What OS is smartctl running under? On Oct 9, 2013, at 3:48 PM, "Arvind Krishnan (arvikris)" <arv...@ci...<mailto:arv...@ci...>> wrote: Lai-Ying, Could the driver filter out the command? What is status 45? Thanks. --Arvind From: Stepan, Lai-Ying [mailto:Lai...@ls...]<mailto:[mailto:Lai...@ls...]> Sent: Wednesday, October 09, 2013 3:15 PM To: Chanda Yadavalli (cyadaval) Cc: Arvind Krishnan (arvikris); Satriya, Erni; Rose, Grant; Pierce, Mark Subject: RE: SmartCtl LSI FW logs Hi Chanda, Are both out files from JBOD mode testing? I can’t find the “[ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ]” issued to controller. The only pass-through commands that I find in the logs are: 10/08/13 19:25:36: CMD_PCI: cmd=03, cmdId=3, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 … 10/08/13 19:25:36: CMD_PCI: cmd=03, cmdId=2, nsg=2, pd=04, timeout=0, cdb= a1 08 2e 00 01 00 00 00 00 ec 00 00 … 10/08/13 19:25:36: CMD_PCI: cmd=03, cmdId=3, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 … 10/08/13 19:25:36: CMD_PCI: cmd=03, cmdId=2, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 d0 00 01 00 00 00 4f 00 c2 00 b0 00 … 10/08/13 19:25:36: CMD_PCI: cmd=03, cmdId=2, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 d1 00 01 00 01 00 4f 00 c2 00 b0 00 From the previous smartctl_health logs; I saw different error status on “85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00” command. Note: 08 – protocol 4 --> PIO Data-In 06 – protocol 3 --> Non-Data Smartctl_health_RAID.txt REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK Input: FR=0xda, SC=...., LL=...., LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 [ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ] sat_device::ata_pass_through: scsi_pass_through() failed, errno=38 [ATA return descriptor not supported by controller firmware] <-- no command/error in FW log REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK returned -1 errno=38 [ATA return descriptor not supported by controller firmware] SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. Smartctl_health_JBOD.txt REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK Input: FR=0xda, SC=...., LL=...., LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 [ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ] scsi_status=0x2, host_status=0x0, driver_status=0x8 <-- scsi status=check condition; don’t about driver status info=0x1 duration=24 milliseconds resid=0 >>> Sense buffer, len=22: 00 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 10 00 4f 00 c2 40 50 <-- no command/error in all your FW logs status=2: [desc] sense_key=1 asc=0 ascq=1d Values from ATA Return Descriptor are: 00 09 0c 00 00 00 00 00 00 00 4f 00 c2 40 50 01 [Duration: 0.025s] Output: ERR=0x00, SC=0x00, LL=0x00, LM=0x4f, LH=0xc2, DEV=0x40, STS=0x50 REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK returned 0 SMART overall-health self-assessment test result: PASSED I don’t have knowledge on SmartCtl application. Can you please check how is “READ SMART DATA SECTION” with “SMART STATUS CHECK command” handled in SmartCtl. Thanks, Lai-Ying From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...]<mailto:[mailto:cya...@ci...]> Sent: Tuesday, October 08, 2013 1:29 PM To: Stepan, Lai-Ying Cc: Arvind Krishnan (arvikris) Subject: RE: SmartCtl LSI FW logs Hi Lai, I am sending two logs, the first one is output of: smartctl –H /dev/sdb And the return code for this is 0. The second one: smartctl –H /dev/sdb –d megaraid, And the return code for this is 4. thanks. chanda From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Tuesday, October 08, 2013 12:55 PM To: Chanda Yadavalli (cyadaval); Arvind Krishnan (arvikris) Cc: Rose, Grant; Satriya, Erni Subject: RE: SmartCtl LSI FW logs Hi Chanda, If the last log that Arvind sent is same test as non-JBOD mode; then I only need the JBOD one. 123m MegaMon>eb pcidebug 1 MegaMon>q Thanks, Lai-Ying From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...] Sent: Tuesday, October 08, 2013 12:38 PM To: Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Rose, Grant; Satriya, Erni Subject: RE: SmartCtl LSI FW logs Hi Lai, I think Arvind already sent you these, right? Do you mean you want the FW logs for JBOD mode? If so, can you tell me again how to enable debug? First: "123m" Then, I tried "ei pcidebug 1", "q", but that didn't work. You typed it in quickly while you were here, but we had to reboot since then. thanks. chanda From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Monday, October 07, 2013 6:44 PM To: Chanda Yadavalli (cyadaval); Arvind Krishnan (arvikris) Cc: Rose, Grant; Satriya, Erni Subject: RE: SmartCtl LSI FW logs Hi Chanda, Can you please send FW logs also? Thanks, Lai-Ying From: Chanda Yadavalli (cyadaval) [mailto:cya...@ci...] Sent: Thursday, October 03, 2013 12:22 PM To: Stepan, Lai-Ying; Arvind Krishnan (arvikris) Cc: Rose, Grant; Satriya, Erni Subject: RE: SmartCtl LSI FW logs Hello Lai-Ying, When this same SATA drive is in JBOD mode, the command succeeds. However, only in RAID mode, we see the error for the SMART STATUS CHECK. Here is an excerpt of the output of smartctl with ioctl logging enabled – both for JBOD mode vs. RAID mode. We are using smartmontools 6.1. Attached are the full logs. Any ideas? thanks. chanda JBOD mode: === START OF READ SMART DATA SECTION === REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK Input: FR=0xda, SC=...., LL=...., LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 [ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ] scsi_status=0x2, host_status=0x0, driver_status=0x8 info=0x1 duration=24 milliseconds resid=0 >>> Sense buffer, len=22: 00 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 10 00 4f 00 c2 40 50 status=2: [desc] sense_key=1 asc=0 ascq=1d Values from ATA Return Descriptor are: 00 09 0c 00 00 00 00 00 00 00 4f 00 c2 40 50 [Duration: 0.025s] Output: ERR=0x00, SC=0x00, LL=0x00, LM=0x4f, LH=0xc2, DEV=0x40, STS=0x50 REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK returned 0 SMART overall-health self-assessment test result: PASSED RAID mode: === START OF READ SMART DATA SECTION === REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK Input: FR=0xda, SC=...., LL=...., LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 [ata pass-through(16): 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 ] sat_device::ata_pass_through: scsi_pass_through() failed, errno=38 [ATA return descriptor not supported by controller firmware] REPORT-IOCTL: Device=/dev/sdb Command=SMART STATUS CHECK returned -1 errno=38 [ATA return descriptor not supported by controller firmware] SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. From: Stepan, Lai-Ying [mailto:Lai...@ls...] Sent: Thursday, September 26, 2013 11:31 PM To: Arvind Krishnan (arvikris) Cc: Chanda Yadavalli (cyadaval); Rose, Grant; Satriya, Erni Subject: Re: SmartCtl LSI FW logs No. The command set to get Smart info are different between SAS and SATA. Example: Use SCSI log sense pages for SAS drive Use ATA SMART commands for SATA disk On Sep 26, 2013, at 7:58 PM, "Arvind Krishnan (arvikris)" <arv...@ci...<mailto:arv...@ci...>> wrote: Lai-Ying, Is it the same for both logs? Thanks. --Arvind On Sep 26, 2013, at 6:44 PM, "Stepan, Lai-Ying" <Lai...@ls...<mailto:Lai...@ls...>> wrote: Hi Arvind, I do not see the ATA_CMD_SMART_RETURN_STATUS (0xda) sending to firmware. Here are all the pass thru commands sent to PD(=4) in the SATA log: 09/26/13 0:42:09: CMD_PCI: cmd=03, cmdId=1, nsg=1, pd=04, timeout=0, cdb= 12 00 00 00 24 00 09/26/13 0:42:09: DONE: id=1, status=0 09/26/13 0:42:10: CMD_PCI: cmd=03, cmdId=1, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 09/26/13 0:42:10: DONE: id=1, status=0 09/26/13 0:42:10: CMD_PCI: cmd=03, cmdId=3, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 09/26/13 0:42:10: DONE: id=3, status=0 09/26/13 0:42:10: CMD_PCI: cmd=03, cmdId=1, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 d0 00 01 00 00 00 4f 00 c2 00 b0 00 09/26/13 0:42:10: DONE: id=1, status=0 09/26/13 0:42:10: CMD_PCI: cmd=03, cmdId=3, nsg=1, pd=04, timeout=0, cdb= 85 08 0e 00 d1 00 01 00 01 00 4f 00 c2 00 b0 00 09/26/13 0:42:10: DONE: id=3, status=0 Thanks, Lai-Ying From: Arvind Krishnan (arvikris) [mailto:arv...@ci...] Sent: Wednesday, September 25, 2013 6:49 PM To: Stepan, Lai-Ying Cc: Chanda Yadavalli (cyadaval); Rose, Grant Subject: RE: LSI FW logs Oops…it helps to actually attach the logs. ☺ Thanks. --Arvind _____________________________________________ From: Arvind Krishnan (arvikris) Sent: Wednesday, September 25, 2013 6:45 PM To: Stepan, Lai-Ying (Lai...@ls...<mailto:Lai...@ls...>) Cc: Chanda Yadavalli (cyadaval); Rose, Grant (Gra...@ls...<mailto:Gra...@ls...>) Subject: FW: LSI FW logs Importance: High Lai-Ying, See attached LSI firmware logs that we collected when you came by (to troubleshoot the smartctl related issue with SATA drives). Thanks. --Arvind |
