Jump to content

Question

Posted

After recently upgrading my server, I purchased a second license (to support developers) and then moved my entire drive array to my new win11 machine (from old win11 machine)

Some of it works fine, but

C:\>icacls n: |more
n: NT AUTHORITY\Authenticated Users:(OI)(CI)(F)
   NT AUTHORITY\SYSTEM:(OI)(CI)(F)
   BUILTIN\Administrators:(OI)(CI)(F)
   BUILTIN\Users:(OI)(CI)(RX)

Successfully processed 1 files; Failed processing 0 files

on one drive I can't seem to take ownership.

Tried this after prev command
C:\>takeown /f N:\ /R /D Y
ERROR: Access is denied.

image.png.2dca695da32b3f5ee638c6a36411d0a4.png

Any suggestions on what I'm doing wrong?

Thanks in advance!!!!

And the first error message shows: 

image.png.0420f5d9e02f46b42d8707a6d1b9b0c1.png

13 answers to this question

Recommended Posts

  • 0
Posted

Hi, the official recommended process to reset a pool's NTFS permissions to defaults is https://wiki.covecube.com/StableBit_DrivePool_Q5510455

If that process fails (because sometimes NTFS permissions break weirdly), the first three posts in this thread https://community.covecube.com/index.php?/topic/5810-ntfs-permissions-and-drivepool/ describes what the ACLs should be and provide instructions on how to fix them.

As a side note, if the $RECYCLE.BIN folder is corrupted and you delete it the OS will automatically recreate it properly when needed. If it's only corrupted on one of the poolparts you may need to stop the DrivePool service and delete the folder directly from each poolpart disk then start the service again.

 

  • 0
Posted
On 10/15/2026 at 10:36 PM, Shane said:

Hi, the official recommended process to reset a pool's NTFS permissions to defaults is https://wiki.covecube.com/StableBit_DrivePool_Q5510455

Hi Shane;  I tried both the official (first solution) and the manual (2nd ones) from the old server:

it didnt work.

