Forum Discussion

Aspirant

Oct 16, 2017

Solved

Firmware update brick

I wish I had looked at these forums before doing the update to my Readynas. I got a prompt to update to 6.8.1 firmware when I logged into the admin console today. I applied the update and now the d...

ReadyNAS OS 6 on Legacy models

Arafel
Oct 17, 2017
Thanks to mdgm for all of his help! It turns out that the Readynas had no issues. A port on my netgear switched seems to have died at the exact time of the reboot to do the new firmware. Given the timing I was chasing the wrong flag.

Arafel

Aspirant

Oct 17, 2017

I was running 6.8.0 and went to 6.8.1 with the firmware update. The only app I had running on it was transmission bit torrent client.

I have a partal backup but not a complete backup. I currently have pulled one of the drives since I was running in Raid 1. I figured whatever I try would only possibly corrupt one disk and the other copy I could attempt a recovery through other means.

Last night I did boot the readynas up into tech support mode due to a private message. With Raidar it couldn't detect the device. After plugging a second network cable in to the other ethernet port I was able to detect it. Raidar showed the 6.8.1 firmware on there. I noticed that the main network port was pulling an invalid IP addresss.

StephenB

Guru - Experienced User

Oct 17, 2017

Did you try a regular boot with only the secondary ethernet port connected?

mdgm-ntgr
NETGEAR Employee Retired
Oct 17, 2017
If there was no network connectivity when booted into tech support mode and you then fixed it then you'd need to power off and boot back into that mode again to get tech support mode setup properly.
- Arafel
  Aspirant
  Oct 17, 2017
  Yes when I initially booted it there was no connectivity. I have now rebooted it so hopefully its in tech support mode properly.
  - Arafel
    Aspirant
    Oct 17, 2017
    Thanks to mdgm for all of his help! It turns out that the Readynas had no issues. A port on my netgear switched seems to have died at the exact time of the reboot to do the new firmware. Given the timing I was chasing the wrong flag.