First of all, thank you for having this forum. When I first purchased my Snap 4100 over two years ago, this forum was a wealth of information and assistance. I never posted prior to now because I was able to find answer to all of my problems by browsing the wiki and the forums.
Unfortunately, I'm stuck now.
As I mentioned, I have a Snap 4100. It is running SnapOS 3.4.805 and has three 80GB Maxtor diamondmax drives and one 120GB Maxtor diamondmax that replaced a failed drive last December. The three 80GB drives were pulled from a system that had severe voltage sag issues, but have been running without any problems for two years.
About a week ago, I saw an error that fsk had failed to "clean" on the drives. (No error message was generated by the snap drive at that time - or at least no error message was sent out by the email notifier.) The drive listed in the log was x1000E. I believed that this was drive #2 (1 IDE) and ordered a new 120GB Maxtor diamondmax.
Today, I installed the new drive. Upon powering up the new drive was recognized but the RAID array was listed as RAID_CRACKED.
Being as I am a rather cautious person, my first thought was to replace the original (non-working) drive back into the array and see if I could get it to rebuild.
The array fails at 5% building.
The output of the
co de info command is:
Quote:
Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 24000 Private Mounted
Label:Private Contains system files only
Unique Id: 0x1924A4B2291D8809 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): 80043008 Fixed
Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 24000 Private Mounted
Label:Private Contains system files only
Unique Id: 0x74BE120D1C216B85 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): 80043008 Fixed
Logical Device: 10008 Position: 1 ORPHAN Size (KB): 79539864 Free (KB): 0 Public Unmounted
Label rive2 Orphan from SNAP502051 - RAID5
Unique Id: 0x7828113D509ECBE5
Partition: 10008 Physical: 1000F ORPHAN Size (KB): 79539864 Starting Blk: 62765 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 80043008 Fixed
Logical Device: 60000 Position: 2 RAID_CRACKED Size (KB): 238619592 Free (KB): 0 Public Unmounted
Label:RAID5 Large data protection disk
Unique Id: 0x7828113D509ECBE5 Mount: /0 Index: 0 Order: 255
Partition: 10000 Physical: 10007 R 60000 Size (KB): 79539864 Starting Blk: 62765 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 80043008 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 79539864 Starting Blk: 87776 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 120060416 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 79539864 Starting Blk: 62765 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 80043008 Fixed
|
I'm not sure what to make of this. The array appears to have three valid members IDE0, 2 and 3) and the IDE1 drive appears to be an an orphan of the -same- drive; the unique IDs are the same for all four drives.
The problem seems to be logical drives 10006 and 1000E (remember that 1000E was what started this whole misadventure) are being problematic.
It "looks" like I should be able to join the four drives back into a working array, but I'm not sure how to accomplish that. I was able to find a thread that described a similar (but not identical) situation at
http://forums.procooling.com/vbb/showthread.php?t=12887, but no real solution was offered. I did try
co de resync 60000 and it did not appear to destroy the data, but the array is still in the same condition, with one exception: the server is now sending Server ERROR emails out each time I try to fsk the disk, whereas it was previously silent about it's errors.
I'm a little hesitant to reformat the drives just yet in the off-chance that the data is recoverable. (If it isn't, I will shed a few tears, but I'll get over it.) If it does come down to a reformat situation, I'd like to hear what others recommend to prevent this from happening again in the future.