NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
flamesong1
Jan 16, 2011Aspirant
Cannot delete problematic folder
My MacBook hung when I was copying a folder of smallish files to my ReadyNAS Duo.
I thought I ought to delete the partially copied files before I started copying them again.
The folder refused to be deleted and I set about removing the sub-folders in batches until I isolated one folder which appears to be empty.
I am logged in as admin but this 'empty' folder will not delete. The only way of getting rid of the 'Preparing to delete immediately' window is to force the Finder to restart.
Can anybody help, please?
I thought I ought to delete the partially copied files before I started copying them again.
The folder refused to be deleted and I set about removing the sub-folders in batches until I isolated one folder which appears to be empty.
I am logged in as admin but this 'empty' folder will not delete. The only way of getting rid of the 'Preparing to delete immediately' window is to force the Finder to restart.
Can anybody help, please?
17 Replies
Replies have been turned off for this discussion
- flamesong1AspirantRebooting was one of the first things I tried.
You don't think it has anything to with the é (e with an acute accent, in case it doesn't show on the forum properly) in the folder's name?
I never thought to open a support ticket - they have been pretty good in the past and exchanged two dead or dying HDs.
I have two drives in it, is that what you meant by a backup? - StephenBGuru - Experienced User
It could be related to the é, but I am thinking it is unlikely, since you are unable to delete it using two different access methods (mac and the browser). Plus, I tried it on my duo (using Windows), and I was able to delete a folder with that character in the name. My first thought would be that it was related to permissions, but you've already tried resetting those on the advanced option page.flamesong wrote: ...You don't think it has anything to with the é (e with an acute accent...
I meant a backup to a different device. RAID is not backup.flamesong wrote: I have two drives in it, is that what you meant by a backup?
The volume check would try to correct any errors it finds in the file system. Usually that is safe, but there is some risk you'd lose other files (depending on what it finds). If it were to delete something, RAID would not help you get it back - because the duo would delete it on the mirrored drive too.
If it were my system, I'd try the volume check (option on system restart), though I would at least make sure I had a copy of the critical files somewhere else first.
I'd also go in with ssh, but I wouldn't recommend that for you unless you are comfortable with linux command line stuff. I was assuming you aren't, which is why I thought you might try an on-line support request. - flamesong1AspirantHi,
I bit the bullet and did a volume check and there were no error. Incidentally, there are no problems to speak of in the disk health checks either.
I did do some SSH once but I was just following step by step instructions.
Personally, I'm not convinced it's a permissions issue because Terminal reports that it isn't even there. Incidentally, when I look at the folder in the AFP share, it says it is zero bytes but in CIFS it is 5.8 MB and yet is empty.
I have to be in the right frame of mind before I open a support case because from my experience, they can be very demanding time wise and I have a few things I need to get out of the way. - StephenBGuru - Experienced UserBTW, did you also reboot the mac? Or just the NAS?
- flamesong1AspirantI didn't reboot my Mac but I will very shortly.
- flamesong1AspirantNah!
Rebooted my Mac, no joy. - flamesong1AspirantI did it!
I don't know why I didn't do this before. I changed the name of the enclosing folder (it is a utility folder and has relative links to its contents) then created a new folder and gave it the name of the original folder. I moved the entire contents apart from the problem folder to the new folder. I then deleted the renamed enclosing folder. It took a few attempts and a ReadyNAS reboot but it eventually worked.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!