Computer Hope
Hardware => Hardware => Topic started by: COKEDUDE on November 14, 2010, 11:32:20 PM
-
I have a external HD that is formatted in NTFS. I found out from binary dump that something is wrong with my ntldr.
00007f80 eb f2 c3 0d 0a 41 20 64 69 73 6b 20 72 65 61 64 |.....A disk read|
00007f90 20 65 72 72 6f 72 20 6f 63 63 75 72 72 65 64 00 | error occurred.|
00007fa0 0d 0a 4e 54 4c 44 52 20 69 73 20 6d 69 73 73 69 |..NTLDR is missi|
00007fb0 6e 67 00 0d 0a 4e 54 4c 44 52 20 69 73 20 63 6f |ng...NTLDR is co|
00007fc0 6d 70 72 65 73 73 65 64 00 0d 0a 50 72 65 73 73 |mpressed...Press|
00007fd0 20 43 74 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f | Ctrl+Alt+Del to|
00007fe0 20 72 65 73 74 61 72 74 0d 0a 00 00 00 00 00 00 | restart........|
00007ff0 00 00 00 00 00 00 00 00 83 a0 b3 c9 00 00 55 aa |..............U.|
00008000 05 00 4e 00 54 00 4c 00 44 00 52 00 04 00 24 00 |..N.T.L.D.R...$.|
00008010 49 00 33 00 30 00 00 e0 00 00 00 30 00 00 00 00 |I.3.0......0....|
How would I go about fixing my ntldr in a external HD? I read this article below but it doesn't have any useful instructions for a external HD. It only has directions for a HD that has a OS on it.
http://www.computerhope.com/issues/ch000465.htm
-
there is nothing wrong with your NTLDR or your external drive.
Think about it. you know those are error messages, right? But they are only error messages when they are being showed to you, not when you go looking for them in the files that contain them!
Your logic here would be similar to performing a binary dump of a executable file such as diskcomp, and because it shows "Disks Compare OK" assuming that any floppies you happen to have in your drives are identical. You're seeing the messages, but you are basically seeing where the program loads those messages when it wants to show them because they are relevant; seeing them in a disk dump doesn't suddenly make them relevant!
What you are seeing is the binary dump of the boot sector itself. Why you would have a bootable external drive I haven't the faintest, but what is relevant here is that unless you are planning on installing the drive into a computer and booting to it, it's rather pointless to lose any sleep because it has a boot sector. NTFS drives do not require NTLDR. NTLDR is the core component used during the windows XP and earlier boot process.
-
You are reading the message area of an NTFS boot block. What you see is normal. Are you actually having any problems? Have you tried to make the external HD bootable? (IF so, why?)
-
there is nothing wrong with your NTLDR or your external drive.
Think about it. you know those are error messages, right? But they are only error messages when they are being showed to you, not when you go looking for them in the files that contain them!
Your logic here would be similar to performing a binary dump of a executable file such as diskcomp, and because it shows "Disks Compare OK" assuming that any floppies you happen to have in your drives are identical. You're seeing the messages, but you are basically seeing where the program loads those messages when it wants to show them because they are relevant; seeing them in a disk dump doesn't suddenly make them relevant!
What you are seeing is the binary dump of the boot sector itself. Why you would have a bootable external drive I haven't the faintest, but what is relevant here is that unless you are planning on installing the drive into a computer and booting to it, it's rather pointless to lose any sleep because it has a boot sector. NTFS drives do not require NTLDR. NTLDR is the core component used during the windows XP and earlier boot process.
??
I can't access my data.
You are reading the message area of an NTFS boot block. What you see is normal. Are you actually having any problems? Have you tried to make the external HD bootable? (IF so, why?)
I can't access my data. Its there, Windows just can't access it.
(http://i255.photobucket.com/albums/hh133/COKEDUDEUSF/missing.jpg)
http://i255.photobucket.com/albums/hh133/COKEDUDEUSF/missing.jpg
-
??
I can't access my data.
I can't access my data. Its there, Windows just can't access it.
OK. so then there is something wrong with your drive.
However it is wholly unrelated to the contents of the boot sector.
-
OK. so then there is something wrong with your drive.
However it is wholly unrelated to the contents of the boot sector.
Any idea what the problem is? Could you help me figure it out please?
-
Maybe it's "busted", to use the technical term. Have you tried connecting it to another computer?
-
Its there, Windows just can't access it.
How do you know it's there still?
How did you get the hex dump?
-
How do you know it's there still?
How did you get the hex dump?
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
Testdist was able to recover my first 10 folders. Thx to lovely limitations of NTFS I was not able to recover the rest of my folders that way.
In Linux I used this command.
sudo dd if=/dev/sdb count=$((2*16384)) | hexdump -C | less