I get the error "Back Fan malfunction", but the fan is working just fine. I have tried updating the firmware and contacting support. But it's just out of warranty (of course) and Buffalo can't help me any further. Anyone out there know what I can do to get this fixed? I paid over $300 for this thing and don't want to let it go to waste! That's an expensive paper weight.
Have you tried the Force Firmware Procedure and then reinit the unit? If that does not work then you can take the drives out of that box and try to find another LS-Quad box with no drives and perform a TFTP boot.
Well, that kinda worked. I don't get the fan error, but I can't seem to get it to recognize the drive anymore.
I can't remember what I did, but after I had performed the force firmware procedure as you suggested, I tried to format or initialize or something like that...I don't remember exactly now; I've done so many things now. Anyway, after a couple hours, I now get 6 red flashes (meaning "hard drive not recognized", and it won't stop doing that. I can press the function button and it stops the red flashes, but I am still not able to access the drive. Any ideas what's going on???
Nothing? Nobody? JoshC???
My unit seems to be bricked now after following the mods advice and now he or nobody else will reply? What gives?
I've been a long time fan of Buffalo; owned both wireless and storage devices. Have recommended them to a ton of people and now this. What kind of customer appreciation is this? This unit stops working just out of warranty and the phone tech support can't help me. I come to the forum and I got help, but unfortunately, what fixed one issue caused another. Quite possible bricking my unit and now no one will answer me? Do I need to resort to legal matters to get this resolved or what?
Have you tried the TFTP boot?
Sorry, but I don't have another LS-Quad box to do this. I can't afford to buy another $400 device just to test this. Besides, there's no point in that.
You don't need another Quad to do a TFTP Boot.
http://forums.buffalotech.com/t5/Storage/FAQ-3-of-5-TFTP-boot-procedure-please-read-this/td-p/11015
Okay, I will try that tonight. The way JoshC had wrote, it seemed like I needed another device to do that.
Sorry it took so long to write back. It took me forever to find a computer that could access that link you gave me for the tftp thing! I was finally able to download it and then finally got the linkstation to run in em mode. But after the tftp does it's thing, the NAS reboots back to the 6 blinking red lights and is not seen by the navigator or updater software. What now???
Here is the result of the tftp program:
Preparing to write TFTP configuration settings.TFTP Configuration settings have been written.TFTP Server Multithreaded Version 1.4 Windows Built 1.400Starting TFTP...alias / is mapped to C:\Users\Chris\Desktop\TFTP Boot Recovery\listening On: 192.168.163.1:69listening On: 192.168.110.1:69listening On: 10.11.12.29:69listening On: 192.168.11.1:69listening On: 127.0.0.1:69permitted clients: allserver port range: allmax blksize: 65464defult blksize: 512default interval: 3overwrite existing files: Nothread pool size: 1accepting requests..Client 192.168.11.150:1967 C:\Users\Chris\Desktop\TFTP Boot Recovery\uImage.buffalo, 4133 Blocks ServedClient 192.168.11.150:2510 C:\Users\Chris\Desktop\TFTP Boot Recovery\initrd.buffalo, 13750 Blocks Served
you have 5 network connections running on your PC.
disable all of them apart from the local area connnection.
Set the IP address of the Local area connection to: 192.168.11.1 Subnet: 255.255.255.0.
Connect the Quad directly to the PC via RJ45 cable.
Run the TFTP application again. wait for the blocks to be served, once done wait 2 mins for the unit to be in EM mode and then reinstall the firmware.
If at this stage you cannot reinstall the FW then post the current IP address of your PC and the Linkstation (use the Nas Navigator to determine the Linkstations IP, if it asks you to automatically correct the IP then click NO and let me know the 169.254 address you get.
Still not working. This is the tftp result:
Preparing to write TFTP configuration settings.TFTP Configuration settings have been written.TFTP Server Multithreaded Version 1.4 Windows Built 1.400Starting TFTP...alias / is mapped to C:\Users\Chris\Desktop\TFTP Boot Recovery\listening On: 192.168.11.1:69listening On: 127.0.0.1:69permitted clients: allserver port range: allmax blksize: 65464defult blksize: 512default interval: 3overwrite existing files: Nothread pool size: 1accepting requests..Client 192.168.11.150:2792 C:\Users\Chris\Desktop\TFTP Boot Recovery\uImage.buffalo, 4133 Blocks ServedClient 192.168.11.150:3320 C:\Users\Chris\Desktop\TFTP Boot Recovery\initrd.buffalo, 13750 Blocks Served
The nas navigator still can't find it as well as the update utility. I ran a network scanning tool and it cannot find the nas either. It's like it's not on the network, but it is plugged in like you said. The IP that I set for the nic is 192.168.11.1. All other adapters were disabled.
I could really use some help here. Is there anything else that I can do?
This really sucks that it died right around the time the warranty expired. Your phone support was not helpful. These forums were kinda helpful. But the bottom line is that I still have a $300+ paper weight now.
I've read a lot of complaints about this device online and it sounds like you guys knew that there were issues, but failed to offer the proper support or long term fix. Maybe I should talk to an attorney? I know that I'm not the only one who had their device brick right around the warranty expires. I didn't pay over $300 to only use this for less than a year before it decides to die!
So you cant ping 11.150? and did you try the force update option of going to debug and checking do not check version and force update?
Yes, that is true. As I said before, I can't even see it anymore. It's not visible on my network. But the TFTP boot thing did seem to work, but other than that, it's not accessible.
One weird thing that I just realized is that when I ping the NAS, it's trying to ping my computer.
C:\Users\Chris>ping 192.168.11.150Pinging 192.168.11.150 with 32 bytes of data:Reply from 192.168.11.1: Destination host unreachable.Reply from 192.168.11.1: Destination host unreachable.Reply from 192.168.11.1: Destination host unreachable.Reply from 192.168.11.1: Destination host unreachable.Ping statistics for 192.168.11.150: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\Chris>tracert 192.168.11.150Tracing route to 192.168.11.150 over a maximum of 30 hops 1 CRMain [192.168.11.1] reports: Destination host unreachable.Trace complete.
I honestly dont know. Could you try another pc?
Tried it with my laptop with the same exact results. :(
Bumping becasue I don't want to walk away from this $360 paperweight that only worked for a year. :o(