[SOLVED] Can ping Buffalo Linkstation Live, but nothing else works
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Can ping Buffalo Linkstation Live, but nothing else works
I was having a computer delete files on my NAS. While that was going on, the drive did it's overheating thing that it does sometimes, and shut itself off. I turned it back on, and it appeared normal. However,I cannot access the web interface or the samba server or any of the services it runs now. I can ping it okay, but that's all. Can someone help me get it back up and running again, prefferebly without losing any of the data on the drive?
According to the online manual:
3 flashes - Partition problem with hard drive. Reformat the hard drive.
4 flashes - Fan problem.
5 flashes - ROM problem.
6 flashes - Hard Drive can not be recognized.
7 flashes - Problem with motherboard (RAM, LAN, or Hard Drive controller).
According to the manual the internal drive is formatted with XFS If the device does indeed have a hardware problem assuming it isn't the drive itself you could remove it and connect it via USB-SATA adapter or install internally to attempt data recovery.
It was flashing when I noticed it. But I don't know how many times. It was also beeping. However, when I turned it off and back on, it ceased to flash and beep. That is why I thought it was back to normal, but it is not.
Loosing data and the ability to access the software/web interface may be two different things. As noted above the data may still be there.
Not sure what you mean by as it usually does. Indicates you had some issue that should have been fixed long ago? Wrong drives in it maybe.
First try this. Shut it down if you can properly. Remove ac power, disconnect the drive(s) and then press the power button a few times. Then try to power it back up and see if you can access the gui or remote access.
I powered it off, unplugged it and pressed the power button a few times. Then I plugged it back in and it still is having the same trouble. I suspect it to be a firmware problem, therefore I was trying to reinstall the firmware with lsupdater. It says that it can't find a linkstation that needs updating. Here is my LSUpdater.ini:
I found it by using java -jar acp_commander.jar -f 192.168.11.150, and this was it's output:
ACP_commander out of the nas-central.org (linkstationwiki.net) project.
Used to send ACP-commands to Buffalo linkstation(R) LS-PRO.
WARNING: This is experimental software that might brick your linkstation!
Using random connID value = 5FE7C1196A4F
Using target: 255.255.255.255/255.255.255.255
Sending ACP-Disover packet...
Found: HS-DHGL-EMB5C (/192.168.11.150) HS-DHGL(JINMU) (ID=00010)
mac: 00:16:01:C5:4B:5C Firmware= 10.00 Key=47B464F8
Found 1 linkstation(s).
---------- Post added 11-23-13 at 07:19 PM ----------
What device corresponds to the firmware? The data in the drive appears to be intact, so I could just find the firmware image from the /boot partition (/dev/sda1), and then reflash it with dd. But I don't know which device corresponds to the firmware. Also, is the file to reflash called u-boot.buffalo?
Well so much for the data. /dev/sda isn't the device for the firmware to go. Accroding to: http://www.yamasita.jp/linkstation.en/flashmemory.html, it's /dev/fl2. I created it with the instructions, as it wasn't there. But with dd trying to use it, I get an error message, "No such device or address". What does that mean? Does that mean it's not working, or that I still have the wrong place, or something else or what?
What I thought I'd been actually told, was that the firmware goes on the hard drive, but where, I'm not sure if so... I'm assuming that the special devices /dev/fl2 and such map to this point, or are supposed to. Either that or I'd still be open to trying LSUpdater, if anyone knows why it's having the error that it can't find the linkstation. The Error light is now flashing red, indicating that regardless of the firmware situation before, there is definately no firmware in it now.
What I'd done, is dd if=u-boot.buffalo.updated of=/dev/sda, thinking that maybe it's like a PC. I guess not exactly, because it wiped out the partition table, and wherever the firmware was, it's definately gone for sure now. I think it was there but corrupted before.
First... tell us which LS live you have.. eg, mine is a HS-DHxxxGL (the xxx isn't important).
Next... boot from an ubuntu live CD (or machine) with gparted and xfsprogs installed.
with xfsprogs, you can access your xfs partition and use gparted to do stuff...
back up /dev/sdx6 (where x might be a b c or whatever). This is your data ie /mnt/disk1 on the LS.
back up /dev/sdx2 - this contains your config, share definitions, user defs and other stuff - ie /etc/melco and other stuff
You can backup using tar:
tar pcvf /home/media/backupsdx6.tar . (when you are in /media/xxx/long number of mounted xfs partition)
the p ensures permissions are taken. Do not use * instead of . As I found out they are not the same.
Next.. go and get the right firmware. I use "Stevie Wonder", which is much better than the stock one. Google that and linkstation firmware and you'll find a hit that says something like "the moth goes to the flame again". Go to the bottom of that post and you'll find a link.
If you are sure you have a good backup, then flash that FW, and repartition your drives. Click the rings on the top left of the program to set advanced options.. there is a readme too iirc.
If you use a new drive, you must copy the first partition from the old to new drive - gparted will let you copy the /boot partition.
Of course, most of this is valid for my LS and not the LS-CHL (black) one.
further to the last post, it is writing that doesn't work, so even cp doesn't work. I would buy a cheap external USB drive, format it ext3, then cp or tar c to that, when attach it to the back of the LS and cp/tar x back again.