Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Storage / Re: New 4TB disks not recognized in Buffalo NAS LS-WXL series
« Last post by 1000001101000 on February 06, 2021, 08:01:39 am »
The link I posted describes how to do exactly what you describe.

If yours is a WXL/E there is an easier method described in the quick start guide:

http://buffalo.jp/support_ap/support/products/ls_wxl.html
72
Wireless / Linkstation 220 cannot find on network
« Last post by woodwardf on February 06, 2021, 07:43:43 am »
I recently replaced my linkstation 210 with the 220 series after the 210 quit working. I could not locate the unit on my network and had to call BestBuy guys who came out and fought with it for over any hour to get it to work. I recently had to disconnect the unit to move it and paint. Now, I am back to the frustration of not being able to connect with it on any of my computers. It is a very expensive paperweight at this point potentially destined for the trash bin unless I can get it working. Any help would be appreciated. OS is Windows 10
73
Storage / New 4TB disks not recognized in Buffalo NAS LS-WXL series
« Last post by paolaG on February 06, 2021, 07:41:09 am »
Hello, thank you for your replies. I see it is getting complicated for me.

The thing is, I simply want to install new disks and start again from scratch copying files into the. I do NOT want any of the files contained in the previous disks to be transferred to these new drives (one of which appears to be damaged).

Is there no other way to do this, except the intervention of a specialist?

Thank you.

Paola
74
Storage / LS-XL FTP connection help
« Last post by jonathanjackson on February 06, 2021, 06:13:42 am »
LS-XL FTP connection help

I need the following FTP settings for my security camera to be able to download images to my Buffalo NAS drive. Can anyone help please...
I have filled in what I think the details should be but it fails to work
I have created a folder called FTP in the root of disk1 and created a username with password ftp1

Camera FTP settings
Server addr: 192.168.0.70
Server port: 21
Username: ftp1
Password ******
Passive mode: yes
Path: \\disk1\FTP

TEST FTP Settings =failed

Thanks
Jonathan
75
Storage / Re: LS-XL FTP client help
« Last post by jonathanjackson on February 06, 2021, 06:10:36 am »
I need the following FTP settings for my security camera to be able to download images to my Buffalo NAS drive. Can anyone help please...
I have filled in what I think the details should be but it fails to work
I have created a folder called FTP in the root of disk1 and created a username with password ftp1

Camera FTP settings
Server addr: 192.168.0.70
Server port: 21
Username: ftp1
Password ******
Passive mode: yes
Path: \\disk1\FTP

TEST FTP Settings =failed
76
Storage / Re: LS_QVL quad pro, swapping drive packs between units what is the result?
« Last post by hca on February 06, 2021, 02:15:38 am »


Ok thanks for the reply, with that in mind I have done further investigations these last couple of days. Bit of a close out.

On the rear label, most obvious near the MAC is stated "LS-QVL Series" lower down by the serial in small print its states LS-QV8  OTL/R5-AP.  Also manufactured Jul 2012.

Running in raid 5 so no data recovery option from 2 drives.

Ssh access: login admin and session terminates when correct password is validated, probably old ssh library used in firmware which is no longer accepted.

On start, flashes blue, then goes to 7 red flashes. Network lights are active. shutdown not working, it responds to the function button by changing from red flash back to blue. The drives all power up and seek, then quiet. The fan starts and runs.
Opening it up reveals no damage or obvious fault, extender board is seated ok. All chips are warm but nothing is running hot.   

I suspect because of the above the boot firmware is ok, processor appears to be up and ok and now its looking for the drive boot tracks. 7 red red flash may mean hardware issue with the sata bridge.
So If I were to bother fixing it, I would be looking at replacing the sata bridge chip first. Better to just load up a linux machine with drives, and serve them with nfs and samba and either raid or mirror (raid 1). Normal drive setups that are a damn side easier to deal with than the buffalo setup.



For what its worth, some observations on the drives from testing that may interest someone else down the track.

Putting them in a Debian pc all 4 have the same partition data as read with fdisk.

In another identical good unit each disk one by one in any slot. Pertaining to the OS or firmware partition, not data partitions, 2 scenarios occur.

A drive will boot with flashing blue, go green, ping after a minute or so, another couple of minutes it will have ssh and web access,
Nas Navi access, normal green light activity and red flash for error 16. Of course no raid array is available.
Empty drive bays show red. Any drives that come up like this will all come up together, shutdown on button press.
These drives will all come up on their original IP.I deem this a good drive on the firmware aspect.

Otherwise it will only get as far as steady green with ping, that's it. No shutdown button operation so you must pull the power plug.
Putting good drives in along with one like this does not help, the process stops at the same point.  In my case that was 2 of the 4 drives.

Next I took two of these sick drives and put it in a win7 box, to be told all the partitions needed formatting.
Disk management in admin tools showed all the partitions as did Debian.

