Snap Server 4000 that thinks it's a 2000 - Page 2

blue68f100 · 03-21-2007, 06:55 AM

Yes, all of these seting reside in the bios. Which happens to be the same flashram used for the OS.

I would concentrate on the bios setting, platformbytes, serial_no, and model. These are the only ones that will have an impact.

It took some playing before I got the 1000 to change. It is sensitive to sequences. I know I had to do mine is sequence, with the platformbytes first, since the model rebooded the unit. But I had no info on the serial number being off.

If you get tired of messing with it and would like me to take a stab let me know.

What happen when you remove all of your HD and install one that is blank. Does if format and init the drive ok, installs the OS.

BobWadd · 03-22-2009, 08:36 AM

Hi,

Was this issue ever resolved? I am having the same problem on a newly acquired SS4000. I have tried all suggestions in this thread with no luck.

Thanks, Bob

blue68f100 · 03-23-2009, 09:27 AM

The SN can be changed and needs to be if it's far off. Snap uses some SN seq to determine which platformbyte to use.....

BobWadd · 03-23-2009, 12:08 PM

Quote:

Originally Posted by blue68f100

The SN can be changed and needs to be if it's far off.

I can change the serial number to the correct one. I have tried everything in this thread. Like to OP I am receiving the "Failsafe Bios not found" message. I can change the serial number, hardware version and platform bytes but they do not stick. Any further suggestions?

Thanks, Bob

blue68f100 · 03-23-2009, 07:16 PM

You must first unlock the bios before any changes will be saved. Once the settings changed lock the bios back.

BobWadd · 03-24-2009, 02:06 PM

Quote:

Originally Posted by blue68f100

You must first unlock the bios before any changes will be saved. Once the settings changed lock the bios back.

This is what I have been doing. Settings are stored through a warm boot. But lost during a cold boot.

Boot log follows:

Quote:

================================================== ==================
03/24/2009 14:49:05 ERROR Ethernet driver : Checksum, signature or ethernet address is wrong. Defaulting E2-Image.
================================================== ==================

The previous message occurred in the following context within the system log:

03/24/2009 14:49:14 INFORMATION System Initialization : Initialization Complete! Memory to be released: 71771472 bytes.
03/24/2009 14:49:14 INFORMATION File System : Opened FDB for device 0x60000
03/24/2009 14:49:14 INFORMATION File System Check : partition is clean.
03/24/2009 14:49:14 INFORMATION File System Check : Executing fsck /dev/rraid0 /fix
03/24/2009 14:49:14 INFORMATION File System : Opened FDB for device 0x1000E
03/24/2009 14:49:12 INFORMATION File System Check : partition is clean.
03/24/2009 14:49:12 INFORMATION File System Check : Executing fsck /dev/ride1g /fix /fixfatal
03/24/2009 14:49:12 INFORMATION File System : Opened FDB for device 0x10006
03/24/2009 14:49:12 INFORMATION File System Check : partition is clean.
03/24/2009 14:49:12 INFORMATION File System Check : Executing fsck /dev/ride0g /fix /fixfatal
03/24/2009 14:49:05 INFORMATION INIT: Setting IP address to 192.168.1.108
03/24/2009 14:49:05 System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 7
03/24/2009 14:49:05 ERROR Ethernet driver : Checksum, signature or ethernet address is wrong. Defaulting E2-Image.
03/24/2009 14:49:05 WARNING Ethernet driver : Writing whole image.
03/24/2009 14:49:05 WARNING Ethernet driver : Changing platform bytes from 0.0.0 (0) to 0.0.0 (2).
03/24/2009 14:49:05 WARNING Ethernet driver : Changing model byte from 0x00 to 0x02.
03/24/2009 14:49:05 ERROR Ethernet driver : Checksum, signature or ethernet address is wrong. Defaulting E2-Image.
03/24/2009 14:49:05 ERROR Ethernet driver : Checksum, signature or ethernet address is wrong. Defaulting E2-Image.
03/24/2009 14:49:05 WARNING Ethernet driver : Writing whole image.
03/24/2009 14:49:05 WARNING Ethernet driver : Changing platform bytes from 0.0.0 (0) to 2.0.1 (0).
03/24/2009 14:49:05 ERROR Ethernet driver : Checksum, signature or ethernet address is wrong. Defaulting E2-Image.

Thanks again, Bob

blue68f100 · 03-24-2009, 02:44 PM

