2003SP2 - Fileserver dACLs killed by Chkdsk
This is regarding a HP Blade BL460C with Server 2003 SP2 connected to a RAID5 SAN volume on an MSA1500 controller. It acts as a fileserver for users' data. Firmwares on both are up to date. There were error messages in the event logs saying that the filesystem on the SAN-based data volume was corrupt and unusable so a chkdsk was scheduled and the server rebooted. On reboot the chkdsk operation started throwing up vast numbers of errors (sorry I was not present to see exactly what it said) and the admin cancelled it mid-way. The end result is that all the ACLs appear to have been wrecked on all the folders. I believe Admin and System had access but no one else. Has anyone any ideas what might have happened to cause this? I've found references online to Server 2000 and Pre-SP2 Server 2003 with hotfixes offered. Since this machine is already SP2, these don't apply to us. Thanks for any help you can offer.
November 9th, 2011 12:18pm

Hi, Generally check disk is not recommanded to be run on a RAID. RAID provider should have their own application to manage RAID disks. For your current situation, we cannot confirm if the ACL issue is caused by the check disk process or the "check disk cancelled in mid-way". You may need to run a restore to get settings back.TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.
Free Windows Admin Tool Kit Click here and download it now
November 10th, 2011 4:02am

Thanks for this info. We've found nothing to suggest the RAID array is in itself unhealthy and can't find any extra HP diagnostic software for it either. In the short term, is there a way to reset the dirty bit on the volume?
November 10th, 2011 8:20am

We think we've found the likely cause. The first signs of problems on the volume coincided with the first time a backup job ran directly against it from a 2nd server using Selective Storage Presentation (to allow two machines to access it) rather than a backup agent in the filestorage server's OS.
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2011 4:43am

We think we've found the likely cause. The first signs of problems on the volume coincided with the first time a backup job ran directly against it from a 2nd server using Selective Storage Presentation (to allow two machines to access it) rather than a backup agent in the filestorage server's OS.
November 11th, 2011 12:42pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics