Welcome, Guest. Please login or register.
Did you miss your activation email?
September 26, 2017, 12:02:06 PM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  Misc. Tools (Moderators: Tom, Joep)
| | |-+  Using MBRTOOL with USB attached hard disks
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Using MBRTOOL with USB attached hard disks  (Read 17365 times)
aardvark_65
member

Posts: 9


« on: June 03, 2013, 06:25:52 AM »

Is there a problem with using MBRTOOL to list (DMP) or backup the MBR of a USB attached hard disk, especially if it's a large disk with more than 1 partition?

When using it on my USB disks, it occasionally lists garbage (hex 41 in all positions) - although, if I try to list the same disk later, it is sometimes O.K. (?), i.e. it seems to be inconsistent.

I am using version 2.3.100 of MBRTOOL, which still appears to be the current version - I see that it's no longer maintained.

My system is Win XP Pro SP3, and I'm running MBRTOOL after booting the PC with a Win98 DOS bootable floppy. If I boot from my Win98 DOS bootable USB stick, MBRTOOL doesn't "see" any other USB disks - it only sees the bootable USB stick as disk 0, and the internal hard disk as disk 1.

The USB disks can be accessed without any problems when the system is booted normally, i.e. in Win XP.   




A sample DMP file is as follows:


Dump MBR for disk 129 (1)
 
Date for MBR dump is 06-02-2013
 
000   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
016   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
032   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
048   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
064   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
080   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
096   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
112   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
128   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
144   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
160   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
176   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
192   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
208   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
224   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
240   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
256   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
272   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
288   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
304   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
320   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
336   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
352   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
368   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
384   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
400   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
416   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
432   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
448   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
464   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
480   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
496   41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41    AAAAAAAAAAAAAAAA
Geometry values (from BIOS!) for this disk : (C/H/S) - 1023/255/63
Partition Table Information
         ACT  TYPE START-C/H/S    END----C/H/S   LBA-start   LBA-length
Entry 1: 65   41   321  65   1    321  65   1    1094795585  1094795585
Entry 2: 65   41   321  65   1    321  65   1    1094795585  1094795585
Entry 3: 65   41   321  65   1    321  65   1    1094795585  1094795585
Entry 4: 65   41   321  65   1    321  65   1    1094795585  1094795585
         Partition table as shown in MBR :
Entry 1: 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41
Entry 2: 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41
Entry 3: 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41
Entry 4: 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41





A sample DMP file for the same disk a few minutes later is as follows:


Dump MBR for disk 129 (1)
 
Date for MBR dump is 06-02-2013
 
000   33 C0 8E D0 BC 00 7C FB 50 07 50 1F FC BE 1B 7C    3м.|P.P..|
016   BF 1B 06 50 57 B9 E5 01 F3 A4 CB BD BE 07 B1 04    ..PW.˽..
032   38 6E 00 7C 09 75 13 83 C5 10 E2 F4 CD 18 8B F5    8n.|.u...
048   83 C6 10 49 74 19 38 2C 74 F6 A0 B5 07 B4 07 8B    .It.8,t ..
064   F0 AC 3C 00 74 FC BB 07 00 B4 0E CD 10 EB F2 88    <.t....
080   4E 10 E8 46 00 73 2A FE 46 10 80 7E 04 0B 74 0B    N.F.s*F.~..t.
096   80 7E 04 0C 74 05 A0 B6 07 75 D2 80 46 02 06 83    ~..t. .uҀF..
112   46 08 06 83 56 0A 00 E8 21 00 73 05 A0 B6 07 EB    F..V..!.s. .
128   BC 81 3E FE 7D 55 AA 74 0B 80 7E 10 00 74 C8 A0    >}Ut.~..t 
144   B7 07 EB A9 8B FC 1E 57 8B F5 CB BF 05 00 8A 56    .멋.W˿..V
160   00 B4 08 CD 13 72 23 8A C1 24 3F 98 8A DE 8A FC    ...r#$?ފ
176   43 F7 E3 8B D1 86 D6 B1 06 D2 EE 42 F7 E2 39 56    Cцֱ.B9V
192   0A 77 23 72 05 39 46 08 73 1C B8 01 02 BB 00 7C    .w#r.9F.s....|
208   8B 4E 02 8B 56 00 CD 13 73 51 4F 74 4E 32 E4 8A    N.V..sQOtN2
224   56 00 CD 13 EB E4 8A 56 00 60 BB AA 55 B4 41 CD    V..V.`UA
240   13 72 36 81 FB 55 AA 75 30 F6 C1 01 74 2B 61 60    .r6Uu0.t+a`
256   6A 00 6A 00 FF 76 0A FF 76 08 6A 00 68 00 7C 6A    j.j.v.v.j.h.|j
272   01 6A 10 B4 42 8B F4 CD 13 61 61 73 0E 4F 74 0B    .j.B.aas.Ot.
288   32 E4 8A 56 00 CD 13 EB D6 61 F9 C3 49 6E 76 61    2V..aInva
304   6C 69 64 20 70 61 72 74 69 74 69 6F 6E 20 74 61    lid partition ta
320   62 6C 65 00 45 72 72 6F 72 20 6C 6F 61 64 69 6E    ble.Error loadin
336   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74    g operating syst
352   65 6D 00 4D 69 73 73 69 6E 67 20 6F 70 65 72 61    em.Missing opera
368   74 69 6E 67 20 73 79 73 74 65 6D 00 00 00 00 00    ting system.....
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
400   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
416   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
432   00 00 00 00 00 2C 44 63 48 EF 0F 00 00 00 00 20    .....,DcH.....
448   21 00 07 FE FF FF 00 08 00 00 62 4C B0 98 00 FE    !......bL.
464   FF FF 07 FE FF FF 62 54 B0 98 5E 5C 39 0C 00 FE    .bT^\9..
480   FF FF 07 FE FF FF C0 B0 E9 A4 81 B6 BE 09 00 00    .餁...
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA    ..............U
Geometry values (from BIOS!) for this disk : (C/H/S) - 1023/255/63
Partition Table Information
         ACT  TYPE START-C/H/S    END----C/H/S   LBA-start   LBA-length
