View Single Post
Unread 08-18-2006, 06:51 PM   #1
Reason_Man
Cooling Neophyte
 
Join Date: Aug 2006
Location: Beaumont, Texas
Posts: 20
Default Snap 4100 orphaned drive question

Hi, i'm new here and to Snap server maint so I could be asking something easily fixed. I searched around and couldn't really find anything that answered my question.

The other day we had a storm and the power went out. After that the server powered back up and seemed to work fine. Later that day someone tried to access files on it(from a Mac) and it threw some error about not being able to mount the volume. I checked around the office and found no one could connect but the web panel was still up and functional, except that the disks were all labeled "offline". I powered it down and back up and still nothing. I checked the logs, which only went back as far as May 10, that after the power up after the storm, the entry "File System Check : FSCK fatal error = 32" is in after every boot. Also, the command "info device" spits out:

Code:
Logical Device: 10006      Position: 0  JBOD     Size (KB):    32296  Free (KB):    22368  Private  Mounted
  Label:Private  Contains system files only
     Unique Id: 0x5C9268DD22EDF7B3    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):    22600  Private  Mounted
  Label:Private  Contains system files only
     Unique Id: 0x0251F4EB11E9CD26    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: 10008      Position: 1  ORPHAN   Size (KB): 59583056  Free (KB):        0  Public   Unmounted
  Label:Drive2  Orphan from SNAP - RAID5
     Unique Id: 0x51688E8607EA3027
     Partition: 10008  Physical: 1000F  ORPHAN   Size (KB): 59583056  Starting Blk: 58422  Public 
      Physical: 1000F    Drive Slot: 1  IDE      Size (KB): 60051456  Fixed    

Logical Device: 60000      Position: 2  RAID_CRACKED Size (KB): 178749168  Free (KB):        0  Public   Unmounted
  Label:RAID5  Large data protection disk
     Unique Id: 0x51688E8607EA3027    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: 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
Now, i've never messed with RAID before so I don't really know how to go about solving this problem. Everything I have managed to find and read says to format the problem disk(assuming disk 2, or 10008?) and rebuild the RAID IF the drive is not dead. The documentation for the server said that if it shows up in the "disk status" panel as orphaned than it might be usable. This is the output of that particular page:

Code:
View log for disk Drive2.   	    	  Drive2   - Orphan from SNAP - RAID5
Error.  Unknown disk operation error.
View the disk log for details. 	  	58,186 	Unknown 	Unknown

View log for disk RAID5. 	  	RAID5  - Large data protection disk
Checking.  75% complete
After checking RAID5, the server seems to shutdown. There is no disk activity. Only the system and single "disk" LED flash. I checked the flash patterns and they don't seem to match anything. Also, NOTHING is accessible, not through the network and not through the web admin page, it just times out.

So, are there any ideas as to what went on and how to fix it? If you need any other information let me know. Thanks.
Reason_Man is offline   Reply With Quote