NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Upgrade 4.2.23 fails on ReadyNAS Pro Pioneer Edition
Hiya,
Was doing an upgrade on my ReadyNas Pro Pioneer edition from 4.2.22 to 4.2.23. I downloaded the zip file, and extracted the .bin file and used the local upgrade option (RAIDiator-x86-4.2.23), but the frontview claims "update file is not valid for this architecture", which is silly. :)
Looking into the frontview error log i see:
and sure enough, there's no "html/enterprise" directory in that location:
Is the firmware upgrade checking for some sort of enterprise option that I dont have installed on my box? The Pro Pioner is listed on the release notes page..
Thanks for any pointers.
-Mark
Was doing an upgrade on my ReadyNas Pro Pioneer edition from 4.2.22 to 4.2.23. I downloaded the zip file, and extracted the .bin file and used the local upgrade option (RAIDiator-x86-4.2.23), but the frontview claims "update file is not valid for this architecture", which is silly. :)
Looking into the frontview error log i see:
[Wed May 29 01:32:11 2013] [error] [client 217.148.94.26] File does not exist: /frontview/ui/resource/html/enterprise
[Wed May 29 22:06:17 2013] [error] [client 192.168.2.55] malformed header from script. Bad header=Couldn't open /tmp/upload_file: get_handler, referer: https://192.168.2.15/admin/
and sure enough, there's no "html/enterprise" directory in that location:
$> /frontview/ui/resource/html# ll
total 232
drwx------ 2 admin admin 4096 2012-10-12 23:08 addons
drwx------ 2 admin admin 4096 2012-10-12 23:08 backup
-rw------- 1 admin admin 115 2012-09-05 00:33 blank.html
-rw------- 1 admin admin 76397 2012-09-05 00:33 dialog.xml
-rw------- 1 admin admin 3638 2012-09-05 00:33 favicon.ico
-rw------- 1 admin admin 32937 2012-09-05 00:33 index.html
drwx------ 2 admin admin 4096 2012-10-12 23:08 messages
drwx------ 2 admin admin 4096 2012-10-12 23:08 network
-rw------- 1 admin admin 21298 2012-09-05 00:33 password_recovery.html
drwx------ 2 admin admin 4096 2012-10-12 23:08 printers
-rw------- 1 admin admin 115 2012-09-05 00:33 redirect.html
drwx------ 2 admin admin 4096 2012-10-12 23:08 security
drwx------ 2 admin admin 4096 2012-10-12 23:08 services
drwx------ 2 admin admin 4096 2012-10-12 23:08 shares
drwx------ 2 admin admin 4096 2012-10-12 23:08 status
drwx------ 2 admin admin 4096 2012-10-12 23:08 system
-rwx------ 1 admin admin 26891 2012-09-05 00:33 user.pl
drwx------ 2 admin admin 4096 2012-10-12 23:08 volumes
drwx------ 2 admin admin 4096 2012-10-12 23:08 welcome
drwx------ 2 admin admin 4096 2012-10-12 23:08 wizard
Is the firmware upgrade checking for some sort of enterprise option that I dont have installed on my box? The Pro Pioner is listed on the release notes page..
Thanks for any pointers.
-Mark
4 Replies
Replies have been turned off for this discussion
- Is the IP asking for ./enterprise even your IP? Do you have HTTPS open to the Internet?
What is the output of these two commands?
# df -h
# ls -ld /tmp chirpa wrote: Is the IP asking for ./enterprise even your IP? Do you have HTTPS open to the Internet?
didn't quite follow you there (IP is installer package?) Anyway, i do not have HTTPS open to the internet, the NAS is off on a subnet inaccessible from offsite.chirpa wrote:
What is the output of these two commands?
# df -h
# ls -ld /tmp
here you go:
# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/md0 4.3G 960M 3.2G 24% /
tmpfs 17k 0 17k 0% /USB
/dev/c/c 15T 15T 137G 100% /c
Ouch, i'm running close to the line, percentage wise, tho its hard to consider 137G as "small" space. too many flac's and raw video projects.. :(
and
# ls -ld /tmp
drwxrwxrwt 3 root root 4096 2013-05-29 23:09 /tmp
And now the good news. I removed all the cruft in my /tmp dir (rm -rf /tmp/*) and rebooted. Tried the update again, and it took this time.
I'm not entirely sure why that might have been needed. I'm not sure if was the reboot or the clearing misc crap out of /tmp/
/var/logs/frontview is clear now and it looks like im running 4.2.23 now. yay!
Thanks for the suggestion about where to twiddle.
-Mark- The reboot probably cleared /tmp on its own.
- Just hit the same problem upgrading my Ultra 4 from 4.2.21 to 4.2.23. Clearing /tmp was enough to fix the problem for me, the error message is definitely misleading.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
