Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 06 Nov 2011 21:37:24 +0100
From:      Alex Samorukov <ml@os2.kiev.ua>
To:        "Marat N.Afanasyev" <amarat@ksu.ru>
Cc:        FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: smartctl / mpt on 9.0-RC1
Message-ID:  <4EB6F004.9060501@os2.kiev.ua>
In-Reply-To: <4EB6B530.9000901@ksu.ru>
References:  <4EB1BCAD.7080206@zzattack.org> <20111102233807.GA67112@icarus.home.lan> <4EB1D6F9.3060008@zzattack.org> <20111103000124.GA67550@icarus.home.lan> <4EB1DD51.4080808@zzattack.org> <20111103002352.GA67904@icarus.home.lan> <4EB2538D.3090108@zzattack.org> <4EB2CB75.6070003@os2.kiev.ua> <CAD4099km0FcvUMSw=sY7HB73dtvfQgcVE16VJdGpGK96V%2B4hhA@mail.gmail.com> <4EB2E2D7.2050809@os2.kiev.ua> <CAD4099nogWP5q1GpHyuyWH%2BHUZYmW1xp9BFTdndL7nNLf6vFSw@mail.gmail.com> <4EB2F510.5070804@os2.kiev.ua> <CAD4099nNx7mkyUc2G7Z5W1Y%2B5BOBnP00mfA=F0x17kVoT76Peg@mail.gmail.com> <4EB307CC.8000705@os2.kiev.ua> <4EB6AD22.4080408@ksu.ru> <4EB6B20A.9090104@os2.kiev.ua> <4EB6B530.9000901@ksu.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

>>
> it doesn't work :( sata drives are accessible, but for sas all we have:
>
> # smartctl -d 3ware,0 -a /dev/twa0
> smartctl 5.40 2010-10-16 r3189 [FreeBSD 8.2-RELEASE amd64] (local build)
> Copyright (C) 2002-10 by Bruce Allen, 
> http://smartmontools.sourceforge.net
>
> Command failed, ata.status=(0x00), ata.command=(0xec), ata.flags=(0x01)
> WARNING - NO DEVICE FOUND ON 3WARE CONTROLLER (disk 0)
> Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)
>
> A mandatory SMART command failed: exiting. To continue, add one or 
> more '-T permissive' options.
>

Ok, looking in the code i found that on "3ware" device only 
"ata_command_interface" is implemented (with 
TW_OSL_IOCTL_FIRMWARE_PASS_THROUGH). The question is if that interface 
actually supports SAS drives at all. From the quick view of the sources 
i found  TWE_Command_ATA packet description, but nothing related to 
SCSI/SATA packets. So i am not sure that it is possible at all. If you 
know any tool which able to get health information for SAS drives we can 
try to debug ioctl it using to find the way to talk with disk.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EB6F004.9060501>