Buffalo NAS-Central Forums

The telnet-enabled firmware and jtymod5 now includes lb_worm's new initrd. The new initrd helps to overcome some issues with the Buffalo Updater. Users are strongly advised to use either these fixed versions.

[b:46b0e]Here is a guideline of how to install OpenLink, jtymod5, and the telnet-enabled firmwares for the LS-Pro correctly[/b:46b0e]

Step 1:

Users must install the "Initrd Only" package if they can answer [b:46b0e]yes[/b:46b0e] to one of the following questions:
a) Has the "Initrd Only" package [b:46b0e]never[/b:46b0e] been installed on the LS-Pro?
b) Have you reverted the LS-Pro back to the Buffalo-Stock Firmware?
c) Are you upgrading the LS-Pro from Buffalo-Stock Firmware?

If you answered yes to any of the above questions, please download the "Initrd Package" here: [url=http://buffalo.nas-central.org/download/LSPro_ARM9/Initrds/for_stock_and_openlink/LS-GL-initrd-only.zip:46b0e]http://buffalo.nas-central.org/download/LSPro_ARM9/Initrds/for_stock_and_openlink/LS-GL-initrd-only.zip[/url:46b0e] The package installs lb_worms initrd only via the Buffalo Updater.

There will be an error saying "hddrootfs.img not found", "uImage.buffalo not found". That is expected as we are only updating initrd. The errors can be overridden by using the "Debug Mode" for the Buffalo Updater. To access the debug menu, right-click the "Buffalo Updater Icon" on the Windows context-bar (the bar at the bottom of the screen that spans between the start menu and the clock). Select "Debug(D)..." and the Debug Mode menu will pop up. In the upper left-hand corner of the menu is an "Update" section. Deselect everything in that section except "Update initrd" and hit ok. Then update as usual.

If you answered no, you do not need to install the "Initrd Only" package. You may go to step 2.

Step 2

Install the fixed version of jtymod5 or the telnet-enable firmwares. These firmwares also contain lb_worm's initrd. Install the firmwares normally.


Fixed versions:

telnet-enabled firmware for v1.03: [url=http://buffalo.nas-central.org/download/LSPro_ARM9/StockFirmware/TelnetEnabled/:46b0e]http://buffalo.nas-central.org/download/LSPro_ARM9/StockFirmware/TelnetEnabled/[/url:46b0e]

jtymod5: [url=http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/FreeStation_jtymod/:46b0e]http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/FreeStation_jtymod/[/url:46b0e]


Support will not be given for the older versions of telnet-enabled firmware and jtymod without lb_worm's initrd except for those that:
a) Are attempting to remove the older versions to replace it with one with lb_worm's initrd -or-
b) Are attempting to remove the older versions for a firmware version that the development team deams acceptable -or-
c) Are reverting from the older version to the stock firmware.

(This is not done to appear mean. Those older versions without lb_worm's initrd have many updating issues and the forums cannot be filled with the same complaints. Sorry. )


Firmwares that will have the initrd fix:
a) OpenLink-arm (not released yet).
b) FreeLink-arm (in developmental stage).
c) Telnet-Enable firmwares for the LS Pro.


Thanks,

jonli447

Hello and a happy new year!

I try this both steps and get the same error-message: "ACP_STATE_FAILURE"
Have you another Tip?

Thanks for the help!!!

At what point did you get the ACP_STATE_FAILURE? Was it on installing just the initrd image?

Once you have installed the new initrd image and it has installed without a problem then a reboot is required to remove the previous images. This should happen in any case as this is what the updater does. You should then be able to install your image after this

I started with the initrd flash. The Updater begins to transfer and after perhabs 45 sec. i get the error-message. Next try , same result.
And, on my mistake, another sh.. happens: I select in the Debug Mode from the B-Updater on the right side (config) "Rebuild partition table" and "Force update".
First it seems to work, the LS reebot and beeps after a few seconds until i push the powerbutton. Now it beeps after any restart and the updater find no LS!!!

The second two tone beep is what I added to the boot process so you know it has happened. If you now have Debian, the updater will not locate it as the server is not run under Debian. To get back to this, you need to reboot in EM mode, set /boot/boot_options [b:b0eb4]MENU_TIMEOUT=EM[/b:b0eb4] which on reboot (everyone until this is reset) to EM mode where the updater will now work

[quote="fredvj":72aac]First it seems to work, the LS reebot and beeps after a few seconds until i push the powerbutton. Now it beeps after any restart and the updater find no LS!!![/quote:72aac]
That's because now you don't have a rootfs or kernel...very very bad. You'll need to connect the sata drive to a linux pc, mount the first partition, and copy uImage.buffalo to the first partition. Edit boot_options for EM-Mode and connect the drive back to the box. Hopefully the box will boot into EM-Mode.