Here are my notes, and a question whether I need to download the CSS server utilities (I'm only running win/11 pro on both machines)

===========notes follow=======

output to try and change permissions for j: (old --mdesk)  or n: (new--tivo) drive-pool.

I Tried the original (preferred) instructions here:         https://wiki.covecube.com/StableBit_DrivePool_Q5510455  from new machine.  failed.
I then tried manual instructions here:               https://community.covecube.com/index.php?/topic/5810-ntfs-permissions-and-drivepool/ from new machine, failed
I then unplugged my jbod (just a box of disks) unit, and replunged it into the old system, which still had drivepool on it (with a different license)

I then moved the JBOD to the OLD machine (mdesk, where it was the J drive)

I then tried   https://wiki.covecube.com/StableBit_DrivePool_Q5510455  from old  machine.  failed.
installed setacl. per manual instructions
I then tried    https://community.covecube.com/index.php?/topic/5810-ntfs-permissions-and-drivepool/ from old machine, failed

error messages: old machine
    C:\Users\mdesk\Favorites\Downloads\SetACL (executable version)\64 bit>dir
 Volume in drive C is m-desk-c
 Volume Serial Number is 4889-A119

 Directory of C:\Users\mdesk\Favorites\Downloads\SetACL (executable version)\64 bit

07/10/2012  09:25 PM    <DIR>          .
07/09/2012  09:45 PM    <DIR>          ..
06/27/2021  01:10 AM           616,312 SetACL.exe
               1 File(s)        616,312 bytes
               2 Dir(s)  12,471,406,592 bytes free

    error (setacl) output:
C:\Users\mdesk\Favorites\Downloads\SetACL (executable version)\64 bit>SetACL.exe -on j:\ -ot file -actn setowner -ownr "n:Administrators" -rec cont_obj -fltr "System Volume Information" -fltr "$RECYCLE.BIN"
Processing ACL of: <\\?\j:\>

SetACL finished with error(s):
SetACL error message: The call to SetNamedSecurityInfo () failed
Operating system error message: Access is denied.

C:\Users\mdesk\Favorites\Downloads\SetACL (executable version)\64 bit>

drivepool J properties tet version
Permissions for DrivePool (J:)

Security

Object name: j:\

Group or user names:
Authenticated Users
SYSTEM
Administrators (MITCH-DESK\Administrators)
Users (MITCH-DESK\Users)
----------------------------------
Permissions for Users
Full control        x
Modify            x
Read & execute        x
List folder contents    x
Read            x

results:  
Error Applying Security

    n error occurred while applying security information to:

    J:\batch\double-u-vs-tee-differences.txt

Failed to enumerate objects in the container. Access is denied.

Now because I previously saw that the $RECYCLE.BIN was causing problems, I deleted the entire (on J/mdesk) j recycle bin, so that directory was empty.
Apparently didn't work because :
the properties of $recyle.bin were:
$RECYCLE.BIN

Type:File folder (.BIN)

Location: J:

Size:730 GB (784,133,422,310 bytes)
Size on disk: 730 GB (784,144,146,432 bytes)

Contains:5,924 Files, 858 Folders

And so the previous delete didn't work?!

I cannot add/delete or change anything on the (tivo [new] system, on the N: drive (formerly the J drive on mdesk system), as I have no write permissions.

ideas?  is there a spot where I can send a support ticket in?

thanks again in advance

  • 0
Posted

Just to confirm, when you opened the command prompt to run SetACL, did you open the command prompt as an Administrator?

E.g. click the Start button on the desktop task bar, type Command Prompt in the search field, click Run as administrator from the resulting displayed options; normally User Account Control should pop up to confirm allowing the program to make changes, and upon clicking Yes you should get an Administrator Command Prompt that begins with its current directory as C:\Windows\System32 (note: I would then use the CD command to change to the directory in which SetACL.exe is installed before running SetACL.exe, as I don't like staying in System32 as the current directory when performing file operations unless I have to).

If SetACL fails on the pool drive, the next step would be to run it on each of the individual poolpart folders on the physical disks that make up the pool, as described in the same post.

  • 0
Posted

Will try this... Yes, I did run it as admin, and I also changed the startup directory for the same reason!

will try again...

Last question, I am presuming you are going to suggest I do this on the NEW system, and not the old one, correct?

 

If SetACL fails on the pool drive, the next step would be to run it on each of the individual poolpart folders on the physical disks that make up the pool, as described in the same post.

  • 0
Posted
1 hour ago, Markbnj said:

OK   I tried again on the new machine:

Failed again with  error message :

SetACL finished with error(s):
SetACL error message: The call to SetNamedSecurityInfo () failed
Operating system error message: Access is denied.

 

The output is postedbelow

thanks

I suppose tomorrow I will attempt to change permissions on all of the individual drivepool parts of n:

sigh.

 

 

 

drivepool-10-20-26.jpg

  • 0
Posted
5 hours ago, Markbnj said:

Last question, I am presuming you are going to suggest I do this on the NEW system, and not the old one, correct?

If SetACL fails on the pool drive, the next step would be to run it on each of the individual poolpart folders on the physical disks that make up the pool, as described in the same post.

In theory it should not matter, since the first SetACL command is to take ownership and all of the listed SetACL commands only invoke default SIDs.

In practice I would suggest doing so on whichever system is the cleanest, i.e. the one with the least cruft running that might interfere with operations on the disks in question.

  • 0
Posted

if the permissions keep failing to be applied, running a CHKDSK pass on the underlying disks may be a good idea.  File system damage/corruption could be preventing them from being saved correctly. 

Alternatively, you can manually apply the permissions to the underlying disks, and to the "poolpart.xxxxx" folder on each drive. And this should work, even if it's erroring out on the pool. 

  • 0
Posted
On 10/22/2026 at 9:33 PM, Christopher (Drashna) said:

if the permissions keep failing to be applied, running a CHKDSK pass on the underlying disks may be a good idea.  File system damage/corruption could be preventing them from being saved correctly. 

Alternatively, you can manually apply the permissions to the underlying disks, and to the "poolpart.xxxxx" folder on each drive. And this should work, even if it's erroring out on the pool. 

OK : ANOTHER  (not so )DUMB QUESTION.  RUN THE CHKDSK ON THE UNDERLYING DISKS WHILE DRIVEPOOL IS UP AND RUNNING? 

 

Current status: have just figured out what drives are pooled, and where they are:  Will start to chk them later today.   

 

  • 0
Posted
the problem has been resolved.   The solution was to go to each individual drive and do the file permissions on that drive.
 
I did NOT need to use the setacl program once I was putting the permissions on the underlying drives.
 
I did need to continually hit alt-c to continue, after I hit one error.  Eventually it finished, and I then again took ownership changed the security permissions as suggested 
(1: changed owner to administrators)
(2: deleted other permissions )
(3: changed owner back to system)
(4: did apply-- That's where I had the occassional 'no read' error above.
5) after hitting that error I hit ALT-C (continue) until the command finished
 
HOPE THIS may help someone else in the future
  • 0
Posted

it's a bit odd that you needed to go to the individual disks, as applying permissions should apply it to the underlying disks.  

My guess is some corruption of the permissions that may have prevented it from being applied that way.

As for the CHKDSK, you can scan "online" while using the pool still, by not using the /f or /r or similar flags (should scan it in a read only mode), or by using the "/scan" flag  (this option enables "online scanning" and can fix many issues, but skips a number of checks to keep the disk only during scanning and fixing).

  • 0
Posted

So, I am doing the chkdsk on the drive-pool disks, or the underlying disks?

 

and I could (in theory) start the scan at night, from a 'dos' prompt if that would be better.

the drive -pool disk is 3 HD's totaling about 21TB

 

And yet another question.

(I am presuming that the answer will be:   DO this from the original pc, not the new one?!) 

Quote

One of the drives was not transferred as it was the  original (old-pc) boot drive

a) (presume I need to do from old pc:

remove the boot drive from the drive-pool.

 

is there a way to find out what was/is on this boot drive ?? (from the drive-pool?)  I  am guessing that  (the fact that one of the pooled drives never made it to new machine) [this] was part of the cause...

  • 0
Posted

The chkdsk is done on the individual disks.

7 hours ago, Markbnj said:

One of the drives was not transferred as it was the  original (old-pc) boot drive

a) (presume I need to do from old pc:

remove the boot drive from the drive-pool.

A pool is transferrable between machines by moving all of the drives.

If you only move some of the drives, the old and new machines (should) complain that there are drives missing (caveat: the new machine will not complain about a drive whose poolpart it has not yet seen).

If you use the DrivePool GUI to "Remove" a present drive, and other drives are missing, it will be unable to "Remove" the present drive.

7 hours ago, Markbnj said:

is there a way to find out what was/is on this boot drive ?? (from the drive-pool?)

If the old machine's boot drive was part of the pool, it will have a hidden poolpart folder like the others (where all the pool content is kept).

If you had full pool duplication enabled, the old boot drive's poolpart content should already be on the new machine (since at least one other drive should have a copy), so you could just delete the old boot drive's poolpart folder on the old machine.

If you did not have full pool duplication, or want to verify, you could compare the content of the old machine's boot drive's hidden poolpart folder with the content of the new machine's pool. You could then copy across anything missing (if you wanted to keep the old boot drive on the old PC).

9 hours ago, Markbnj said:

I  am guessing that  (the fact that one of the pooled drives never made it to new machine) [this] was part of the cause...

This should not cause ownership issues. I would suspect one of the drives simply had broken ACLs.

  • 0
Posted

 

Thank you Shane.  This is/was very helpful.  In order to make it clearer (to myself and others, I am requoting parts of your answer to make this crystal clear (for others-in future!)

I asked: 

ME--> So, I am doing the chkdsk on the drive-pool disks, or the underlying disks?

YOU-> You said: The chkdsk is (ALWAYS) done on the individual disks. (always : implied)

ME--> One of the drives (drives from pool disk) was not transferred as it was the  original (old-pc) boot drive.

  • YOU->A pool is transferrable between machines by moving all of the drives.
  • YOU--> If you only move some of the drives, the old and new machines (should) complain that there are drives missing
  •        --> (Caveat: the new machine will not complain about a drive whose poolpart it has not yet seen).

ME-->  One of the drives was not transferred as it was the  original (old-pc) boot drive.

      ME-->  I presume need to do (from the old pc):

               ME-->   remove the boot drive from the drive-pool.

YOU-> If you use the DrivePool GUI to "Remove" a present drive, and other drives are missing, it will be unable to "Remove" the present drive.

       --> (implied ) so YES, you need to bring the 'Just bunch of disks (JBOD) back to the original machine to successfully remove.

         --> This is because  if you do this on the old machine (without bringing the JBOD back to that machine), it will be unable to "Remove" the present drive.

And then I ask another (beginner?) question : 

ME-->  is there a way to find out what was/is on (the old boot drive)  ?? (from the drive-pool?)

   --> I.E., to see what may be missing from the original boot drive from the pool?

YOU-> Yes [since],  (the old machine's boot drive was part of the pool), it will have a hidden poolpart folder like the others (where all the pool content is kept).

 You ---->> (and two possible scenarios here):

  1.  you --->If full pool duplication enabled then
  •           YOU -->The old boot drive's poolpart content should already be on the new machine. 
  •                   -->         (since at least one other drive should have a copy), so you could just delete the old boot drive's poolpart folder on the old machine.

     2.                   --> f you did not have full pool duplication Enabled on [OLD machine],

                                              OR

                           --> you want to compare the content of the (old machine's boot drive) hidden poolpart folder

                                --> with the content of the new machine's pool.

                            --> You could then copy across anything missing (if you wanted to keep the old boot drive on the old PC).

 

Critical take aways (for me)  from above :

  • Chkdsks are done on UNDERLYING drives, not from the 'drive-pool' drive.  
  • A missing drive (on new system)  will not complain about a drive whose poolpart it has not yet seen).
  • A method of comparing stuff from old to new machine:

 

Thanks again, this product ROCKS!

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...