Buffalo Forums

Hi there all.
I have one LS-WXL that will not start its media server regardless of what I do.
Firmware version: 1.75 (DTCP-IP:1.65-20130731)
I have restarted several times, RESET to factory, restarted with function button pressed, nothing will make it start up.
Of course I have been through the regular steps to "enable" it, and even though the web settings page says it is running, it isn't. Clues!!

1. The NAS appears in the NAS Navigator and the network tab of windows explorer, BUT MISSING THE USUAL NAMING CONVENTION eg: it should be "LS-WXL14A:LinkStation" but only shows up as "LS-WXL14A".
2. When I right click the icon in the network tab of windows explorer the option to "view device webpage" is available, it opens a browser window but that is blank with a message of 'not available'.
3. After an extended period of time, the NAS icon will disappear from the network tab of windows, but the connection to the 'share' folder is still active, and file management can continue.

I'm stumped, I know these are 'OLD' now but this is the newest of the three and it has pi**ed me that they have been quite reliable for quite a while til today.
IDEAS ANYONE??
cheers CD

One More Clue -  the NAS Navigator reports that the used space is still shown as 95% full even though I have transferred all contents to another drive. ie: it is empty.!????

Sept 1st UPDATE
Ran the 'check disk' process on both HDD - passed
Factory reset again - passed
Delete raid - passed
tried to create a share - NOT ABLE to create a share with a different name from the previous share.
FULL RESET ERASE - estimated duration 881 minutes

Sept 2nd UPDATE
step 2 of 4 estimated duration 1300 mins

Sept 3rd UPDATE
step 3 of 4 estimated duration 681mins

Step 4 of 4 estimated duration 1200mins

Sept 4th UPDATE
turns out that I need not have kept the browser window open during the FULL ERASE process
Finally the process completed and the browser showed a "process completed" message.

So the process took the most part of four days.
This leaves the disks as two seperate drives inside the nas, each of which can be created as a share using the web browser, but only ONE can have the media server enabled at one time. To have the full 4Tb to act as a server you will need to create a RAID array using both disks.

The full erase has fixed the issue that I had where the media server wasn't behaving correctly, but why the nas created this problem is not known.

hope this experience may be helpful to others