PANIC on SNAP 4000 - cannot acces files

[F1GAME]

Yesterday my SNAP packed in and I can no longer access the files. the lights on the front are going mad, I switched it off and on, checked the log file thereafter, see below. I guess what I am hoping for is for someone to let me know if I can fix it without losing the data or even identiy the drive that is faulty and how to replace it!! Very new to this, sorry to be such a bore!! Log belowL-
SNAP01 • Server Log




Change the following fields and press Refresh to specify how the log is displayed.
Severity EverythingWarnings/ErrorsErrors only
Display last days
Most recent first



Severity legend: I=Information, W=Warning, E=Error, F=Fatal Error, S=Server Startup
Message Source Date Time
I SMB : Resolved IP address (192.168.0.3) for domain controller PDCCTO. Network 7/11/2009 8:35:33
I SMB : Located domain controller PDCCTO via TCP/IP. Network 7/11/2009 8:35:24
I DHCP/BOOTP: Setting IP address to 192.168.0.20 Network 7/11/2009 8:35:14
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000
RAID 5 7/11/2009 8:34:23
W File System Check : partition is NOT clean. Disk 60000
RAID 5 7/11/2009 8:34:22
I File System Check : Executing fsck /dev/rraid0 /fix Disk 60000
RAID 5 7/11/2009 8:34:22
I File System : Opened FDB for device 0x1000E Disk (Priv) 7/11/2009 8:34:22
I File System Check : partition is clean. Disk (Priv) 7/11/2009 8:34:20
I File System Check : Executing fsck /dev/ride1g /fix /fixfatal Disk (Priv) 7/11/2009 8:34:20
I File System : Opened FDB for device 0x10006 Disk (Priv) 7/11/2009 8:34:20
I File System Check : Cleanup completed... Disk (Priv) 7/11/2009 8:34:20
I File System Check : 706 files, 1068 used, 2969 free (0 frags, 2969 blocks, 0.0%% fragmentation) Disk (Priv) 7/11/2009 8:34:20
W File System Check : Clean flag not set in superblock (Fixed) Disk (Priv) 7/11/2009 8:34:20
W File System Check : Modified flag set in superblock (Fixed) Disk (Priv) 7/11/2009 8:34:20
W File System Check : Summary information bad (Salvaged) Disk (Priv) 7/11/2009 8:34:20
W File System Check : Blk(s) missing in bit maps (Salvaged) Disk (Priv) 7/11/2009 8:34:20
W File System Check : Free blk count(s) wrong in superblk (Salvaged) Disk (Priv) 7/11/2009 8:34:20
I File System Check : ** Phase 5 - Check cylinder groups Disk (Priv) 7/11/2009 8:34:20
I File System Check : ** Phase 4b - Check backlinks Disk (Priv) 7/11/2009 8:34:20
W File System Check : Zero Length Dir I=2304 Owner= Mode=41200
/dev/ride0g: Size=0 (Cleared) Disk (Priv) 7/11/2009 8:34:20
I File System Check : ** Phase 4 - Check reference counts Disk (Priv) 7/11/2009 8:34:20
I File System Check : ** Phase 3 - Check connectivity Disk (Priv) 7/11/2009 8:34:20
I File System Check : ** Phase 2 - Check pathnames Disk (Priv) 7/11/2009 8:34:20
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk (Priv) 7/11/2009 8:34:20
I File System Check : ** Phase 1 - Check blocks and sizes Disk (Priv) 7/11/2009 8:34:20
W File System Check : partition is NOT clean. Disk (Priv) 7/11/2009 8:34:19
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 7/11/2009 8:34:19
S System Initialization : Server v4.0.854
Build Date: Aug 20 2004 10:50:51
Boot Count: 18 System 7/11/2009 8:34:13
F Call Stack :
$00225C8A
$002203D6
$002203B3
$0021FF0E
$00229FA5
$0022A131
$0020BFFC
$0020BF33
$00222A99
$002084CF
$0020856D
$00179F51
$0017475E
$0016A457
$0016A5A8
$00169EC0
$0010413C
$001041C3
================================
System 6/11/2009 15:28:21
F PANIC : blkfree: freeing free block System 6/11/2009 15:28:21
W Call Stack :
0010513F
002D1414
002D8456
002DF6DA
002B2147
002B0917
002BC396
002BD776
002B1E9F
002B07A5
002BC274
002B0A6C
0010413C
001041F6 System 6/11/2009 15:27:15
W Maximum yield time exceeded at $002BCE56 System 6/11/2009 15:27:15
I System Database : System Configuration Backup has completed successfully System 5/11/2009 20:30:11
I System Database : System Configuration Backup has begun System 5/11/2009 20:30:11

[blue68f100]

Try using the "co de info" cmd from debug, see if it show a HD or 2 mia.

I think the other cmd is "in dev pa" or "info log -t" will give more info on what has failed.

Is this a 2 din height 4000 or a 1 din heigth 4100?

and is any of the leds for the HD showing a problem?