cam errors?

[joeschmuck]

When you say versions of FreeNAS are we talking all 9.10 or does that include 9.3.x ? I'm just trying to get a feel for what generic versions you had this problem with.

If someone else doesn't chime in about the problem in the next few days, I'd submit a bug report and be as descriptive as possible. Dru has already seen your issue and maybe someone else at iXsystems can lend a hand.

 

[hugovsky]

I've tested with diferent versions.

With 9.10-stable-201603252134 -> no errors
Anything after this version gives the 15 min error behavior.

 

[hugovsky]

"anything" ->

9.10-stable-201604111739
9.10-stable-201604181743
9.10-stable-201605240427
9.10-stable-201606072003

These were the versions I had available in boot environment

 

[joeschmuck]

I've tested with diferent versions.

With 9.10-stable-201603252134 -> no errors
Anything after this version gives the 15 min error behavior.

My suggestion then is to submit a bug report and note the last version which worked fine since it was a 9.10 version and then the versions which generated the error messages. This would be a valid bug report to file.

Next, you could either live with the messages or roll back to the version which didn't generate those messages, it's up to you.

 

[hugovsky]

Thanks, "Old man"... ;) I'll file the bug report and I think I'll go back to the version without errors, at least for awhile. Be right back.

 

[joeschmuck]

I suspect other users have this issue too but either have not seen it or ignore it because the system is running fine. Also while I didn't mention it, please post the bug report number here for anyone else who may want to reference it.

"Old Man"

P.S. I'm feeling old today, yesterday I replaced the front brakes and calipers on my wives car in the damn heat and high humidity. Today I need to work on my daughters car, more front end work. Well at least I know how to do the work, saves me lots of money that way but I just wish these things happened during nicer weather.

 

[hugovsky]

Done!

Issue #16267 created.

@joeschmuck Have a beer and relax, friend. Brakes are a dirty work but they can get computers out of your head for a while.

Thanks to all that had the time to read and write something.

 

[joeschmuck]

Done!

Issue #16267 created.

@joeschmuck Have a beer and relax, friend. Brakes are a dirty work but they can get computers out of your head for a while.

Thanks to all that had the time to read and write something.

I should have taken your advice but instead after looking at my daughters car front end, it was not a pretty sight. I was looking at probably over $1000 in parts alone (I didn't price them all but it was getting up there) and although I didn't mind tackling this job, the daughter said to me while I broke the bad news to her "Oh yea, did I tell you about the electrical problem..." and it snowballed from there. There was an additional transmission issue too. I try to tells these people to let me know when something happens that isn't normal, don't wait for it to fully break. Nope, all at once the car became a huge risk on how much money I should sink into it. I do not repair transmissions and I know a great repair shop. I can do the electrical, it sounds like the Alternator was going bad. But everything combined was well over the amount I was willing to spend on repairs for a car that isn't worth that much and I had no idea what would break next.

So the wife and I went car shopping, well it was originally "looking" and wait a few days to figure out what she wanted. By 6PM we had a new car for my wife and my wives old car will become my daughters new car. I got to "look" at a Miata but the Mazda dealership had two bottom dollar models so I didn't get the new car. But my buddy in Massachusetts bought a Miata yesterday and rubbed it in my face. That is okay, I waiting on the 2017 model anyway.

So long story short, I bought a new car I wasn't planning to.

 

[mav@]

Just a status update: Reported issue was purely cosmetic and does not tell about any hardware problem. SCSI statuses reported in those messages are part of normal ATA SMART operation on SAS HBA. I've committed patch that should filter out those and alike non-error statuses from devd/syslog.

 

[Mirfster]

So long story short, I bought a new car I wasn't planning to.

Well if your wife got a new car and your daughter got a "new to her" car, then I think it is only fair you get at least 1/3 the value in computer equipment. ;)

 

[hugovsky]

Thanks for posting the report mav@. It's a private bug but I'll copy the last info here:

Code:

Updated by Kris Moore 2 days ago
Comment

Has this been sent to avago?
#6
Updated by Alexander Motin about 8 hours ago

    Assignee changed from Josh Paetzel to Alexander Motin

Comment

"72 01 00 1d" sense data mean: "ATA pass through information available". The commands are ATA SMART requests wrapped into SCSI ATA pass-through commands. I think this is just a useless spam, reported by kernel about errors that can and should be handled at user level (smartd probably). I think kernel should not log errors caused by requests from user-level. I'll take this.
#7
Updated by Alexander Motin about 3 hours ago

    Target version set to 9.10.1-U1
    Category changed from Hardware to FreeBSD
    Status changed from Investigation to Ready For Release
    Priority changed from Important to Nice to have

Comment

It is not exactly trivial to differentiate normal and error conditions in SCSI. I've committed patch that should filter out at least some subset of false errors.

 

[wreedps]

Ever fix this?