Memory error on SNAP 1000's

[rusty.hill]

Hi

I've u/gd several 1000's, 1100's & 2000's over the years and once you get the hang of it it seems to go OK. (The bigest one is a 2000 with a pair of 750Gb drives in ...)

But last night I had a problem with a pair of 1000's which I was putting a 500Gb in one and a 750 Gb in the other.

All went well using a 'tried & tested' image (via Winhex) and the usual debug command - co de format 10000 /reinit - worked fine too.

I then got a 500Gb drive in one and a 750GB in the other.

As a test, I thought I'd run a disk check and that's when the trouble started...

The SNAP rebooted and trashed the disk. Same in the other 1000.

So I ran co de format 10000 /reinit again - all looks well. Copy files etc, run disk check - dead disk.

Rerun co de format 10000 /reinit - pull power to get a dirty disk, and on reboot it trashes it again.

The logs say:
--------------------------------------------------------------------------------
Message Source Date Time
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:09
Boot Count: 7 System 12/1/2007 15:56:51
W File System : Format terminated unsuccessfully Disk 10000
Individual 12/1/2007 15:55:37
W File System : mkfs failed!!! Error = 8 Disk 10000
Individual 12/1/2007 15:55:37
W File System : Failed to allocate 1425408 bytes for mkfs!!! Disk 10000
Individual 12/1/2007 15:55:37
E File System Check : FSCK fatal error = 8 Disk 10000
Individual 12/1/2007 15:53:46
W File System Check : partition is NOT clean. Disk 10000
Individual 12/1/2007 15:53:46
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:09
Boot Count: 6 System 12/1/2007 15:53:41
---------------------------------------------------------------------------

Any ideas about:

W File System : Failed to allocate 1425408 bytes for mkfs!!! Disk 10000
Individual 12/1/2007 15:55:37
E File System Check : FSCK fatal error = 8 Disk 10000

What's with the 'failed to allocate' msgs..?

All thoughts much appreciated!

Brgds

Rusty

[blue68f100]

Well, you are in uncharted territory with those drives. And those are the perpindicular tech drives. You may have a bad one. May try the drive in a PC and do the long format to prepare the drive, this may help test the integerty of the drive.

What are the Snap Vitals, HW, OS version .... Need to know if the 1000 is a v1 or v2.

May need to reload the OS, something may be corrupt.

If a HD is not clean and it sees a bsd file structure, a snap will not use it unless clean.

I have started using SpinRite to do surface scan on new drives. Mfg no longer test the recording media, they rely on the SMART tech to make repairs on the fly.

[rusty.hill]

Thanks for the prompt reply....

So some more info....

1) I've used these new perp. recording disks in some Snap 2000's before & they are OK... for what that might tell us!

2) I get the same problem in 2 1000's, one with a 500 & the other with a 750Gb Seagate so I doubt it's bad disks...

3) In terms of version number of the Snap - where does it say v1 or v2? (sorry to be dim..)

TiA

R

[blue68f100]

From the admin page, click on the SnapAppliance Logo. A popup will give the vitals.

[rusty.hill]

Thanks...

Model Software Hardware Server # BIOS
1000 series 4.0.860 (US) 3.1.2 127381 2.1.366

Is this version 1 or 2 or what?

TiA

Rusty

[blue68f100]

Yours is a v2 HW.

Seagates come with a utility for checking smart data & drive integerty. I would run them.

If all good, try the process again.

Did you look at the original drive logs for errors?

[rusty.hill]

Thanks -

What tells you it's V 2 h/w pls?

The 'old' SNAP disks - an 80 & a 40 - both are good and the logs clean.

I'll pull the 500GB out and load it into a PC & run some diags...

Any clues as to what the 'unable to allocate 'x' memory' error really means? Does it try to allocate RAM for some sort of file table building or is it related to allocating space on the disk?

TiA

Rusty

[blue68f100]

I believe its a file table, Snap-Tech will have the answer.

[rusty.hill]

Thanks v much.

'Snap-Tech'... who/what that?

TiA

Rusty

[blue68f100]

He is an X Snap tech. Worked in the drive division for a while also did tech support. Has his own bussiness in HD recovery including All brands of Raid's. He checks in ever couple of days. I will foward this post to him.

If I recall the fix was a different MFG drive, but Snap-tech will know what is generateing the error.

[rusty.hill]

Ah-- Another Elite Guru - always good to have two around!

Many thanks for all your help on this.

Brgds

Rusty.

[re3dyb0y]

Originally Posted by rusty.hill

Ah-- Another Elite Guru - always good to have two around!

Many thanks for all your help on this.

Brgds

Rusty.

2????


*Sam Goes off in a Huff*

[blue68f100]

Sam you have been MIA to long , Too much School Work

[Phoenix32]

Originally Posted by rusty.hill

Ah-- Another Elite Guru - always good to have two around!

Many thanks for all your help on this.

Brgds

Rusty.

Excuse me?

[blue68f100]

The rest of the Elite Group is :
On the 4000's Sets Master Phoenix32
On the 4100's we have Master Jontz
On 1x00 and 2x00 I get support from re3dyb0y (PooglesUK)
And the Newest Member is Snap-tech covering all models.

I have the most time since I'm retired.

[rusty.hill]

More the better - sorry if I offended any one....

Rusty

[re3dyb0y]

Originally Posted by Phoenix32

Excuse me?

My thoughts exactly