Restoring the MBR: How the heck do you RUN MbrFix.exe?? Won't run in DOS and it won't run in XP!

[computer]

I'm hoping someone is familiar with this program, or knows how
to restore the MBR.

I don't understand this. I've d'loaded MbrFix.exe and no where
do they state, what to do next!
http://www.sysint.no/nedlasting/mbrfix.htm . I put it on a
floppy and it's not bootable! I put in on a BOOTABLE floppy
and tried to run it, and it actually says "This program cannot
be run in DOS"!!!! WTF?? It can't be run in Windows either!
So, how the heck do you run it? Murmur chants?? :Q

I made the fatal mistake of putting that POS Ghost (2003) on a
customer's PC and now the HD is toast. I tried to create a
backup with an external HD in a USB enclosure (something I
always do with NO PROBLEM), and it kept hanging and
crashing/freezing up while in that Ghost PC-DOS area. I tried
several times, same thing. Then, when I tried to get back into
XP, the damn thing wouldn't boot!! I would choose the option
to cancel then boot back into XP and it just sat there and did
nothing. If I'd get to a screen where it says Ghost failed,
and it "would return to XP in X seconds", it never did!! This
is BS, doesn't work. http://tinyurl.com/yac6ep . "Ghreboot" and
"Gdisk" was a total waste of time.

I tried ptedit.exe http://www.goodells.net/multiboot/ptedit.htm
recommend here:
http://archive.midrange.com/pctech/200507/msg00018.html and did
what that dude said that FIXED his EXACT problem as mine, but
it didn't do JACK other than make things worse!

I tried booting off the XP CD and doing a "repair" and "fixmbr"
and it said it FIXED IT, DONE, yet when I try and boot it says
"DISK BOOT FAILURE".

I even tried hooking up the HD to my PC, going into the Admin
tools area and Computer Management, then deleting that "spawned
from hell" Ghost 8mb partition, and that didn't even work!!
ALL of the files are STILL THERE on the HD; Windows,
Program Files, even all the boot.ini, autoexec.bat, ntldr,
etc., files!

So POH-LEEZE can someone tell me how to make this #%$&! drive
so it can boot back into XP??
Thank you.

 

[Bozo]

From the repair consul, have you tried 'fixboot' ??

http://www.microsoft.com/resources/docu...cs/en-us/bootcons_fixmbr.mspx?mfr=true

Bozo

 

[computer]

Originally posted by: Bozo
From the repair consul, have you tried 'fixboot' ??

http://www.microsoft.com/resources/docu...cs/en-us/bootcons_fixmbr.mspx?mfr=true

Bozo

Thanks for replying, but that didn't work. To show you how much of a dumb-ass Windows is, it said: "FIXBOOT cannot find the system drive, or the drive specified is not valid"!! If it ain't there or it's not valid, then how the hell can I do a "help" at the Windows prompt and SEE the list of hundreds of files, including "FIXMBR", "FIXBOOT", etc. etc!

 

[computer]

So I just tried "fixboot c:", and it said the new boot area was created successfully or something like that, I restarted, and I got:
"Building DMI pool........success"
"Verifying DMI pool data......success"

Then, immediately after, the same crap!
"DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ANY ENTER".
WTF is going on here???? :disgust: :frown: :shocked:

 

[Brazen]

I would boot to the XP recovery console and do "FIXMBR" and then "FIXBOOT"

 

[computer]

Originally posted by: Brazen
I would boot to the XP recovery console and do "FIXMBR" and then "FIXBOOT"

Thanks...still didn't work, still the same thing. I did a "fixboot C:" since it won't work with just "fixboot". Each time I do the fixmbr or fixboot, it says it was "successfully created" or "successfully written"!!

 

[computer]

I'm even able to run through the "bootcfg" options with no problems!! It sees the boot info, lists it, I also tried setting "default" for the boot option.

 

[jlbenedict]

Is the BIOS even detecting your drive?
You know....


"Building DMI pool........success"
"Verifying DMI pool data......success"

"IDE Drive 0: WDC blah blah"
"IDE Drive 1: Some sort of cdrom"..


It should list the drives too, before actually booting..

 

[computer]

