Can I fix permissions on my NTFS drives all at once?

I would not start with recursive chmod commands. On NTFS, the permissions Linux shows can depend on the driver and mount options. In some setups, chmod changes the permissions Linux presents; in others, the displayed modes are largely set when the drive is mounted. So a command that seems to fix one file may not be a reliable fix for every drive or mount.

First check how the problem drive is mounted, including its filesystem type and options. Then test a single troublesome folder and its parent. Moving or deleting an item often depends on write and execute permission on the containing directory, not just the item's own mode. Make sure you have a backup before applying changes recursively.

For a quick, low-risk route, use Windows to inspect the folders that give you trouble. Check their security permissions and whether anything is marked read-only or actively in use. If the drive is shared between Windows and Linux, Windows is also a useful way to check for filesystem problems before making a large batch of changes.

That does not mean Linux cannot write to NTFS. It just avoids guessing at what a displayed Linux mode means on a particular mount.

Be careful with mode 777. It gives every local user broad access, and it may not address the cause if the drive's permissions are being determined by mount settings or Windows ACLs. Also, a file can be impossible to delete because its parent directory is not writable, even when the file itself looks editable.

If chmod does change the troublesome items on your setup, try it on one folder first and verify the result before running anything across the whole drive.

If these drives are mainly for ordinary media and you ever decide to reformat one, exFAT is a common option for sharing files between Windows and Linux. But reformatting erases the drive, so it is not a quick permissions fix and you would need another copy of the data first. For the existing drives, check the mount configuration and test a small change rather than assuming one recursive command will behave the same everywhere.