Project

General

Profile

Bug #17643

Kernel Log

Added by Bruno Ormanes Tamer almost 4 years ago. Updated about 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:
ChangeLog Required:
No

Description

Hi,

Since the installation, I've configured S.M.A.R.T tests to run periodicaly.

Yesterday, when it ended, I've received the folowing message by e-mail:

freenas.local kernel log messages:

(da5:ciss0:32:5:0): READ. CDB: 28 00 41 79 f9 30 00 00 10 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 41 79 f9 18 00 00 10 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 41 79 f9 10 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 08 e0 ca e0 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 08 e0 ca f0 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 08 e0 ca e8 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 08 e0 ca f8 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 08 e0 cb 40 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): READ. CDB: 28 00 08 e0 c8 c0 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): WRITE. CDB: 2a 00 00 40 02 38 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): WRITE. CDB: 2a 00 00 40 04 38 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command
(da5:ciss0:32:5:0): WRITE. CDB: 2a 00 74 70 6a 38 00 00 08 00
(da5:ciss0:32:5:0): CAM status: CCB request completed with an error
(da5:ciss0:32:5:0): Retrying command

-- End of security output --

For your information, da5 is one 1TB SATA disk.

Can you help me understanding the meaning of these messages?

History

#1 Updated by Bruno Ormanes Tamer almost 4 years ago

  • File debug-freenas-20160920082733.txz added

#2 Updated by Bonnie Follweiler almost 4 years ago

  • Assignee set to William Grzybowski

#3 Updated by William Grzybowski almost 4 years ago

  • Assignee changed from William Grzybowski to Alexander Motin

#4 Updated by Alexander Motin almost 4 years ago

  • Category changed from 53 to 129
  • Status changed from Unscreened to Closed: Third party to resolve
  • Seen in changed from Unspecified to 9.10.1

Unfortunately those messages don't provide significant information. I've checked ciss driver for "CCB request completed with an error" error and only two cases where it is used are "adapter error" or "unknown error". Both of those cases has to be addressed either to HBA firmware developers or respective FreeBSD driver developers. Unfortunately we are neither of those, and don't even have the respective hardware.

On the other side, I would like to attract your attention to other messages in your logs: "Failed SMART usage Attribute: 190 Airflow_Temperature_Cel." Make sure your system has proper cooling, otherwise it may cause more problems then errors you've reported here.

#5 Updated by Bruno Ormanes Tamer almost 4 years ago

Alexander, thanks for you effort.

As you mentioned, I researched for this error and the information that I've recahed said the same you just did. I saw one case that the user hado to change the HBA hardware to dismiss the problem. It seems to be something about teh compatibility between Freenas and the HBA firmware. The funny thing is that this error never appeared till I updated FreeNas to 9.10.1 version last saturday.

As you mentioned the error code 190, indeed the server is working in a place that is not properly made for it. As a mater of fact, the noise level is always high because of the cooling system, I've already alerted for this error and I expect to correct this problem as soon as possible.

#6 Updated by Dru Lavigne about 3 years ago

  • File deleted (debug-freenas-20160920082733.txz)

#7 Updated by Dru Lavigne about 3 years ago

  • Target version set to N/A
  • Private changed from Yes to No

Also available in: Atom PDF