Opened 10 years ago

Closed 10 years ago

#305 closed defect (wontfix)

smartctl loses 1 byte from response to scsiModeSense in FreeBSD

Reported by: fedsim Owned by: Alex Samorukov
Priority: major Milestone:
Component: all Version: 6.2
Keywords: freebsd Cc:

Description

smartctl -a (and smartd as well) gives an error when trying to examine some disks because the response to a mode sense command cannot be parsed (see attached file smartctl.log).

However, if the same command is sent with camcontrol, the response is correct (note the leading byte in camcontrol.log, which is not present in smartctl.log).

Attachments (3)

smartctl.log​ (4.1 KB ) - added by fedsim 10 years ago.
Log of smartctl -a
camcontrol.log​ (304 bytes ) - added by fedsim 10 years ago.
Log of camcontrol
smartctl-r3874.log​ (3.2 KB ) - added by fedsim 10 years ago.

Download all attachments as: .zip

Change History (17)

by fedsim, 10 years ago

Attachment: smartctl.log​ added

Log of smartctl -a

by fedsim, 10 years ago

Attachment: camcontrol.log​ added

Log of camcontrol

comment:1 by Christian Franke, 10 years ago

Milestone: → Release 6.3

comment:2 by Christian Franke, 10 years ago

Keywords: freebsd added

comment:3 by Christian Franke, 10 years ago

This was possibly fixed with r3873. Please test current SVN version of smartctl.

by fedsim, 10 years ago

Attachment: smartctl-r3874.log​ added

comment:4 by fedsim, 10 years ago

Nope. The missing byte is still... missing (see smartctl-r3874.log)

comment:5 by Alex Samorukov, 10 years ago

We dont have any similar reports. Are you sure that your kernel is in sync with your includes and source tree?

comment:6 by fedsim, 10 years ago

I've had this issue not only when compiling from source but with precompiled smartmontools in FreeNAS 8.3...9.2.1 too. I wouldn't think that is the case but I'd appreciate some help on how to check this because I'm no expert at all when it comes to FreeBSD.

Anyway, this seems to happen only with the SAS disks in the machine. SATA disks work just fine, as do those same SAS disks when I plug them in a Linux box. Hope this helps.

comment:7 by Alex Samorukov, 10 years ago

Owner: changed from somebody to Alex Samorukov
Status: new → accepted

Thank you for feedback, it seems to be a bug then. Is it possible to provide somehow access to the affected machine? I really have no idea whats going on and unfortunately unable to reproduce this locally.

comment:8 by fedsim, 10 years ago

The machine is in production right now. I can give you unprivileged access and do the real testing for you. Would that help?

comment:9 by Alex Samorukov, 10 years ago

This should help a little, at least. I`ll compile version which will print a lot of debug to show why answer from smartctl is so different compared to camcontrol tool. my email is samm@…

comment:10 by Christian Franke, 10 years ago

Milestone: Release 6.3 → Release 6.4

comment:11 by Alex Samorukov, 10 years ago

Resolution: → fixed
Status: accepted → closed

Hi, unfortunately i am unable to work on this ticket w/o root access. If you have possibility to provide it i will continue working on it.

comment:12 by Christian Franke, 10 years ago

Milestone: Release 6.4

Please check the ticket resolution. It should possibly be "wontfix" or "worksforme".

comment:13 by Alex Samorukov, 10 years ago

Resolution: fixed
Status: closed → reopened

comment:14 by Alex Samorukov, 10 years ago

Resolution: → wontfix
Status: reopened → closed
Note: See TracTickets for help on using tickets.