Win XP, LinkStation Pro Duo 1tb.
I was able to successfully tftp boot earlier to perform a recovery, however now it is in a state when you check the web, it shows the message.
Currently a Format or Disk Check is being carried out.
During this time the LinkStation settings can not be changed.
Also the file share service will not be available.
Assuming it was doing something productive, i've left it on for several days, many times. Each time it says it's doing a format, flashes 5 !'s (the first ! is a long flash), after awhile the web control can't be accessed, but the flashes still occur.
A piece of information is left out of doing the tftp document on the board. You are told to set the address to 192.168.11.1 and mask to 255.255.255.0, however the gateway is not mentioned, nor dns addresses. These are probably meaningles, i was using 192.168.11.2 for gateway and leaving the dns address blank. I think i might have used a different gateway the last time tftp worked. This time running "TFTP Boot.exe" it never gets a message and just sits there waiting at "accepting requests..", while it appears to do a succefful EM boot with blue light flashing then solid.
Someone said it's ok to delete the partitions on the drives, (that doesn't sound like the most logical thing to do) the drive 4(+3 extend) partitions are still intact, but would it be ok to delete them and attempt another tftp?
TFTP Boot only boots a unit with no boot image and it will do nothing more. Bottom line, if the unit is booting then a TFTP Boot will not solve any issues! And Yes, the Gateway does not matter, nor does any DNS.
buscha wrote:
Someone said it's ok to delete the partitions on the drives, (that doesn't sound like the most logical thing to do) the drive 4(+3 extend) partitions are still intact, but would it be ok to delete them and attempt another tftp?
This is not supported by Buffalo is not recommended!
The Info code you are recieving is a RAID check, this can take anywhere from 8-16 hours in which you will not be able to access the unit but it should not take days! Seems to be stuck in that mode if it doesn't finish... It will restart the check all over again if the unit is rebooted before it finishes.
Try booting the unit into EM and then Force Update FW with rebuilding the partition tables along with delete user config (through debug settings in the Updater).
thanks, i've tried em booting and forcing update with the rebuild partition tables set, it appears to do some work (with a progress popup) but them gives me a cryptic error message. I will post when i can see the error message again. But i think when i was flash updating it wasn't stricly in EM mode. When i attempt and em mode boot it goes to solid blue but then goes to green, does that mean it's still in EM mode, or do i have to perform the flash while the blue light is solid to do the update while in em mode.
I also noticed that i was getting port submits to 137/138 while the tftp booter was listening on port 69. I guess if it is already booting and giving me web access tftp boot wont help me.
The only other thing i'd like to ask is how do i determine if i need a v3 or a v1 update. I have two usb ports on my pro duo, but somehow i don't think that's a good way to tell if i need v3 or v1.
If you have the 2 usb ports you have version 3. You also can tell because your unit has a function button and an on/off switch. Version 1s have a reset button and a power button on the back above the fan. This is actually a pretty clear cut way to make sure considering it was a hardware revision.
Let us know about that error.
Ok after booting for ages with 5/6 flashes, it eventually booted up in LS-WTG-EM mode from DHCP client table with no warning flashes. Couldn't get web login. Tftp boot did not work again, so i Tried lsupdate, and Didn't get the error again on an LSUpdate = probably because this time i had firewall off. Formated, deleted user config, lots of prompts and progress bars succeeded and i got it to boot normally. Not sure if it was patience or luck here and more importantly even though this is a really convenient machine for backups and such i'm affraid of using it for a live system now, but i'll see how long this good status lasts and rethink. thanks to EVERYONE on this group, i would be lost with out it.
Message Edited by buscha on 07-17-2009 09:05 AM
The unit booted into EM mode. The TFTP wouldn't help much from there as the unit had already booted. Flashing the firmware was the correct idea. I am glad that you got it working.
Browser ID: smf
(is_webkit)
Templates: 1:
Printpage (default).
Sub templates: 4:
init,
print_above,
main,
print_below.
Language files: 1:
index+Modifications.english (default).
Style sheets: 0:
.
Hooks called: 74 (
showintegrate_autoload, integrate_pre_load, integrate_load_session, integrate_verify_user, integrate_pre_load_theme, integrate_user_info, integrate_load_board, integrate_board_info, integrate_allowed_to_general, integrate_allowed_to_general, integrate_boards_allowed_to, integrate_mod_cache, integrate_pre_load_theme, integrate_allowed_to_general, integrate_simple_actions, integrate_allowed_to_general, integrate_load_theme, integrate_pre_log_stats, integrate_actions, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_codes, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_menu_buttons, integrate_current_action, integrate_theme_context, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general)
Files included: 27 - 1055KB. (
show./index.php, ./Settings.php, (Cache)/db_last_error.php, (Sources)/QueryString.php, (Sources)/Subs.php, (Sources)/Subs-Auth.php, (Sources)/Errors.php, (Sources)/Load.php, (Sources)/Security.php, (Sources)/Subs-Compat.php, (Sources)/Subs-Db-mysql.php, (Sources)/Cache/CacheApi.php, (Sources)/Cache/CacheApiInterface.php, (Sources)/StopForumSpam.php, (Sources)/Subs-Charset.php, (Sources)/Unicode/Metadata.php, (Sources)/Unicode/QuickCheck.php, (Sources)/Session.php, (Sources)/Logging.php, (Sources)/Class-BrowserDetect.php, (Sources)/Unicode/RegularExpressions.php, (Sources)/Unicode/CaseUpper.php, (Sources)/Unicode/CaseTitle.php, (Current Theme)/languages/index.english.php, (Current Theme)/languages/Modifications.english.php, (Sources)/Printpage.php, (Current Theme)/Printpage.template.php)
Memory used: 723KB.
Tokens:
post-login.
Queries used: 14.
[Show Queries]