Windows Security

Howie Kay
Howie Kay used Ask the Experts™

I have a Raid Stripped drive system.  It was setup years ago under XP Pro Sp3.  It is part of a server class Windows system with removable boot drives.
I have recently built a Windows 7 drive and I am migrating all my apps to that drive.
I have had some random permission errors trying to access the raid drive from the Win 7 boot drive.  However, most  of the documents I have on that drive are available from the applications which created them from the Win 7 drive.  Some documents which were accessible are not now accessable.

The problem has increased and now Windows Explorer is not permitted to access the Raid drive.

I am now on the XP SP3 drive and I would like to reset  the permission properties by adding "Everyone" .  There is presently not an issue with the Raid system using the Xp boot drive.  But, just in case, I would like your support on this issue.

be well be happy,
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Howie KaySystems Engineer Lockheed-Retired


Hi Jcimarron,

I temporarily fixed the problem by including "everyone"  with full permissions from the root of the file system to all child objects (files and folders) on the Raid drive.   Thanks for the references,  I'll study them for a more secure solution.   These references should be helpful.

The problem is a bit more extensive than I originally described.
Some months ago,  when booting the XP Pro drive,  Windows ran a chkdsk at boot up and reset the entire Raid drive to admin access only, one folder at a time.
This did not cause a problem for me since I am the admin.  Since then,  I thought I had added the "everyone" access again.   So something is going on I do not understand.  Why is my access from my Win 7 drive to the Raid drive restricted?   To fix the problem I again include "everyone" which  is missing from the previous assignment.  What is resetting my permissions?  And how,  since I have only been using the Win 7 drive forn last three months? I may need to open a case with  Microsoft before I loose the Raid drive completely.

I also have had this issue with a Xp Home drive, which I use for charity support.  
The only drive I have not had a problem with is the original XP Pro SP3 drive, thank goodness.

Howie KaySystems Engineer Lockheed-Retired


To clarify the previous comment,  if that is possible:

All permission changes were made from the XP Pro SP3 drive

Sorry about that
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Hi Howie_Lynn took a fair bit for me to access your question since my AV blocked it
hope I can help
the points I'm looking at>I have had some random permission errors trying to access the raid drive from the Win 7 boot drive.
and>Some months ago,  when booting the XP Pro drive,  Windows ran a chkdsk at boot up and reset the entire Raid drive to admin access only, one folder at a time.
This did not cause a problem for me since I am the admin

Sounds like some folders or files were in use or still open not logged off?
Possible a problem with one of the drives clusters?
Redundant files?
Because different segments of data are kept on different storage devices, the failure of one device causes the corruption of the full data sequence.
In effect, the failure rate of the array of storage devices is equal to the sum of the failure rate of each storage device.
This disadvantage of striping can be overcome by the storage of redundant information, such as parity, for the purpose of error correction.
In such a system, the disadvantage is overcome at the cost of requiring extra storage.

fswatch is a small, simple utility that detects changes in a filesystem. it watches for a file system integrity. it checks inode, links, uid, gid, mode, size, flags, ctime, checksum (SHA1).
file system checksum checker

2  Causes of Integrity Violations
 Integrity violations can be caused by hardware or software malfunctions, malicious activities, or inadvertent user errors.
 In most systems that do not have integrity assurance mechanisms, unexpected modifications to data either go undetected, or are not properly handled by the software running above, resulting in software crash or further damage to data.
In this section,  describe three main causes of integrity violations and provide scenarios for each cause.
Ensuring Data Integrity in Storage: Techniques and Applications

SnapRAID is a backup program for disk arrays. SnapRAID stores redundancy information in the disk array, and it allows recovering from up to two disk failures.
Howie KaySystems Engineer Lockheed-Retired


Thanks Merete,

At about the time of the failure,  I was trying to move Outlooks 2010's data file (*.pst) to my array.  
2010 can be cantankerous.   By the time I sorted things out I had a profile corruption error which Outlook mis-diagnosed as a datafile corruption.   So all this troubleshooting took some effort.   But learning is worth the effort.    Several struggles later,  I learned something wortwhile.   One can create a data file with a unuquie name  and then move and paste old mail into the new pst file for archiving.  One of the things with which Outlook has a problem.

Perhaps, in addition to lots of other interesting challenges,  could the problems of moving the pst file have caused the occasional access failure to some of the files on my Raid?  And also the failure of Windows Explorer to acquire access?  Funny thing,  Outlook never had an access problem.  But I did loose access to my Lightroom's data.

When booting from my XP drive I found "everyone"  in place in most of the docment files to which I needed access.   So I added everyone to the root of the array and migrated that setting to all children.  That seemed to fix the access problem from my Win 7 drive.

The raid seemed to be ok on the XP drive.   The access problem occurred on the Win 7 drive.

Thanks again for the info.   I'll study your comments and learn.  And I'll be careful with the array.

Howie KaySystems Engineer Lockheed-Retired


Since SATA interface has increased access speed and since disk drives are much larger,  should I consider removing the array and formatting and restoring to the two seperate drives?
Hi Howie, that is really entirely up to you. personally go with your gut feeling.
When problems start it's usually indication of a mess somewhere maybe time to cleanup.
You could consider a Nas?
Something like these
Howie KaySystems Engineer Lockheed-Retired


Thanks for the help.   I have a lot to think about.  But first,  a new complete backup.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial