Buffalo Forums

I have been working on this issue ever since getting my NAS (for about a year) and have yet to be able to solve it so maybe someone can help.  Every time I turn on my iTunes server on the NAS and check the logs I get a success but the server never actually starts.  I know this because it doesn't show up in iTunes and when I do a port scan the necessary port of 3689 doesn't appear.  I've tried a countless number of things, but I will provide a few here:

1.  I offloaded my data and restored the NAS to its original state
     a.  This worked and I kept the server running for a few days while slowly adding music to it.  It stayed on until I placed all of my music on it (which is about 150GB and takes up 6.76TB on disk)

2.  I changed the folder location and nothing happened

3.  I disabled the service, rebooted the NAS and then re enabled it and again nothing happened


I've tried a couple other things, but the above should cover the main troubleshooting steps.  I have pasted below a section of my log:

Jan  4 10:47:19 [NASName] nasapi - -1246731152 - 6229 -generic - service_control - INFO- service_name=itunes, command=enable
Jan  4 10:47:20 [NASName] nasapi - -1246731152 - 6229 -generic - service_control - INFO- success

I think the issue has something to do with the "nasapi" text because it shows me that something may be corrupted.  I realize it is likely the music that is causing the issue but without deleting my entire library and starting over again I currently have no way to tell what song/songs or folders are causing the issue.  The log is all but useless to me.  Any help would be appreciated.

What firmware is the TS3400 on? Also you can create another folder move like 5 songs over to that folder, and then set the itunes server to that folder as well. See if it now shows. The share are pretty much like partitions on the drive. Well they act like it so you dont have to worry about the other share interfering with the new test share you are going to make,

Thanks for responding!  The firmware I have is 1.12.  As far as moving stuff around as you mentioned... I did try that.  I think the corrupted files forever mess up the service, but there is no way to tell what files are causing it.  Before I offload all of my data again and rebuild the raid array (about 6TB's worth) I would like to find out what exactly is causing the issue.  The other method would be to load chunks at a time but even with that method I could take the risk of having the service messed up and not knowing what file or combination of files in a specific chunk caused the issue.  Any other ideas would be greatly appreciated.