Bug 196083 - ciss drivers: smartctl going to reboot HP ProLiant DL160 G6 with HP Smart Array P410
Summary: ciss drivers: smartctl going to reboot HP ProLiant DL160 G6 with HP Smart Arr...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-18 06:29 UTC by v.chernyadev
Modified: 2015-02-06 16:01 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description v.chernyadev 2014-12-18 06:29:13 UTC
The HP ProLiant DL160 G6 with HP Smart Array P410 restarts after about 250 tests smartctl SATA drives. I have two SATA drives on the 0 and 3 channel and two SAS drives on the 1 and 2 channel. So:
smartctl -a /dev/ciss0 -d sat+cciss,3
smartctl -a /dev/ciss0 -d sat+cciss,0
smartctl -a /dev/ciss0 -d cciss,2
The first and second line leading to reboot after ~ 250 repetitions, the third can run indefinitely.
There is nothing strange in /var/log/messages and dmesg.
I can repeat that. I run:
===
while(); do (/usr/local/sbin/smartctl -i -A -H /dev/ciss0 -d sat+cciss,3>/dev/null;date;) done
===
And after 250 cycles server rebooted.
smartmontools v. 6.3
FreeBSD 9.3-RELEASE-p2 #0: Mon Sep 15 16:44:27 UTC 2014     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2014-12-18 23:30:47 UTC
Fix Summary and notify maintainer.
Comment 2 Oleksii Samorukov freebsd_committer 2014-12-19 19:30:56 UTC
It has nothing todo with smartmontools, which is userland application and should not reboot system in any case. I do not have such hardware and unable to debug this issue, but i would recommend to reassign it with to the ciss driver maintainers. 
It is also possible that reboot is caused by buggy controller firmware which reacting to the SAT commands this way. In this case i would recommend to make sure that you are using latest firmware version available. Also it could be a good idea to check if this happens in Linux.
Comment 3 John Marino freebsd_committer 2015-02-06 16:01:13 UTC
Reclassifying as kernel PR