Then, use the full updater package (not the "intrd only" package) to reinstall the rootfs.

Thank you for the fast help!
I have to go to a friend with linux knowhow and an modern PC (s-ata)
and do the steps you have told me. This will take a few days.

Hi,

I'm getting a new LSPro this afternoon and planning on following the steps above so that I can then compile mt-daap and get a music server up and running. I just want to make sure that the steps above are the current state of the art and that people have run them without a problem - don't want to brick it immediately!

So given that I am getting it stock new, I will run both steps 1 and 2 above, right? Anything I need to do to avoid the problems fredvj saw?

Thanks,
Charles.

Also, what is the difference between installing

[url=http://buffalo.nas-central.org/download/arm9-LS_Pro/telnet_enabled_no_root_password/LS-GL-103.2-fixed.zip:89b14]http://buffalo.nas-central.org/download/arm9-LS_Pro/telnet_enabled_no_root_password/LS-GL-103.2-fixed.zip[/url:89b14]
vs.
[url=http://buffalo.nas-central.org/download/arm9-LS_Pro/LS-GL_FW_103-jtymod5-fixed.zip:89b14]http://buffalo.nas-central.org/download/arm9-LS_Pro/LS-GL_FW_103-jtymod5-fixed.zip[/url:89b14]

Which one makes sense for me since I want to compile mt-daap?

Thanks,
Charles.

You have got to be very very careful here. You only want to upload new hdd image and not UBoot. Any problems during flashing of UBoot [b:5a457]will[/b:5a457] brick your box. As this box has never been updated before, you do not need to apply my initrd patch before you begin as this is incorporated into the image. Neither of these alone will offer what you want. You need the devtools that jonli447 has developed too. You could wait until either Openlink of Freelink are available or alternativly, jonli447 will produce a clear set of procedures to follow. Try the wiki site first to see if this has been done yet.

OK, thanks for the info - although

[quote="jonli447":8055b]Users must install the "Initrd Only" package if they can answer yes to one of the following questions:
a) Has the "Initrd Only" package never been installed on the LS-Pro?
b) Have you reverted the LS-Pro back to the Buffalo-Stock Firmware?
c) Are you upgrading the LS-Pro from Buffalo-Stock Firmware? [/quote:8055b]

makes me think I DO need the Initrd patch...not the case? The stock Buffalo firmware now contains that fix?

Understood that I need the devtools - I've been looking into grabbing those - are you saying that I can install those and compile / run mt-daap without flashing my firmware? Don't I need root access? In order to use the devtools, shouldn't I flash it with the telnet enabled / no root password firmware?

Thanks,
Charles.

[quote="charlesdesaintaignan":a5716]makes me think I DO need the Initrd patch...not the case? The stock Buffalo firmware now contains that fix? [/quote:a5716]

Sorry, you are quite correct. The stock box leaves an image behind which you need to remove if the replacement hdd image is either of [url=http://buffalo.nas-central.org/download/arm9-LS_Pro/telnet_enabled_no_root_password/LS-GL-103.2-fixed.zip:a5716]http://buffalo.nas-central.org/download/arm9-LS_Pro/telnet_enabled_no_root_password/LS-GL-103.2-fixed.zip[/url:a5716] or [url=http://buffalo.nas-central.org/download/arm9-LS_Pro/LS-GL_FW_103-jtymod5-fixed.zip:a5716]http://buffalo.nas-central.org/download/arm9-LS_Pro/LS-GL_FW_103-jtymod5-fixed.zip.[/url:a5716] You can use the telnet_enabled (1st one) for your use and add the devtools afterwards. [b:a5716]Follow the installation notes carefully and ensure you use the right updater and run it debug mode so you can control the downloads.[/b:a5716]

All "initrd only" does is installs lb_worm's initrd. I recommended users use the "initrd only" package when updating from the buffalo stock firmware to save confusion (It doesn't hurt to install the "initrd only" package). But, technically, if you have never updated before, you don't need the "initrd only" package.

[quote="charlesdesaintaignan":f7cb8]Understood that I need the devtools - I've been looking into grabbing those - are you saying that I can install those and compile / run mt-daap without flashing my firmware?[/quote:f7cb8]
It's still in testing mode (devtools), but theoritically, yes.

[quote="charlesdesaintaignan":f7cb8]Don't I need root access? In order to use the devtools, shouldn't I flash it with the telnet enabled / no root password firmware? [/quote:f7cb8]
Yes, you'll need root access/ telnet or ssh access.

Should be sticky this post...

Okay Good idea.