Project

General

Profile

Bug #18506

FreeNAS-9.10.1-U2 (f045a8b): "mfi0 Unexpected sense: Encl PD 0c Path..." and "smartd is not running"

Added by Максим Мухачев almost 3 years ago. Updated almost 3 years ago.

Status:
Closed: Third party to resolve
Priority:
No priority
Assignee:
Alexander Motin
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

CPU: Intel Xeon 2.66 Ghz
RAM: 8157MB
RAID HW: SROMBSAS18E
HDD: Western Digital WD20EFRX (6 pieces) in RAID 50

ChangeLog Required:
No

Description

Hi! On the terminal screen the group of warnings with the text periodically appears:

"mfi0: <XXXXXX> (530769250s/0x0002/info)- Unexpected sense: Encl PD 0c Path 5000403d3cfe6000 , CDB: 1c 01 0a 80 00 00, Sense: 70 00 05 00 00 00 00 1d 00 00 00 00 35 01 0"

<XXXXXX> - six-digit number.

Such records of 6 lines (by the number of HDD).
And two records with the text:

"<date and time> freenas smbd: in openpam_check_error_code(): pam_sm_setcred(): unexpected return value 12
<date and time> freenas smbd: in openpam_check_error_code(): pam_sm_acct_mgmt(): unexpected return value 12"

<date and time> - current date and time.

History

#1 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 3 years ago

  • Category changed from 32 to 129
  • Assignee changed from Kris Moore to Alexander Motin
  • Target version set to 9.10.2

I want to get Sasha's opinion on this, but I believe those mfi errors might be some indication of a read issue?

#2 Updated by Alexander Motin almost 3 years ago

  • Status changed from Unscreened to 15

I believe 'Unexpected sense..." messages is a harmless spam. Something (either SES driver or mfi firmware itself) periodically tries to talk to enclosure, while enclosure does not support support specific command. mfi firmware for some unclear reason consider it worth logging.

Максим, could you show me output of `camcontrol cmd ses0 -c '1c 01 00 01 00 00' -i 256 - | hd` command?

#3 Updated by Максим Мухачев almost 3 years ago

Alexander Motin wrote:

I believe 'Unexpected sense..." messages is a harmless spam. Something (either SES driver or mfi firmware itself) periodically tries to talk to enclosure, while enclosure does not support support specific command. mfi firmware for some unclear reason consider it worth logging.

Максим, could you show me output of `camcontrol cmd ses0 -c '1c 01 00 01 00 00' -i 256 - | hd` command?

[root@freenas ~]# camcontrol cmd ses0 -c '1c 01 00 01 00 00' -i 256 - | hd
00000000 00 00 00 09 00 01 02 03 05 07 0a 0e 86 37 00 00 |.............7..|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

  • 00000100

#4 Updated by Максим Мухачев almost 3 years ago

two records with the text:

"<date and time> freenas smbd: in openpam_check_error_code(): pam_sm_setcred(): unexpected return value 12
<date and time> freenas smbd: in openpam_check_error_code(): pam_sm_acct_mgmt(): unexpected return value 12"

These records don't appear any more, the problem was in the Samba setup.

#5 Updated by Alexander Motin almost 3 years ago

  • Status changed from 15 to Closed: Third party to resolve

Максим Мухачев wrote:

[root@freenas ~]# camcontrol cmd ses0 -c '1c 01 00 01 00 00' -i 256 - | hd
00000000 00 00 00 09 00 01 02 03 05 07 0a 0e 86 37 00 00 |.............7..|

Looking on this I think it is enclosure firmware problem. It reports that it supports Additional Element Status diagnostic page, but reports error when asked to read it. You may try to update enclosure firmware, if there are any, but as I have told before, it is not critical.

#6 Updated by Максим Мухачев almost 3 years ago

Alexander Motin wrote:

Максим Мухачев wrote:

[root@freenas ~]# camcontrol cmd ses0 -c '1c 01 00 01 00 00' -i 256 - | hd
00000000 00 00 00 09 00 01 02 03 05 07 0a 0e 86 37 00 00 |.............7..|

Looking on this I think it is enclosure firmware problem. It reports that it supports Additional Element Status diagnostic page, but reports error when asked to read it. You may try to update enclosure firmware, if there are any, but as I have told before, it is not critical.

Thank you for the answer!
The firmware is set fresh. We close a subject!

#7 Updated by Dru Lavigne over 1 year ago

  • File deleted (debug-freenas-20161026092257.tgz)

Also available in: Atom PDF