Buffalo NAS-Central Forums

Just for starters, I'm pretty sure it's not Shonks mod that screwed this up, but my n00b skills.

I got my Linkstation yesterday with FW 1.4x on it. First thing I did was getting Shonks 1.53 mod 1b on and it went without a glitch.
I then fooled around trying to get nzbget working and also flexget. It went somewhat OK, but stuff got f%&8 up and to make a long story short, I wanted to start over with a fresh install. I went to the Linkstations web settings, system tab and chose erase. That had the thing working ~8 hours erasing the whole drive. Then it started writing 0's to the whole drive, which would take just as long and this was only step 2/4 so I was assuming it would take 24 hours more for it to be done - I was not willing to wait (read: stupid) and asked it to restart with the result of ending up in EM mode.

I tried flashing again with Shonks 1.53 mod 1b, but it told me that it was unsure of the partition and no update would be made. I had checked the "rebuild parition" in debug mode, so this made no sense to me (later found out I probably should have changed NoFormatting = 0 in the LSUpdater.ini - but here we are).

OK - I'll try stock fimware and then Shonk again - bad idea. I tried updating with the stock firmware from osx and now it went into blinking red mode! I am not able to tftp to it. I've tried with TFTP Boot Recovery 1.43 which is the latest I can find. Mind you, I'm doing this in VMWare with an XP image, bridged network. The ip is set to 192.168.11.1 and tftp is listening on that. When I start the Linkstation i keep the function button pressed. It blinks blue, one red, and then back to blinking blue.

I've tried telnet 192.168.11.150 with no luck.

I'm really hoping this only fails 'cause of the vmware thing or because of wrong tftp version, but I fear not. Is it really royally screwed? I guess I broke warranty as soon as I installed mod firmware


Edit 1: While writing this it has given me:
client 192.168.11.150:2258 C:/documents and settings/admin/desktop/tftp/uimage.buffalo, 5322 blocks served

I don't know what to do now. Shouldn't it have been two lines?

Edit 2: waiting 15 more minutes helped me get line 2: client 192.168.11.150:2258 C:/documents and settings/admin/desktop/tftp/initrd.buffalo, 20826 blocks served, it rebooted and is now flashing 6x red again. Nothings changed

Edit 3: I tftp'ed once more. This time I let it sit for half an hour, got steady blue light, kept the tftp open while I changed windows IP to match the new range of the Linkstation (firmware updater found it - 169.254.137.1) and updated.

Succes!

Everything's in japanese, but I figured how to change that from the web interface (http://buffalo-helpdesk.dyndns.org/jp-en.htm or http://forums.buffalotech.com/t5/Storage/How-to-Change-language-Menu-on-LinkStation-Live-LS-CHL-1T/td-p/32575)

Hopefully somebody will find this post useful

make sure it survives a reboot on the stock firmware

e.g. reboot it from the web interface
aslong as it comes back up

you can flash it with 1.53 mod again

yes it was your n00b skillz and not the firmware

I didn't give it a go on stock - just straight to your mod, and it is surviving reboots! I managed to get it back, but it took quite some time to gather all the info. In the wiki, it says that it didn't work if it didn't pull the files within two minutes. For me it took almost half an hour, but I'm sure it's 'cause of the vmware thing. You wrote somewhere the trick about tftp'ing it twice, let the tftp connection stay open and then reflash. -This also could go in the wiki.

I'm trying to write a noobs-how-to for people like me on how to get your mod firmware on a brand new box, bootstrapping and setting up nzbget, nzbgetweb and some sort of rss parser.

So far I have it bootstrapped, and tomorrow I'll look into the rest. I think I'm going to need SSH access at some point. Is it correctly understood that I just need to go to /etc/melco/info and edit the line SSH=off to SSH=on, restart and tadaa! SSH into the box?

yes

you must have run stock at some point if it came up in japanese
as mine defaults to english

I think that was when I ran the osx updater...