Readynas Pro -NOT updating, Pioneer =OK

[emerson8]

Hi, I got 2 readynas 6 bay devices.
1 pro pioneer6 with 6x1tb
and
1 pro6 with 6 x 3 tb drives.

Both been working ok. But applying the latest 2 different builds of 4.2.20 only works on the Pro Pioneer box.
( tested with both build 23 and now build 28 )

Updated Pro pioneer, prompted to reboot = everything OK.

Updating the Pro, uploading the file, then "to fast" get a message update complete, please reboot.
Rebooting do NOT work. I previously tested by doing a hard power-off and then power-on again. After that, no system log, etc.

But, scenario is still the same, The pro6 box simply refuses to do anything with the last 2 updates. What I found however
is that when the update doesn't "take" and no reboot can be achieved, I instead re-install the enable SSH again which prompts for a reboot
and DO reboot the unit. Still, the firmware do not update.

Edit; Addition; Both units (when I started) 4.2.20 - t19

[beisser1]

this may be a case of full root. either all space is taken or all inodes are used up.

techsupport should be able to check which is the case.

[emerson8]

Actually, the Pro unit is more or less brand new. Updating it was the first thing I did, so it might be true....
Worth noting; both the pro and the pro pioneer was previously "non-beta" versions initially so both succeeded in going from
previous version to the T19 build.

[ReadySECURE]

I recommend contacting support. If the units are new see if after a factory default you can apply the update.

[emerson8]

Doing a df -h to check space, this is reported;
dev# df -h

Filesystem Size Used Avail Use% Mounted on
/dev/md0 4.0G 3.8G 16M 100% /

tmpfs 16K 0 16K 0% /USB

/dev/c/c 14T 6.5T 7.2T 48% /c

/c/Media2 14T 6.5T 7.2T 48% /home/ftp/Media2

df -BG

Filesystem 1G-blocks Used Available Use% Mounted on
/dev/md0 4G 4G 1G 100% /

tmpfs 1G 0G 1G 0% /USB

/dev/c/c 13885G 6598G 7288G 48% /c

/c/Media2 13885G 6598G 7288G 48% /home/ftp/Media2

[emerson8]

Seems there was some "admin download something something...zip" that was 3.5 GB in /tmp
I guess that's NOT by design!

- Removed that file in /tmp, rebooted and retried the fw update = OK again !


Case closed

[mdgm-ntgr]

What was that file called? Did you have any add-ons installed?

[emerson8]

No add-ons besides SSH access, it was called something like admindownload??????.zip