Advertisement
VolleMelk

TFTP for LS-WVL

Mar 17th, 2013
6,318
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.96 KB | None | 0 0
  1. LS-WVL TFTP procedure
  2. ---------------------
  3.  
  4. Last update 8-sept-2013
  5.  
  6. Prequel:
  7. --------
  8. If you ever find yourself in a situation where you actually WANT your LS-WVL to be in EM mode (after faulty debian installation, unresponsive, unable to locate on the network etc etc) do this: Get yourself a computer on which you can boot Linux (If you do not have Linux, download KNOPPIX. You can use the Live CD from USB) and use gparted to DELETE all the partitions on BOTH drives. It should be ONE big unallocated drive.
  9.  
  10. You can also use this live cd/usb to mount the drive, and copy your data from. Once you have mounted the drive, it is not possible to delete partitions. I have found, that the only way to delete partitions after a data backup is to reboot linux and start gparted without mounting the partitions.
  11.  
  12. Once both drives do not contain any partitions, insert both drives in the NAS and boot. You will now have a NAS in EM mode (See paragraph 'LS-WVL behaviour' below).
  13.  
  14. And for those who are wondering: Yes, you really need to do this with both drives. Also, in this article I mention ftp and TFTP. These two are something totally different. Don't get confused, read twice.
  15.  
  16. Also, in this guide we do NOT use the buffalo stock firmware. We are using a modified firmware by Shonk. Read below where to get this.
  17.  
  18. It is VITAL that you perform the steps below in the exact same order
  19.  
  20. Requirements:
  21. -------------
  22. * Shonks 1.64 mod1: http://forum.buffalo.nas-central.org/viewtopic.php?f=68&t=23603
  23. * TFTP files for LS-WVL: ftp://24.153.165.234/mnt/array1/share/nas-recovery/TFTP%20Boot%20Recovery-LS%20Pro%20DUO.exe (Use ftp client in case you have bad/slow connection (filezilla))
  24. mirror: http://http://members.ziggo.nl/roodgoudzilver/lswvl/TFTP%20Boot%20Recovery-LS%20Pro%20DUO.exe
  25. * Windows 7 or XP - I have read mixed results with running Windows in a virtual machine. I have always done TFTP on Windows 7. It really works. Turn off any firewalls and virusscanners.
  26.  
  27. Optional (Try the guide before you download this, you may not need it)
  28. LSRecovery: http://http://members.ziggo.nl/roodgoudzilver/lswvl/LSRecovery.zip
  29.  
  30. Note 1:
  31. ------
  32. Allthough this guide is part of a greater series on "Installing Debian Squeeze with custom kernel 3.8.3 on LS-WVL", you can use this guide only to recover your bricked LS-WVL. The complete guide can be found here: http://pastebin.com/H6rEZ5ge
  33.  
  34. Note 2:
  35. -------
  36. You can possibly use this guide to restore other Buffalo models. Make sure you download the correct TFTP program from here: ftp://24.153.165.234/mnt/array1/share/nas-recovery (read the "READ ME FIRST.txt" file!). Use a proper ftp client (Google for Filezilla). If you're not using a ftp client, browsing will be VERY slow.
  37.  
  38. Note 3:
  39. -------
  40. Step 3 is about replacing buffalo TFTP files. I had to do this before I could recover my LS-WVL. If I didn't, the NAS would hang after the files were transferred. I don't know if this is necessery for other models. I suggest you skip step 3 on your first/second attempt. If it's not working, try again and perform step 3.
  41.  
  42. Note 4:
  43. -------
  44. As stated before, I had to use Shonk's modified firmware. If at the end of this guide you're not getting your NAS unbricked, you can try to use the original Buffalo firmware. If this is the case, SKIP step 3 (explained in note 3).
  45.  
  46. LS-WVL Behaviour:
  47. -----------------
  48. * Turn on NAS
  49. * Rapid flashing blue light
  50. * After a few seconds, the red light blinks 6 times and the blue light is out
  51. Conclusion: EM mode
  52.  
  53. If you are not in EM mode, you can not perform a TFTP recovery. If you do not have the LS-WVL, you may need to search the internet for symptons your Linkstation my have for EM mode.
  54.  
  55. Solution:
  56. ---------
  57. 1) Extract the TFTP files (the .exe is a 7zip self extracting)
  58.  
  59. 2) In ls_series-164-mod1 directory, open lsupdater.ini and check if you have:
  60. [Flags]
  61. VersionCheck = 0
  62. NoFormatting = 0
  63.  
  64. [specialflags]
  65. debug = 1
  66.  
  67. at the end of the file. If not, change or copy/paste.
  68.  
  69. 3a) In the TFTP directory, rename these files:
  70. * initrd.buffalo -> initrd_original.buffalo
  71. * uImage.buffalo -> uImage_original.buffalo
  72.  
  73. 3b) From ls_series-164-mod1 copy these files to the TFTP directory:
  74. * initrd.buffalo
  75. * uImage.buffalo
  76.  
  77. 4) Disable firewalls, and set your ethernet network adapter to
  78. * IP: 192.168.11.1
  79. * Subnet: 255.255.255.0
  80. Leave other fields (gateway and DNS) empty. Remember previous settings, you have to set these back in step 11.
  81.  
  82. 5) Connect the NAS directly to the computer with an ethernet cable
  83.  
  84. 6) Turn on the NAS, wait for blinking red light (EM mode)
  85.  
  86. 7) Start "TFTP Boot.exe" in "TFTP Boot Recovery" folder
  87.  
  88. 8) Check if you see
  89. listening On: 192.168.11.1:69
  90. If you do NOT see this, the procedure will not work and you failed to properly configure you ethernet adapter (go back to step 4) OR your ethernet cable is faulty. I did this with a normal (straight) ethernet cable.
  91.  
  92. 9) Press and hold function button on back of LS-WVL. The red light will go out, and the blue light will start flashing rapidly. You should almost see immediately two files getting pulled (initrd.buffalo and uImage.buffalo). See this screenshot: http://buffalo.nas-central.org/wiki/File:Buffalo_TFTP_Boot_After.png
  93.  
  94. 10) When the blue light becomes steady (the fan in the LS-WVL will also spin down):
  95. - Close "TFTP Boot.exe"
  96. - Remove ethernet cable between NAS and PC
  97. - Revert the static IP changes you did in step 4 (probably DHCP)
  98. - Connect the NAS to your network (switch or router)
  99. - Connect the PC to your network (switch or router)
  100.  
  101. 11) Start LSUpdater.exe in ls_series-164-mod1 (This is NOT the buffalo stuck LSUpdater!) directory. Your NAS will be detected on an IP that is normal for your network, and you can Click UPDATE.
  102.  
  103. 12) Nas will ask if you want to format the partition, confirm.
  104.  
  105. Your NAS now is working, you should be able to login to the webinterface with admin/password. If this does NOT work, you need to reset your NAS back to factory settings. I have ONLY been able to do that with LSRecovery.exe. There is a link to LSRecovery.zip in the 'Requirements' section of this guide.
  106.  
  107. Final Notes:
  108. * If you WANT to get into EM mode to use this procedure, hook up the drives to another linux box (or use knoppix), and delete ALL the partitions on both drives so it's one big unallocated drive. Put drives back in NAS, power on and see the red light blinking red 6 times
  109. * Also, you can telnet in to the NAS with admin/password.
  110. * I've been having mixed results with ssh. You can try to connect, if it works you're lucky.
  111. * If SSH does not work, you have to turn it on:
  112. - Connect with telnet (user: admin, password: password) and pass these commands:
  113. su
  114. vi /etc/melco/info
  115. - Scroll down, you will find SSH=off, change that to SSH=on (Google for a manual on vi. In short: use arrows to move cursor, press 'i' to 'insert' text (now the backspace also comes active), when you are done press 'esc' and enter
  116. :wq (that is with the : and then wq. wq is write+quit)).
  117. reboot
  118.  
  119. After the reboot, you should have your SSH connection
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement