NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 2304 in status TFTP_REQ after Firmware Upgrade to 6.9.4
After Upgrading my ReadyNAS 2304 to Firmware 6.9.4 the device does not re-boot into normal operation: Neither the Admin page nor the shares are accessible.
An access attempt with RAIDar is show...
1) Yes, this can happen sometimes. Could be a problem with the filesystem on the internal flash, a failing internal flash, corrupt files on the internal flash or some other issue.
2) Yes, but how to proceed does depend on different factors such as what happens when you try to mount the internal flash, what errors relating to the internal flash you see in dmesg etc.
Normally with this error USB Boot Recovery would be attempted (may need to try multiple different USB keys).
Support knows how to manually update the files on the internal flash and even write a flash image to the flash.
If you can’t boot to tech support mode getting to the TFTP_REQ state would mean that TeamViewer would be an option to look at it using local telnet.
The .os_update procedure involves the system mounting the flash and extracting the OS files over the top of the OS partition. That’s highly unlikely to fix TFTP_REQ imo.
2) Yes, but how to proceed does depend on different factors such as what happens when you try to mount the internal flash, what errors relating to the internal flash you see in dmesg etc.
Normally with this error USB Boot Recovery would be attempted (may need to try multiple different USB keys).
Support knows how to manually update the files on the internal flash and even write a flash image to the flash.
If you can’t boot to tech support mode getting to the TFTP_REQ state would mean that TeamViewer would be an option to look at it using local telnet.
The .os_update procedure involves the system mounting the flash and extracting the OS files over the top of the OS partition. That’s highly unlikely to fix TFTP_REQ imo.
First Step: Backing Up Data
Thanks a lot to StephenB for guiding me to a successful data backup. Indeed it was possible to mount the RAID successfully via telnet using his suggested sequence (from within chroot):
# btrfs device scan
# btrfs fi show
# mount -ro /dev/md127 /data
After :smileyhappy: seeing my data again, I then connected an external USB hard disk (formatted with ext4) and copied all my data to it. Despite I experienced a little "unreliability" during recursively copying the /home folders, I'm now on the safe side and have all my data on a separate hardware. Maybe I should note that backing up data via scp did work as well from within the telnet access.
Yet Open: Firmware Update
Unfortunately the suggestion to use touch /.os_update to re-trigger firmware update did not prove to be successful. As a consequence, the device is still in state TFTP_REQ and I was trying to follow the advice of user "mdgm" for a USB Boot Recovery.
To my disappointment, the device does not recognise the Recovery-USB-sticks (tried two different makes yet). Some questions as to this suggested USB-Boot procedure:
The advice is to "power on" the device whilst keeping the reset-microswitch pressed and wait for "fast flashing LED". It seems to me that the device is quite hard to convince to get into such boot mode, because I had to disconnect ethernet and to use the "hard" power switch on the rear panel to switch from off to on (and of course, the USB-stick needs to be plugged in). Can this "USB Boot mode entering sequence" be confirmed? In my case, only the green LED is flashing (decently) fast, but there is only little activity on the USB stick. Update attempts yet have all failed :smileyfrustrated:
Similarly, getting into the "boot menu" (well, I don't have a display connected. I have to rely on LED patterns) seems only possible with disconnected ethernet and using the "hard" power switch on rear panel and of course without any USB stick - or did I miss something here? However, an "OS reinstall" did again not lead to any success - and I'm yet hesitating to perform the "Factory default" procedure.
Suggestions are welcome...
Thanks in advance and kind regards,
Tom
Status: Worse than before...
Well, as reported in my last posting, at least I was able to retrieve and backup all the data from my ReadyNAS2304.
Today, I have set aside my hesitance and tried to overcome the situation by triggering a "Factory Default" procedure in the boot menu. Unfortunately, the resulting state seems worse than before:
- RAIDar is still showing firmware 6.9.4 and state "TFTP_REQ"
- Access via telnet is basically still possible. From the fact that the device is now reporting with its initial name (i.e. nas-MA-Ct-ail) I get that the "Factory Defaulting" process has been completed
- It is now not possible anymore to get into the chroot environment. When entering rnutil chroot the device is now responding "chroot: can't execute 'bash': No such file or directory"
Any suggestions on how to proceed?
Kind regards,
Tom
I have same problem, someone can help me to fix my RN102 with TFTP_REQ.
1.-I try Boot recover
2.-Reninstall firmware
3.-Factory Default, reinstall firmware
I can login into Telnet. I read someone fix create small filesystem, the questions is "Where is this small filesystem?
https://community.netgear.com/t5/New-ReadyNAS-Users-General/RN102-TFTP-REQ/m-p/1532495#M16020
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
