Help! Fatal Error on Snap 4100

[stty0]

I have a Snap Server 4100 (Quantum), with these details:

RAID 4 (4 x 60GB Disks)
Version: 4.0.860 (US)
Hardware: 2.2.1
BIOS: 2.4.437

A couple of days ago it emailed me about a FATAL error 33. Since then I have tried rebooting it a couple of times, it errors out each time. It returns pings, but I am unable to get to the webserver on it (it is using https).

Here are snippets of the emails:

================================================== ==================
09/10/2007 10:11:46 ERROR File System Check : Inode = 3728674 - Bad direct addr[1]: 13359776
================================================== ==================

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

09/10/2007 10:11:46 INFORMATION System Initialization : Initialization Complete! Memory to be released: 44384880 bytes.
09/10/2007 10:11:46 ERROR File System Check : FSCK fatal error = 33
09/10/2007 10:11:46 ERROR File System Check : Inode = 3728674 - Bad direct addr[1]: 13359776
09/10/2007 10:06:40 INFORMATION File System Check : ** Phase 1 - Check blocks and sizes
09/10/2007 10:06:38 WARNING File System Check : partition is NOT clean.
09/10/2007 10:06:38 INFORMATION File System Check : Executing fsck /dev/rraid0 /fix
09/10/2007 10:06:38 INFORMATION File System : Opened FDB for device 0x1000E
09/10/2007 10:06:36 INFORMATION File System Check : partition is clean.
09/10/2007 10:06:36 INFORMATION File System Check : Executing fsck /dev/ride1g /fix /fixfatal
09/10/2007 10:06:36 INFORMATION File System : Opened FDB for device 0x10006
09/10/2007 10:06:36 INFORMATION File System Check : Cleanup completed...
09/10/2007 10:06:36 INFORMATION File System Check : ***** File system was modified *****
09/10/2007 10:06:36 INFORMATION File System Check : 710 files, 1046 used, 2991 free (0 frags, 2991 blocks, 0.0%% fragmentation)
09/10/2007 10:06:36 WARNING File System Check : Clean flag not set in superblock (Fixed)
09/10/2007 10:06:36 WARNING File System Check : Modified flag set in superblock (Fixed)
09/10/2007 10:06:36 WARNING File System Check : Summary information bad (Salvaged)
09/10/2007 10:06:36 WARNING File System Check : Blk(s) missing in bit maps (Salvaged)
09/10/2007 10:06:36 WARNING File System Check : Free blk count(s) wrong in superblk (Salvaged)
09/10/2007 10:06:36 INFORMATION File System Check : ** Phase 5 - Check cylinder groups
09/10/2007 10:06:36 INFORMATION File System Check : ** Phase 4b - Check backlinks
09/10/2007 10:06:36 WARNING File System Check : Zero Length Dir I=1710 Owner= Mode=41200
/dev/ride0g: Size=0 (Cleared)
09/10/2007 10:06:36 INFORMATION File System Check : ** Phase 4 - Check reference counts
09/10/2007 10:06:36 INFORMATION File System Check : ** Phase 3 - Check connectivity
09/10/2007 10:06:36 INFORMATION File System Check : ** Phase 2 - Check pathnames
09/10/2007 10:06:36 INFORMATION File System Check : ** Phase 1b - Rescan for more duplicate blocks
09/10/2007 10:06:36 INFORMATION File System Check : ** Phase 1 - Check blocks and sizes
09/10/2007 10:06:36 WARNING File System Check : partition is NOT clean.
09/10/2007 10:06:36 INFORMATION File System Check : Executing fsck /dev/ride0g /fix /fixfatal
09/10/2007 10:06:29 INFORMATION INIT: Setting IP address to 10.0.0.118
09/10/2007 10:06:29 System Initialization : Server v4.0.860



Can anyone help me to recover the data? I am unsure from those logs which disk is failing and why the webserver is not running.

[blue68f100]

Give it 30-60 min after doing rapairs, some repairs require a longer time before it can mount the shares.

Also read the Notice of 4100, and verify you have a good unit.

[stty0]

The array is not accessible after that log message, I have left it overnight. Also no web access or ftp access works, but it does still return a ping.

Where is this notice you are referring to?


PS .. my bad for the typo in my original message, its a RAID5 array, of course.

[blue68f100]

It's on my signature, There is one strictly for the 4100. It has a Special Problem if the unit was upgraded (<240gig to >). You will be required to look at the MB.

If you have a copy of spinrite, you may give it a try (Maintance Mode). It has fixed some.

Post the results of "co de info" from debug.

[stty0]

This unit was never upgraded, has the factory installed 4 60GB disks in it. Also, I cannot access debug or anything else for that matter, since I cannot access the webserver anymore. Assist does not see the server. It does return pings though.

It had been setup to use HTTPS and not HTTP. HTTPS in a browser returns nothing, if I try to do HTTP, i get a 403 'Forbidden' error.

Is there any way to reset the server back to defaults .. like a pin hole or button somewhere? The unit is in a rack and the back is hard to reach at the moment.

Note: I can FTP into the server, but of course cant really do anything, since it hasnt mounted files, etc. The logs I pasted earlier are all from emails it sends me when it gets an error. So the OS seems alive, but not able to run https .. which its configured to use.

[stty0]

OK, did some research, and did a reset to default settings. the webserver works again, here is the output of co de info:

09/14/2007 13:35:14 Command: co de info

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22272 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2DB9D1865825AA0B 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): 60051456 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23776 Private Mounted
Label:Private Contains system files only
Unique Id: 0x5C762B177979035D 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): 60051456 Fixed

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


It seems to panic (system LED rapid flashing) and get inaccessible after some point. I am doing a few reboots, it says its checking disk 5% complete at the moment ...

[blue68f100]

You may have a drive failing. Or it could be a hardware problem, over heating. We see this quite regularly. The 5% is an area on a HD that contains all of the drive sector tables. The problem is determing which one.

Did you check to see if you have a revised MB. Without this mod the server can become unstable. If you have another server (4100), try moving your drives over to it. This may help locate where the problem is.

[sgt.baker]

This may help. Found this in some of my notes from 2002!

Fix Fatal Command line:
co dev fsck [device number] /fix /fixfatal

Device Numbers ( can be determined using: "in dev" )
60000 - Raid 5
50000 - Mirror
40000 - Span
If individual drives
10000 - drive 1
10008 - drive 2
10010 - drive 3
10018 - drive 4