NAS542: read only subfolders after moving folders between drives

Tpedro
Tpedro Posts: 4  Freshman Member
First Comment
in Personal Cloud Storage

Hi,

I just installed a new HDD and moved some folders/files between the new/old drives.

Partially used the NAS file browser but as after a while it throws an error I used telnet to move most of the folders/files.

Some of the folders I moved are now read only.

If I enter such a folder using total commander, I cannot delete any files within, nor can I create any subfodlers.

However I can create subfolder using the NAS file browser. Then I can copy/delete files in this new folder but not the ones I moved.

Not all of the moved folder cause this error so I'm gessing it matters if I used file browser or telnet.

How can I make all my fodlers accessible again?

All Replies

  • Tpedro
    Tpedro Posts: 4  Freshman Member
    First Comment

    Managed to narrow it down:

    It seems the issues lies with the folders I moved (copied actually) with telnet (used the cp -r command).

    Let's say I have a shared folder called: 'RootFolder'

    I am able to create folders/copy files under 'RootFolder', but if I enter any subfolders: 'RootFolder\SubFolder1' then everything is read only if I use total commander or windows file explorer.

    However I am able to create folders/copy files using the nas file browser and if I create a new folder with file browser then I have full acces over it in total commander as well.

    The access for the shared folder is set read/write.

    Those subfolders that I moved with nas file browser I have full access over, no issues there whatsoever.
    (Even within the same 'RootFolder').

  • Mijzelf
    Mijzelf Posts: 2,968  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary

    How were you logged in, in telnet? If that's not root it can't copy files preserving the ownership, as only root can create files with another owner.

    Further you should have used 'cp -a', to copy the directories, to copy attributes also.

  • Tpedro
    Tpedro Posts: 4  Freshman Member
    First Comment

    I was logged in as admin.

    Managed to solve my issue by running the cmhod -r 777 command on the folders/files.

    Thanks for the tip regarding 'cp -a' didnt know about that one.

Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）