Buffalo Forums

Products => Storage => : MikeRubin June 24, 2012, 03:11:39 PM

: LS-WV4.0TL/R1: No longer can access video file shared directory with media server apps
: MikeRubin June 24, 2012, 03:11:39 PM

I have an LS-WV4.0TL/R1, which, for the last year or so, has been operating without issue.  However, a few days ago, the video folder in my "share" directory became inaccessible to all of the UPnP/DLNA applications on my iPhone and Android devices.  (I use 8player on the iOs device and both Bubble UPnP and UPnPlay on Android devices to access the media server when I want to view videos.  I use those and PlugPlay when I want to access music.)  I still can see and use the music folders in the same "share" directory.  

 

The first time this happened, I created a new video folder with a different name in the share directory and moved all video content to that new directory; I then was able to access the video material for a day or so until the new folder became inaccessible.  I tried the "move to new folder" strategy again, but, this time, it did not work. The video folder remains inaccessible.

 

I then modified the settings in the "extensions" section of the web console so that the shared directory no longer was "share" but, instead the "share/video" folder.  When the share is limited to the video folder, that folder and its contents ARE accessible to the renderer apps.

 

Then, if I switch back from "share/video" to the main "share" directory, the video folder again no longer is visible.  Apparently, i must now choose whether to allow access to music or to video, but I cannot restore access to both by enabling the main share folder.

 

This is baffling to me. Before this happened, I changed no settings at all on the NAS for a very, very long time.  Similarly, I had not changed any settings on all four of my renderer devices that would result in disabling access by all four of them.  I just updated from firmware 1.56 to firmware 1.57, hoping against hope, but that did not change anything relevant to this post.

 

This is very, very annoying and it's time-consuming to switch shares each time I want to switch between media sources.  I'll appreciate all help anyone can offer.  Thanks.  

: Re: LS-WV4.0TL/R1: No longer can access video file shared directory with media server apps
: MikeRubin June 26, 2012, 12:43:54 AM
Did that. Made no difference. Same issue: can select "share" and have access to music or select "share/video" and have access to video. No longer have access to all media in the renderer apps.
: Re: LS-WV4.0TL/R1: No longer can access video file shared directory with media server apps
: cristen_ June 26, 2012, 03:15:31 PM

If resetting the unit via the web interface did not have any effect, then, from here, you would want to try re-flashing the firmware on the unit. If you are not currently at the latest firmware version, then simply run the firmware update. If you are currently at the latest firmware version, you would need to perform a forced firmware update so that the current firmware version can be ignored. Updating the firmware on the unit also does not have any effect on the data.

 

The latest firmware for your unit (version 1.58) can be found on the downloads page for your LS-WVL, available here:

http://www.buffalotech.com/products/network-storage/home-and-small-office/linkstation-pro-duo-1#downloads

 

And, instructions on how to perform a forced firmware update can be found at the following link:

http://forums.buffalotech.com/t5/Storage/FAQ-2-of-5-Force-Firmware-update-procedure/td-p/100317

: Re: LS-WV4.0TL/R1: No longer can access video file shared directory with media server apps
: MikeRubin June 26, 2012, 03:27:43 PM

Thank you for the link.  Before I posted here, I went to the download page for my device and only found the 1.57 update, which I ran right before posting.  I will try 1.58 now. 

: Re: LS-WV4.0TL/R1: No longer can access video file shared directory with media server apps
: MikeRubin June 28, 2012, 08:22:02 AM
That update seems to have solved the problem. It took overnight for the database to rebuild and become completely accessible from the mobile devices. I therefore wonder if I simply did not wait long enough after the 1.57 upgrade and the restoration before concluding they did not resolve the issue. In any event, the entire library again is available. Thank you for your help with this.