Drobo

"Error Deleting File or Folder" message (FIXED)

Hi, i noticed this error on a tmp file that was created back in november 2009, and not updated since then.
i went to delete it but windows xp sp2 gave this message:

“Error Deleting File or Folder”
& “Cannot delete TEMP2: The file or directory is corrupted and unreadable”

its about 385mb in size, and i can rightclick it to get properties dialog box, but if i try and change anything there, it says " an error occurred applying attributes to the file" and the same message as above “The file or directory is corrupted and unreadable”

its not a masssive problem, but just concerned in case theres something more sinister?

(this file is on my v1 drobo)

other info is that there another 927 objects in the same folder which all work fine. tried reboots of pc and drobo(s) etc.
wasnt sure if there is anything i need to run for this like a windows defrag or similar, just that i read somewhere else that drobo does its own checks and defrags etc so wasnt sure?

thanks,
Paul

have you tried running chkdsk on your drobo?

you should do that relatively regularly anyway

thanks doc, phase 1 running now

edit 60%
hmm it got to about 90% and sais "windows unable to complete the disk check) (i think it might have been me trying to access something meanwhile - i’ll not touch it and make a tea :slight_smile:

it didnt work…
its unable to complete it…

I tried again and ticked the auto fix checkbox, and it said =~ “windows can check it on the next restart of windows so get more access to the disk” so i said yes, but when i did a restart, nothing actually ran?

i tried checkdisk again from the rightclick-properties-tools-check now

but should i be doing this from start>run instead?

(i tried booting into safemode but windows seemed to hang on loading drivers (xp home sp2) - maybe it simply just takes a lot of time getting into safe mode with 2 drobos plugged in?

regards,
Paul

Chkdsk only gives you the ‘on next restart’ message if you have open files on the volume.

Was it being indexed? Virus scan?

You can run it from the command line and get more information that the GUI normally gives.

chkdsk “drive letter” /f

An alternate method is to set the ‘dirty’ bit for the volume so chkdsk will run automatically.

fsutil dirty set “drive letter”

Here is a link to a TechNet article on all the switches for chkdsk.
http://technet.microsoft.com/en-us/library/cc730714(WS.10).aspx

If you do get it to run and fix errors, run it again until it reports no errors.[hr]
BTW- there is a rather infamous NTFS bug that will give you that message forever on a clean file system if the file name or directory itself contains illegal characters.

The problem is NTFS will allow a file/directory to be copied with those characters (say from a ext or HFS+ volume), but then can’t touch the file/directory. You will get a ‘can’t find the file/directory specified’ or the message you are getting.

Illegal characters are: ? [ ] / \ = + < > : ; " , * |

many thanks mrgriffin, am running it in basic read only mode via command prompt currently, to see shat it says, and will then try it with the /f parameter (or /x from what i saw Jeniffer say)[hr]
hmm this is interesting:
it just ran the basic one and gave this:

chkdsk b:
The type of the file system is NTFS.
Volume label is DROBO.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)…
Deleted corrupt attribute list entry
with type code 128 in file 167240.
Truncating corrupt attribute list for file 168444.
Deleted corrupt attribute list entry
with type code 128 in file 168444.
Deleting corrupt attribute record (128, “”)
from file record segment 168457.
Deleting corrupt attribute record (128, “”)
from file record segment 168789.
Deleting corrupt attribute record (128, “”)
from file record segment 168856.
Deleting corrupt attribute record (128, “”)
from file record segment 168858.
Deleting corrupt attribute record (128, “”)
from file record segment 168860.
Deleting corrupt attribute record (128, “”)
from file record segment 168862.
Deleting corrupt attribute record (128, “”)
from file record segment 168864.
Deleting corrupt attribute record (128, “”)
from file record segment 168866.
Deleting corrupt attribute record (128, “”)
from file record segment 168868.
Deleting corrupt attribute record (128, “”)
from file record segment 168870.
Deleting corrupt attribute record (128, “”)
from file record segment 168872.
Deleting corrupt attribute record (128, “”)
from file record segment 168874.
Deleting corrupt attribute record (128, “”)
from file record segment 168876.
Deleting corrupt attribute record (128, “”)
from file record segment 168878.
Deleting corrupt attribute record (128, “”)
from file record segment 168880.
Deleting corrupt attribute record (128, “”)
from file record segment 168883.
Deleting corrupt attribute record (128, “”)
from file record segment 168885.
Deleting corrupt attribute record (128, “”)
from file record segment 168887.
Deleting corrupt attribute record (128, “”)
from file record segment 168889.
Deleting corrupt attribute record (128, “”)
from file record segment 168891.
Deleting corrupt attribute record (128, “”)
from file record segment 168894.
Deleting corrupt attribute record (128, “”)
from file record segment 168896.
81 percent completed.
then:
File verification completed.
Deleting orphan file record segment 168457.
Deleting orphan file record segment 168789.
Deleting orphan file record segment 168856.
Deleting orphan file record segment 168858.
Deleting orphan file record segment 168860.
Deleting orphan file record segment 168862.
Deleting orphan file record segment 168864.
Deleting orphan file record segment 168866.
Deleting orphan file record segment 168868.
Deleting orphan file record segment 168870.
Deleting orphan file record segment 168872.
Deleting orphan file record segment 168874.
Deleting orphan file record segment 168876.
Deleting orphan file record segment 168878.
Deleting orphan file record segment 168880.
Deleting orphan file record segment 168883.
Deleting orphan file record segment 168885.
Deleting orphan file record segment 168887.
Deleting orphan file record segment 168889.
Deleting orphan file record segment 168891.
Deleting orphan file record segment 168894.
Deleting orphan file record segment 168896.
Deleting orphan file record segment 168898.

