Some storage drivers actually expose their LEDs that way:
You would expect so, but LaCie is not known for doing things the standard way, and Seagate have made things even worse since they acquired LaCie.
Doing yet more digging, it would appear that the LED can be controlled through another project called led_ctrl which is part of the
lacie-nas-tools. An excerpt from the
readme states:
Code:
led_ctrl is a POSIX shell script which allow to configure LEDs (compatible
with the GNU/Linux sysfs LED API) via an understandable configuration file
and goes onto indicate that the script simply requires
make install
to be run from the source directory and then the
led_ctrl
can be run. I have run this successfully from the command line in my VirtualBox instance of FreeBSD, but rightfully getting the error
missing or empty syses LED directory: /sys/class/leds
since sysfs is not native to FreeBSD.
I can try using the
sysfsutils ports (this seems to expose
/sys
), but unsure if the LaCie device will expose the LED's that way until I can give it a go later today (hopefully FreeNAS supports installation of ports, haven't tried yet).
Update: I am able to
make install
the code just fine in FreeNAS as well, but get the same
missing or empty syses LED directory: /sys/class/leds
error as in FreeBSD. There is already a /sys folder in the root of FreeNAS but it does not contain anything. Installing
sysfsutils from ports fails with
checking for C compiler default output file name... configure: error: C compiler cannot create executables
so that's a no go. I am beginning to think this custom LaCie LED is simply is not meant to behave in the BSD world...