Entry 1: 0    07   0    32   33   1023 254  63   2048        2561690722
Entry 2: 0    07   1023 254  63   1023 254  63   2561692770  205085790
Entry 3: 0    07   1023 254  63   1023 254  63   2766778560  163493505
Entry 4: 0    00   0    0    0    0    0    0    0           0
         Partition table as shown in MBR :
Entry 1: 00 20 21 00 07 FE FF FF 00 08 00 00 62 4C B0 98
Entry 2: 00 FE FF FF 07 FE FF FF 62 54 B0 98 5E 5C 39 0C
Entry 3: 00 FE FF FF 07 FE FF FF C0 B0 E9 A4 81 B6 BE 09
Entry 4: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00



Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #1 on: June 03, 2013, 08:54:50 AM »

The current MBRtool version is 2.3.200 and there was a small update last week, though that was only to add better bootable USB support.

Your problem seems odd, I've never seen that before. Have you checked the health of the disk? Do you know it to be in good working order? Is the USB interface okay (I assume you have an external drive bay system where an IDE or SATA disk uses a converter to connect the disk to USB)? You could check the disk's SMART info but that won't work over USB, you'd have to connect the disk directly. If you decide to do that, more info here: http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm.

The only thing I can think of that might have an effect is power supply. I've had external USB drives act weird on me until I gave them extra power, this is especially the case when connecting external USB drives to laptops because the USB power output for laptops is not so good. I now always use a power fed USB hub to connect disks, and have not had problems since.

I know about the 'only one USB hard disk' problem when booting from a USB drive. This seems to be a BIOS problem and is not something we can fix, annoying as it is. I'll look into it a bit more, see if something can be done.
Logged

aardvark_65
member

Posts: 9


« Reply #2 on: June 03, 2013, 10:39:07 AM »

O.K., I'll download version 2.3.200 and try that.

I haven't done any specific health checks on the disks, but I haven't had any problems using them with Win XP. I've actually noticed the problem on 2 different USB attached disks (1.5TB, 500GB), both with multiple partitions. I haven't noticed the problem with a 3rd USB disk (750GB) which only has 1 partition.

All are WD "elements" disks - they appear to be sealed units, i.e. they aren't "normal" disks inside a USB casing.

My PC is a laptop, and 2 of the USB disks rely on the laptop's USB power output. However the 3rd one has its own power supply, and it is one of the drives giving the problem.

I agree the "only 1 USB hard disk" is almost certainly a BIOS problem - I had the same problem when using PTEDIT in Win98 DOS. When booting from a floppy, it still only sees 1 USB disk, even if 2 are connected. To make things really weird, MBRTOOL only saw one of the USB disks, and PTEDIT only saw the other one (Huh).
Logged
aardvark_65
member

Posts: 9


« Reply #3 on: June 04, 2013, 07:28:15 AM »

I downloaded version 2.3.200 and did some test runs today. I got some rather confusing results, and I'm still getting garbage (hex 41) sometimes. All runs were after booting from a Win98 DOS floppy, and I only had one external USB disk attached at a time.

In the first run with the 1.5TB disk connected to a USB port, version 2.3.200 didn't see the disk at all. I then tried version 2.3.100, and got the same result.

I rebooted, with the 1.5TB still attached, and this time ran version 2.3.100 - that worked O.K. I then ran version 2.3.200, and that worked too.

I rebooted again, with the 1.5TB still attached, and ran version 2.3.200. This time it worked O.K. (Huh)

The 1.5TB USB disk has its own power supply.

I rebooted with the 500GB disk connected to a USB port and ran version 2.3.200. The MBR listed O.K. on the screen (option 4 (display) under "MBR actions"), and the DMP file was O.K. However the backup file (xxxxxx.129) was not O.K. - it was full of hex 41's (see example below).

I ran version 2.3.300 again (without rebooting), and this time listed the MBR of disk 0 (the internal hard disk) first. Then I listed the MBR of the 500GB (option 4), and this time it was not O.K. - I got hex 41's everywhere. I created DMP and backup files again, and it was the same as just above - the DMP file was O.K., but the backup wasn't.

I rebooted with the 750GB disk connected to a USB port. Version 2.3.200 didn't see the disk at all. However neither did version 2.3.100, nor PTEDIT (partition table editor).

I have a powered USB hub, so I decided to try connecting the USB disks to that. In short, it made no difference to the 500GB disk - I got exactly the same results as above. However when I connected the 750GB disk to the powered hub and rebooted, it worked O.K. - listing on the screen, DMP file and backup file were all O.K. I then connected the 750GB disk directly to a USB port on the laptop again and rebooted, and same as above - neither version of MBRTOOL saw it, and PTEDIT didn't either.

The results with the 500GB disk are the same as I got yesterday with the old version of MBRTOOL. However yesterday with the old version of MBRTOOL, I didn't have any problems with the 750GB disk at all. As a final test, I rebooted with the 750GB disk directly connected to a USB port on the laptop and ran the old version of MBRTOOL (which worked yesterday), and it didn't see the disk at all (Huh)



Hence, in summary, the powered USB hub made a difference with the 750GB disk, but no difference with the 500GB disk. The results with the 500GB were consistent yesterday and today, but the results with the other 2 disks varied.