I ran chkdsk from the RC and it said "the disk appears to be in good shape" so no additional checking was done. Then I ran the chkdsk /p so it would really check it well, it said the usual "checkdisk found one or more errors on the drive" (like it always does regardless of the drive) and didn't say if it fixed them...also as usual. That didn't work.

 

[computer]

Originally posted by: jlbenedict
Is the BIOS even detecting your drive?
You know....


"Building DMI pool........success"
"Verifying DMI pool data......success"

"IDE Drive 0: WDC blah blah"
"IDE Drive 1: Some sort of cdrom"..


It should list the drives too, before actually booting..

Yeah I just mentioned that above. It's seen at POST, in the BIOS, and when it boots I get:
"Building DMI pool........success"
"Verifying DMI pool data......success"

Then, immediately after, the same crap!
"DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ANY ENTER".
WTF is going on here????

There's nothing wrong with the drive nor files on it, like I said I can go into all folders on it when it's hooked up to my main PC and ALL of the typical XP files are there in the root directory! It's just the MBR or boot record somewhere is fried!

 

[computer]

FWIW, when I run fixmbr, it says something like "the disk appears to have an unconventional boot sector" or something like that, and that if I continue "the partitions may be not be accessible" and to only run it if I "cannot access the drive otherwise". That's NOT verbatim, that's just going from memory which is pretty shot right now from exhaustion.

Symantec should be shot for creating something that can do this kind of damage. Ironic isn't it, a BACKUP TOOL that destroys your f'ing HD.

 

[Scitex]

You may want to try the solution from the third post in this thread:
http://www.thetechlounge.com/forum/archive/index.php/t-2419.html

 

[computer]

I hope by tonight someone has a "genius fix" for this. I have to go get some sleep now. :disgust: If not, I'm going to have to reformat the SOB and start all over again....setting up XP, installing tons of drivers and software along with hours and hours of software settings. I should send the #$@!%& bill to Symantec. I hate computers.

 

[computer]

Originally posted by: Scitex
You may want to try the solution from the third post in this thread:
http://www.thetechlounge.com/forum/archive/index.php/t-2419.html

Thank you, but I already mentioned in my first post that I tried that and it didn't work... This is BS, doesn't work. http://tinyurl.com/yac6ep . "Ghreboot" and
"Gdisk" was a total waste of time.

It just hangs there and does nothing after I try and run them. The cursor goes down the next line, and blank line, and just flashes there. The HD LED stays on, 15 minutes, half an hour go by, etc., still just stays there in "DOS" or whatever it is.

 

[computer]

Well, I apparently got it fixed. Out of desperation, I booted from the Ghost 10 CD. (I didn't install it because I'm unfamiliar with it, heard bad things about it, and I never had a single issue with Ghost 2003 before).

I got to a nice GUI interface with a host of tools. I tried them all, so I don't know which one worked. All I remember is "Fix MBR", something about making a partition active, and maybe 4 or 5 other areas I tried. One of them worked. Through all these areas, these checks and info, it never once said anything was wrong with the drive! If this tells anyone anything, this is from something Ghost 10 calls "SME Dump", it does say errors in there, but I have no idea what it means since like I said, this SME and Ghost 10 are totally new to me. It may be normal. Errors I noticed I made bold.

(Root) SME
Kind PropertyId Root
Computer Array array[1] = {SME~Computer}
Name String SME
Version String 2005-09-09T18:25:54Z -- SquawPeak

(Computer) SME~Computer
Kind PropertyId Computer
Description String Microsoft Windows Server 2003 PE 5.2.3790
Device Array array[1] = {SME~Computer~Sg1E59944C}
Disk Group Array array[1] = {SME~Computer~BgM509187148Region-0}
Encoding uint32 1252 (4e4h)
File System Encoding uint32 437 (1b5h)
Installed Software Array array[2] = {SME~Computer~Is12258533:283181262-SME~Computer~BgM509187148Region-0~VM50918714
Region-0-1~Fs1/WINDOWS/, SME~Computer~Is12258534:12258278-SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/boot.ini}
Name String MININT-JVC
Root ObjectId SME

