kahlil88 Posted November 2, 2010 Share Posted November 2, 2010 Someone brought a laptop to the computer repair shop I work at, and initially the problem was that it was stuck in a reboot cycle regarding a PBR error and "NTLDR not found". The hard drive passed the SeaTools long test and I ran a filesystem check from the OS disc. After that, it hung at "loading PBR for descriptor" so I tried running FIXMBR, FIXBOOT and then did a repair install because it just hung with a blinking cursor. Even after another repair install and trying FIXMBR/FIXBOOT again, it still just hangs at a black screen with a blinking cursor. Link to comment Share on other sites More sharing options...
jaclaz Posted November 2, 2010 Share Posted November 2, 2010 Someone brought a laptop to the computer repair shop I work at, and initially the problem was that it was stuck in a reboot cycle regarding a PBR error and "NTLDR not found". The hard drive passed the SeaTools long test and I ran a filesystem check from the OS disc. After that, it hung at "loading PBR for descriptor" so I tried running FIXMBR, FIXBOOT and then did a repair install because it just hung with a blinking cursor. Even after another repair install and trying FIXMBR/FIXBOOT again, it still just hangs at a black screen with a blinking cursor.The blinking cursor is typical of:wrong data in bootsector (PBR)conflicting CHS vs. LBA (that also causes the above) on some BIOSesThe "loading PBR for descriptor" is NOT a message in standard MBR (meaning NOT a standard 2K/XP one), it should mean that original user has installed a "custom" MBR of some kind, like a bootmanager of something like it.The problem is usually fixable but I will need to see BOTH the MBR and the PBR of the boot partition.HDhacker is handy to make such images:http://dimio.altervista.org/eng/See here for a quick howto for HDhacker use:jaclaz Link to comment Share on other sites More sharing options...
Ponch Posted November 2, 2010 Share Posted November 2, 2010 The blinking cursor is typical of:wrong data in bootsector (PBR)conflicting CHS vs. LBA (that also causes the above) on some BIOSesIf I may add, also- no active partition. Link to comment Share on other sites More sharing options...
jaclaz Posted November 2, 2010 Share Posted November 2, 2010 If I may add, also- no active partition.Actually NO. "no active partition" should return an "explicit" error, like the ones actually embedded in MBR or PBR:http://www.msfn.org/board/index.php?showtopic=121391&st=25or one coming from BIOS.jaclaz Link to comment Share on other sites More sharing options...
kahlil88 Posted November 2, 2010 Author Share Posted November 2, 2010 (edited) If I may add, also - no active partition. That was one of my initial thoughts, but I checked it out with GParted and FDISK and the Windows partition is definitely set as active. I'm also considering the possibility of a boot sector virus. I scanned the drive with HDHacker and (after some garbage characters) it said "A disk read error occurred...NTLDR is missing...NTLDR is compressed...Press Ctrl+Alt+Del to restart" Edited November 3, 2010 by kahlil88 Link to comment Share on other sites More sharing options...
jaclaz Posted November 2, 2010 Share Posted November 2, 2010 I scanned the boot sector with HDHacker and (after some garbage characters) it said "A disk read error occurred...NTLDR is missing...NTLDR is compressed...Press Ctrl+Alt+Del to restart"You don't "scan" anything with HDhacker , you use it to make a copy of the MBR and of the PBR and you post them.Under Linux you can use dd allright for this. (but since you think that hex code is "garbage" I doubt that you are familiar with dd usage )jaclaz Link to comment Share on other sites More sharing options...
kahlil88 Posted November 3, 2010 Author Share Posted November 3, 2010 Here are the PBR and MBR images. Hope I did this right. Thanks.BootSector_DriveK.dat.gzMBR_HardDisk4.dat.gz Link to comment Share on other sites More sharing options...
jaclaz Posted November 3, 2010 Share Posted November 3, 2010 (edited) Here are the PBR and MBR images. Hope I did this right. Thanks.Sure, the files are allright. The contents may not. It seems like there is (I would say "was") a DELL recovery partition (partition ID "DE") 96327 sectors in size (i.e. 96327x512=49319424 bytes).But it is missing the corresponding "DB" one.It seems to me "strange" that such a small "service" partition exists without the "big" one.The CHS and LBA seem like "balanced", but the partitioning does not respect Cylinder boundaries, which on some BIOSes may cause a problem.(edited: no, the boundaries are respected also)Definitely by doing all you did to that laptop you have replaced the "peculiar" Dell MBR with the ""standard" 2K/XP one, it is possible that the original Dell one could work with the broken boundary and the standard XP MBR doesn't.(edited: but it is higly improbable)Post some info on the actual hardware, maybe there is a fix on the manufacturer0s site (Dell), there are several types/versions of those partitions:http://www.goodells.net/dellrestore/Have you checked to e actual filesystem (with CHKDSK)?jaclaz Edited November 3, 2010 by jaclaz Link to comment Share on other sites More sharing options...
Ponch Posted November 3, 2010 Share Posted November 3, 2010 2nd try. A blinking cursor can also be caused by-more active partitions.Like if you restore the image of an active partition next to an other already active partition. I'm pretty sure of that. Link to comment Share on other sites More sharing options...
kahlil88 Posted November 3, 2010 Author Share Posted November 3, 2010 Post some info on the actual hardware, maybe there is a fix on the manufacturer0s site (Dell), there are several types/versions of those partitions:http://www.goodells.net/dellrestore/Have you checked to e actual filesystem (with CHKDSK)?Running CHKDSK was the first thing I did after the drive passed the SeaTools long test. If I remember correctly, that got it out of the reboot cycle but then it just hung at "Loading PBR for descriptor" (it had this error before, but it was hard to read because it flashed quickly on the screen, then the NTLDR error and rebooted).The machine is a Dell Inspiron 600m, and it appears Microsoft Security Essentials found something malicious on the drive, but I'm still waiting for the scan to complete. Link to comment Share on other sites More sharing options...
jaclaz Posted November 3, 2010 Share Posted November 3, 2010 2nd try. A blinking cursor can also be caused by-more active partitions.Like if you restore the image of an active partition next to an other already active partition. I'm pretty sure of that.But the partition table in the MBR Kahlil88 has a single visible partition, set Active. (and a Dell "service partition" hidden and NOT active)@kahlil88When you have finished, can you try running CHKDSK again and report?jaclaz Link to comment Share on other sites More sharing options...
kahlil88 Posted November 4, 2010 Author Share Posted November 4, 2010 Connected the drive to our tech machine and removed a few viruses with Microsoft Security Essentials. Put it back in the laptop and it's booting fine now. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now