asked on

Please help decipher this chkdsk log, it fixed our Ghost problem.

Hi Everyone,

We were getting an ODD error in our backup software (Norton Ghost), it was completing but with an odd error that took several hours with support to finally figure it out. They claimed they had never seen this before. They ended up escalating up to a software engineer who recommended doing a chkdsk /f /r. Sure enough, it fixed the problem!

Can anyone help decipher the log and let us know if it looks like anything we should be concerned about? We do believe the staff has powered it down before without a proper shutdown for what it's worth.

If anyone is interested, the odd error Norton Ghost was throwing that was finally fixed by this chkdsk was Error "E98F0004: RPAM initialisation failed." Hopefully if anyone gets it again this post will help.

The code is attached. Thanks!

A disk check has been scheduled.
Windows will now check the disk.                         
Cleaning up minor inconsistencies on the drive.
Cleaning up 218 unused index entries from index $SII of file 0x9.
Cleaning up 218 unused index entries from index $SDH of file 0x9.
Cleaning up 218 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

 488335837 KB total disk space.
  34918776 KB in 74611 files.
     23016 KB in 6601 indexes.
         0 KB in bad sectors.
    210505 KB in use by the system.
     65536 KB occupied by the log file.
 453183540 KB available on disk.

      4096 bytes in each allocation unit.
 122083959 total allocation units on disk.
 113295885 allocation units available on disk.

Internal Info:
90 6b 01 00 46 3d 01 00 76 a6 01 00 00 00 00 00  .k..F=..v.......
7c 01 00 00 06 00 00 00 e7 02 00 00 00 00 00 00  |...............
4a 12 ca 06 00 00 00 00 3a 57 4c 18 00 00 00 00  J.......:WL.....
76 cc 5e 0e 00 00 00 00 f4 94 07 0e 02 00 00 00  v.^.............
d6 ad ca 33 0a 00 00 00 04 e0 e1 7d 0c 00 00 00  ...3.......}....
99 9e 36 00 00 00 00 00 90 38 07 00 73 23 01 00  ..6......8..s#..
00 00 00 00 00 e0 45 53 08 00 00 00 c9 19 00 00  ......ES........

Open in new window

ASKER CERTIFIED SOLUTION

noxcho

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

edbedb

The log shows that errors were found on the drive and they were repaired.
Improper shut downs are a great way to mess up the file system on the hard drive.
Several hours to suggest you check the drive for errors? That is funny.

Jsmply

ASKER

Well I guess we spoke too soon. The error came back on last nights backup and Norton has no idea why it is occuring. Noxcho, no they didn't know exactly what it means. They said it refers to the "boot drive" is all he could say. At this point we don't know what else to try as Norton is stumped.

noxcho

Shame on symantec. Did you check the drive with HDD vendor made tools? The problem could be in failing drive.

Mark Kiser

Download ultimate boot CD here.
http://ubcd.sourceforge.net/download.html
It has a variety of tools including hard drive test software from most manufacturers. It has helped me with diagnosing several drive problems.

Jsmply

ASKER

Okay well we heard back from Symantec. They supposedly researched the error and they say its a registry issue or a corrupted dll and running /sfc scannow will fix the problem. We can't test that till afer the weekend. Any thoughts? Regarding the UBCD, anyone ever tried it with a RAID 1 array? Will the hard drive tests see both drives?

SOLUTION

ocanada_techguy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jsmply

ASKER

So if the chkdsk found zero bad sectors, would that lean towards the hard drive not being bad? The chkdsk log didn't seem that bad to me. The raid array info on boot says both drives are healthy. We ran the Dell diagnostic utility and it took almost 9 hours to get to 96 percent and we had to cancel the test as the staff needed the machine. It did not find any errors but took forever doing the read tests on the two drives. This was the Dell diagnostic pre boot assesment that then goes to the utility partition. We had never tried it on a raid array though. Any idea if it can accurately see both drives that way?

Oh and yes, its Windows XP and it came with sp3 integrated. Norton wants us to either do the /sfc scannow or do a system restore point to before that error began (about a week ago). They say its a system issue and it should NOT impact the database backups on this machine. They assured us those are fine. It is Ghost 15.

SOLUTION

ocanada_techguy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jsmply

ASKER

Thanks. Actually yes, Norton has to reinstall Ghost due to an update to the program. The uninstall froze and needed the Norton removal tool. The RPAM error started after that. The system works other than that and is peppy and shares a database with several machines.

noxcho

Looks like Norton was not removed completely and thus it left some traces in your registry, Try to uninstall Norton and then erase all the traces from registry via regedit - search (symntec or ghost or norton) then install Norton and see if you get these errors again.

Jsmply

ASKER

WIll do. We are going to take the machine offline this weekend so all of this can be done thoroughly and non-rushed. Will post again then. Thanks again!

Jsmply

ASKER

Thanks everyone. The machine is offline for the weekend and the diagnostic is being run. After that (assuming it checks out) we are going to take this opportunity to start with a fresh image and install Windows 7 as it's been on the list of things to for a bit. That should take care of the issue. Thanks for the help!