Hi Elizabeth et al,
My landlord's PC can't complete the initialisation of the Operating System (OS) due to a damaged File System.
The error message indicates a file (Windows\AppPatch\drvmain.sdb) is damaged and that to repair it the Original CD-ROM should be used to initiate a Repar of the Installation.
However, unfortunately, my landlord doesn't have that CD and nor do I have a copy.
Using GParted Live on a USB Flash drive to Boot the PC I was able to obtain the following details.
Some of the information I found on the Internet, however, indicates that "chkdsk /f" can sometimes make things worse.
So, before I try to use that as a final option, I was wanting to know what actually happens when a person chooses the Repair option for an installation from an Original CD-ROM? Does the Repair process actually use "chkdsk /f" also? And then, what happens next?
Using the ntfsfix utility, which is included with GParted Live, the following information was obtained.
Second part to follow ...
My landlord's PC can't complete the initialisation of the Operating System (OS) due to a damaged File System.
The error message indicates a file (Windows\AppPatch\drvmain.sdb) is damaged and that to repair it the Original CD-ROM should be used to initiate a Repar of the Installation.
However, unfortunately, my landlord doesn't have that CD and nor do I have a copy.
Using GParted Live on a USB Flash drive to Boot the PC I was able to obtain the following details.
Code:
Check and repair file system (ntfs) on /dev/sda1 00:00:01 ( ERROR )
calibrate /dev/sda1 00:00:00 ( SUCCESS )
path: /dev/sda1
start: 63
end: 32772599
size: 32772537 (15.63 GiB)
check file system on /dev/sda1 for errors and (if possible) fix them 00:00:01 ( ERROR )
ntfsresize -i -f -v /dev/sda1
ntfsresize v2014.2.15AR.1 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 16779538944 bytes (16780 MB)
Current device size: 16779538944 bytes (16780 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
100.00 percent completed
Accounting clusters ...
Cluster accounting failed at 101901 (0x18e0d): extra cluster in $Bitmap
Cluster accounting failed at 101902 (0x18e0e): extra cluster in $Bitmap
Cluster accounting failed at 101903 (0x18e0f): extra cluster in $Bitmap
Cluster accounting failed at 101904 (0x18e10): extra cluster in $Bitmap
Cluster accounting failed at 101905 (0x18e11): extra cluster in $Bitmap
Cluster accounting failed at 101906 (0x18e12): extra cluster in $Bitmap
Cluster accounting failed at 101907 (0x18e13): extra cluster in $Bitmap
Cluster accounting failed at 101908 (0x18e14): extra cluster in $Bitmap
Cluster accounting failed at 101909 (0x18e15): extra cluster in $Bitmap
Cluster accounting failed at 101910 (0x18e16): extra cluster in $Bitmap
Cluster accounting failed at 101911 (0x18e17): extra cluster in $Bitmap
Cluster accounting failed at 101912 (0x18e18): extra cluster in $Bitmap
Cluster accounting failed at 1596926 (0x185dfe): missing cluster in $Bitmap
Cluster accounting failed at 1596927 (0x185dff): missing cluster in $Bitmap
Cluster accounting failed at 1596928 (0x185e00): missing cluster in $Bitmap
Cluster accounting failed at 1596929 (0x185e01): missing cluster in $Bitmap
Cluster accounting failed at 1596930 (0x185e02): missing cluster in $Bitmap
Cluster accounting failed at 1596931 (0x185e03): missing cluster in $Bitmap
Cluster accounting failed at 1596932 (0x185e04): missing cluster in $Bitmap
Cluster accounting failed at 1596933 (0x185e05): missing cluster in $Bitmap
Cluster accounting failed at 1596934 (0x185e06): missing cluster in $Bitmap
Cluster accounting failed at 1596935 (0x185e07): missing cluster in $Bitmap
Cluster accounting failed at 1596936 (0x185e08): missing cluster in $Bitmap
Cluster accounting failed at 1596937 (0x185e09): missing cluster in $Bitmap
Cluster accounting failed at 1603961 (0x187979): extra cluster in $Bitmap
Cluster accounting failed at 1604195 (0x187a63): extra cluster in $Bitmap
Cluster accounting failed at 1604270 (0x187aae): extra cluster in $Bitmap
Cluster accounting failed at 1604804 (0x187cc4): extra cluster in $Bitmap
Cluster accounting failed at 1605595 (0x187fdb): extra cluster in $Bitmap
Cluster accounting failed at 1605598 (0x187fde): extra cluster in $Bitmap
Filesystem check failed! Totally 30 cluster accounting mismatches.
ERROR: NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
and will be made to NTFS by this software until it gets repaired.Some of the information I found on the Internet, however, indicates that "chkdsk /f" can sometimes make things worse.
So, before I try to use that as a final option, I was wanting to know what actually happens when a person chooses the Repair option for an installation from an Original CD-ROM? Does the Repair process actually use "chkdsk /f" also? And then, what happens next?
Using the ntfsfix utility, which is included with GParted Live, the following information was obtained.
Code:
ntfsfix /dev/sda1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda1 was processed successfully.Second part to follow ...
