We help IT Professionals succeed at work.

Verifying directory file structure

corptech
corptech asked
on
614 Views
Last Modified: 2010-04-21
ServeRaid 3L card with RAID 5 with 6 drives. had some bad hard drives which have been replaced.  Now, keep losing SYS volume and have to do NSS /poolrebuild to recover SYS vol.   Hard drives test ok.  appears to be file corruption.  It has been a while since I have worked on Novell.   What is best way to verify directory file integrity?
Comment
Watch Question

Commented:
Can you tell us what it means when you "keep losing SYS volume?"

Are you getting messages about pool data integrity, then it goes through a dismount process, basically rendering your server useless?

Because if I had to guess (and I know I'm waaay pre-mature on this guess) I would say that it's possible you've got a RAID controller problem and not a pool problem.  Especially if you are constantly going through pool rebuilds.

Your pool rebuilds are the sickness - treat the disease.

Any information that shows on the server console or logger screen would be great.  I just had to deal with this on 2 servers with the same type of RAID controller card.  Replaced the card and the server was great - but the pools would dismount and upset everyone because their data would be lost if it wasn't saved.

But yeah, turned out to be 2 bad RAID controllers and not drives or pool/volume issues.  Here's the kind of message I was getting on both of them (I've attached a pic to this link here):

http://www.bndservices.com/ee/badraid1.jpg

Commented:
You've not make it very clear as to what you mean, but a quick and dirty answer is to look in nss /?, there are many verification and rebuild options.

Author

Commented:
Sorry about not being clear on this issue.  When booting server up, server fails to mount SYS and VOL1.   Volumes cmd only shows  _Admin volume.     By doing a NSS /poolrebuild on SYS, I can get the SYS volume back  and mount it.   I can also mount VOL1.  After running the server a short period of time ( 30 to 180 minutes) I will lose both SYS and VOL1 with an error message on screen -
NSS-3.00-5001:  Pool  ServerName/SYS is being deactiveated.  
An I/O error (20204(Zio.c[2279])) at block 3845073 ( file block 28099) Z1D3)
 has compromised pool integrity.

Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thanks for the feedback.  Am looking at getting a replacement RAID controller card.  Thanks.

Commented:
OP, did you see my screenshot?  Sounds exactly like what you are experiencing. Let me also add this:

Pool rebuilds have you roll the dice on whether or not you're going to lose data as part of the process. It's a fact - so for anyone reading if you care to disagree, bring on the supporting arguments please. People do this operation a bit too candidly. I've had people do it and damage files in their volumes. This is most commonly a result of bad information being passed by the controller to the volumes you are fixing.

PLEASE make sure you have current volume backups before doing rebuild operations.

Commented:
OP, did you see my screenshot?  Sounds exactly like what you are experiencing. Let me also add this:

Pool rebuilds have you roll the dice on whether or not you're going to lose data as part of the process. It's a fact - so for anyone reading if you care to disagree, bring on the supporting arguments please. People do this operation a bit too candidly. I've had people do it and damage files in their volumes. This is most commonly a result of bad information being passed by the controller to the volumes you are fixing.

PLEASE make sure you have current volume backups before doing rebuild operations.

Commented:
I'd like to echo Ghost96's warning about pool rebuilds.  NetWare people are far to use to VREPAIR (I think it was called).  Pool rebuilds in NSS are not the same thing and can be destructive.  Do a search on Novell's support website & you'll find lots of TIDs warning you about this very thing.

Not to be taken lightly.

Author

Commented:
thanks for info.  was a combo of bad hard drives, bad controller.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.