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.
