Buffalo Quad Pro – Updating to Shonk’s Firmware v1.64 Mod1 and reverting to v1.63 Mod1

I have been running Shonk’s v1.54 firmware for many months now and I don’t really have any issues with it. Now that I am back from holidays and have a bit of spare time before going back to work, I decided to upgrade to the latest firmware. Here are the steps I have documented, more so for my own record really.

Shonk has continuously updated and enhance Buffalo linkstation’s firmware and the latest version is v1.64 mod1. Way to go Shonk. You can see that I am exactly 10 revisions behind. Yes. I am outdated. Hopefully this update will bring me back up to speed.

Here is the main forum thread that says it all: http://forum.buffalo.nas-central.org/viewtopic.php?f=68&t=23603

And here is the v1.64 mod1 firmware: http://www.mediafire.com/?s2fnreo5nafpd. An alternative to this archive is here: http://download.discountnetz.com/oxygenacht/ls_series-164-mod1.zip. Courtesy of Oxygen8, another very active (and helpful) forum member of the linkstation community.

Again, the updating process is very simple. Just un-archived the firmware, run LSUpdater.exe and you will see the following:


Click the update button.


Enter the Admin password (which is the password for root access).

Then you will just have to be patient as the firmware is being updated.




In my case, half way through the process, the NAS will go into yellow alert mode (2 long flash and 5 short flashes). I just let it be.



Upon running LSUpdater again, it now shows that the firmware is now 1.64-3.29. I guess that means this is all good.


Now that the firmware is setup, here are some over simplified steps to reinstall ipkg again. Some of my steps could be redundant and may not be the best way to do things.

# rm -rf /mnt/disk1/.optware

# cd /mnt/disk1/tmp (this directory previously existed in my case, otherwise you could create this yourself)

I have previously downloaded optware into /mnt/disk1/tmp so I did not bother to re-download again. But if you must, here is the command to do so:

# wget http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/stable/ls-mvkw-bootstrap_1.2-7_arm.xsh

Note – Thanks to xjiang12 who commented on my post earlier, I guess a more correct optware version to use if you do run a raid array out of the linkstation is: 

# wget http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/teraprov2-bootstrap_1.2-7_arm.xsh

I no longer run a raid array on the NAS as I needed all the disk space that I have so I have not tried the above version so you would probably need to google this a little yourself. I just stick to the ls-mvkw-bootstrap_1.2-7_arm.xsh link.

# sh ./ls-mvkw-bootstrap_1.2-7_arm.xsh


# cd /opt/bin

# ./ipkg update

# ipkg install mc

# ipkg install nano

# mv /etc/init.d/optware /etc/init.d/rc.optware

# cd /etc/init.d

# nano rc.optware and ensure that the line “mount –bind /mnt/disk1/.optware /opt” is immediately below the first line of the file (which is the header #! /bin/sh). Save the file.

Do a shutdown and restart the NAS. Check if everything is running ok, including executing the ipkg packages such as mc and nano.

The last thing to do is to setup whatever scripts and the like, setup the crontabs, etc.

Things that don’t work

Unfortunately, while the firmware seems to be running fine, it broke the Network USB support.


Network-USB Navigator will be able to detect the presence of the NAS but will not be able to display any of the USB devices connected to it, no matter whether the device is directly connected to the NAS or connected via a USB hub. I wasn’t too happy and I am determined to get USB Navigator back. It is an important component to our workflow right now.

So I decided to revert back to an earlier version to see if I could get USB Navigator back running.

As I was upgrading from v1.54, I decided to try if version 1.60 works at all. The conclusion is that USB Navigator works right out of the box after the firmware was reverted to v1.60. Here is a screenshot:


The next test is to see if v1.63 mod1a works and the good news is that it does. Here is another screenshot.


So for the time being, the latest firmware that I can safely apply without breaking things is v1.63 mod1 and hopefully this time, everything works….not quite…

As I was upgrading from v1.54 to v1.64 and then downgrade to v1.63 and v1.60 for troubleshooting purposes, this messed up Samba’s password on the NAS. I can no longer connect to the NAS via samba (although the files are still intact on the drives).

This is what I have to do to fix this (sort of):

1. SSH into the NAS.

2. # cp /etc/samba/smbpasswd /etc/samba/smbpasswd.old

3. # cp /usr/local/bin/smbpasswd /etc/samba and replace the original file there.

4. # cd /etc/init.d

5. # ./smb.sh restart

That solve the Samba issue I have.

Things that works

I finally managed to get itunes server back up and running. Itunes support was previously broken under v1.54 and I never bother to upgrade the NAS to fix this. Apparently this is fixed for all firmwares starting from v1.58.

USB Navigator now works fine. I am happy.

Well, that’s all for this post.

Thanks for dropping by.




Posted on January 4, 2013, in Buffalo Quad Pro NAS and tagged , , , , , , . Bookmark the permalink. 5 Comments.

  1. Hi Joseph, thanks for the wealth of information. I’ve got a Buffalo Dual Pro and your posts have been more than helpful.

    Did you have to reinstall any of your other custom packages (eg: nano) or was install optware all you need to do?

    Also, have you been able to get drive spindown to work? Shonk recently updated to 1.64a and one of the updates is that he disabled excessive head parking on seagate / others that support apm via mod.sh. I assume this is due to the spin down feature, but I can’t seem to find the option anywhere (I’m currently running 1.64).

  2. Hi Justin. I am glad you find the blog helpful. Generally when I flash a new firmware, I like to reinstall all the custom packages (such as nano, mc, etc). I don’t run many packages nowadays on the NAS so it is not a problem for me to reinstall, plus the process is extremely quick.

    I run my NAS 24/7 with the drives never spin down. I have rsync enabled on the NAS and rsync clients on all the other PCs in the house and all PCs will periodically sync to the NAS so I don’t see how spindown can help me, apart from saving some energy cost.

    Re. your question on spindown. I won’t lie. I don’t have an answer for you. I am not sure if the latest v1.63/v1.64 firmware has spindown features. The last time I checked, spindown is more like an experimental feature from shonk but I could never get it to work on my system (not that I need to).

    I did peak at the mod.sh on my box and I don’t see references to enable spindown. But I could have missed.

    If you are really keen to enable spindown, I would suggest to jump on the forum and post a question. I am sure Shonk/Oxygen would be able to help you there.

    Good luck. Thanks for stopping by.

  3. Thanks Justin. That is a helpful comment from shonk.

  4. Hi Joseph, thank you for the very comprehensive posting on the setup of Buffalo Link-Station Quad. Do you know if there is any configuration to be done on StarHub’s Maxinfinity Fibre Broadband using HuaWei HG256s Home Gateway? I could not log in to Buffalonas.com and getting the error message “Could not connect to IP address”

  5. Hi Vincent, I m not familiar with those hardware but if u are getting connection errors, I would suggest u check your firewall settings. Have u opened a port and port forward that port to the ip address of the nas? Try that. Good luck! Thanks for dropping by.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: