Go Back   Pro/Forums > ProCooling Technical Discussions > Snap Server / NAS / Storage Technical Goodies
Password
Register FAQ Members List Calendar Chat

Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides

Reply
Thread Tools
Unread 03-30-2007, 07:24 PM   #1
MaddMatt
Registered User
 
MaddMatt's Avatar
 
Join Date: Dec 2006
Location: Houston, Texas
Posts: 65
Default Snap 4100 issues;

Snap 4100 issues;

I had a psu blow so I swapped it out with a tested psu from work, now it does strange things;

When I start it up it comes up on the Language page asking me to select English US, then after I select that and hit ok it says “cannot save the language to the server”.

It will not load any hard drives at all, I have tried a few different drives with no success.

When I try to upgrade the OS it opens a completely white browser page and gives me a message saying something like “request entity too large”.

On an older version of snap assist it gives me a regular Snap4100 Icon and allows me to open a web browser.

On n newer version of snap assist it gives me an “Unknown Server” icon (Snap2000 Icon gray in color with a question mark through it) but still allows me to open a web browser.

I have checked the post Attention All 4100 owners ( http://forums.procooling.com/vbb/showthread.php?t=13825 ) and it is the 003 version and the modification/repair’s have been done.

I have reset it three times and still the issue persist…

Does anyone know what this means and what debug commands should I run to get the logs?

Any help would be greatly appreciated
MaddMatt is offline   Reply With Quote
Unread 03-30-2007, 07:34 PM   #2
MaddMatt
Registered User
 
MaddMatt's Avatar
 
Join Date: Dec 2006
Location: Houston, Texas
Posts: 65
Default Re: Snap 4100 issues;

The output from running an "info log T" on config/debug


Command

03/31/2007 11:44:44 Command: info log T

Requested: Log=Temporary, Boot=N/A Direction=Fwd Types=All Source=All

03/31/2007 11:11:18 5 S SYS | System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 5
03/31/2007 11:11:18 5 D SYS | Executable built by KEVIN
03/31/2007 11:11:18 5 D SYS | Hardware platform:2.2.1 Model:2 (256 MBytes) S/N:550929
03/31/2007 11:11:18 5 D SYS | ETH: Reset- Eaddr set to 00 C0 B6 08 68 11
03/31/2007 11:11:18 5 D SYS | Update IP...
03/31/2007 11:11:18 5 I NET | INIT: Setting IP address to 192.168.0.84
03/31/2007 11:11:18 5 D SYS | Update IP...
03/31/2007 11:11:18 5 D SYS | Initial file system BIO cache size is 26838528 bytes, 3232 buffers
03/31/2007 11:11:18 5 D SYS | DISK: Initial ARBs: 3232 Memory: 530048
03/31/2007 11:11:18 5 D SYS | Code Page set to 437
03/31/2007 11:11:19 5 D SYS | QDL System is ENABLED
03/31/2007 11:11:19 5 D SYS | Disk cache flush enabled
03/31/2007 11:11:19 5 D SYS | SNMP agent enabled for ReadWrite.
03/31/2007 11:11:19 5 D SYS | SNTP disabled.
03/31/2007 11:11:19 5 D SYS | AFP: not started
03/31/2007 11:11:19 5 D SYS | 'FTPD' started.
03/31/2007 11:11:19 5 D SYS | Update WorkGroup...
03/31/2007 11:12:08 5 D SYS | ide_BaseDriverEntry: Ready Error at start.
03/31/2007 11:12:08 5 D SYS | ide_BaseDriverEntry: Ready Failed
03/31/2007 11:12:38 5 D SYS | ide_BaseDriverEntry: Ready Error at start.
03/31/2007 11:12:38 5 D SYS | ide_BaseDriverEntry: Ready Failed
03/31/2007 11:13:08 5 D SYS | ide_BaseDriverEntry: Ready Error at start.
03/31/2007 11:13:08 5 D SYS | ide_BaseDriverEntry: Ready Failed
03/31/2007 11:13:08 5 D SYS | Intf: 0, dev: 0: Failed to find drive.
03/31/2007 11:13:08 5 D SYS | Intf: 1, dev: 0: Failed to find drive.
03/31/2007 11:13:08 5 D SYS | Intf: 2, dev: 0: Failed to find drive.
03/31/2007 11:13:08 5 D SYS | Intf: 3, dev: 0: Failed to find drive.
03/31/2007 11:13:08 5 D SYS | NFS: The hash table has been initialized.
03/31/2007 11:13:08 5 D SYS | NFS: the NFSID <--->FDBID cache has been initialised.
03/31/2007 11:15:36 5 D SMB | SMB : Becoming master browser for X
03/31/2007 11:31:27 5 D SYS | DANGER: Unable to initialize pseudoflash!
03/31/2007 11:31:27 5 D SYS | Pseudoflash partition not found. Return from read -2.
03/31/2007 11:31:45 5 I SYS | HTTP : Upload file begin. Parameters Func=OSUpdateRecv&OSUpdateFilename=snap_sys.sup
03/31/2007 11:31:45 5 I SYS | HTTP : Upload file encountered error 413, parameters Func=OSUpdateRecv&OSUpdateFilename=snap_sys.sup&Up loadedFilename=

eventLogGetRecord() printed 34 records at 03/31/2007 11:44:44

------------
Command executed without error.
MaddMatt is offline   Reply With Quote
Unread 03-30-2007, 07:43 PM   #3
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap 4100 issues;

The info it is giving you is like the BIOS settings got reset. Check to see if the battery 2032 failed.

What platformbytes and model number does it think it is?
__________________
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
blue68f100 is offline   Reply With Quote
Unread 03-30-2007, 07:59 PM   #4
MaddMatt
Registered User
 
MaddMatt's Avatar
 
Join Date: Dec 2006
Location: Houston, Texas
Posts: 65
Default Re: Snap 4100 issues;

Where do I find out what the "platformbytes and model number" it thinks it is?
MaddMatt is offline   Reply With Quote
Unread 03-30-2007, 08:08 PM   #5
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap 4100 issues;

The log show the platformbytes.

to find them from debug enter:
bios platformbytes
bios model
__________________
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
blue68f100 is offline   Reply With Quote
Unread 03-30-2007, 09:18 PM   #6
MaddMatt
Registered User
 
MaddMatt's Avatar
 
Join Date: Dec 2006
Location: Houston, Texas
Posts: 65
Default Re: Snap 4100 issues;

Hi Blue

Here they are;

Bios platformbytes


03/31/2007 12:26:06 Command: bios platformbytes

Platform Bytes are "2.2.1"

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


Bios model

03/31/2007 12:25:31 Command: bios model

Model Byte currently is:
0 - 2 drive IDE: "Minnie"
1 - 1 drive IDE: "Mortie"
==> 2 - 4 drive IDE: "Laser"
3 - 12 drive IDE: "Clipper"

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

Last edited by MaddMatt; 03-30-2007 at 11:05 PM.
MaddMatt is offline   Reply With Quote
Unread 03-31-2007, 11:37 AM   #7
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap 4100 issues;

The bios settings are correct.

A couple of things to try. Check to see if the 2032 battery is good.

1. Reload the OS, which I think you tried and failed.

2. Remove the drives (all) and do a quick zero of the MBR. This will remove all data from the drives. Make sure all drives are set to master. Then reinstall and see if it can setup the clean drives. If it can not do this we will need to work on reload the bios with 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
blue68f100 is offline   Reply With Quote
Unread 04-02-2007, 06:56 AM   #8
MaddMatt
Registered User
 
MaddMatt's Avatar
 
Join Date: Dec 2006
Location: Houston, Texas
Posts: 65
Default Re: Snap 4100 issues;

Hi Blue,

I zapped the drives and booted it up, it went into an initialization mode; Double flashes from the System led and a completely solid Disk led but still the disks would not show even though the English US issue did not reoccur.

So I tried rebooting it after having a look at the logs and it seemed to go back into the initialization mode as described above so I am a little confused.

Tomorrow night I all restart it and wait for it to come back up which takes about 60-90 minutes then if it seems to start up ok I will see if it will let me do the reinstall of the OS unless you feel it is not worth it?

Or should we look at working on a reload the bios with the OS?
MaddMatt is offline   Reply With Quote
Unread 04-05-2007, 03:53 PM   #9
MaddMatt
Registered User
 
MaddMatt's Avatar
 
Join Date: Dec 2006
Location: Houston, Texas
Posts: 65
Default Re: Snap 4100 issues;

Hi,

It has taken a while but I can tell you that I am at least now getting some consistency.

I zapped the drives and I replaced the battery with a brand spanker just to make sure…

Now when I start up the Snap I wait for it to come back up (takes about 60-90 minutes) when it finally shows up in Assist it appears as a new un-configured unit –Yellow- as it also does on the older Assist I use to double check (before on the older Assist it was showing as an “Unknown Server” icon)

Here’s where we get too; I run the utility to assign it an IP address and it comes back to me that it cannot assign it, when I also tried to leave it as DHCP it came back with the message that it could not ping the server and that’s about all I can get from it.

I have tried to assign it an IP address 5 times and the DHCP 3 times but no luck

What you think?

Thanks in advance!
MaddMatt is offline   Reply With Quote
Unread 04-05-2007, 04:49 PM   #10
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap 4100 issues;

Sounds like you have a bad system board.
__________________
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
blue68f100 is offline   Reply With Quote
Unread 04-05-2007, 07:39 PM   #11
MaddMatt
Registered User
 
MaddMatt's Avatar
 
Join Date: Dec 2006
Location: Houston, Texas
Posts: 65
Default Re: Snap 4100 issues;

I was hoping you wouldn’t say that... so basically there is nothing that can be done for it apart from a replacement MB?

I'd guess it got zapped when that PSU died
MaddMatt is offline   Reply With Quote
Reply


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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 08:19 PM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
(C) 2005 ProCooling.com
If we in some way offend you, insult you or your people, screw your mom, beat up your dad, or poop on your porch... we're sorry... we were probably really drunk...
Oh and dont steal our content bitches! Don't give us a reason to pee in your open car window this summer...