Index6 failed on EV9 with EventID41021

[Manuel_L_]

Hi there!

I´m working on a problem, that i can´t solve:

Win2k3r2, EV 9.0.2 - singleserver - FSA (no mail)

6 Month ago, the customer removed theire EV-Environment quick-and-dirty on theire own after robocopy-ing all files to another Partition.

Now they discovered, that some files are corrupted and has the offlinebit set.

removing the offline attribute with common symantec-tools was not sucessfull for all files, so they restored the Whole EV-Environment, but cant use the same volume, as the "original-files" from one of the archives are on another LUN.

All other archives can be accessed and archive explorer shows the files and they can restore, but  only one (the one who moved from F$ to I$) are not acessable/searchable.

This was the point, where i got called and discovered, that the index6 is failed.

Rebuilding the failed index leeds to sucess for about 3 days - files was serachable and restoreable from archive explorer and points to the newly created F$-drive. Suddenly the browsing wasn´t able and the index was failed again with EventID41021

What may possibly happens to failing again? -> What should i do now?

I would be pleased with your suggestions

[JesusWept3]

Can you paste the whole event? Also can you go to the directory for the failed index and look at the log files there to see if it gives any clues?

[Manuel_L_]

Hi JW3!

Thanks for your help -

Index-logs are 0 kb and all lock, etc.. seems to be okay

i have a couple of eventids, that leads me to nothing.

One Eventlog tells me, that no space is left (EVENTID 7180 - INDEX SERVER), but ther is the same space as before (simple VM restore with the same vmdks).

I´ve uploaded the logs - please have a look at ev_id.docx

Here`s the eventid-list:

• 7180 - INDEX SERVER
• 7284 - INDEX SERVER
• 7288 - INDEX SERVER
• 7271 - INDEX SERVER
• 7292 - INDEX SERVER
• 7313 - INDEX SERVER
• 7235 - INDEX SERVER
• 41008 - Monitoring
• 41021 - Monitoring

[Manuel_L_]

Hi JW3 - thanks for your help!

In the index ive found just the normal files - no hint to the problem -> all looks as normal

I´ve got a couple of logs collectet in the attached file ev_id.docx

Overview of the EventID´s:

• 41021 - Monitoring
• 41008 - Monitoring
• 7235 - INDEX SERVER
• 7313 - INDEX SERVER
• 7292 - INDEX SERVER
• 7271 - INDEX SERVER
• 7288 - INDEX SERVER
• 7284 - INDEX SERVER
• 7180 - INDEX SERVER

the last entry is very mysterious, as there IS enough space as the LUN comes from the whole restored VM (with all vmdk´s)...

[Manuel_L_]

any ideas - i really need help in this case