To Cornel and Lcrooks:
Lcrooks had mentioned that in his conversations with Apple, it was suggested that the culprit is Mavericks new support for SMB2 that was causing this problem, and that it was possible to force MAvericks to revert back to SMB as the default. However, Lcrooks also mentioned that in his talk with Apple, that this was only possible on the Server version and they were unable to figure out a way to do this on the client version.
Subsequentlyl, Cornel posted Terminal commands to use to force Mavericks to use the older SMB protocol instead of SMB2
echo "[default]" >> ~/Library/Preferences/nsmb.conf;
echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf
I came across this ZDNet article about similar issues with SMB2 in Mavericks, which also included the same command tips, as well as tips to revert to an even older protocal called CIFS
http://www.zdnet.com/mavericks-smb2-problem-and-fixes-7000022519/
Apparently these Terminal echo commands can be used on the client version. What is unclear to me from either of you gentlemen, and I apologize in advance if I'm just missing something, is the following:
IF you execute the echo command to create a new nsmb.conf file, forcing Mavericks to use SMB instead of SMB2, does it solve the problem of Firewire connected drive not sleeping or spinning down?
I tried the commands, in the client version of 10.9.1, I don't see a difference (External mounted firewire drives still don't spin down or sleep), but maybe I'm missing something? the comments from you two gentlemen seemed to suggest that switching back to SMB solved the problem.
Please clarify if you would.
Thanks,
Michael