Re: [smartmontools-support]smartctl not opening scsi-specific device file

[Christian F. <Chr...@t-...>]

Hi,

>... Now I copied the smartctl.exe (only the exe and not the other files) to the NAS box and ran it from cygwin 
>

This is OK. The Cygwin smartctl.exe should run if cygwin1.dll is 
somewhere in the PATH, no need for a full Cygwin installation.


>... and gave the path as /dev/sda. But it gave an error as : 
>
>Smartctl open device: /dev/sda failed: No such file or directory
>  
>

Unlike ATA disks, smartctl/smartd do not use Linux like device names for 
SCSI devices. The syntax is "/dev/scsi[0-9][0-f]" for SCSI devices on 
ASPI adapter 0-9 and ID 0-15, see smartctl man page.

An installed ASPI interface is required to access SCSI devices, see 
"Windows" section in INSTALL file.


>But when did a dd  ie. executed the "dd" command with if=/dev/sda and of=something, it worked, which showed the existence of /dev/sda. But why then did smartctl didn't recognise it? 
>

smartctl relies on SCSI pass through access which is not provided by 
Cygwin. But fortunately Cygwin allows direct access to the Windows API.


>... but there is no os_cygwin.c. So, which file the cygwin-specific distribution uses? Since cygwin runs on top of windows, the smartmontools use the os_win32.c file? OR the os_generic.c file?
>

The module os_win32.c is used also for Cygwin. From "Cygwin" section of 
INSTALL file:
"Both Cygwin and Windows versions of smartmontools share the same code 
to access the IDE/ATA or SCSI devices".


>I'm using smartmontools-5.32 on cygwin 1.59 on win 2000 on a NAS appliance to which two scsi disks are connected and represented as /dev/sda & /dev/sdb.
>  
>

Try "smartd -q onecheck" without a smartd.conf to scan SCSI/ASPI devices 
for harddisks.


Hope this helps

Christian