Snap 4100 Question

[snappov]

Hello there--

We have a Snap 4100, running 4.0.860, hardware v. 2.2.1 BIOS v. 2.4.437

And we got this error Friday night:

F PANIC : Maximum yield time exceeded at $002BCE96
4/3/2009 7:44:07 PM

F Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 4/3/2009 7:44:07 PM

Is this from data corruption?
A problem with the RAID (RAID-5)?
A drive problem?

Device report is:

04/06/2009 11:54:52 Command: info devices

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22688 Private Mounted
Label:Private Contains system files only
Unique Id: 0x4D59ADA145291340 Mount: /priv Index: 12 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 120060416 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 22528 Private Mounted
Label:Private Contains system files only
Unique Id: 0x05203A59474C9919 Mount: /pri2 Index: 13 Order: 1
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 120060416 Fixed

Logical Device: 60000 Position: 1 RAID Size (KB): 357875928 Free (KB): 0 Public Unmounted
Label:RAID5 Large data protection disk
Unique Id: 0x533956316F7294EF Mount: /0 Index: 0 Order: 255
Partition: 10000 Physical: 10007 R 60000 Size (KB): 119291976 Starting Blk: 95927 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 120060416 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 119291976 Starting Blk: 95927 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 120060416 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 119291976 Starting Blk: 95927 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 120060416 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 119291976 Starting Blk: 95927 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 120060416 Fixed

Does anyone know what this problem is, how to resolve it?
Also, this Snap has 4 120GB drives. Is it OK to replace one with a 160GB drive, if the other three are 120s?

Thanks!

--David.

[blue68f100]

Need to look at the complete log. Save in HTML format.

What you posted was a timing problem. Can be caused by a lot of different things.

The 4100 does not support HD >137gig. You can substitute a larger HD if needed but not in Drive 1 position. It will be resized to match your current drives.

If you have this server off line I would use SpinRite and scan the the HD's in Maintance mode. SpinRite will correct a lot of HD problems. Snaps are real sensitive to timing. SpinRite will build the bad sector table so the Smart Tech does not have to do it on the fly. I've seen snaps handle 1 bad sector but 2 consective will generate this timing error. You will have to remove the HD to run Spin Rite.

I assume you restarted the server. Did it come up clean or go back into panic?

Have you read the sticky thread related to the 4100?

[snappov]

Thanks very much for your help!!

Attached is the log you requested (zipped).

The Snap *did* come back up, after a /fix /fixfatal/ disk check, seems to be OK for the moment.

I will definitely read the thread you recommended, thank you.

Is there a way to determine which drive is causing the error? Is there a debug command to report hard disk errors or help determine which disk might be failing?

thanks for your advice!

-David.

[snappov]

Hmm...

the plot thickens...it looks like there is a disk error--got this in the log:

E File System : Failed to resynchronize logical set 60000, error -1
Disk 60000 4/6/2009 6:42:01 PM

Complete log file attached.

Does that mean drive 1 has failed?

How can I determine which drive has failed and needs replacement?

I assume, once I di figure out which it is, I power down and install a replacement 120 GB drive (or a 160 GB drive as long as it's not drive number 1)?

Thanks so much!

--David.

[blue68f100]

You did not save the complete log, only 1 page full. From your browser when you have the log file up use Save As ... Complete.

By what you gave me indicates the HD is all most Full. You should try to keep 10 % free. Your down to the 5% area.... 41,352,675 used, 2,770,097 free

You said you have 120gig hd installed, these are not using all by the log file supplied. Apparently you swapped the HD's but failed ot reformat the HD's to use all of it.

use these cmds from debug

co de info
info Log T
in lo p -1

Also need to know what revision MB you have in the unit. READ the Sticky thread on the 4100's...

[snappov]

Hello--

Thanks for the info. This unit was actually just sent to us from Overland as a refurb warranty replacement in January '09. I will verify the drives and board info with photos Weds. afternoon, as you describe in the 4100 sticky post, but wanted to get the log info you requested sooner.

The results of the three commands are attached.

Will try to clear out some space as you suggest to get above the 10% threshold.

Thank you very much for your help!

--David.

[blue68f100]

I have taken a quick look and still going through the log. A few things pop out.

1. Your having network transmission trouble. real consistant
2. It's reporting problems with PW being longer than 24 chr. Which is causing users in and out in 2-3 sec or less.

Probably APPLE Users.... or Vista ?
SMB : sesssetup Unicode pwd exceeded max len: 92, truncate to 24

3. You have apple users. SnapOS is not compatiable with OSX or Vista.
4. ReSync is failing at ~70%
5. It has Maxtor's HD which I do not like or trust, POS. Good for target practice. I would highly recommend running SpinRite on these POS HD's. They are just an accident looking for a place to happen.

6. -->A language must be chosen, You did not use assist to do the inital setup which sets this.

It's not indicating a single HD as being bad, probably MAXTOR add feature. I susspect that you have newer computers that are not compatable with the Snap OS, Vista and OSX. I know the PW errors are causing havic.

If it was me I would reset everyone Passwords as a start, and select the language. But if your using OSX it want make any difference. There is a flag that can be set on the Apple that may fix this, but I do not recall where I saw it at.

[snappov]

Sire, you are a godsend--seriously! I will do as you suggest, and reset PWs, and set language.

I don't like Maxtor either (prefer West. Digital) --that's how Overland shipped this refurb to us--with remanufactured Maxtors no less!

I have the photos of the MB which you might be interested in seeing. Also a shot of Maxtor disk label.

Does it look like this 4100 MB has been fixed as you describe in the Sticky 4100 post, or is it still susceptible to data corruption? (Or do you need more detailed photos?)

Thanks again!

David.

[blue68f100]

The MB has the mod done to it, so it's safe. Should not have any problems in reporting trouble.

It was Adaptec's idea of using the Maxtor HD to save money. No wonder Adaptec is having problems. Since these units have been discontinue they care less if there problems..

[mandamadmin]

Hi guys. Is this the right place to post questions about problems I am having with a Snap Server 4100? Can anyone help?

The error is "File System Check : FSCK fatal error = 33"

[mandamadmin]

I restart the unit and get this:

E File System Check : FSCK fatal error = 33 Disk 1 4/11/2009 3:45:28 PM
E File System Check : Inode = 400913 - Bad direct addr[3]: 665113 Disk 1 4/11/2009 3:45:28 PM
I File System Check : ** Phase 1 - Check Blocks and Sizes Disk 1 4/11/2009 3:45:04 PM
W File System Check : Failed to allocate 32701444 bytes for rcd_backlinks!!! Disk 1 4/11/2009 3:45:04 PM
I File System Check : partition is clean. Disk 1 4/11/2009 3:45:03 PM
I File System Check : Executing fsck /dev/rraid0 /force /fix