I have had one unit that gave me fits. I was eventually able to get to take, but I do not recall what I did. It's been way to long....

BobWadd · 03-26-2009, 07:31 PM

Thought I had the issue fixed. Made it through 4 cold boots last night. I turned the unit off before going to bed. Powered it up this this morning and all settings where intact, powered down. Just powered it up again this night and it's back to thinking it's a SS 2000.

Back to the drawing board, Bob

Edit: Just warm booted it and --> PRESTO !!! it's a 4000 again ?!?!?!?!?!?!?!?

BobWadd · 04-13-2009, 07:10 PM

Update . . .

Platformbytes and Model are now correct! Unfortunately Serial Number occasionally reverts to - 16999. Any further suggestions? Anyone . . .

Bob

blue68f100 · 04-14-2009, 08:00 AM

Try reloading the OS now that it thinks it a 4000 again.

BobWadd · 04-16-2009, 05:06 PM

Reloaded the OS. Now it thinks it's a 2000 again. Back to square one!!!

Bob

BobWadd · 04-28-2009, 06:22 PM

Update:

Platformbytes and Model are once again correct for a 4000. Unfortunately Serial Number still occasionally reverts to - 16999.

Bob

otoc · 06-01-2009, 11:22 AM

Stupid question, but has the 2032 battery been replaced on these model 4000s?

I've got the same board in my 2000s and I've gone back and forth setting it up as either a 2 drive 2000 or a 4 drive 4000 using the bios unlock/lock model setting tricks.

That's not to say a battery will cure the issue, just that documentation on what it saves and the fact that it hasn't been mentioned warrants a try considering the small cost.

BobWadd · 06-04-2009, 05:39 AM

Quote:

Originally Posted by otoc

Stupid question, but has the 2032 battery been replaced on these model 4000s?

I have replaced the battery. Up until yesterday I thought the unit was fixed. I shut my Snap Servers down to rearrange my office and when I rebooted I was back to the same problem!!!

Bob

zutt · 12-19-2009, 10:02 AM

Hello
i am experiencing the same thing on my 4000 ( as decribed above)
was this solved somehow ?

bitor · 12-19-2009, 12:07 PM

Dave, so all they need is a bios file program from the factory? How would one, having a good raw bios file, upload to the said bad bios chip via FLUP command?
Is it possible for anybody to receive a good bios file from there Snap4000 with FLUP ?

bitor

Quote:

Originally Posted by blue68f100

If you had the BIOS file you could. But there presents the problem, do you have the BIOS files?

You have the proper OS loaded, just all of the flags are off.

Some of the early early OS Update files (v2) had the MOAI files but none that I have seen included the BIOS files. Unless it was hidden on the factory cd shipped with unit. But none that I have seen. All of the sup files are in Intel HEX code. So the code is loaded to specific flashram addresses. I do not have a program that extracts the code from a working unit, nor have I heard of one.

The BIOS FLUP (5 blinks) mode is what is used when you use assist to load the OS. Snapup is like a early Assist program.

It took me over a year to figure how to reset a 1000 that was set to a 2000 model, would not boot at all.

blue68f100 · 12-19-2009, 01:41 PM

The bias is part of the OS in these units. The platformbyte tell the updater as to what needs to be installed. If the platfrombyte was not correct during os update, you my have got the wrong modules loaded for your hardware.

bitor · 12-19-2009, 07:35 PM

I see, Dave, but I thought they released a solo bios update years ago for the SnapOS models. I think it was bios version 2.

bitor

blue68f100 · 12-20-2009, 01:43 PM

The only single bios update I know of was for the v1 2000. And it was required so OS v2 could be loaded.

bitor · 12-21-2009, 01:31 AM

Dave, I'll have to check my docs to see which Snap model(s) the solo bios updated. But I would guess that, like the SnapOS, they would make one file for all Snap models at that time.

bitor

Quote:

Originally Posted by blue68f100

The only single bios update I know of was for the v1 2000. And it was required so OS v2 could be loaded.

03-21-2007, 06:55 AM	#26
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap Server 4000 that thinks it's a 2000 Yes, all of these seting reside in the bios. Which happens to be the same flashram used for the OS. I would concentrate on the bios setting, platformbytes, serial_no, and model. These are the only ones that will have an impact. It took some playing before I got the 1000 to change. It is sensitive to sequences. I know I had to do mine is sequence, with the platformbytes first, since the model rebooded the unit. But I had no info on the serial number being off. If you get tired of messing with it and would like me to take a stab let me know. What happen when you remove all of your HD and install one that is blank. Does if format and init the drive ok, installs the OS. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

