NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Keligh
May 24, 2017Tutor
"Err: could not properly extract"
Hi,
When I logged in the admin frontview interface, I was signaled an available update to 6.7.3 (currently running in 6.7.1).
I accepted, download finished and it proposed a reboot.
I accepted, NAS rebooted, Update began ... and after a while a message "Err: could not properly extract" appeared and it tried to "restart" (that's what was shown on LCD screen). But it tried and tried ... and never succeeded.
What would be the best course of action from here ?
For USB Boot Recovery one would need to rename the standard OS6 firmware to RAIDiator-x86-something and put it on the 4.2.x USB Boot Recovery key. USB Boot Recovery with 6.7.3 would not have helped here.
It looks like your volume is mounted read-only. Is your backup up to date?
Edit:
USB Boot Recovery with ReadyNAS OS 6.7.4 which is now available! would have helped thoguh with legacy systems there is the risk that a side effect can be run into when you do USB Boot Recovery that requires a manual fix. If your system has already been fixed I would still suggest updating to 6.7.4 normally using the web admin GUI.
19 Replies
Replies have been turned off for this discussion
- jak0lantashMentor
If you want to check the logs since the last boot (download the logs from the GUI), look at systemd-journal.log and search for the last instance of "jenkins@blocks". Search for clues from there.
You may also check in initrd.log if there is any error related to the firmware update.
- KelighTutor
NAS cannot boot properly anymore (since at every boot, it begins with "updating FW" etc etc ... :(
How can I check those logs ? tech support mode ?
- jak0lantashMentor
OK.
Unless you know how to use Tech Support mode, it's not something that's self explanatory and can be destructive if you try random things.
You could try to boot in Volume Read Only mode via the Boot Menu.
If still no luck, you could try an OS Reinstall via the Boot Menu.
- KelighTutor
It seems Netgear guy finished his work, NAS rebooted and everything is fine (and in 6.7.3)
However, I don't know yet what he did or what was the problem.
But it's solved :).
- mdgm-ntgrNETGEAR Employee Retired
For USB Boot Recovery one would need to rename the standard OS6 firmware to RAIDiator-x86-something and put it on the 4.2.x USB Boot Recovery key. USB Boot Recovery with 6.7.3 would not have helped here.
It looks like your volume is mounted read-only. Is your backup up to date?
Edit:
USB Boot Recovery with ReadyNAS OS 6.7.4 which is now available! would have helped thoguh with legacy systems there is the risk that a side effect can be run into when you do USB Boot Recovery that requires a manual fix. If your system has already been fixed I would still suggest updating to 6.7.4 normally using the web admin GUI.- KelighTutor
True, I was too enthousiastic before. No, my backup is not fully up to date (mainly because I just became aware that the built in amazon drive tool didn't do his job properly) so I was in the process on completing it (yeah I know, doing an upgrade with an incomplete backup, that was a stupid move)
I didn't see that the volume was readl only at the time (to my defense, It was 2am :) ). Was it made that way when you did the repair or is it a unexpected side effect ? It's shown a read/write in frontview.
Also it seems a balance started, but stuck at 0%.
Should I order a restart from frontview ? Or just complete my backup while I can ?
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!