Errors found. CHKDSK cannot continue in read-only mode.

(just running it again in the same way to see if i get the same or if it actually did fix something despite being in read only mode)[hr]
ok i ran it again and its 100% the same error.
i’ll try it with the /f[hr]
ok chkdsk /f got this far:

chkdsk b: /f
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) n

i said no here.

chkdsk /f and chkdsk /x perform the same function - /x just forces dismount of the drive before doing the repair that /f does.

In read-only mode, no changes are performed, just reports.

now ive tried this:

chkdsk b: /x
The type of the file system is NTFS.
Volume label is DROBO.

CHKDSK is verifying files (stage 1 of 3)…
25 percent completed. (so far)

time for another drink :slight_smile:
(i just hope the old saying of “if it aint broke dont fix it” doesnt come back to haunt me - after all, my drobo is working fine its just 1 poxy file sitting there :D[hr]
ok Stage 1 is complete:

CHKDSK is verifying files (stage 1 of 3)…
Deleted corrupt attribute list entry
with type code 128 in file 167240.
Truncating corrupt attribute list for file 168444.
Deleted corrupt attribute list entry
with type code 128 in file 168444.
Deleting corrupt attribute record (128, “”)
from file record segment 168457.
Deleting corrupt attribute record (128, “”)
from file record segment 168789.
Deleting corrupt attribute record (128, “”)
from file record segment 168856.
Deleting corrupt attribute record (128, “”)
from file record segment 168858.
Deleting corrupt attribute record (128, “”)
from file record segment 168860.
Deleting corrupt attribute record (128, “”)
from file record segment 168862.
Deleting corrupt attribute record (128, “”)
from file record segment 168864.
Deleting corrupt attribute record (128, “”)
from file record segment 168866.
Deleting corrupt attribute record (128, “”)
from file record segment 168868.
Deleting corrupt attribute record (128, “”)
from file record segment 168870.
Deleting corrupt attribute record (128, “”)
from file record segment 168872.
Deleting corrupt attribute record (128, “”)
from file record segment 168874.
Deleting corrupt attribute record (128, “”)
from file record segment 168876.
Deleting corrupt attribute record (128, “”)
from file record segment 168878.
Deleting corrupt attribute record (128, “”)
from file record segment 168880.
Deleting corrupt attribute record (128, “”)
from file record segment 168883.
Deleting corrupt attribute record (128, “”)
from file record segment 168885.
Deleting corrupt attribute record (128, “”)
from file record segment 168887.
Deleting corrupt attribute record (128, “”)
from file record segment 168889.
Deleting corrupt attribute record (128, “”)
from file record segment 168891.
Deleting corrupt attribute record (128, “”)
from file record segment 168894.
Deleting corrupt attribute record (128, “”)
from file record segment 168896.
File verification completed.
Deleting orphan file record segment 168457.
Deleting orphan file record segment 168898.

CHKDSK is verifying indexes (stage 2 of 3)…[hr]
hmm 22minutes and still at 0% :slight_smile:

CHKDSK is verifying indexes (stage 2 of 3)…
0 percent completed.

(i gave cmd and chkdsk higher cpu priority in xp just in case it helps)
time to sleep on it i think :slight_smile:

Yes, sleep on it. Chkdsk can take a LONG time.

cool - i got lucky :slight_smile:

Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)…
Security descriptor verification completed.
Inserting data attribute into file 167240.
Inserting data attribute into file 168444.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

2147480810 KB total disk space.
1734444876 KB in 388010 files.
219948 KB in 19508 indexes.
0 KB in bad sectors.
549690 KB in use by the system.
65536 KB occupied by the log file.
412266296 KB available on disk.

  4096 bytes in each allocation unit.

536870202 total allocation units on disk.
103066574 allocation units available on disk.

now for the ultimate test… can that file be zapped…[hr]
Excellent - the file became 0bytes, and i was able to send it to the recycling bin and then empty the bin :slight_smile:
phew - thanks a lot for the help guys

you should run chkdsk relatively regularly (monthly?).

drobo protects against hard disk failure/errors - if your file systems gets corrupted then drobo will simply carry on protecting that corrupted file system

ok thanks indeed, i’ll be sure to do that.
i’ll set a chkdsk on my v2 drobo too

What is the OS X equivalent to chkdisk? I just ran into an issue last night where I can no longer write files to my Drobo. Keeps crashing midway through. I can’t delete the temporary files that are created either. I should note that my Drobo is connected to a DroboShare over the network. Do I need to plug it directly into my Mac and use disk utility?

hi alkie, i dont have a mac (and havent used my droboshare yet) but i believe the norm is to plug the drobo direct to the mac via usb, and to use something called drisk warrior but best to double check.

Disk Utility first, if that doesn’t work, then DRI has recommended Disk Warrior in the past.