(Device) SME~Computer~Sg1E59944C
Kind PropertyId Device
Computer ObjectId SME~Computer
Device Id String M509187148
Device Number uint32 0
Is Available bool true
Is Media Removable bool false
Location String
Media ObjectId SME~Computer~Sg1E59944C~M509187148
Media Type StringId Fixed
Model String
Name String \\.\PhysicalDrive0
Serial Number String

(Media) SME~Computer~Sg1E59944C~M509187148
Kind PropertyId Media
Device ObjectId SME~Computer~Sg1E59944C
Is Missing bool false
Is Mounted bool true
Region Array array[1] = {SME~Computer~Sg1E59944C~M509187148~M509187148Region-0}
Sector Count uint64 72303840 (44f44e0h)
Sector Size uint32 512 (200h)
Size uint64 37019566080 (89e89c000h)

(Region) SME~Computer~Sg1E59944C~M509187148~M509187148Region-0
Kind PropertyId Region
Disk Group ObjectId SME~Computer~BgM509187148Region-0
Disk Layout ObjectId SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1
Is Restricted bool false
Is in known DiskGroup bool true
Media ObjectId SME~Computer~Sg1E59944C~M509187148
Offset On Media uint64 0
Sector Count uint64 72303840 (44f44e0h)
Segment Array array[2] = {SME~Computer~BgM509187148Region-0~SM509187148Region-0-1, SME~Computer~BgM509187148Region-0~SM509187148Region-0-2}
Size uint64 37019566080 (89e89c000h)

(Disk Layout) SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1
Kind PropertyId Disk Layout
Partition Array array[1] = {SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1~P63}
Region ObjectId SME~Computer~Sg1E59944C~M509187148~M509187148Region-0
Type StringId MBR

(Partition) SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1~P63
Kind PropertyId Partition
Disk Layout ObjectId SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1
Has Redirected Sectors bool false
Is Active bool true
Is Hidden bool false
Is Logical bool false
Offset On Media uint64 63 (3fh)
Partition Data Start uint64 0
Partition Name String
Partition Type StringId IFS (HPFS, NTFS), QNX, Advanced Unix
Sector Count uint64 72276372 (44ed994h)
Segment Array array[1] = {SME~Computer~BgM509187148Region-0~SM509187148Region-0-1}
Virtual Partition ObjectId SME~Computer~BgM509187148Region-0~VP1
Volume Usage Type StringId Basic Data

(Disk Group) SME~Computer~BgM509187148Region-0
Kind PropertyId Disk Group
Computer ObjectId SME~Computer
Extended Partition empty
Region Array array[1] = {SME~Computer~Sg1E59944C~M509187148~M509187148Region-0}
Segment Array array[2] = {SME~Computer~BgM509187148Region-0~SM509187148Region-0-1, SME~Computer~BgM509187148Region-0~SM509187148Region-0-2}
Sub Type StringId Unknown
Type StringId Basic
Virtual Partition Array array[1] = {SME~Computer~BgM509187148Region-0~VP1}
Volume Array array[1] = {SME~Computer~BgM509187148Region-0~VM509187148Region-0-1}

(Segment) SME~Computer~BgM509187148Region-0~SM509187148Region-0-1
Kind PropertyId Segment
Can Create Logical bool false
Can Create Primary bool false
Disk Group ObjectId SME~Computer~BgM509187148Region-0
Is Allocated bool true
Is Logical bool false
Offset In Volume uint64 0
Offset On Media uint64 63 (3fh)
Partition ObjectId SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1~P63
Partition Type uint32 7
Partition Type Label StringId IFS (HPFS, NTFS), QNX, Advanced Unix
Position in Volume uint32 0
Region ObjectId SME~Computer~Sg1E59944C~M509187148~M509187148Region-0
Sector Count uint64 72276372 (44ed994h)
Sector Size uint32 512 (200h)
Size uint64 37005502464 (89db32800h)
Volume Replicant ObjectId SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~R1