When I rebooted into XP, I connected all 3 external disks directly to USB ports on the laptop at the same time (i.e. I didn't use the powered USB hub), with the mouse connected to the 4th USB port (i.e. maximum power drain to the USB ports I guess), and they all worked fine. Hence there don't seem to be any problems with the disks themselves.




Sorry for the comment yesterday about MBRTOOL no longer being maintained. On the download page, I saw "please note that this program is no longer supported!" just under the remarks for MBRtool, and I initially thought it was referring to MBRtool. However I now realise it was referring to CHK-Mate, just under MBRtool. And of course you wouldn't be updating it if it wasn't supported, and probably not answering questions about it on the forum!



A sample garbage backup file is as follows:


MBRtool
2.3.200
MBR129
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
41414141414141414141414141414141414141414141414141414141414141410A30
414141414141414141414141414141414141414141414141414141414141BBBB0B24
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #4 on: June 04, 2013, 09:51:47 AM »

Thanks for all the testing, some interesting stuff here.

The backup you posted has some marks that show that MBRtool actually "thought" it was reading the disk. Meaning, there are no errors as such, MBRtool actually thinks that the MBR contains &H41. This is significant because that tells me that the problem lies either with the actual connection, or with how MBRtool deals with that connection. That in turn means that we can't do much about this because the disk communication we use is standardized PC-internal stuff.
If you say the disks are healthy and have not shown other signs of trouble, we can eliminate that.

If you'd be willing you could test DiskPatch, see what that does. The trial version doesn't write anything to disk so you're safe and can have a look around without fear of doing damage. You could start DiskPatch and start the disk editor, then take a look at the MBR. You can browse up and down the disk a bit, see if that does anything for the problem if the &H41 shows up again.

And how about doing this on another PC (if you have the option to do so)? That may help determine where to look for the problem.

To make sure: the behavior you see is the same for any of the start methods; diskette, CD or USB?
Logged

aardvark_65
member

Posts: 9


« Reply #5 on: June 04, 2013, 12:43:52 PM »

O.K., I'll download Diskpatch and try it, hopefully tomorrow (it's now late evening in Australia).

Unfortunately I haven't got another PC that I can use.

I've only tried MBRTOOL on my USB disks when booting from a diskette, since booting from a USB stick doesn't allow me to access any other USB disks. I haven't tried booting from a CD, but I guess I could try that as well.
Logged
aardvark_65
member

Posts: 9


« Reply #6 on: June 05, 2013, 11:20:25 AM »

I installed and ran Diskpatch, and the results were similar to MBRTOOL.

In all cases I got a yellow exclamation mark for disk health on startup, which I see from the help file means it couldn't determine disk health.

I connected the 500GB disk to a USB port and ran Diskpatch. When I ran the disk editor, it showed sector 0 as having hex F6 in all bytes. Sector 1 also had hex F6 everywhere, but sector 2 had hex 00 everywhere. When I went back to sector 1 it now showed hex 00 everywhere, and going back to sector 0 now showed what looked like a valid boot sector. F5 show partitions looked O.K. However at one stage when I was looking at sector 0 again, it had gone back to all hex F6. I did an export with F7, and the sector 0 display in the editor looked O.K. again. However after I exited Diskpatch and looked at the exported file, it was all hex F6.

I ran the editor on the internal hard disk and it all looked O.K.

I connected the 500GB to the powered USB hub and rebooted. The results were pretty much the same as when it was connected directly to a laptop USB port, although initially sector 0 looked O.K. in the editor. However when I looked at it again a bit later it was showing hex F6 again. At one stage I displayed the partition table with F5 and pressed 1 to jump to partition 1 (sector 2048 in this case), and it showed all hex F6. I displayed 2049, which was also all hex F6, but when I went back to 2048, it now looked O.K. When I exported sector 0 to a file, the file came out with all hex F6.

I connected the 750GB directly to a laptop USB port and rebooted, and Diskpatch couldn't see it at all. However when I connected it to the powered USB hub and rebooted, Diskpatch could now see it, and all looked O.K. - I didn't get any hex F6's or any other problems. When I exported sector 0 to a file it looked O.K.

I connected the 1.5TB disk directly to a laptop USB port and rebooted. All looked O.K. in the disk editor, and an export file also looked O.K.

I noticed that Diskpatch produces log files, so I had a look. It looks like, soon after startup, it lists the MBR's of the disks it finds, and for all disks they looked O.K. - I didn't see any hex F6's anywhere. The only thing I sometimes saw that looked like it might be an error was "129/000:46/VEC> BS and BBS not equal, dump follows;", although I also saw "129/000:46/VEC> BS and BBS equal"; and sometimes I got the "not equal" message for disks that were O.K. in the disk editor.

All runs were started after booting from a Win98 DOS diskette.

After all the above runs, I attached all the USB disks directly to laptop USB ports at the same time on bootup into XP, and they were all O.K.

Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #7 on: June 05, 2013, 01:23:19 PM »

The F6 seems to confirm the idea that the reading of a disk goes wrong at the connection level. F6 is what DiskPatch stuffs into a sector buffer before reading a sector from disk, so if the F6 is still there after the read the sector was never actually read (even though DiskPatch seems to think it was). Any chance you can put the DiskPatch log file up?

To me it all seems like a problem that is specific to your setup. The BIOS may play a role, the external disk may, it's hard to tell. But we always say that, wherever possible, one should eliminate unneeded or external connection types when working on a disk recovery. So if you would run into problems with these disks you should try to connect them directly, and if that doesn't work you should probably try another PC.
Logged

aardvark_65
member

Posts: 9


« Reply #8 on: June 05, 2013, 02:45:13 PM »

Diskpatch log file for 500GB disk is below.

The USB disks are all WD sealed units, so it's not possible to directly connect them to a PC; and unfortunately I don't have access to another PC.

My PC is a Dell laptop, 8-9 years old now. I read somewhere (a Dell forum I think) that the BIOS doesn't support an internal hard disk greater than about 120GB, and I was recently reading about 48bit LBA, so my BIOS almost certainly doesn't support that. However XP has certainly been able to read and write the USB disks without problems. I think I read somewhere that the BIOS limitation doesn't apply to USB attached disks - but I don't really understand all this stuff.

Could it be that XP handles USB drives greater than 120GB (or whatever the non 48 bit LBA limit is) O.K., but that DOS (i.e. what MBRTOOL and Diskpatch run under) has a problem? Although not always - 2 of the USB disks seem to be mostly O.K.

I'm only trying to backup the MBR's as insurance against possible future problems, as I have done for the internal hard disk.


Diskpatch log file follows. Internal hard disk is 128, 500 GB USB attached disk with 4 partitions is 129.


