I am mostly replying to my prior email to the list to provide a little
bit of amusement for some of you who may remember your greener days, and
also to ask a general question (at the bottom the message).
I work for a large company that is only recently making the transition
from winXP to win7, so I am also a recent adopter of win7. You can
translate that as "complete idiot about all things win7, and most things
Since I could not get smartctl to work on this newly built up win7
machine with the 1882ix in it, and since it did work fine on our older
winXP machines with the 1231MLs, I went ahead and got cygwin, etc.
installed on it, grabbed the latest source tarball and went crazy
digging through the code, adding lots of debug statements and reverse
engineering how the Areca discovery process worked. I had never looked
at the SCSI interface to the controller before, and I did not even know
it had a RAID DummyDevice sitting at targetID 16 (SATA controllers, it
looks like) and at targetID 127 (SAS controllers, it looks like), which
also seems to connect with the 16 and 127 volume limits for each type of
controller, etc. I spent several hours playing with the code before I
finally got all the way down to the DeviceIOControl call.
Whereupon I read the MSDN description which pointed out that little
detail about having to be running in adminstrator mode for it to work
with win7/vista and GENERIC_WRITE...
So starting my command window in administrator mode allows the latest
official release to work just fine and the 1882ix is now recognized.
Umm, yeah, I did mention idiot... ;)
So the question I am wondering about is whether it makes sense to add a
message (or maybe even a permission check) to smartctl about
administrator mode on windows and warn newcomers like me when their
requested controller is not found due to improper invocation? This
requirement is probably in the docs somewhere, but I missed it when I
was skimming over things (still not used to UAC, at all). Not a big
deal either way, but I thought I would toss the idea out there. If it
is a foolish one, then please freely ignore it. ;)
Anyway, my thanks to the many people who have worked on smartmontools
and who have put together such a useful toolkit.
On 1/11/2013 3:16 AM, Kyl Scott wrote:
> Hello, I am a recent convert to smartmontools (I previously used
> Speedfan for manual SMART checking of the drives on my Areca
> controllers). While smartctl does recognize my Areca 1231ML
> controllers, the latest version I can find for windows (6.0,
> 2012-10-10) does not have (as far as I can tell from the email
> archives) the support for the newest SAS/SATA controllers like the
> Areca 1882ix controller I just installed, and indeed, it does not
> recognize this controller.
> I am not set up to compile the SVN source for windows, and was
> wondering if there was a schedule for when the next official release
> or SVN test build for windows might be available?
> Now that I have discovered smartmontools, I am very much looking
> forward to getting it working and being able to set up monitoring,
> logging and email notifications (which would all be much better than
> the occasional manual checks I used to do).