Opened 7 years ago

Closed 6 years ago

Last modified 22 months ago

#255 closed defect (wontfix)

Smartctl 5.43 testing issue in Suse 10 (LSI 1064E)

Reported by: jackson4015 Owned by: somebody
Priority: major Milestone:
Component: smartctl Version: 5.43
Keywords: linux Cc:

Description (last modified by Christian Franke)

Server+ LSI RAID card 1064E+ Seagate new Gen of 10K HDD:ST 900MM0006

RAID 1 seeting on 2 x SAS HDD;
Use smartctlv5.43 to do test DST, skip;
report error: not supported

But for centos/federo, no such issue;

Attachments (5)

smartctl debug (-r ioctl,2) outputs.txt (2.9 KB) - added by jackson4015 7 years ago.
Debug data for Suse 10
Debug with -d.rtf (2.3 KB) - added by jackson4015 7 years ago.
debug -d data
Dev info.rtf (38.5 KB) - added by jackson4015 7 years ago.
FC 17 Smartctl 5.43 ok.txt (2.8 KB) - added by jackson4015 7 years ago.
Attach#1
Even Smartctl 5.38 test OK on Suse10.txt (6.3 KB) - added by jackson4015 7 years ago.
Attach#2

Download all attachments as: .zip

Change History (15)

comment:1 Changed 7 years ago by Christian Franke

Description: modified (diff)
Keywords: linux added; compatibility issue removed

Please provide smartctl debug (-r ioctl,2) outputs as attachments(!) to this ticket.

Changed 7 years ago by jackson4015

Debug data for Suse 10

comment:2 in reply to:  1 ; Changed 7 years ago by jackson4015

Replying to chrfranke:

Please provide smartctl debug (-r ioctl,2) outputs as attachments(!) to this ticket.

Hello,Chrfranke.

Thx for your advice.

As V6.0 has been released, so we try it,still fail again,same as V5.43,
we provide the logs of V6.0,also you could get the Linux ver(suse/10sp3/64bit)in the
attach.And only RAID1 could observe such failure.
PLS note it.


comment:3 in reply to:  2 ; Changed 7 years ago by Christian Franke

Replying to jackson4015:

And only RAID1 could observe such failure.

Please retry with correct -d option and device name, see man page and Wiki.

Changed 7 years ago by jackson4015

Attachment: Debug with -d.rtf added

debug -d data

Changed 7 years ago by jackson4015

Attachment: Dev info.rtf added

comment:4 in reply to:  3 Changed 7 years ago by jackson4015

And only RAID1 could observe such failure.

Please retry with correct -d option and device name, see man page and Wiki.

Hello,chrfranke.

As the raid card is neither LSI's 3ware nor Megaraid card,but 1064E, so we use:

smartctl -d scsi /dev/sgx

to retry.Observerd the the diagnostic CMD for SDST was sent : 1d 20 00 00 00 00
Errno is set to EPERM:"SG_IO ioctl failed".

comment:5 Changed 7 years ago by Christian Franke

Summary: Smartctl 5.43 testing issue in Suse 10Smartctl 5.43 testing issue in Suse 10 (LSI 1064E)

Adding -d scsi has no effect because it is the default.

The outputs suggest that the (mptlinux?) driver does not properly implement the SG_IO I/O-control. If this is the case, we cannot fix this.

Does it work with same controller under other distributions?

(BTW: Please provide future text attachments as plain .txt, not as .rtf)

comment:6 in reply to:  5 Changed 7 years ago by jackson4015

Replying to chrfranke:

Does it work with same controller under other distributions?

Yes. Same system/config. but different distribut:
Use Fedora17 and CentOS to do short DST test on SAS HDD:ST900MM0006,it works OK;
Pls see the attach#1;

Btw,

In order to exclude HDD reason, use another SAS Drv:ST9146853SS under Suse 10,
smartctl 5.38, short DST passed, but switch to smart5.43/6.0, failure took place.
That means only smartctl Ver. is different,it seems that the bug follows the tool because of "SG_IO ioctl failed",PLS see attach#2.
We are eager to know why it happened.If any evidence proved that it is related to
Suse 10, we would report that bug to Novell.
Thx!

Changed 7 years ago by jackson4015

Attachment: FC 17 Smartctl 5.43 ok.txt added

Attach#1

Changed 7 years ago by jackson4015

Attach#2

comment:7 Changed 7 years ago by Christian Franke

Please report a bug to Novell and provide the link to the ticket here. Make sure to provide detailed info about controller, driver, kernel and smartmontools version. The smartmontools package may contain Suse-specific patches.

Testing with 5.38, 5.39, ..., 5.43 (each build from src tarball) would possibly help to track down the change which introduced the problem.

comment:8 in reply to:  7 Changed 7 years ago by jackson4015

OK, thx,would do it right now.
But could you pls ask the smartmontools developers to review the code of V5.43,
Novell may challenge why 5.38 works OK on same OS,hope get more clue of
"SG_IO ioctl failed".

Btw,
Testing with 5.38, 5.39, ..., 5.43 (each build from src tarball)
Yes, is there more debugging method in smartctl helping to track down that change?
At present,only debug (-r ioctl,2) is available.

comment:9 Changed 7 years ago by Christian Franke

Test which smartmontools versions (rebuild from tarballs) in the mentioned interval work as expected or not. This info is needed to review the code changes.

comment:10 Changed 6 years ago by Alex Samorukov

Resolution: wontfix
Status: newclosed

6 months without feedback, please reopen if needed.

Note: See TracTickets for help on using tickets.