Unsolved

This post is more than 5 years old

3 Posts

7781

December 1st, 2004 07:00

Powervault 705N RAID 5 Errors

Hi,
 
I'm running a powervault 705N with RAID 5 on 4*120gb drives (upgraded from 4*30gb). I was in the process of copying across a large amount of data, everything was fine and I had breaks every 3gb or so. The last copy however caused the whole thing to crash and not respond. It boots up ok but everytime I run the disk checker it crashes at varying levels with the following errors. My thought is that one of the drives is faulty. Can anyone help me with this?
 
==================================================================== 11/29/2004 18:07:21 FATAL ERROR PANIC : ffs_alloccg: map corrupted ====================================================================  
The previous message occurred in the following context within the system log:
11/29/2004 17:43:46 INFORMATION System Database : SDB has been written to flash at 2004/11/29 17:43:46.
11/29/2004 15:43:45 INFORMATION System Database : SDB has been written to flash at 2004/11/29 15:43:45.
11/29/2004 12:11:42 INFORMATION System Database : SDB has been written to flash at 2004/11/29 12:11:42.
11/29/2004 10:59:41 INFORMATION System Database : SDB has been written to flash at 2004/11/29 10:59:41.
 
==================================================================== 11/30/2004  9:53:24 ERROR       File System Check : FSCK fatal error = 33 ====================================================================
 
==================================================================== 11/30/2004 10:07:38 ERROR       File System Check : Bad state 0 for inode I=4186 ====================================================================
 
==================================================================== 11/30/2004 10:07:38 ERROR       File System Check : FSCK fatal error = 39 ====================================================================
 
==================================================================== 11/30/2004 10:50:29 FATAL ERROR PANIC : ASSERT(fcbp->fcb_magic == FCB_MAGIC) ====================================================================
 
==================================================================== 11/30/2004 16:21:36 FATAL ERROR PANIC : ASSERT((*dp)->dino_number == inumber) ====================================================================
 
==================================================================== 12/01/2004  9:13:17 ERROR       File System Check : Bad state 7 for inode I=110536 ====================================================================
 
 

Message Edited by alan.shaw on 12-01-2004 03:38 AM

718 Posts

December 4th, 2004 20:00

To determine if you have a failed disk drive, use your Web Browser and connect
to the Server Debug page.
where P705n is the IP address.
From here you should be able to determine if a disk has failed if it does not appear
as one of 4 partitions 10000,10008,10010,10018.
 
 
No Events found!

Top