It is currently restoring all the files to my EX-503. I haven't checked, but I presume it uses the current time to fix the errors.Īnyway, after fixing the invalid FileTime entries, SyncToy no longer threw any errors. Surprisingly, it also offered to fix them. It found about 30 files with invalid FileTime entries. I downloaded the utility and ran it on my WHS2011. In his post he included a URL to a utility he wrote that will search a specified directory tree for files with invalid FileTime entries. I came across a thread on /forums that contained a post by a guy named ISDigital. I had no way of knowing, so I started doing some internet searching. The obvious question is, "Which file is it?". So now I knew it wasn't the file being displayed. I wasn't sure if it was the file currently showing in the progress meter or some other file, so I created a new Folder Pair of only the directory that contained the suspect file - doing a Preview of that Folder Pair did not repeat the error. When the Preview of the copy operation was almost complete it threw an error, stating that it encountered a file with an "invalid FileTime". I'm not sure why maybe it's multi-threaded of something.Īnyway, SyncToy ran into a major problem. I did a couple of quick tests and it seemed that SyncToy was faster than RoboCopy. While contemplating the task ahead, I thought it might be interesting to try using SyncToy 2.1 instead of RoboCopy. Rather than fool around with it any more, I decided to reformat the array and copy everything back to it (thank goodness I have so many backups of my data). However, when I tried to run the backup again, I got the same errors. I ran CHKDSK on the drive (NTFS) and it found a pile of problems, and supposedly fixed them. Sure enough, when I tried to access some of the directories manually, I couldn't. The RoboCopy procedure started throwing "file system corrupt" and "destination not available" errors at me. 2 days ago I was trying to do a backup of my WHS2011 ServerFolders directory to the RAID array in my Lian-Li EX-503 external enclosure when something went seriously awry.
0 kommentar(er)
