This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!



I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!

Upgrade 394 -> 427 failed

For "upgrading" from FreeNAS/NAS4Free Legacy to XigmaNAS and upgrading XigmaNAS to newer builds.
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
Alyce
NewUser
NewUser
Posts: 10
Joined: 02 Nov 2012 07:17
Status: Offline

Upgrade 394 -> 427 failed

Post by Alyce »

Hello.
I am trying upgrade through web from 394 to 427 and get error "Image upload failed (out of memory?)"
Size of var/tmp/ftmp is 175303 KB
May be too small for new firmware?
How to increase it?
How to upgrade nas4Free?

User avatar
alexey123
Moderator
Moderator
Posts: 1469
Joined: 19 Aug 2012 08:22
Location: Israel, Karmiel
Contact:
Status: Offline

Re: Upgrade 394 -> 427 failed

Post by alexey123 »

Alyce wrote:Hello.
I am trying upgrade through web from 394 to 427 and get error "Image upload failed (out of memory?)"
How to upgrade nas4Free?
You have embedded version. You want backup config, and make fresh install. After install restore config
Home12.1.0.4 - Ingva (revision 7091)/ x64-embedded on AMD A8-7600 Radeon R7 A88XM-PLUS/ 16G RAM / UPS Ippon Back Power Pro 600
Lab 12.1.0.4 - Ingva (revision 7091) /x64-embedded on Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz / H61M-DS2 / 4G RAM / UPS Ippon Back Power Pro 600

Alyce
NewUser
NewUser
Posts: 10
Joined: 02 Nov 2012 07:17
Status: Offline

Re: Upgrade 394 -> 427 failed

Post by Alyce »

Hm. That not good.
This comp does not have monitor and kyeboard.
But if there is no other way...
Thanks.

User avatar
alexey123
Moderator
Moderator
Posts: 1469
Joined: 19 Aug 2012 08:22
Location: Israel, Karmiel
Contact:
Status: Offline

Re: Upgrade 394 -> 427 failed

Post by alexey123 »

Alyce wrote: But if there is no other way...
Thanks.
Why? You have embedded - backup config, write it into compact flash directly, boot from it, connect to webgui on 192.198.1.250 ( if you have another network- temporary replace ip adress for your pc).
restore config and reboot. When your nas make reboot - restore your PC ip adress. No need monitor :D
If you want hardwork - see my post
Home12.1.0.4 - Ingva (revision 7091)/ x64-embedded on AMD A8-7600 Radeon R7 A88XM-PLUS/ 16G RAM / UPS Ippon Back Power Pro 600
Lab 12.1.0.4 - Ingva (revision 7091) /x64-embedded on Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz / H61M-DS2 / 4G RAM / UPS Ippon Back Power Pro 600

User avatar
daoyama
Developer
Developer
Posts: 394
Joined: 25 Aug 2012 09:28
Location: Japan
Status: Offline

Re: Upgrade 394 -> 427 failed

Post by daoyama »

Alyce wrote:Hello.
I am trying upgrade through web from 394 to 427 and get error "Image upload failed (out of memory?)"
Size of var/tmp/ftmp is 175303 KB
May be too small for new firmware?
How to increase it?
How to upgrade nas4Free?
If you have not enough memory (probably continuous free region), you may fail to use /var/tmp/ftmp.
Also /var/tmp must have correct permission.
Work around is reboot the server, then upgrade immediately.

Daisuke Aoyama
NAS4Free 10.2.0.2.2115 (x64-embedded), 10.2.0.2.2258 (arm), 10.2.0.2.2258(dom0)
GIGABYTE 5YASV-RH, Celeron E3400 (Dual 2.6GHz), ECC 8GB, Intel ET/CT/82566DM (on-board), ZFS mirror (2TBx2)
ASRock E350M1/USB3, 16GB, Realtek 8111E (on-board), ZFS mirror (2TBx2)
MSI MS-9666, Core i7-860(Quad 2.8GHz/HT), 32GB, Mellanox ConnectX-2 EN/Intel 82578DM (on-board), ZFS mirror (3TBx2+L2ARC/ZIL:SSD128GB)
Develop/test environment:
VirtualBox 512MB VM, ESXi 512MB-8GB VM, Raspberry Pi, Pi2, ODROID-C1

kernow
experienced User
experienced User
Posts: 92
Joined: 23 Jun 2012 01:28
Status: Offline

Re: Upgrade 394 -> 427 failed

Post by kernow »

alexey123 wrote:
Alyce wrote: But if there is no other way...
Thanks.
Why? You have embedded - backup config, write it into compact flash directly, boot from it, connect to webgui on 192.198.1.250 ( if you have another network- temporary replace ip adress for your pc).
restore config and reboot. When your nas make reboot - restore your PC ip adress. No need monitor :D
If you want hardwork - see my post
Why would you do it this way? There's absolutely no need to. Just do what daoyama said, reboot it once, upgrade, done.
HP Microserver N36L / 6GB ECC RAM / 2 x 2TB WD20EARS, N4F9.1.x

mc51
Starter
Starter
Posts: 17
Joined: 04 Dec 2016 19:22
Status: Offline

Re: Upgrade 394 -> 427 failed

Post by mc51 »

I have the same problem as well.

Is it suitable to "upgrade" from embedded to "full"?
What about the config restore in this case?#

Thx a lot!

by mc

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4865
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: Upgrade 394 -> 427 failed

Post by raulfg3 »

mc51 wrote:I have the same problem as well.

Is it suitable to "upgrade" from embedded to "full"?
What about the config restore in this case?#

Thx a lot!

by mc
yes is posible ( not recomended unless you know what are doing).

Config is the same for embeded & full, so restore is always possible.

Need to do a new install is normally because a resize of boot slice on boot medium, and normally only one time at year or so on.
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)

Wiki
Last changes

HP T510

Post Reply

Return to “Upgrade XigmaNAS”