Snap Server 2000 rejecting upgrade

[wozzy_wombat]

I have a snap server 2000 running 3.4.803/2.052 Bios that rejects the sup file as being invalid. Strange as I've used it before on other 2000s and it worked fine. This happens from both Assist and the webpage config menu. I can't seem to find any difference in the bios setting between this one and another one I've successfully upgraded.

Any Ideas?

[blue68f100]

What version of the sup file are you tring to do.

V4.0.860 was an updater (not full), there is a complete version for users purchasing v4 from Adaptec.

[wozzy_wombat]

4.0.830 to be applied first. Even tried 3.4.805, and he does not like any of them. Serial # 36487, it's a Meridian one. I've found a lot of variability in the Meridian v2 models. The Quantum ones are easier to upgrade.

[blue68f100]

Post the results of "SnapAppliance Logo" on the admin page, on the unit your tring to upgrade. All of the Meridian Units I have seen are v1 Bios, 32 meg SIMMS memory.

If your using Vista (MEII) throw it out the door, will not work.

What version of Assist are you using to upgrade the Snap? v3 or v4
How are you putting the unit in FLUP mode?

If the "bios oem" is set it will give you the same error.

[wozzy_wombat]

Model Software Hardware Server # BIOS
2000 series 3.4.803 (US) 0.0.0 36487 2.0.252

I've upgraded similar 2000's without a problem before. It seems to be doing a checksum or something similar as from assist it says "sup file invalid" after communicating with the server. From the OS Upgrade option in the web gui, it uploads the sup file, and then rejects it.

Error log says this: OS Update : OS Update encountered error 101016. SUP file
From debug, the OEM option is not set but I tried it both ways and no joy.

Any ideas? This one has me stumped and I've done a few of these.

Thanks.

[blue68f100]

Check your PlatformBytes if this is not correct, to the hardware it will reject the OS. BIOS is showing 0.0.0 this is a platform identifier.

[wozzy_wombat]

How to I change the platform bytes? I think it should be 2.0.0, but doing the command "bios PlatformBytes 2.0.0" does not change the value, even with the bios unlocked. Some of my other 2000s report this value as 2.0.0., so I think that's why the sup file is being rejected. Thanks!

[blue68f100]

Yes, you are correct the PlatformBytes should be 2.0.0 . I have a table I have put together on Platformbytes and BIOS versions.

Try "bios platformbytes 2 0 0"

[wozzy_wombat]

That did it! Muchas Gracias!

Just in case anyone else has this problem, I did the following:

bios unlock
bios platformbytes 2 0 0 (syntax needs to be exact)

He then said platform bytes set to 2.0.0. The upgrade then proceeded normally.

[blue68f100]

Every bios version has a different PlatformByte. So you really need to know what the BIOS is.

Glad everything worked out.

[jkempthorne]

Hello, I have a similar problem. I have upgraded three other 2000s to the latest with no issues.

Please look at the Unlock and OEM commands below.

Here is the server information:

02/01/1980 14:52:32 Command: bios Version


Failsafe Bios not found

Bios stamp 2.0.282 Tue Mar 14 12:53:29 2000

Plat Bytes 2.0.0

Model Byte 0

02/01/1980 14:56:06 Command: bios Flags


Bios Boot Flags:

Auto Reboot is Enabled
Forced Broadcast mode is Disabled
Forced Promiscuous mode is Disabled
L1 Cache is Enabled
L2 Cache is Disabled

Enet Flags (0x3EED):

IDE Power off is by Sleep Command


02/01/1980 15:00:59 Command: bios Unlock

EEPROM is now ULOCKED for update

------------
Command executed without error.

02/01/1980 15:01:27 Command: bios OEM None

Pseudoflash does not exist, so this box cannnot be OEMed.

------------
Command returned with console error 1.

Thank you in advance,
Jim

[blue68f100]

What's your current version, and what are you upgrading to?

There is no need to go into debug for an OS upgrade.

[jkempthorne]

This Snap Server is a Dell 701N that is running version:

Model Software Hardware Server # BIOS
2000 series 3.4.790 (US) 2.0.0 53819 2.0.282

As shown above, I entered the debug commands and attempted the upgrade to 3.4.803 -- error Invalid.

Any thoughts?

Thank you,
Jim

[rpmurray]

edit: reread the above and realized you'd already tried this, so am deleting the reply.

[netmgr]

Ihave a similar problem with a 2200. Trying to upgrade to 4.0.860 from 3.4.805. Bios is 3.4.758 plat bytes is 2.0.4 and response through both assist and browser is invalid sup file. I was able to complete upgrades to virtual machine that accompanied the os. Any suggestions?

[blue68f100]

Originally Posted by jkempthorne

This Snap Server is a Dell 701N that is running version:

As shown above, I entered the debug commands and attempted the upgrade to 3.4.803 -- error Invalid.

Any thoughts?

Thank you,
Jim

Lets back up so I get my facts correct.

Dell 701N running Dell SnapOS or Snap OS?

If doing the switch to snap OS you need to Use Assist After change the OEM Flag. I do not recall the upgrade through the OS working.

Make the OEM change Re lock the BIOS and reboot an see if it took.

NetMGR: Do you have the full version of 4.0.860 or the updater. You require the full to upgrade from v3 the reason for the error.