From: Kyl S. <kyl...@ti...> - 2013-01-11 09:16:33
|
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). Thanks, -Kyl |
From: Kyl S. <kyl...@ti...> - 2013-01-12 22:30:06
|
Hello again... 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 non-win7". 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. Thanks, -Kyl 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). > > Thanks, > > -Kyl > |
From: Andreas M. <an...@us...> - 2013-01-13 10:00:36
|
Hi, On Sun, Jan 13, 2013 at 02:09:29AM +0000, sma...@li... wrote: > Date: Sat, 12 Jan 2013 16:29:34 -0600 > From: Kyl Scott <kyl...@ti...> Let me just say that this email was perfect (I especially liked the "idiot" part, but I'm sure the controller details might be helpful to some people as well). > 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. ;) It seems like such a warning would be very desireable from a usability POV. Rather than doing a broad admin-permissions check and always printing such a warning on permission failure (which might or might not be correct about a request actually subsequently failing due to permissions), which would be a rather unspecific way of checking this, it should probably be implemented in the most direct way possible. I.e. directly check for request failure in Win32 code layer, and generate such a warning message, either by generating it right in the request handling layer (dirty), or perhaps signalling permission error to upper smartmontools handling via a smartmontools-specific error enum, for upper handling to then be able to generate an appropriate error. Possible pseudo code: res = do_request_inner_win32(); if (failed(res) && perms_failure_probable(res)) { if (insufficient_perms_win32() /* do UAC checks and such */) res = SMARTMON_INSUFFICIENT_PERMS; } If nobody is (avail~)able to fully implement such a check currently, then at least a prominent FIXME comment should be added immediately. Andreas Mohr |
From: Christian F. <Chr...@t-...> - 2013-01-13 12:21:40
|
Andreas Mohr wrote: > Possible pseudo code: > res = do_request_inner_win32(); > if (failed(res) && perms_failure_probable(res)) > { > if (insufficient_perms_win32() /* do UAC checks and such */) Checking a Windows access token is non-trivial and IMO not worth the effort here. An "access denied" error message should be sufficient to indicate that admin rights are missing. Thanks, Christian |
From: Christian F. <Chr...@t-...> - 2013-01-13 12:15:28
|
Kyl Scott wrote: > 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? The missing "access denied" message is a problem specific to the Areca code, in particular its method used to search controllers. I'm unable to fix it soon due to the lack of a controller. Patches are welcome. For other devices, specific error messages are printed if admin rights are missing (yes, for SCSI, the message should be improved). Please note that the installer creates a shortcut "smartctl (Admin CMD)" which starts a console as admin and adds the install dir to PATH. A note about required admin rights is actually missing on man page. I will add this soon. Thanks, Christian |
From: Frieder F. <fri...@we...> - 2013-01-13 15:42:32
|
Hi, Am 13.01.2013 13:15, schrieb Christian Franke: > Kyl Scott wrote: >> 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? > > The missing "access denied" message is a problem specific to the Areca > code, in particular its method used to search controllers. I'm unable to > fix it soon due to the lack of a controller. Patches are welcome. > > For other devices, specific error messages are printed if admin rights > are missing (yes, for SCSI, the message should be improved). Please note > that the installer creates a shortcut "smartctl (Admin CMD)" which > starts a console as admin and adds the install dir to PATH. Maybe I should mention in this context that I somewhat unexpectedly get "Not in smartctl database" when invocing smartctl as user and "In smartctl database" when invocing with admin rights. Also serial number is different (it is displayed including a space when invoced as user) and only the first 4 characters of the firmware version are shown and "Series" is missing from Device Model. No fancy controller just plain SATA on a Lenovo M91. This is with the newly added Samsung SSD 840 PRO (thanks for that:) I updated drivedb.h and used parameter -B just to be sure. Greetings, Frieder As user: ======== smartctl 6.0 2012-10-10 r3643 [x86_64-w64-mingw32-win7-sp1] (sf-6.0-1) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org Warning: Limited functionality due to missing admin rights === START OF INFORMATION SECTION === Device Model: Samsung SSD 840 PRO Serial Number: 1SP2ENCA1B5534 Y Firmware Version: DXM0 Device is: Not in smartctl database [for details use: -P showall] ATA Version is: [No Information Found] Local Time is: Sun Jan 13 15:50:25 2013 MZ SMART support is: Available - device has SMART capability. Enabled status cached by OS, trying SMART RETURN STATUS cmd. SMART support is: Enabled Read SMART Thresholds failed: Function not implemented === START OF READ SMART DATA SECTION === [..] As Admin: ========= smartctl 6.0 2012-10-10 r3643 [x86_64-w64-mingw32-win7-sp1] (sf-6.0-1) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: Samsung SSD 840 PRO Series Serial Number: S12PNEACB15543Y LU WWN Device Id: 5 002538 55003fd17 Firmware Version: DXM04B0Q User Capacity: 128.035.676.160 bytes [128 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Jan 13 15:50:23 2013 MZ SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1] === START OF READ SMART DATA SECTION === [..] |
From: Frieder F. <fri...@we...> - 2013-01-13 16:02:40
|
Hi, Am 13.01.2013 16:42, schrieb Frieder Ferlemann: > Serial Number: 1SP2ENCA1B5534 Y > Serial Number: S12PNEACB15543Y On second look it looks like an endianness problem? Greetings, Frieder |
From: Christian F. <Chr...@t-...> - 2013-01-13 16:44:58
|
Frieder Ferlemann wrote: > Maybe I should mention in this context that I somewhat unexpectedly get > "Not in smartctl database" when invocing smartctl as user and > "In smartctl database" when invocing with admin rights. > > Also serial number is different > (it is displayed including a space when invoced as user) > and only the first 4 characters of the firmware version > are shown and "Series" is missing from Device Model. > > No fancy controller just plain SATA on a Lenovo M91. > This is with the newly added Samsung SSD 840 PRO (thanks for that:) > I updated drivedb.h and used parameter -B just to be sure. > > Greetings, > Frieder > > > > As user: > ======== > > smartctl 6.0 2012-10-10 r3643 [x86_64-w64-mingw32-win7-sp1] (sf-6.0-1) > Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org > > Warning: Limited functionality due to missing admin rights This should make clear that admin rights are recommended :-) > === START OF INFORMATION SECTION === > Device Model: Samsung SSD 840 PRO IOCTL_STORAGE_QUERY_PROPERTY returns truncated info. > Serial Number: 1SP2ENCA1B5534 Y Endianess issue in WMI call. Some drivers do not properly pass ATA strings (LE words) to WMI. Try with WMI shell: wmic diskdrive get Model,Name,SerialNumber > Firmware Version: DXM0 IOCTL_STORAGE_QUERY_PROPERTY returns truncated info. Try "smartctl -i -r ioctl,2 ..." to print full output of IOCTL_STORAGE_QUERY_PROPERTY. Thanks, Christian |
From: Frieder F. <fri...@we...> - 2013-01-13 17:53:08
Attachments:
as_admin.txt
as_user.txt
|
Hi Christian, Am 13.01.2013 17:44, schrieb Christian Franke: >> Serial Number: 1SP2ENCA1B5534 Y > > Endianess issue in WMI call. Some drivers do not properly pass ATA > strings (LE words) to WMI. > > Try with WMI shell: > wmic diskdrive get Model,Name,SerialNumber wmic didn't like the SerialNumber ("Ungültiger XML-Inhalt" means "invalid XML content") so I also tried wmic diskdrive get Model,Name >> Firmware Version: DXM0 > > IOCTL_STORAGE_QUERY_PROPERTY returns truncated info. > > Try "smartctl -i -r ioctl,2 ..." to print full output of > IOCTL_STORAGE_QUERY_PROPERTY. appending output as user and as admin. Greetings, Frieder |