larrymcg Posted August 25, 2003 Report Share Posted August 25, 2003 Using Retrospect 6.5.283 on WinXP. I'm doing a duplicate of all files on the C: drive to another physical disk F:. The duplicate is to a subvolume (folder) named "bkup of C on F". There's two interesting things going on. Here is info out of the log: =============================================== + Retrospect version 6.5.283 Launched at 8/23/2003 10:35 PM + Executing Immediate Duplicate at 8/23/2003 10:37 PM To volume bkup of C on F on Mcg (F:)... - 8/23/2003 10:37:34 PM: Copying LMM (C:) File "C:\Documents and Settings\All Users\Application Data\Retrospect\config65.dat": appears incomplete File "C:\WINDOWS\Prefetch\RTHLPSVC.EXE-289FBD89.pf": appears incomplete File "C:\WINDOWS\Prefetch\VSSVC.EXE-0F74375A.pf": appears incomplete System configuration restored, please reboot the computer. 8/23/2003 10:40:50 PM: 3 execution errors Completed: 1440 files, 873.6 MB Performance: 308.3 MB/minute Duration: 00:03:15 (00:00:04 idle/loading/preparing) Quit at 8/23/2003 10:44 PM =========================================== 1. Should I be concerned about the three "appears incomplete" messages? I am including open files if that makes a difference. 2. Why does it say "System configuration restored, please reboot the computer" ? Thanks, Larry Link to comment Share on other sites More sharing options...
natew Posted August 26, 2003 Report Share Posted August 26, 2003 Hi The reboot message is showing up because you ave turned on the option to duplicate the registry. Retrospect knows it as duplicated the registry but is not aware that the destination was not a system folder. In other words - you can ignore this, retrospect is just a bit confused. I wouldnt worry about the prefetch files either. Are both disks formatted with NTFS? I would try running scandisk on all drives. Nate Link to comment Share on other sites More sharing options...
larrymcg Posted August 26, 2003 Author Report Share Posted August 26, 2003 The C: drive is NTFS; the F: drive is FAT32. The F: drive was the system disk off of my now dead WinMe system. ScanDisk is happy with both drives. Thanks, Larry Link to comment Share on other sites More sharing options...
awnews Posted August 26, 2003 Report Share Posted August 26, 2003 I'm running Windows XP Pro so the "scandisk" command is "chkdsk" for me. A year ago or so I was having problems with an NTFS harddisk (and couldn't "ghost" the drive to another drive, with the ghosting program failing part way thru the process) and at first couldn't figure out what was wrong. Chkdsk said everything was fine and Norton Utilities didn't find anything wrong. I eventually found that I had to run "chkdsk /r /f" (see below) to force the chkdsk command to deal with bad sectors and internal (non-OS) data structures and fix them. Chkdsk didn't do this complete check and fix by default. Sure enough, my drive had some bad sectors and after running the more extensive chkdsk (with a restart so that the program could run with the drive unlocked) the drive is fine and I can ghost it (without setting an "ignore errors" option I uncovered). I have no idea if this will make a difference for you, but it's worth being aware that a normal scandisk/chkdsk may not prove that the drive is 100% OK. ---------------------------------------------------------- Chkdsk Creates and displays a status report for a disk based on the file system. Chkdsk also lists and corrects errors on the disk. Used without parameters, chkdsk displays the status of the disk in the current drive. Syntax chkdsk [volume[[path] filename] [/f] [/v] [/r] [/x] [/c] [/lsize]] Parameters volume: Specifies the drive letter (followed by a colon), mount point, or volume name. [path] filename Specifies the location and name of a file or set of files that you want chkdsk to check for fragmentation. You can use wildcard characters (that is, * and ?) to specify multiple files. /f Fixes errors on the disk. The disk must be locked. If chkdsk cannot lock the drive, a message appears that asks you if you want to check the drive the next time you restart the computer. /v Displays the name of each file in every directory as the disk is checked. /r Locates bad sectors and recovers readable information. The disk must be locked. /x Use with NTFS only. Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated. /x also includes the functionality of /f. /i Use with NTFS only. Performs a less vigorous check of index entries, reducing the amount of time needed to run chkdsk. /c Use with NTFS only. Skips the checking of cycles within the folder structure, reducing the amount of time needed to run chkdsk. /lsize] Use with NTFS only. Changes the log file size to the size you type. If you omit the size parameter, /l displays the current size. /? Displays help at the command prompt. Link to comment Share on other sites More sharing options...
natew Posted August 27, 2003 Report Share Posted August 27, 2003 Hi For the duplicate to be 100% accurate you should use the same filesystem on both volumes if possible. A full restore of your system may not work the way you are doing things now. Nate Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.