03-22-2009, 08:36 AM	#27
BobWadd Cooling Neophyte Join Date: Jul 2005 Location: Central Florida, USA Posts: 18	Re: Snap Server 4000 that thinks it's a 2000 Hi, Was this issue ever resolved? I am having the same problem on a newly acquired SS4000. I have tried all suggestions in this thread with no luck. Thanks, Bob

03-23-2009, 09:27 AM	#28
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap Server 4000 that thinks it's a 2000 The SN can be changed and needs to be if it's far off. Snap uses some SN seq to determine which platformbyte to use..... __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

03-23-2009, 07:16 PM	#30
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap Server 4000 that thinks it's a 2000 You must first unlock the bios before any changes will be saved. Once the settings changed lock the bios back. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

03-24-2009, 02:44 PM	#32
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap Server 4000 that thinks it's a 2000 I have had one unit that gave me fits. I was eventually able to get to take, but I do not recall what I did. It's been way to long.... __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

03-26-2009, 07:31 PM	#33
BobWadd Cooling Neophyte Join Date: Jul 2005 Location: Central Florida, USA Posts: 18	Re: Snap Server 4000 that thinks it's a 2000 Thought I had the issue fixed. Made it through 4 cold boots last night. I turned the unit off before going to bed. Powered it up this this morning and all settings where intact, powered down. Just powered it up again this night and it's back to thinking it's a SS 2000. Back to the drawing board, Bob Edit: Just warm booted it and --> PRESTO !!! it's a 4000 again ?!?!?!?!?!?!?!?

04-13-2009, 07:10 PM	#34
BobWadd Cooling Neophyte Join Date: Jul 2005 Location: Central Florida, USA Posts: 18	Re: Snap Server 4000 that thinks it's a 2000 Update . . . Platformbytes and Model are now correct! Unfortunately Serial Number occasionally reverts to - 16999. Any further suggestions? Anyone . . . Bob

04-14-2009, 08:00 AM	#35
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap Server 4000 that thinks it's a 2000 Try reloading the OS now that it thinks it a 4000 again. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

04-16-2009, 05:06 PM	#36
BobWadd Cooling Neophyte Join Date: Jul 2005 Location: Central Florida, USA Posts: 18	Re: Snap Server 4000 that thinks it's a 2000 Reloaded the OS. Now it thinks it's a 2000 again. Back to square one!!! Bob

04-28-2009, 06:22 PM	#37
BobWadd Cooling Neophyte Join Date: Jul 2005 Location: Central Florida, USA Posts: 18	Re: Snap Server 4000 that thinks it's a 2000 Update: Platformbytes and Model are once again correct for a 4000. Unfortunately Serial Number still occasionally reverts to - 16999. Bob

06-01-2009, 11:22 AM	#38
otoc Cooling Neophyte Join Date: Apr 2003 Location: Massachusetts Posts: 44	Re: Snap Server 4000 that thinks it's a 2000 Stupid question, but has the 2032 battery been replaced on these model 4000s? I've got the same board in my 2000s and I've gone back and forth setting it up as either a 2 drive 2000 or a 4 drive 4000 using the bios unlock/lock model setting tricks. That's not to say a battery will cure the issue, just that documentation on what it saves and the fact that it hasn't been mentioned warrants a try considering the small cost.

12-19-2009, 10:02 AM	#40
zutt Registered User Join Date: Jan 2004 Location: Hilversum, The Netherlands Posts: 3	Re: Snap Server 4000 that thinks it's a 2000 Hello i am experiencing the same thing on my 4000 ( as decribed above) was this solved somehow ?

12-19-2009, 01:41 PM	#42
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap Server 4000 that thinks it's a 2000 The bias is part of the OS in these units. The platformbyte tell the updater as to what needs to be installed. If the platfrombyte was not correct during os update, you my have got the wrong modules loaded for your hardware. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

12-19-2009, 07:35 PM	#43
bitor Cooling Savant Join Date: Mar 2006 Location: USA Posts: 257	Re: Snap Server 4000 that thinks it's a 2000 I see, Dave, but I thought they released a solo bios update years ago for the SnapOS models. I think it was bios version 2. bitor

12-20-2009, 01:43 PM	#44
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap Server 4000 that thinks it's a 2000 The only single bios update I know of was for the v1 2000. And it was required so OS v2 could be loaded. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)