(Segment) SME~Computer~BgM509187148Region-0~SM509187148Region-0-2
Kind PropertyId Segment
Can Create Logical bool true
Can Create Primary bool true
Disk Group ObjectId SME~Computer~BgM509187148Region-0
Is Allocated bool false
Is Logical bool false
Offset In Volume uint64 0
Offset On Media uint64 72276435 (44ed9d3h)
Partition empty
Partition Type uint32 0
Partition Type Label StringId Unused or unknown
Position in Volume uint32 0
Region ObjectId SME~Computer~Sg1E59944C~M509187148~M509187148Region-0
Sector Count uint64 16065 (3ec1h)
Sector Size uint32 512 (200h)
Size uint64 8225280 (7d8200h)
Volume Replicant empty

(Volume) SME~Computer~BgM509187148Region-0~VM509187148Region-0-1
Kind PropertyId Volume
Disk Group ObjectId SME~Computer~BgM509187148Region-0
File System ObjectId SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1
Installed Software Array array[2] = {SME~Computer~Is12258533:283181262-SME~Computer~BgM509187148Region-0~VM50918714
Region-0-1~Fs1/WINDOWS/,{SME~Computer~Is12258533:283181262-SME~Computer~BgM509187148Region-0~VM50918714
Region-0-1~Fs1/WINDOWS/, SME~Computer~Is12258534:12258278-SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/boot.ini}
Is Active bool true
Is Hidden bool false
Is Lockable bool true
Is Mounted bool true
Minimum Sotf Size uint64 5462290944 (14593f200h)
Mount Points Array array[1] = {C:\}
Mount state StringId Mounted
Partition Oriented Type StringId NTFS
Retarget Required bool false
Sector Count uint64 72276372 (44ed994h)
Sector Size uint32 512 (200h)
Size uint64 37005502464 (89db32800h)
Uses Restricted Region bool false
Volume Name String BasicDiskVolume-M509187148Region-0-1
Volume Replicant Array array[1] = {SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~R1}
Volume Status StringId Healthy
Volume Type StringId Simple
Volume Usage Type StringId Basic Data

(Volume Replicant) SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~R1
Kind PropertyId Volume Replicant
Segment Array array[1] = {SME~Computer~BgM509187148Region-0~SM509187148Region-0-1}
Volume ObjectId SME~Computer~BgM509187148Region-0~VM509187148Region-0-1

(File System) SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1
Kind PropertyId File System
Cluster Count uint64 9034546 (89db32h)
Cluster Size uint32 4096 (1000h)
Creation Date and Time uint32 0
Encoding uint32 65001 (fde9h)
Free Bytes uint64 33856053248 (7e1fa6000h)
Is File Access Available bool true
Label String
Last Modified Date and Time uint32 0
Sector Count uint64 72276368 (44ed990h)
Sector Size uint32 512 (200h)
Serial Number String 14181860682057063916
Type StringId NTFS
Used Bytes uint64 3149447168 (bbb8c000h)
Version String 3.1
Volume ObjectId SME~Computer~BgM509187148Region-0~VM509187148Region-0-1

(Virtual Partition) SME~Computer~BgM509187148Region-0~VP1
Kind PropertyId Virtual Partition
Disk Group ObjectId SME~Computer~BgM509187148Region-0
Partition Array array[1] = {SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1~P63}

(Partition) SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1~P63
Kind PropertyId Partition
Disk Layout ObjectId SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1
Has Redirected Sectors bool false
Is Active bool true
Is Hidden bool false
Is Logical bool false
Offset On Media uint64 63 (3fh)
Partition Data Start uint64 0
Partition Name String
Partition Type StringId IFS (HPFS, NTFS), QNX, Advanced Unix
Sector Count uint64 72276372 (44ed994h)
Segment Array array[1] = {SME~Computer~BgM509187148Region-0~SM509187148Region-0-1}
Virtual Partition ObjectId SME~Computer~BgM509187148Region-0~VP1
Volume Usage Type StringId Basic Data

(Installed Software) SME~Computer~Is12258533:283181262-SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/WINDOWS/
Kind PropertyId Installed Software
Computer ObjectId SME~Computer
Location String SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/WINDOWS/
Sub Type StringId Microsoft Windows XP
Type StringId Installed OS
Volume Array array[1] = {SME~Computer~BgM509187148Region-0~VM509187148Region-0-1}

(Installed Software) SME~Computer~Is12258534:12258278-SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/boot.ini
Kind PropertyId Installed Software
Computer ObjectId SME~Computer
Location String SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/boot.ini
Sub Type StringId NT Boot Manager
Type StringId Boot Manager
Volume Array array[1] = {SME~Computer~BgM509187148Region-0~VM509187148Region-0-1}

-------------------------------------------------------------
Debug Log Contents

* 2006-12-27T12:21:48.8900000Z Main Thread(1176)
---------------------------------------------------------
Starting Application Debug Log


* 2006-12-27T12:21:48.9060000Z Main Thread(1176) Context: UTIL_MON : ERR
.\UmResourceWin.cpp(113) Function: `anonymous-namespace'::LocalizedCounter::LocalizedCounter
error getting required buffer size, error# 2

* 2006-12-27T12:21:48.9210000Z Main Thread(1176) Context: SME : INFO
.\SmeCommon.cpp(373) Function: SmeCommon::Initialize
----------------------------- Starting Engine Initialization -------------------------------------

* 2006-12-27T12:21:48.9210000Z Main Thread(1176) Context: SME : WARN
.\Win2kMountPoints.cpp(206) Function: `anonymous-namespace'::InitializeLogicalDrives
InitializeLogicalDrives::GetVolumeNameForVolumeMountPointW error 1 for "Z:\"

* 2006-12-27T12:21:48.9210000Z Main Thread(1176)

Windows Mount Point Map
--------------------------------
[DRIVE_REMOVABLE ] A:\ --> \\?\Volume{0aab06b0-95a3-11db-aea4-806e6f6e6963}\ --> \Device\Floppy0
[DRIVE_FIXED ] C:\ --> \\?\Volume{0aab06b4-95a3-11db-aea4-806e6f6e6963}\ --> \Device\HarddiskVolume1
[DRIVE_CDROM ] E:\ --> \\?\Volume{0aab06b2-95a3-11db-aea4-806e6f6e6963}\ --> \Device\CdRom1
[DRIVE_CDROM ] X:\ --> \\?\Volume{0aab06b1-95a3-11db-aea4-806e6f6e6963}\ --> \Device\CdRom0
[DRIVE_FIXED ] Z:\ --> --> \Device\Ramdrv


Win2kComputer Mount Point Map
--------------------------------
[DRIVE_FIXED ] C:\ --> \\?\Volume{0aab06b4-95a3-11db-aea4-806e6f6e6963}\ --> \Device\HarddiskVolume1


* 2006-12-27T12:21:48.9370000Z ThrottleRunner(1180) Context: PROCESS : THREAD
New Thread is running

* 2006-12-27T12:21:48.9370000Z Main Thread(1176)
DeviceCommon constructor: unique id: Sg1E59944C name: \\.\PhysicalDrive0

* 2006-12-27T12:21:48.9370000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(836) Function: WinNtDevice::GetDeviceCharacteristics
GetDriveGeometry succeeded for \\.\PhysicalDrive0. Cyls: 4500, Hds: 255, Scts: 63, BPS: 512.

* 2006-12-27T12:21:48.9370000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(1147) Function: WinNtDevice::CheckKernelDeviceName
The kernel device name for \\.\PhysicalDrive0 is \Device\Harddisk0\DR0.

* 2006-12-27T12:21:48.9370000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(891) Function: WinNtDevice::GetDeviceCharacteristics
IOCTL_DISK_GET_PARTITION_INFO returned 72303840 bytes.

* 2006-12-27T12:21:48.9370000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(898) Function: WinNtDevice::GetDeviceCharacteristics
maxSectorCount is now 72303840 sector(s).

* 2006-12-27T12:21:48.9370000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(958) Function: WinNtDevice::GetDeviceCharacteristics
GetScsiFormatAndGeometry on \\.\PhysicalDrive0 returned. Cyls: 35304, Hds: 64, Scts: 32, BPS: 512, SctCnt: 72303840.

* 2006-12-27T12:21:48.9370000Z Main Thread(1176) Context: RESULT_CLASS : RESULT
Error 00000001: Incorrect function.

* 2006-12-27T12:21:48.9370000Z Main Thread(1176) Context: RESULT_CLASS : RESULT
e0bb0107
1: \\.\PhysicalDrive0
2: IOCTL_SCSI_RESCAN_BUS
3: Error 00000001: Incorrect function.
Error SME_ERROR_IOCTL_FAILED (E0BB0107): Ioctl call IOCTL_SCSI_RESCAN_BUS to device \\.\PhysicalDrive0 failed. Error 00000001: Incorrect function.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: RESULT_CLASS : RESULT
e0bb010f
1: IDENTIFY DEVICE
2: \\.\PhysicalDrive0
3: Error E0BB0107: Ioctl call IOCTL_SCSI_RESCAN_BUS to device \\.\PhysicalDrive0 failed. Error 00000001: Incorrect function.
Error SME_ERROR_SENDING_ATA_COMMAND_FAILED (E0BB010F): Sending the ATA command IDENTIFY DEVICE failed for device '\\.\PhysicalDrive0'. Error SME_ERROR_IOCTL_FAILED (E0BB0107): Ioctl call IOCTL_SCSI_RESCAN_BUS to device \\.\PhysicalDrive0 failed. Error 00000001: Incorrect function.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(1027) Function: WinNtDevice::GetDeviceCharacteristics
The NT Drive Signature for \\.\PhysicalDrive0 is 509187148.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(1050) Function: WinNtDevice::GetDeviceCharacteristics
Creating a media common for \\.\PhysicalDrive0, with 509187148 as the NT Drive Signature.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : INFO
.\WinNtDevice.cpp(2948) Function: WinNtDevice::CheckGoBackEnabled
GoBack is not active on device \\.\PhysicalDrive0

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : ERR
.\WinNtDevice.cpp(2465) Function: WinNtDevice::GetDriveGeometry
Unable to get handle for \\.\PhysicalDrive1 Error: The system cannot find the file specified.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : ERR
.\WinNtDevice.cpp(2465) Function: WinNtDevice::GetDriveGeometry
Unable to get handle for \\.\PhysicalDrive2 Error: The system cannot find the file specified.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : ERR
.\WinNtDevice.cpp(2465) Function: WinNtDevice::GetDriveGeometry
Unable to get handle for \\.\PhysicalDrive3 Error: The system cannot find the file specified.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : ERR
.\WinNtDevice.cpp(2465) Function: WinNtDevice::GetDriveGeometry
Unable to get handle for \\.\PhysicalDrive4 Error: The system cannot find the file specified.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: DEVICE : ERR
.\WinNtDevice.cpp(2465) Function: WinNtDevice::GetDriveGeometry
Unable to get handle for \\.\PhysicalDrive5 Error: The system cannot find the file specified.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: RESULT_CLASS : RESULT
Warning SME_DEVICE_UNSUPPORTED (A0BB006A): The device type is not supported.

* 2006-12-27T12:21:48.9530000Z Main Thread(1176)

GetDriveLayout for drive: 1E59944C
PartitionStyle: MBR
PartitionCount: 4
Part StartingOffset PartitionLength PN PT BI Recgnz HidSects
---- ----------------- ------------------ -- -- -- ------ --------
0 7E00 89DB32800 1 7 0 1 3F
1 0 0 0 0 0 0 0
2 0 0 0 0 0 0 0
3 0 0 0 0 0 0 0


* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: SME : INFO
.\DiskLayoutFactory.cpp(96) Function: DiskLayoutFactory::Create
DiskLayout for SME~Computer~Sg1E59944C~M509187148~M509187148Region-0~L1 is WinNtMbrDisk

* 2006-12-27T12:21:48.9530000Z Main Thread(1176) Context: RESULT_CLASS : RESULT
Error ERROR_ERRORS_EXIST (EBAB0005): Errors exist.

* 2006-12-27T12:21:49Z Main Thread(1176) Context: BASE : INFO
.\OsVersion.cpp(1026) Function: OsVersion::TestForWindows
Loading registry hive file:///C:/WINDOWS/system32/config/system

* 2006-12-27T12:21:49.1250000Z Main Thread(1176) Context: BASE : INFO
.\OsVersion.cpp(1149) Function: OsVersion::TestForWindows
LoadHive ():Loading registry hive file:///C:/WINDOWS/system32/config/SECURITY

* 2006-12-27T12:21:49.1250000Z Main Thread(1176) Context: SME : INFO
.\SmeCommon.cpp(400) Function: SmeCommon::Initialize
----------------------------- DiscoRoot Initialize -------------------------------------

* 2006-12-27T12:21:50.9060000Z Main Thread(1176) Context: TIMING : INFO
SmeCommon::Initialize (Pre-Apply)
Result: Success!

CPU Speed: 2992MHz
TimingData
App Total : 1 2.001
Section Total : 1 2.001
Computer Initialization : 1 0.202
Init All Devices : 1 0.020
Init Windows Devices : 1 0.020
ThrottleRunner : 19 0.000 0.000001
ThrottledObject:\\.\PhysicalDrive0 : 51 0.000 0.000000
Init Windows device \\.\PhysicalDrive0 : 1 0.018
SB Cache Init : 8 0.000 0.000001
SB Cache Read : 3 0.001 0.000289
NT SPhyDrv0:Read : 51 0.038 0.000748
Init all diskgroups : 1 0.021
Init Windows MbrDisk : 1 0.002
Init Dynamic diskgroups : 1 0.000
IsLdm(M509187148Region-0) : 1 0.000
Init BasicDisk BgM509187148Region-0 : 1 0.018
SB User Read : 9 0.039 0.004318
SB Cache Init : 27 0.000 0.000003
SB Cache Read : 48 0.037 0.000777
Init Volume VM509187148Region-0-1 : 1 0.000
FSFactory::Create(1) BasicDiskVolume-M509187148Region-0-1: 1 0.000
DG::GenerateMetaData BasicDiskVolume-M509187148Region-0-1: 1 0.008
LinkVolumes : 1 0.000
Enumerate Snapshot Devices : 1 0.000
Init InstalledSoftwares : 1 0.160
File Open: OS: kernel32.dll : 1 0.003
File Read: OS: kernel32.dll : 15 0.001 0.000043
File Close: OS: kernel32.dll : 1 0.000
ThrottledObject:LogicalDriveC: : 15 0.000 0.000000
File Open: OS: SECURITY : 1 0.000
File Read: OS: SECURITY : 17 0.000 0.000003
File Close: OS: SECURITY : 1 0.000
sme init : 1 0.066


* 2006-12-27T12:21:50.9060000Z Main Thread(1176) Context: SME : INFO
Partition Info:
Computer: MININT-JVC

DiskGroup: SME~Computer~BgM509187148Region-0 (Basic): 34.5 GB
DL A L FileSys Label Clust FS Size FS Used DN StartSector EndSector PT Layout Rep FS Serial Number Segment Name Volume Name
=== = = ======= ==================== ===== ======= ======= == ============= ============= == ======== === ==================== ========================= =========================
C: A P NTFS 4096 34.5 GB 2.93 GB 0 63 72276435 07 Simple 14181860682057063916 SM509187148Region-0-1 VM509187148Region-0-1
P 7.84 MB 0 72276435 72292500 SM509187148Region-0-2

Installed Software:
Installed OS : Microsoft Windows XP : SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/WINDOWS/
Boot Manager : NT Boot Manager : SME~Computer~BgM509187148Region-0~VM509187148Region-0-1~Fs1/boot.ini

Known Threads:
Main Thread(1176)
ThrottleRunner(1180)

* 2006-12-27T12:21:50.9060000Z Main Thread(1176) Context: SME : INFO
.\SmeCommon.cpp(434) Function: SmeCommon::Initialize
----------------------------- Finished Engine Initialization -------------------------------------

 

[greylica]

The only thing you have to do is simple, but it was done. At least one Drive and One partition on your hard drive have to be active even if you had things on MBR or not. what tyou have to do is simple in this case, Put an Xp disk and Iniciate the disc one, format in an kind of partition ( the same as it was used by Ghost ), the first partition of the fiirst hard drive was initiated by windows is set to active by default. After all, is all done by the ghost archive.

If you do an Fdisk for the first time on any recognized hard drive , the 98 boot diskette will ask you " Set the first partition as active ", normally you will say Yes and everything work fine. If you do not do this, even if you put all the archives and the command.com in place, it will not boot.

 

[computer]

Well as I feared, it's still f**ked up. BSOD when I shut it down tonight. Earlier today it was FINE.

First it hung when I tried to shut it down, the finally went out of Windows, then the BSOD.

KERNEL_DATA_INPAGE_ERROR
STOP: 0x0000007A (0xE1687290 [etc]
win32k.sys BF849924 base at BF800000 [etc]

I'm researching that right now. I ran a chkdsk c: /r and at 55% it said "The volume appears to have one or more unrecoverable problems". But it booted right back into XP just fine. I'm now running the pre-boot chkdsk after right clicking the drive and going to "Properties" and check for errors, both boxes were checked. It just completed that and went into XP ok, and the Event Viewer showed the results just FINE!! No problems reported! So now I'm running chkdsk c: /r again to see what that does.

 

[computer]

BTW, when I first tried to run chkdsk c: /r, I pressed the "R" to run repair and it said no HD's were attached or no recognizable!!! I restarted and tried it again with no problem, and that's when it ran the chkdsk c: /r Ok but stopped at 55%.

 

[computer]

Just ran chkdsk c: /r and it got up to 75% complete, then dropped back down to about 40-something %, then went past 55 & 56% Ok, got up to 71%, then fell back to 50% complete, got back up to 75% then the same crap again, "The volume appears to have one or more unrecoverable problems".

 

[pcgeek11]

It sounds like to me that the disk has physical problems as in damaged sectors... Just a guess on my part but everytime I have seen chkdsk run through this starting over routine it is trying to recover these BAD Sectors.

pcgeek11

 

[computer]

This is phenomenal. What kind of "phenomenon" can keep making SATA cables go bad?? :Q The first SATA cable I was using was apparently bad because I started getting odd behavior, (hanging in POST sometimes, etc.), I replaced it, and everything was ok.

Shortly after this Ghost episode, and I thought I had that issue fixed, I started having these other issues I mentioned tonight. Then about an hour ago, it also hung in the BIOS. I went to reformat and install XP again, and it would not. It said something about an unrecognized disk or something like that. So I ran the WD diag's on the WD360 and I got "ERROR/STATUS CODE: 0132". I tried to write zeroes to the drive (LLF) since that can fix issues sometimes and it wouldn't even do that, it gave the same error code.

So I'm preparing (yet another) RMA for a Raptor, and I thought I'd try a WD740. SAME THING. "ERROR/STATUS CODE: 0120" with the WD740 then I also got a code 0132 with it. So then I'm thinking the freakin' controller is bad. But for some reason I thought I'd try yet another SATA cable. NO ERRORS this time for EITHER drive. WTF?? So I hook the WD360 back up, it goes into XP with no problems.

I'm now running chkdsk c: /r on it again, but it looks like I'm going to get that same error I mentioned earlier "The volume appears to have one or more unrecoverable problems", because it's hopping around percentages completed like it did before.

Is it common for that chkdsk c: /r command to return that type of error? Have any of you run it error free to completion? It's at 72% right now, taking a while. It hopped around a bit at first....it jumped right to 25% then slowed down, when it got to about 70% it backed down to about 50%, but it's been steady climbing since then. Ah, it just completed with NO ERRORS! Well, no problems I should say, it completed and said "chkdsk found and fixed one or more errors on the volume". Went back into Windows again with no problem.

I'm stunned.

 

[computer]

^

 

[pcgeek11]

With so many different drives and cables I would have to Guess a problem with the SATA Controller.

pcgeek11

 

[computer]

Originally posted by: pcgeek11
With so many different drives and cables I would have to Guess a problem with the SATA Controller.

pcgeek11

That would make the SATA cables keep going bad? How?

 

[pcgeek11]

Originally posted by: computer

Originally posted by: pcgeek11
With so many different drives and cables I would have to Guess a problem with the SATA Controller.

pcgeek11

That would make the SATA cables keep going bad? How?

I didn't say that the controller was making the SATA Cables bad. All of the data in and out of the drive goes through the SATA Controller if the controller is crap... any data going through gets crapped up, then it could cause these symptoms. The cables are probably good, and so are the drives.

pcgeek11