I deleted them, made a single partition, drive letter and quick format and windows is happy with it.
Next after 7 hours of disk check, both came up with out any reported errors and work fine. A good idea to use a better test than MS to be sure of this.
 
77
Solved Storage Threads / Re: Buffalo Linkstation LS-QVL 6 red flash fix
« Last post by hca on February 06, 2021, 02:11:48 am »
Something went wrong on the last post so I try again.

Ok thanks for the reply, with that in mind I have done further investigations these last couple of days. Bit of a close out.

On the rear label, most obvious near the MAC is stated "LS-QVL Series" lower down by the serial in small print its states LS-QV8  OTL/R5-AP.  Also manufactured Jul 2012.

Running in raid 5 so no data recovery option from 2 drives.

Ssh access: login admin and session terminates when correct password is validated, probably old ssh library used in firmware which is no longer accepted.

On start, flashes blue, then goes to 7 red flashes. Network lights are active. shutdown not working, it responds to the function button by changing from red flash back to blue. The drives all power up and seek, then quiet. The fan starts and runs.
Opening it up reveals no damage or obvious fault, extender board is seated ok. All chips are warm but nothing is running hot.   

I suspect because of the above the boot firmware is ok, processor appears to be up and ok and now its looking for the drive boot tracks. 7 red red flash may mean hardware issue with the sata bridge.
So If I were to bother fixing it, I would be looking at replacing the sata bridge chip first. Better to just load up a linux machine with drives, and serve them with nfs and samba and either raid or mirror (raid 1). Normal drive setups that are a damn side easier to deal with than the buffalo setup.



For what its worth, some observations on the drives from testing that may interest someone else down the track.

Putting them in a Debian pc all 4 have the same partition data as read with fdisk.

In another identical good unit each disk one by one in any slot. Pertaining to the OS or firmware partition, not data partitions, 2 scenarios occur.

A drive will boot with flashing blue, go green, ping after a minute or so, another couple of minutes it will have ssh and web access,
Nas Navi access, normal green light activity and red flash for error 16. Of course no raid array is available.
Empty drive bays show red. Any drives that come up like this will all come up together, shutdown on button press.
These drives will all come up on their original IP.I deem this a good drive on the firmware aspect.

Otherwise it will only get as far as steady green with ping, that's it. No shutdown button operation so you must pull the power plug.
Putting good drives in along with one like this does not help, the process stops at the same point.  In my case that was 2 of the 4 drives.

Next I took two of these sick drives and put it in a win7 box, to be told all the partitions needed formatting.
Disk management in admin tools showed all the partitions as did Debian.

I deleted them, made a single partition, drive letter and quick format and windows is happy with it.
Next after 7 hours of disk check, both came up with out any reported errors and work fine. A good idea to use a better test than MS to be sure of this.
 
78
Storage / An error occurred while reconnecting X: to \\LS-WVLB9C\share - Windows 2004
« Last post by The_Hat on February 05, 2021, 03:37:27 pm »
On 1/28/2021 when I upgraded my Windows 10 Desktop and Laptop to Windows 2004 it changed my ability to view my files on my Buffalo LS-WVL/E.

Prior to that date when I powered on either computer Both the Network Drive and the Mapped Drive icons showed the Buffalo LS-WVL/E was connected and I could easily view the files by expanding the “Share” folder.

Now when both computers have fully started up when I open File Explorer the Mapped Drive icon has a red X imposed on it and when I try to expand the folder I receive the error message “An error occurred while reconnecting X: to \\LS-WVLB9C\share Microsoft Windows Network: The local device name is already in use. The connection has not been restored”.

When I move to the Network icon and try to expand it I receive the error message “Windows cannot access \\LS-WVLB9C. Check the spelling of the name. Otherwise there might be a problem with your network. To try to identify and resolve network problems, click Diagnose. When I click on “Diagnose” I get the message “Troubleshooting couldn’t identify the problem.

How can I resolve this issue
79
Storage / NFS sharing: folders disappear/reappear at random
« Last post by tonster on February 05, 2021, 10:09:28 am »
I just recently purchased a TS5810D and everything seems to be setup properly and went pretty smoothly, however I'm noticing that over NFS folders just randomly disappear and then reappear.  I'll do an ls and a bunch of stuff will report permission denied, and then another ls immediately afterwards and everything is fine. Has anyone else seen this or are there some tuning parameters I'm missing? 

Here's what I see:

[root@docker1 dir1]# ls /dir1/share
ls: cannot access '/dir1/share/dir': Permission denied
ls: cannot access '/dir1/share/dir2': Permission denied
ls: cannot access '/dir1/share/dir3': Permission denied
ls: cannot access '/dir1/share/dir4': Permission denied

Immediately after that, doing an ls /dir1/share and everything is listed.
80
Storage / Re: LS-XL FTP client help
« Last post by davo on February 05, 2021, 03:14:23 am »
path is: disk1/FTPshare
Pages: 1 ... 6 7 [8] 9 10