What is the native linux driver for that card? Does the card support passing single devices through to the o.s. without using a proprietary driver? Here's the problem: once we start adding proprietary drivers it is very common for them not to compile correctly with the 'latest' linux kernel releases as they become available. Now what do we do? If we release the new kernel then everyone who relies on those non-updated drivers will not be able to update (and we will not be able to tell then if/when they can update). If we don't release a new kernel, then we will get behind with bug fixes/features required for other components. Our policy now is to not include any proprietary drivers, though from time-to-time we have strayed from that: for example the realtek NIC drivers. In that case since half the m/b's out there used Realtek chips it was pretty much required to deal with the never ending issues with trying to keep those drivers up to date. Thankfully it seems the linux Realtek driver is finally stable and hopefully those days are behind us. But you can appreciate why we don't want to go down that path again.
Having said all that, are there any messages in the system log being generated as a result of trying to spin down?
Ok i fully understand, about problem
this is from dmesg (all about this LSI) i dont see nothing special
http://pastebin.com/71at8EyU
about spin down - i get in log normal info like
mdcmd (75): spindown 0
mdcmd (76): spindown 3
mdcmd (77): spindown 7
mdcmd (78): spindown 6
mdcmd (79): spindown 5
mdcmd (80): spindown 2
mdcmd (81): spindown 0
mdcmd (82): spindown 1
mdcmd (83): spindown 5
mdcmd (84): spindown 3
mdcmd (85): spindown 0
mdcmd (86): spindown 4
but disks still working (i touched and HDDs vibrating and also on webinterface Green Poit from disk all time is ON, not blink)