.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.100
.../000:01/LOG> (C) 2000-2013 DIY DataRecovery
.../000:01/LOG> Contact info: www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 69Kb
.../000:01/LOG> CommandLineParms:
.../000:01/LOG> LogDate: 06-05-2013
.../000:01/CFG> FilePath="A:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> ReadDelay="0"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> WriteAfterReadError="1"
.../000:01/CFG> VfyFixedBadSect="1"
.../000:01/CFG> CleanAfterDOD="1"
.../000:01/CFG> DiskReset="1"
.../000:01/CFG> SectorSkip="1024"
.../000:01/CFG> AutoSaveState="1"
.../000:01/CFG> DumpFoundSectors="0"
.../000:01/CFG> FixFats="1"
.../000:01/CFG> MaxFatScan="51200"
.../000:01/CFG> MaxDataColEntries="256"
.../000:01/CFG> IgnoreF8FF="0"
.../000:01/CFG> DownSizeExt="1"
.../000:01/CFG> ScanSignature="55AA"
.../000:01/CFG> Rebuild="00"
.../000:01/13H> Ext13H installed test requested
.../000:01/13H> Disk found at 128
.../000:01/13H> Ext13H version: 2.1 / EDD-1.1
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 128 X13H data : 16383/16/63 234441648/512
.../000:01/13H> Disk found at 129
.../000:01/13H> Ext13H version: 2.1 / EDD-1.1
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 1024/255/63 976773168/512
.../000:01/13H> Ext13H tested ok
.../000:01/FDL> DiskList requested
.../000:01/FDL> Disk found at 128
.../000:01/FDL> Disk found at 129
### DISKLIST ###
__D_|________LBA_|___H_|__S_|___GB_|__GEO_|___SS_
128 | .234441648 | 255 | 63 | .111 | BIOS | .512
129 | .976773168 | 255 | 63 | .465 | BIOS | .512
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
.../000:05/IAS> AdmiSector found on disk 0 (128)
.../000:05/IAS> AdmiSector found on disk 1 (129)
.../000:06/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:06/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:06/WAS> AdmiSectors in use : 0+ 1+
.../000:13/KEY> DEMO/1
.../000:13/PFC> PQstuff signature not detected on disk 0 (128)
.../000:15/PFC> PQstuff signature not detected on disk 1 (129)
.../000:15/PFC> UDMA driver not loaded
.../000:15/PFC> Disk health not checked
.../000:16/PFC> Partition State backup not found on disk 0 (128)
.../000:16/PFC> Partition State backup not found on disk 1 (129)
.../000:16/PFC> No Repair date found on disk 0 (128)
.../000:16/PFC> No Repair date found on disk 1 (129)
.../000:35/MNU> - Main, Select Disk
.../000:41/CSD> Start CheckDisk for disk 1 (129)
.../000:41/CSD> 0 (0 0 1)
.../000:41/CSD> 16064 (0 254 63)
.../000:41/CSD> 976768065 (60801 0 1)
.../000:41/CSD> 976773167 (60801 80 63)
.../000:45/CSD> CheckDisk complete, ReadErrors 0
.../000:45/USD> Disk 1 (129) selected
.../000:45/GSC> No geo change detected for disk 1 (129)
.../000:45/WAS> AdmiSectors in use : 0+ 1+
129/000:45/USD> MBR for disk 1 (129)
129/000:45/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C FB 50 07 50 1F FC BE 1B 7C  |  3м.|P.P..|
016   BF 1B 06 50 57 B9 E5 01 F3 A4 CB BD BE 07 B1 04  |  ..PW.˽..
032   38 6E 00 7C 09 75 13 83 C5 10 E2 F4 CD 18 8B F5  |  8n.|.u...
048   83 C6 10 49 74 19 38 2C 74 F6 A0 B5 07 B4 07 8B  |  .It.8,t ..
064   F0 AC 3C 00 74 FC BB 07 00 B4 0E CD 10 EB F2 88  |  <.t....
080   4E 10 E8 46 00 73 2A FE 46 10 80 7E 04 0B 74 0B  |  N.F.s*F.~..t.
096   80 7E 04 0C 74 05 A0 B6 07 75 D2 80 46 02 06 83  |  ~..t. .uҀF..
112   46 08 06 83 56 0A 00 E8 21 00 73 05 A0 B6 07 EB  |  F..V..!.s. .
128   BC 81 3E FE 7D 55 AA 74 0B 80 7E 10 00 74 C8 A0  |  >}Ut.~..t 
144   B7 07 EB A9 8B FC 1E 57 8B F5 CB BF 05 00 8A 56  |  .멋.W˿..V
160   00 B4 08 CD 13 72 23 8A C1 24 3F 98 8A DE 8A FC  |  ...r#$?ފ
176   43 F7 E3 8B D1 86 D6 B1 06 D2 EE 42 F7 E2 39 56  |  Cцֱ.B9V
192   0A 77 23 72 05 39 46 08 73 1C B8 01 02 BB 00 7C  |  .w#r.9F.s....|
208   8B 4E 02 8B 56 00 CD 13 73 51 4F 74 4E 32 E4 8A  |  N.V..sQOtN2
224   56 00 CD 13 EB E4 8A 56 00 60 BB AA 55 B4 41 CD  |  V..V.`UA
240   13 72 36 81 FB 55 AA 75 30 F6 C1 01 74 2B 61 60  |  .r6Uu0.t+a`
256   6A 00 6A 00 FF 76 0A FF 76 08 6A 00 68 00 7C 6A  |  j.j..v..v.j.h.|j
272   01 6A 10 B4 42 8B F4 CD 13 61 61 73 0E 4F 74 0B  |  .j.B.aas.Ot.
288   32 E4 8A 56 00 CD 13 EB D6 61 F9 C3 49 6E 76 61  |  2V..aInva
304   6C 69 64 20 70 61 72 74 69 74 69 6F 6E 20 74 61  |  lid partition ta
320   62 6C 65 00 45 72 72 6F 72 20 6C 6F 61 64 69 6E  |  ble.Error loadin
336   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74  |  g operating syst
352   65 6D 00 4D 69 73 73 69 6E 67 20 6F 70 65 72 61  |  em.Missing opera
368   74 69 6E 67 20 73 79 73 74 65 6D 00 00 00 00 00  |  ting system.....
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
400   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
416   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
432   00 00 00 00 00 2C 44 63 4A BB 07 00 00 00 00 20  |  .....,DcJ.....
448   21 00 07 FE FF FF 00 08 00 00 C7 6F A9 17 00 FE  |  !........o..
464   FF FF 0F FE FF FF C7 77 A9 17 7A D4 8E 22 00 00  |  .....w.zԎ"..
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  |  ..............U
###
129/000:45/VEC> Start Verify EPBR Chain for disk 1 (129)
129/000:45/VEC> Listing current partitions on disk:
129/000:45/VEC>     NTFS (P)  Elements 50        2048   396980167     (189 Gb)
129/000:45/VEC>     NTFS (L)  BackupMar13   396982278    87586317      (42 Gb)
129/000:45/VEC>     NTFS (L)  BackupNov08   484568658   154946862      (74 Gb)
129/000:45/VEC>     NTFS (L)  BackupMar12   639515588   337252477     (161 Gb)
129/000:45/VEC> Extended starts at 396982215 (24711 0 1)
129/000:45/VEC> Partition Table info for sector 0 (0 0 1)
129/000:45/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | ....0..32..33 | .1023.254..63 | ......2048 | .396980167
..2 ...0 | ..0F | .1023.254..63 | .1023.254..63 | .396982215 | .579785850
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/000:45/VEC> 55AA sig Ok
129/000:45/VEC> Partition Table info for sector 396982215 (24711 0 1)
129/000:45/LOG> PartListDump requested at 396982215 (24711 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | .1023.254..63 | .1023.254..63 | ........63 | ..87586317
..2 ...0 | ..05 | .1023.254..63 | .1023.254..63 | ..87586380 | .154946925
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/000:45/VEC> 55AA sig Ok
129/000:45/VEC> Partition Table info for sector 484568595 (30163 0 1)
129/000:45/LOG> PartListDump requested at 484568595 (30163 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | .1023.254..63 | .1023.254..63 | ........63 | .154946862
..2 ...0 | ..05 | .1023.254..63 | .1023.254..63 | .242533310 | .337252540
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/000:45/VEC> 55AA sig Ok
129/000:45/VEC> Partition Table info for sector 639515525 (39808 0 6)
129/000:45/LOG> PartListDump requested at 639515525 (39808 0 6)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | .1023.254..63 | .1023.254..63 | ........63 | .337252477
..2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/000:45/VEC> 55AA sig Ok
129/000:45/LOG> Boot sector dump requested at 2048 (0 32 33)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 2048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 396980166
........MFT Location (dec): 36614714
.MFT Mirror Location (dec): 19145683
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 5A78DA6578DA3F85
........Volume Label (txt): Elements 50
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:46/VEC> BS and BBS not equal, dump follows;
129/000:46/LOG> Boot sector dump requested at 396982214 (24710 254 63)
### BootSectorDump for BStype NTFS (B)
...........Jump Code (hex): 000000
............OEM Name (txt): ........
....Bytes per Sector (dec): 0
.Sectors per Cluster (dec): 0
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): 00
..............Unused (hex): 0000
...Sectors per Track (dec): 0
.....Heads per Track (dec): 0
......Hidden Sectors (dec): 0
..............Unused (hex): 00000000
.............Unknown (hex): 00000000
.......Total Sectors (dec): 0
........MFT Location (dec): 0
.MFT Mirror Location (dec): 0
....Clusters per FRS (dec): 0
.Clusters/Indx Block (dec): 0
...........Volume ID (hex): 0000000000000000
........Volume Label (txt): (Err)
............Checksum (hex): 00000000
....Sector Signature (hex): 0000
129/000:46/LOG> Boot sector dump requested at 396982278 (24711 1 1)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 87586316
........MFT Location (dec): 3
.MFT Mirror Location (dec): 5474144
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CE2D69A04E8700
........Volume Label (txt): BackupMar13
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:46/VEC> BS and BBS equal
129/000:46/LOG> Boot sector dump requested at 484568658 (30163 1 1)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 154946861
........MFT Location (dec): 3
.MFT Mirror Location (dec): 9684178
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CD09E6FD1F56F0
........Volume Label (txt): BackupNov08
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:46/VEC> BS and BBS equal
129/000:46/LOG> Boot sector dump requested at 639515588 (39808 1 6)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 337252476
........MFT Location (dec): 2
.MFT Mirror Location (dec): 28890889
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CCF64D23EEA9A0
........Volume Label (txt): BackupMar12
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:46/VEC> BS and BBS not equal, dump follows;
129/000:46/LOG> Boot sector dump requested at 976768064 (60800 254 63)
### BootSectorDump for BStype NTFS (B)
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 212250716
........MFT Location (dec): 3
.MFT Mirror Location (dec): 13265669
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CCF64D23EEA9A0
........Volume Label (txt):
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:46/VEC> Verify EPBR Chain completed
129/000:46/USD> Select disk completed
129/000:56/MNU> - Main, Options
129/001:19/MNU> - Main, Utilities
129/001:21/MNU> - Tools, DiskEditor
129/001:25/UND> Undo skipped
129/001:26/LOG> Undo settings: GL(+) DE(+) FAT(+)
129/001:26/DED> Start DiskEditor, ScanReady 0
129/009:39/EXS> 1 Sector(s) exported from 0 (0 0 1) to file SECTOR0
129/010:44/DED> Sector 0 (0 0 1) copied to Clipboard
129/010:59/DED> Start HexEdit for sector in ClipBoard (0)
129/011:13/DED> Exit HexEdit, changes discarded
129/011:34/DED> Exit DiskEditor at 0 (0 0 1)
129/011:39/MNU> - Main, Select Disk
129/011:43/CSD> Start CheckDisk for disk 0 (128)
129/011:43/CSD> 0 (0 0 1)
129/011:43/CSD> 16064 (0 254 63)
129/011:43/CSD> 234436545 (14593 0 1)
129/011:43/CSD> 234441647 (14593 80 63)
129/011:43/CSD> CheckDisk complete, ReadErrors 0
129/011:43/USD> Disk 0 (128) selected
129/011:43/GSC> First DP run, geo info for disk 0 (128) not yet recorded
129/011:43/WAS> AdmiSectors in use : 0+ 1+
128/011:43/USD> MBR for disk 0 (128)
128/011:43/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C FB 50 07 50 1F FC BE 1B 7C  |  3м.|P.P..|
016   BF 1B 06 50 57 B9 E5 01 F3 A4 CB BD BE 07 B1 04  |  ..PW.˽..
032   38 6E 00 7C 09 75 13 83 C5 10 E2 F4 CD 18 8B F5  |  8n.|.u...
048   83 C6 10 49 74 19 38 2C 74 F6 A0 B5 07 B4 07 8B  |  .It.8,t ..
064   F0 AC 3C 00 74 FC BB 07 00 B4 0E CD 10 EB F2 88  |  <.t....
080   4E 10 E8 46 00 73 2A FE 46 10 80 7E 04 0B 74 0B  |  N.F.s*F.~..t.
096   80 7E 04 0C 74 05 A0 B6 07 75 D2 80 46 02 06 83  |  ~..t. .uҀF..
112   46 08 06 83 56 0A 00 E8 21 00 73 05 A0 B6 07 EB  |  F..V..!.s. .
128   BC 81 3E FE 7D 55 AA 74 0B 80 7E 10 00 74 C8 A0  |  >}Ut.~..t 
144   B7 07 EB A9 8B FC 1E 57 8B F5 CB BF 05 00 8A 56  |  .멋.W˿..V
160   00 B4 08 CD 13 72 23 8A C1 24 3F 98 8A DE 8A FC  |  ...r#$?ފ
176   43 F7 E3 8B D1 86 D6 B1 06 D2 EE 42 F7 E2 39 56  |  Cцֱ.B9V
192   0A 77 23 72 05 39 46 08 73 1C B8 01 02 BB 00 7C  |  .w#r.9F.s....|
208   8B 4E 02 8B 56 00 CD 13 73 51 4F 74 4E 32 E4 8A  |  N.V..sQOtN2
224   56 00 CD 13 EB E4 8A 56 00 60 BB AA 55 B4 41 CD  |  V..V.`UA
240   13 72 36 81 FB 55 AA 75 30 F6 C1 01 74 2B 61 60  |  .r6Uu0.t+a`
256   6A 00 6A 00 FF 76 0A FF 76 08 6A 00 68 00 7C 6A  |  j.j..v..v.j.h.|j
272   01 6A 10 B4 42 8B F4 CD 13 61 61 73 0E 4F 74 0B  |  .j.B.aas.Ot.
288   32 E4 8A 56 00 CD 13 EB D6 61 F9 C3 49 6E 76 61  |  2V..aInva
304   6C 69 64 20 70 61 72 74 69 74 69 6F 6E 20 74 61  |  lid partition ta
320   62 6C 65 00 45 72 72 6F 72 20 6C 6F 61 64 69 6E  |  ble.Error loadin
336   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74  |  g operating syst
352   65 6D 00 4D 69 73 73 69 6E 67 20 6F 70 65 72 61  |  em.Missing opera
368   74 69 6E 67 20 73 79 73 74 65 6D 00 00 00 00 00  |  ting system.....
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
400   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
416   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
432   00 00 00 00 00 2C 44 63 AF F6 AF F6 00 00 80 01  |  .....,Dc...
448   01 00 07 FE FF FE 3F 00 00 00 82 37 F9 0D 00 00  |  ....?...7...
464   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  |  ..............U
###
128/011:44/VEC> Start Verify EPBR Chain for disk 0 (128)
128/011:44/VEC> Listing current partitions on disk:
128/011:44/VEC>     NTFS (P)    (no name)          63   234436482     (112 Gb)
128/011:44/VEC> Partition Table info for sector 0 (0 0 1)
128/011:44/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 .128 | ..07 | ....0...1...1 | .1022.254..63 | ........63 | .234436482
..2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
128/011:44/VEC> 55AA sig Ok
128/011:44/LOG> Boot sector dump requested at 63 (0 1 1)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 234436481
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 14652280
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): C0B8E67BB8E66F7B
........Volume Label (txt): (no name)
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/011:44/VEC> BS and BBS equal
128/011:44/VEC> Verify EPBR Chain completed
128/011:44/USD> Select disk completed
128/011:49/MNU> - Main, Utilities
128/011:50/MNU> - Tools, DiskEditor
128/011:51/UND> Undo skipped
128/011:53/LOG> Undo settings: GL(+) DE(+) FAT(+)
128/011:53/DED> Start DiskEditor, ScanReady 0
128/017:01/DED> Exit DiskEditor at 0 (0 0 1)
128/017:08/MNU> - Main, Select Disk
128/018:30/USD> No source / disk selected
.../018:30/USD> Select disk completed
.../018:34/MNU> - Main, Select Disk
.../018:37/CSD> Start CheckDisk for disk 1 (129)
.../018:37/CSD> 0 (0 0 1)
.../018:37/CSD> 16064 (0 254 63)
.../018:37/CSD> 976768065 (60801 0 1)
.../018:37/CSD> 976773167 (60801 80 63)
.../018:41/CSD> CheckDisk complete, ReadErrors 0
.../018:41/USD> Disk 1 (129) selected
.../018:41/GSC> No geo change detected for disk 1 (129)
.../018:41/WAS> AdmiSectors in use : 0+ 1+
129/018:41/USD> MBR for disk 1 (129)
129/018:41/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C FB 50 07 50 1F FC BE 1B 7C  |  3м.|P.P..|
016   BF 1B 06 50 57 B9 E5 01 F3 A4 CB BD BE 07 B1 04  |  ..PW.˽..
032   38 6E 00 7C 09 75 13 83 C5 10 E2 F4 CD 18 8B F5  |  8n.|.u...
048   83 C6 10 49 74 19 38 2C 74 F6 A0 B5 07 B4 07 8B  |  .It.8,t ..
064   F0 AC 3C 00 74 FC BB 07 00 B4 0E CD 10 EB F2 88  |  <.t....
080   4E 10 E8 46 00 73 2A FE 46 10 80 7E 04 0B 74 0B  |  N.F.s*F.~..t.
096   80 7E 04 0C 74 05 A0 B6 07 75 D2 80 46 02 06 83  |  ~..t. .uҀF..
112   46 08 06 83 56 0A 00 E8 21 00 73 05 A0 B6 07 EB  |  F..V..!.s. .
128   BC 81 3E FE 7D 55 AA 74 0B 80 7E 10 00 74 C8 A0  |  >}Ut.~..t 
144   B7 07 EB A9 8B FC 1E 57 8B F5 CB BF 05 00 8A 56  |  .멋.W˿..V
160   00 B4 08 CD 13 72 23 8A C1 24 3F 98 8A DE 8A FC  |  ...r#$?ފ
176   43 F7 E3 8B D1 86 D6 B1 06 D2 EE 42 F7 E2 39 56  |  Cцֱ.B9V
192   0A 77 23 72 05 39 46 08 73 1C B8 01 02 BB 00 7C  |  .w#r.9F.s....|
208   8B 4E 02 8B 56 00 CD 13 73 51 4F 74 4E 32 E4 8A  |  N.V..sQOtN2
224   56 00 CD 13 EB E4 8A 56 00 60 BB AA 55 B4 41 CD  |  V..V.`UA
240   13 72 36 81 FB 55 AA 75 30 F6 C1 01 74 2B 61 60  |  .r6Uu0.t+a`
256   6A 00 6A 00 FF 76 0A FF 76 08 6A 00 68 00 7C 6A  |  j.j..v..v.j.h.|j
272   01 6A 10 B4 42 8B F4 CD 13 61 61 73 0E 4F 74 0B  |  .j.B.aas.Ot.
288   32 E4 8A 56 00 CD 13 EB D6 61 F9 C3 49 6E 76 61  |  2V..aInva
304   6C 69 64 20 70 61 72 74 69 74 69 6F 6E 20 74 61  |  lid partition ta
320   62 6C 65 00 45 72 72 6F 72 20 6C 6F 61 64 69 6E  |  ble.Error loadin
336   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74  |  g operating syst
352   65 6D 00 4D 69 73 73 69 6E 67 20 6F 70 65 72 61  |  em.Missing opera
368   74 69 6E 67 20 73 79 73 74 65 6D 00 00 00 00 00  |  ting system.....
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
400   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
416   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
432   00 00 00 00 00 2C 44 63 4A BB 07 00 00 00 00 20  |  .....,DcJ.....
448   21 00 07 FE FF FF 00 08 00 00 C7 6F A9 17 00 FE  |  !........o..
464   FF FF 0F FE FF FF C7 77 A9 17 7A D4 8E 22 00 00  |  .....w.zԎ"..
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  |  ..............U
###
129/018:41/VEC> Start Verify EPBR Chain for disk 1 (129)
129/018:41/VEC> Listing current partitions on disk:
129/018:41/VEC>     NTFS (P)  Elements 50        2048   396980167     (189 Gb)
129/018:41/VEC>     NTFS (L)  BackupMar13   396982278    87586317      (42 Gb)
129/018:41/VEC>     NTFS (L)  BackupNov08   484568658   154946862      (74 Gb)
129/018:41/VEC>     NTFS (L)  BackupMar12   639515588   337252477     (161 Gb)
129/018:41/VEC> Extended starts at 396982215 (24711 0 1)
129/018:41/VEC> Partition Table info for sector 0 (0 0 1)
129/018:41/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | ....0..32..33 | .1023.254..63 | ......2048 | .396980167
..2 ...0 | ..0F | .1023.254..63 | .1023.254..63 | .396982215 | .579785850
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/018:41/VEC> 55AA sig Ok
129/018:41/VEC> Partition Table info for sector 396982215 (24711 0 1)
129/018:41/LOG> PartListDump requested at 396982215 (24711 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | .1023.254..63 | .1023.254..63 | ........63 | ..87586317
..2 ...0 | ..05 | .1023.254..63 | .1023.254..63 | ..87586380 | .154946925
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/018:41/VEC> 55AA sig Ok
129/018:41/VEC> Partition Table info for sector 484568595 (30163 0 1)
129/018:41/LOG> PartListDump requested at 484568595 (30163 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | .1023.254..63 | .1023.254..63 | ........63 | .154946862
..2 ...0 | ..05 | .1023.254..63 | .1023.254..63 | .242533310 | .337252540
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/018:41/VEC> 55AA sig Ok
129/018:41/VEC> Partition Table info for sector 639515525 (39808 0 6)
129/018:41/LOG> PartListDump requested at 639515525 (39808 0 6)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | .1023.254..63 | .1023.254..63 | ........63 | .337252477
..2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/018:41/VEC> 55AA sig Ok
129/018:41/LOG> Boot sector dump requested at 2048 (0 32 33)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 2048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 396980166
........MFT Location (dec): 36614714
.MFT Mirror Location (dec): 19145683
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 5A78DA6578DA3F85
........Volume Label (txt): Elements 50
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/018:41/VEC> BS and BBS not equal, dump follows;
129/018:41/LOG> Boot sector dump requested at 396982214 (24710 254 63)
### BootSectorDump for BStype NTFS (B)
...........Jump Code (hex): 000000
............OEM Name (txt): ........
....Bytes per Sector (dec): 0
.Sectors per Cluster (dec): 0
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): 00
..............Unused (hex): 0000
...Sectors per Track (dec): 0
.....Heads per Track (dec): 0
......Hidden Sectors (dec): 0
..............Unused (hex): 00000000
.............Unknown (hex): 00000000
.......Total Sectors (dec): 0
........MFT Location (dec): 0
.MFT Mirror Location (dec): 0
....Clusters per FRS (dec): 0
.Clusters/Indx Block (dec): 0
...........Volume ID (hex): 0000000000000000
........Volume Label (txt): (Err)
............Checksum (hex): 00000000
....Sector Signature (hex): 0000
129/018:41/LOG> Boot sector dump requested at 396982278 (24711 1 1)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 87586316
........MFT Location (dec): 3
.MFT Mirror Location (dec): 5474144
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CE2D69A04E8700
........Volume Label (txt): BackupMar13
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/018:42/VEC> BS and BBS equal
129/018:42/LOG> Boot sector dump requested at 484568658 (30163 1 1)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 154946861
........MFT Location (dec): 3
.MFT Mirror Location (dec): 9684178
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CD09E6FD1F56F0
........Volume Label (txt): BackupNov08
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/018:42/VEC> BS and BBS equal
129/018:42/LOG> Boot sector dump requested at 639515588 (39808 1 6)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 337252476
........MFT Location (dec): 2
.MFT Mirror Location (dec): 28890889
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CCF64D23EEA9A0
........Volume Label (txt): BackupMar12
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/018:42/VEC> BS and BBS not equal, dump follows;
129/018:42/LOG> Boot sector dump requested at 976768064 (60800 254 63)
### BootSectorDump for BStype NTFS (B)
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 212250716
........MFT Location (dec): 3
.MFT Mirror Location (dec): 13265669
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 01CCF64D23EEA9A0
........Volume Label (txt):
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/018:42/VEC> Verify EPBR Chain completed
129/018:42/USD> Select disk completed
129/018:52/MNU> - Main, Disk Ops
129/019:00/MNU> - Main, MBR ops
129/019:08/MNU> - Main, Options
129/019:22/MNU> - Support, Analyze Disk (no repair, create log)
129/019:30/SCN> DiskScan requested, ScanType is 3
129/019:30/SCN> from 0 (0 0 1) to 976773167 (60801 80 63), 976773168 sectors
129/019:30/SCN> Starting QuickScan (pre-vista) at 63 (0 1 1)
129/019:34/CDC> No DataCollection entries, CleanDatacollection aborted
129/019:34/MPL> No DataCollection entries, MakePartList aborted
129/019:34/SCN> Next QuickScan location at 0 (0 0 1)
129/019:35/SCN> QuickScan finished
129/019:35/SCN> Starting SmartScan (pre-vista) at 0 (0 0 1) (JMP=16065, RNG=63)
129/019:57/SCN> DiskScan aborted at JumpSector 899640 (56 0 1)
129/019:59/EXE> Analysis aborted
129/020:12/MNU> - Main, Disk Ops
129/020:19/MNU> - Main, MBR ops
129/020:23/MNU> - Main, Utilities
129/020:31/MNU> - Tools, Backup / Restore
129/020:40/MNU> - Main, Options
129/020:52/MNU> - Main, Quit
129/020:52/LOG> RunTime: 020:52
129/020:52/LOG> ### CLOSE LOG ###

Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #9 on: June 06, 2013, 09:40:45 AM »

Quote
My PC is a Dell laptop, 8-9 years old now. I read somewhere (a Dell forum I think) that the BIOS doesn't support an internal hard disk greater than about 120GB, and I was recently reading about 48bit LBA, so my BIOS almost certainly doesn't support that.
That is incorrect, the BIOS and the PC most likely WILL support that, given the age of the machine (if BIOS firmware and Windows service packs are up to date). Also, if it works now (and DP sees the disks correctly) this is not an issue.
Quote
Could it be that XP handles USB drives greater than 120GB (or whatever the non 48 bit LBA limit is) O.K., but that DOS (i.e. what MBRTOOL and Diskpatch run under) has a problem? Although not always - 2 of the USB disks seem to be mostly O.K.
Possible but not likely, given that DP sees the disk correctly (size and all).

The log shows none of the problems you have had earlier so I'm not sure what else I can add to what I've already posted.
Logged

aardvark_65
member

Posts: 9


« Reply #10 on: June 10, 2013, 12:20:48 PM »

The backup you posted has some marks that show that MBRtool actually "thought" it was reading the disk. Meaning, there are no errors as such, MBRtool actually thinks that the MBR contains &H41. This is significant because that tells me that the problem lies either with the actual connection, or with how MBRtool deals with that connection.

One thought I just had. The 500GB disk spins down very quickly after accessing the disk (after just seconds), which was very irritating, until I changed the disks around and am now using this one just for backup, where the fast spindown doesn't matter so much. It takes several seconds for it to spin up again. Could it be that MBRTOOL, after initially accessing the disk, somehow doesn't recognise that it has spun down, and hence "thinks" it has read the disk, when it hasn't?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #11 on: June 10, 2013, 08:55:37 PM »

Sounds plausible. The spin up/down is not an issue when running in Windows, but when running through the BIOS it may cause unexpected behavior. It should be easy enough to verify this, I suppose.
Logged

aardvark_65
member

Posts: 9


« Reply #12 on: June 13, 2013, 06:20:44 AM »

I imagine the only way to verify it would be to somehow stop the disk from spinning down so quickly - in fact, I think it might be parking the heads rather than actually spinning down, but anyway the end result is a significant delay when trying to access the disk again.

I've been looking around on the internet, but it's all a bit unclear. It seems there are WD utilities that address this, but I haven't found anything for my particular WD disk model. I might have to post a question on the WD forums.
Logged
aardvark_65
member

Posts: 9


« Reply #13 on: June 19, 2013, 09:29:18 AM »

The WD forum advised that there is no way to stop the disk spinning down so quickly.

Today I tried running MBRTOOL from a RAM disk in Win98 DOS, also writing the backup and DMP files to the RAM disk, to try to speed up the running of MBRTOOL so that perhaps the USB disk didn't spin down between MBRTOOL operations. However I wasn't quick enough, and the disk still span down - I could see the delay when I ran a MBRTOOL option that required reading the disk. However MBRTOOL seemed to wait for the disk to spin up before displaying the MBR, or writing the DMP or backup files. The MBR display option (to the screen) worked the first time, but not when I tried it a second and third time, and both the DMP file and backup file contained hex 41 everywhere.

I exited MBRTOOL, and restarted it. This time I was somehow quick enough to stop the disk spinning down (although the initial display to the screen of the MBR had to wait for the disk to spin up), and everything was O.K. - the display to the screen, the backup file, and the DMP file.

All my runs to date had been using the MBRTOOL menus. Still using the RAM disk, I then decided to try running the options from the command line, i.e.

MBRTOOL /DSP /DSK:1
MBRTOOL /DMP /DSK:1
MBRTOOL /BCK /DSK:1 /FIL:xxxxxx

and they all worked O.K. I was typing the commands directly at the command prompt, i.e. not using a BAT file, so the disk span down between commands. To confirm it, I reran them from the command line, and again all was O.K.

Hence, it seems that the disk spindown does cause problems. However the FIRST command to be issued that accesses the disk (or the only command when specified at the command line) seems to work O.K.

From now on when running MBRTOOL with this disk, I'll be using the command line!

Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #14 on: June 21, 2013, 11:14:46 AM »

I'm not sure I fully understand what is going on here, but it's good to see you found a workaround.
Logged

Pages: [1] Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!