3 TB Drive is now showing up as a 1 TB Drive!!!

I have a My book External Hard Drive from Western Digital 3.0 USB Size of the Drive is 3 TB , i also have a Asus RT-N16 Multi-functional Gigabit Wireless N Router with USB Storage, Printer and Media Server ..

So here is the problem i Connect the Drive to the Router and for some reason it undersized the hard drive to 1 TB and i can't get the other 2 TB to show up......does anyone have any idea what to do without losing all my Data and reformatting.
24 answers Last reply
More about drive showing drive
  1. anyone ? any other info you guys need to help?
  2. If you connect the HDD to a PC, what size is shown there?

    Page 25 of the RT-N16 user manual states that "the wireless router works with most USB HDDs/Flash disks (up to 2TB size) and supports read-write access for FAT16, FAT32, EXT2, EXT3, and NTFS".

    User Guide for RT-N16 Multi-functional Gigabit Wireless N Router:
    http://www.bhphotovideo.com/lit_files/46056.pdf

    I would examine sector 0 of the HDD using a disc editor.

    DMDE (DM Disk Editor and Data Recovery):
    http://softdm.com/download.html

    Your 3TB My Book has an LBA size of 4KB rather than 512 bytes. Perhaps the router was confused by this. If for some reason the router has modified your drive, DMDE should tell us what happened.
  3. fzabkar said:
    If you connect the HDD to a PC, what size is shown there?

    Page 25 of the RT-N16 user manual states that "the wireless router works with most USB HDDs/Flash disks (up to 2TB size) and supports read-write access for FAT16, FAT32, EXT2, EXT3, and NTFS".

    User Guide for RT-N16 Multi-functional Gigabit Wireless N Router:
    http://www.bhphotovideo.com/lit_files/46056.pdf

    I would examine sector 0 of the HDD using a disc editor.

    DMDE (DM Disk Editor and Data Recovery):
    http://softdm.com/download.html

    Your 3TB My Book has an LBA size of 4KB rather than 512 bytes. Perhaps the router was confused by this. If for some reason the router has modified your drive, DMDE should tell us what happened.

    If you connect the HDD to a PC, what size is shown there?
    it says 52.7GB free of 746 GB ...

    ok i got the DMDE but what do i do with it?

    Ok with DMDE i went to Partitioning Says current partitioning

    Logical drive I: NTFS Size 3TB indicators nothing First Sector 0 Last Sector 732 588 079

    My Book (I) NTFS Size 802 GB indicators B F First Sector 0 Last Sector 195 687 167

    My Book (I) NTFS Size 802 GB indicators C F First Sector 0 Last Sector 195 687 167
    Sub under no name :

    Partition Found NTFS Size 802 GB Indicators X XX First Sector 536 870 912 Last Sector 732 558 079

    Sub $Volume 02 Found NTFS Size 802 GB XCXX First 536 870 912 079


    So how do i make it just one big Partition so i can have my 3 TB hard back .
  4. Normally the 3TB My Books ship with a single 3TB MBR partition with a sector size of 4096 bytes. Your original partition table would reflect that.

    732 588 080 sectors x 4096 bytes per sector = 3 000 680 775 680 bytes

    However, you now appear to have an 800GB partition at the beginning of the drive and a second 800GB partition at the end.

    195 687 167 x 4096 = 801 534 636 032

    (732 558 079 - 536 870 912) x 4096 = 801 534 636 032

    Could we see the contents of sector 0 in hexadecimal mode (select Mode -> Hexadecimal)?

    BTW, I'm assuming that you still want to recover your data, if possible.
  5. Yes i would like to keep all my Data if Possible ,

    Sector 0: EB 52 90 4E-54 46 53 20-20 20 20 00-10 01 00 00

    think you are looking for the EB

    in the next Partition it has 46 49 4C 45-30 00 09 00-C5 26 02 09-00 00 00 00 F
  6. I'd like to see the first 512 bytes, from offset 0 to offset 200.

    Something like this ...
    http://thestarman.pcministry.com/asm/mbr/Win2kmbr.htm#CHS

    Your hex data look like you may be viewing the boot sector of the logical drive:
    http://thestarman.pcministry.com/asm/mbr/NTFSbrHexEd.htm

    Instead you need to select the physical drive. Sector 0 of the physical drive and sector 0 of the logical drive are two different things. The former contains the partition table.
  7. There has to be some way for me to Export some of this Text and paste it here...i found a way to export it out of the program but no way to read it and paste it here.. any idea's?
  8. Tools -> Copy Sectors
    First Sector = 0
    Number of Sectors = 1
    Destination -> File -> sec_0_1.ima

    Upload the IMA file to a file sharing service.
  9. fzabkar said:
    Tools -> Copy Sectors
    First Sector = 0
    Number of Sectors = 1
    Destination -> File -> sec_0_1.ima

    Upload the IMA file to a file sharing service.



    Thank you for your help you have been great man here are the Links. ,,,

    https://www.dropbox.com/s/emh85m0p2xibzd8/sec_0_1.ima

    https://www.dropbox.com/s/cucpri2v10878u1/sec_0_2.ima
  10. The following section is your partition table:

    Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

    000001B0 00 00 00 00 00 2C 44 63 C8 DC 02 00 00 00 00 04
    000001C0 05 00 07 FE FF FF 00 01 00 00 00 F3 A9 2B 00 00
    000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

    It is telling you that the drive has a single NTFS partition (type 07), beginning at LBA 256 (= 0x0100) and with a capacity of 3TB (0x2BA9F300 x 4096 = 3 000 557 895 680).

    http://www.google.com/search?q=0x2BA9F300+x+4096+in+decimal

    Therefore it appears that sector 0 has not been modified.

    I would now examine sector 256 of the physical drive. That should be the NTFS boot sector.

    There should also be an identical backup boot sector at the end of the partition, ie sector 732558335.

    0x0100 + 0x2BA9F300 - 1 = 732 558 335
  11. fzabkar said:
    The following section is your partition table:

    Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

    000001B0 00 00 00 00 00 2C 44 63 C8 DC 02 00 00 00 00 04
    000001C0 05 00 07 FE FF FF 00 01 00 00 00 F3 A9 2B 00 00
    000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

    It is telling you that the drive has a single NTFS partition (type 07), beginning at LBA 256 (= 0x0100) and with a capacity of 3TB (0x2BA9F300 x 4096 = 3 000 557 895 680).

    http://www.google.com/search?q=0x2BA9F300+x+4096+in+decimal

    Therefore it appears that sector 0 has not been modified.

    I would now examine sector 256 of the physical drive. That should be the NTFS boot sector.

    There should also be an identical backup boot sector at the end of the partition, ie sector 732558335.

    0x0100 + 0x2BA9F300 - 1 = 732 558 335



    So how do we fix or repair the Drive, do you think it would be safe to remove one of the 800GB partition .
  12. IMHO, before you start repairing anything, you should try to ascertain the nature and extent of the damage. That's why I would like to see the contents of sectors 256 and 732558335.

    The original layout of your drive appears to be as follows:

    0TB |-- LBA 0 -- LBA 256 ------------------- LBA 732558335 --| 3TB

    After connecting your drive to your router, it appears that an 800GB volume has been inserted near the end of the drive, between sectors 536870912 (point X) and 732558079 (point Y).

    0TB |-- LBA 0 -- LBA 256 -------------X--800GB--Y-- LBA 732558335 --| 3TB

    Point X is right at the 2TiB mark in the user area:

    http://www.google.com.au/search?q=536870912+x+4096+bytes+in+terabytes

    536 870 912 x 4096 bytes = 2 terabytes

    So at the moment it appears that any files that were in the user area between points X and Y may have been overwritten, at least partially.

    If you could also show us the contents of sectors 536870912 and 732558079, that would help us confirm what has happened. Once we know the full extent of the damage, then we can go about trying to recover as much of your data as possible.
  13. fzabkar said:
    IMHO, before you start repairing anything, you should try to ascertain the nature and extent of the damage. That's why I would like to see the contents of sectors 256 and 732558335.

    The original layout of your drive appears to be as follows:

    0TB |-- LBA 0 -- LBA 256 ------------------- LBA 732558335 --| 3TB

    After connecting your drive to your router, it appears that an 800GB volume has been inserted near the end of the drive, between sectors 536870912 (point X) and 732558079 (point Y).

    0TB |-- LBA 0 -- LBA 256 -------------X--800GB--Y-- LBA 732558335 --| 3TB

    Point X is right at the 2TiB mark in the user area:

    http://www.google.com.au/search?q=536870912+x+4096+bytes+in+terabytes

    536 870 912 x 4096 bytes = 2 terabytes

    So at the moment it appears that any files that were in the user area between points X and Y may have been overwritten, at least partially.

    If you could also show us the contents of sectors 536870912 and 732558079, that would help us confirm what has happened. Once we know the full extent of the damage, then we can go about trying to recover as much of your data as possible.


    First link is for the Primary Drive 73258330 Sectors : https://www.dropbox.com/s/k20qradhl4puzbo/PrimaryDrive-73258330-732558335-Sectors

    Primary Drive 250-260 Sectors : https://www.dropbox.com/s/aawdrxyjuvdkn63/PrimaryDrive-250-260-Sectors

    2nd Petition drive 732558334 Sectors : https://www.dropbox.com/s/ul7wdfxpbz4ckds/2ndDrive-732558334-732558335-Sectors


    2nd Petition Drive 250 - 260 Sectors : https://www.dropbox.com/s/9psgeh4smhvqldh/2ndDrive-250-256-Sectors


    hope these help .
  14. Thanks. I think I can see what happened. Give me some time and I'll come back with some ideas.
  15. Sector 256 and sector 732558335 both look like the following:

    Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

    00006000 EB 52 90 4E 54 46 53 20 20 20 20 00 10 01 00 00 ...NTFS
    00006010 00 00 00 00 00 F8 00 00 3F 00 FF 00 00 01 00 00
    00006020 00 00 00 00 80 00 80 00 FF F2 A9 0B 00 00 00 00
    00006030 00 00 0C 00 00 00 00 00 02 00 00 00 00 00 00 00

    The above data are telling us that the partition contains an NTFS volume with a sector size of 4096 (= 0x1000) bytes and a capacity of 195687168 (= 0x0BA9F2FF + 1 = 0x0BA9F300) sectors, ie 801GB. The volume begins at sector 256 (= 0x0100).

    If you compare these data against the data in the partition table in sector 0 we find that the partition sizes don't match. That is, the boot sector reports a size of 0x0BA9F300 sectors while the partition table reports 0x2BA9F300 sectors.

    0x0BA9F300
    0x2BA9F300

    The difference is 0x20000000. This equates to a capacity of 2TiB.

    Therefore it appears that the router cannot handle drives larger than 2TiB (= 2.2TB), irrespective of the sector size.

    That said, not only has the router messed up the beginning of the drive, it has also added an 800GB logical volume at the 2TiB point. To me that's bizarrre.

    Can you tell us exactly what you did? Did the drive have any data before you attached it to your router? Did you format the drive while it was attached to the router, or did the router do this on its own? Can you still recover any data while the drive is on the router or the PC?
  16. fzabkar said:
    Sector 256 and sector 732558335 both look like the following:

    Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

    00006000 EB 52 90 4E 54 46 53 20 20 20 20 00 10 01 00 00 ...NTFS
    00006010 00 00 00 00 00 F8 00 00 3F 00 FF 00 00 01 00 00
    00006020 00 00 00 00 80 00 80 00 FF F2 A9 0B 00 00 00 00
    00006030 00 00 0C 00 00 00 00 00 02 00 00 00 00 00 00 00

    The above data are telling us that the partition contains an NTFS volume with a sector size of 4096 (= 0x1000) bytes and a capacity of 195687168 (= 0x0BA9F2FF + 1 = 0x0BA9F300) sectors, ie 801GB. The volume begins at sector 256 (= 0x0100).

    If you compare these data against the data in the partition table in sector 0 we find that the partition sizes don't match. That is, the boot sector reports a size of 0x0BA9F300 sectors while the partition table reports 0x2BA9F300 sectors.

    0x0BA9F300
    0x2BA9F300

    The difference is 0x20000000. This equates to a capacity of 2TiB.

    Therefore it appears that the router cannot handle drives larger than 2TiB (= 2.2TB), irrespective of the sector size.

    That said, not only has the router messed up the beginning of the drive, it has also added an 800GB logical volume at the 2TiB point. To me that's bizarrre.

    Can you tell us exactly what you did? Did the drive have any data before you attached it to your router? Did you format the drive while it was attached to the router, or did the router do this on its own? Can you still recover any data while the drive is on the router or the PC?


    Ok the Drive was in use before i moved it to the Router it had 800 or so GB of Data on the Drive , i removed it from the Computer and attached it to the router , it booted fine and i was able to get any Data but i seen i had Zero space on the Drive so i checked it and it was just gone......i removed it from the Router and Attached it back to the Computer to find out if it would show 3 TB but nothing......i even checked it with windows Disk Management to see if it had mult Petitions stopping me from seeing the 3 TB of Drive Space ...nothing....


    i am Still able to use any Data on the Drive just can't use anymore Space on it... that's all i got .


    I would just reformat the drive and be done with the Problem but i have no where to Move the Data ...really should buy another drive for this, but as it stands right now i am ok with using the Drive on the computer if i can get the 3TB working again .
  17. It's not a good idea to work on live data, but if you are willing to try, then you can return the partition size to its original condition with two simple sector edits. If things don't turn out as we hope, then you could always undo the edits in the same easy way.

    Specifically, you would need to go to sectors 256 and 732558335 and change the "0B" byte on the third line to "2B".

    That is, change this ...

    EB 52 90 4E 54 46 53 20 20 20 20 00 10 01 00 00
    00 00 00 00 00 F8 00 00 3F 00 FF 00 00 01 00 00
    00 00 00 00 80 00 80 00 FF F2 A9 0B 00 00 00 00

    ... to this ...

    EB 52 90 4E 54 46 53 20 20 20 20 00 10 01 00 00
    00 00 00 00 00 F8 00 00 3F 00 FF 00 00 01 00 00
    00 00 00 00 80 00 80 00 FF F2 A9 2B 00 00 00 00

    Launch DMDE, choose your Physical Drive, and then ESCape out of the Partitions menu.

    Select ...

    Mode -> Hexadecimal
    Editor -> Goto Object Offset
    Sector = 256
    Sector offset = 0
    select Dec radio button
    type OK

    You should now be at LBA 256.

    To switch from readonly mode to edit mode, select Edit -> Edit Mode.

    Make the change then select Edit -> Write Changes.

    Repeat the procedure for sector 732558335.

    Now exit DMDE, safely eject the USB drive, and then reconnect the drive. This will force the OS to re-examine the file system. Hopefully you will now see the full 3TB capacity and your data will be intact. Be aware that any file that was overwritten by the router will be corrupt. Therefore I suggest that you do not write any new data to your drive without testing the existing files. For example, I would check your JPEGs in an image viewer (you could regenerate and inspect the thumbnails on another drive), and I would confirm that all your videos play correctly.
  18. fzabkar said:
    It's not a good idea to work on live data, but if you are willing to try, then you can return the partition size to its original condition with two simple sector edits. If things don't turn out as we hope, then you could always undo the edits in the same easy way.

    Specifically, you would need to go to sectors 256 and 732558335 and change the "0B" byte on the third line to "2B".

    That is, change this ...

    EB 52 90 4E 54 46 53 20 20 20 20 00 10 01 00 00
    00 00 00 00 00 F8 00 00 3F 00 FF 00 00 01 00 00
    00 00 00 00 80 00 80 00 FF F2 A9 0B 00 00 00 00

    ... to this ...

    EB 52 90 4E 54 46 53 20 20 20 20 00 10 01 00 00
    00 00 00 00 00 F8 00 00 3F 00 FF 00 00 01 00 00
    00 00 00 00 80 00 80 00 FF F2 A9 2B 00 00 00 00

    Launch DMDE, choose your Physical Drive, and then ESCape out of the Partitions menu.

    Select ...

    Mode -> Hexadecimal
    Editor -> Goto Object Offset
    Sector = 256
    Sector offset = 0
    select Dec radio button
    type OK

    You should now be at LBA 256.

    To switch from readonly mode to edit mode, select Edit -> Edit Mode.

    Make the change then select Edit -> Write Changes.

    Repeat the procedure for sector 732558335.

    Now exit DMDE, safely eject the USB drive, and then reconnect the drive. This will force the OS to re-examine the file system. Hopefully you will now see the full 3TB capacity and your data will be intact. Be aware that any file that was overwritten by the router will be corrupt. Therefore I suggest that you do not write any new data to your drive without testing the existing files. For example, I would check your JPEGs in an image viewer (you could regenerate and inspect the thumbnails on another drive), and I would confirm that all your videos play correctly.



    Didn't work i did what you said and made the edits and saved it now the drive is saying The File or Directory is Corrupted and unreadable. any other idea's ? and thank you for your help .
  19. I would restore the two bytes to their original values, safely eject and reconnect the drive, and then confirm that the file system is as it was.

    My next approach would be to edit the partition table in sector 0 to match the boot sector.

    In sector 0, I would change this ...

    Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

    000001B0 00 00 00 00 00 2C 44 63 C8 DC 02 00 00 00 00 04
    000001C0 05 00 07 FE FF FF 00 01 00 00 00 F3 A9 2B 00 00
    000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

    ... to this ...

    000001B0 00 00 00 00 00 2C 44 63 C8 DC 02 00 00 00 00 04
    000001C0 05 00 07 FE FF FF 00 01 00 00 00 F3 A9 0B 00 00
    000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

    The change is at offset 0x01CD, from 2B to 0B.

    Once again, safely eject and reconnect the drive to allow the OS to re-examine the file system.

    In Disk Management you should now see a single 746GiB NTFS partition, plus 2TiB of unallocated space. Do not be tempted to add new partitions, or to write anything to the drive. Just confirm that your files are accessible as before, and that they are not corrupt, particularly the ones that were added last.

    If this works out, then I suggest that we add a second entry to the partition table. This entry will correspond to the 800GB volume at the end of the drive, just beyond the 2TiB point. This volume appears to have been added when the drive was on the router. If this is successful, then you should be able to see two NTFS volumes.
  20. fzabkar said:
    I would restore the two bytes to their original values, safely eject and reconnect the drive, and then confirm that the file system is as it was.

    My next approach would be to edit the partition table in sector 0 to match the boot sector.

    In sector 0, I would change this ...

    Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

    000001B0 00 00 00 00 00 2C 44 63 C8 DC 02 00 00 00 00 04
    000001C0 05 00 07 FE FF FF 00 01 00 00 00 F3 A9 2B 00 00
    000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

    ... to this ...

    000001B0 00 00 00 00 00 2C 44 63 C8 DC 02 00 00 00 00 04
    000001C0 05 00 07 FE FF FF 00 01 00 00 00 F3 A9 0B 00 00
    000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

    The change is at offset 0x01CD, from 2B to 0B.

    Once again, safely eject and reconnect the drive to allow the OS to re-examine the file system.

    In Disk Management you should now see a single 746GiB NTFS partition, plus 2TiB of unallocated space. Do not be tempted to add new partitions, or to write anything to the drive. Just confirm that your files are accessible as before, and that they are not corrupt, particularly the ones that were added last.

    If this works out, then I suggest that we add a second entry to the partition table. This entry will correspond to the 800GB volume at the end of the drive, just beyond the 2TiB point. This volume appears to have been added when the drive was on the router. If this is successful, then you should be able to see two NTFS volumes.



    not able to restore the drive to the way it was i have all new Lay out ok so i am in 256 with an offset of 0 and here is what i have for the first 3 lines .

    E5 26 9C ED-BA 0E 23 16-41 64 DC 4E-CD 18 2C 31
    65 17 76 93-BE 99 9B 9C-67 3E 05 29-92 7A 21 FC
    4D 3D 05 5F-46 9E 37 A4-05 C2 AF-EC CE C5 4D


    Here are the Sectors now after the first edit, https://www.dropbox.com/s/n4pppxbzxvmk2gh/After%20the%20edit%20Sector%20256-260

    https://www.dropbox.com/s/5lp65dgr6k3c6vx/After%20the%20edit%20Sector%20732558330-732558335
  21. Your edits were OK. Assuming that you did not do anything else to the drive, ISTM that you may now be showing us the logical drive rather than the physical one.

    What do you see at sector 0? Do see an NTFS boot sector, or do you see the MBR?

    BTW, I don't understand what you mean by "all new Lay out". Are you perhaps referring to the second partition window when DMDE starts up? If so, then press the Escape key.
  22. ok did the Edit to the Boot sector 0 and saved and checked the files they are all working fine, here is what i have in Disk Management .

    746.49 GB NTFS Primary partition
    1301.51GB Unallocated
    746.49 GB Unallocated

    what is are next Step.


    BTW, I don't understand what you mean by "all new Lay out". Are you perhaps referring to the second partition window when DMDE starts up? If so, then press the Escape key.

    Ya....think i got lost in all the code nevermind on it... hah
  23. It looks like your data are intact. I think we should now try to see the 800GB NTFS volume at the end of the drive. However, we would first need to see the contents of the following physical sectors:

    536870912 - MBR + partition table
    536871168 - NTFS boot sector
    732558079 - data area

    I suspect that my previous guess was slightly out and that I was looking at logical sectors rather than physical ones, in which case logical sector 732558079 (point Y) is actually physical sector 732558335, and logical sector 536870912 (point X) is actually physical sector 536871168. This would then suggest that physical sector 536870912 would contain a second MBR and partition table which would have been created when the drive was attached to the router.

    Once we see the above three physical sectors, then we will know how to edit sector 0. We will also need to edit sectors 536871168 and 732558335.

    BTW, notice that Windows Disk Management has split the unallocated space into two sections, presumably because it insists on a 2TiB boundary, irrespective of the larger sector size.

    1301.51GB + 746.49 GB = 2048GB = 2TiB

    As for the router, what it appears to have done is to wrap any sector beyond 2TiB back to zero, ie when the router accesses sector N, it actually accesses sector 2TiB + N. The 2TiB point corresponds to physical sector 536870912.

    sector 0 -> sector (536870912 + 0)
    sector 256 -> sector (536870912 + 256)
    sector (256 + 195687167) -> sector (536870912 + 256 + 195687167) = sector 732558335

    That's why we see two partition tables and two NTFS volumes.
  24. fzabkar said:
    It looks like your data are intact. I think we should now try to see the 800GB NTFS volume at the end of the drive. However, we would first need to see the contents of the following physical sectors:

    536870912 - MBR + partition table
    536871168 - NTFS boot sector
    732558079 - data area

    I suspect that my previous guess was slightly out and that I was looking at logical sectors rather than physical ones, in which case logical sector 732558079 (point Y) is actually physical sector 732558335, and logical sector 536870912 (point X) is actually physical sector 536871168. This would then suggest that physical sector 536870912 would contain a second MBR and partition table which would have been created when the drive was attached to the router.

    Once we see the above three physical sectors, then we will know how to edit sector 0. We will also need to edit sectors 536871168 and 732558335.

    BTW, notice that Windows Disk Management has split the unallocated space into two sections, presumably because it insists on a 2TiB boundary, irrespective of the larger sector size.

    1301.51GB + 746.49 GB = 2048GB = 2TiB

    As for the router, what it appears to have done is to wrap any sector beyond 2TiB back to zero, ie when the router accesses sector N, it actually accesses sector 2TiB + N. The 2TiB point corresponds to physical sector 536870912.

    sector 0 -> sector (536870912 + 0)
    sector 256 -> sector (536870912 + 256)
    sector (256 + 195687167) -> sector (536870912 + 256 + 195687167) = sector 732558335

    That's why we see two partition tables and two NTFS volumes.



    Here you go Sorry for the wait,

    https://www.dropbox.com/s/kbskbxczyndsaiz/Sector_536870912_12-18-2012

    https://www.dropbox.com/s/a21hh598h9zuoip/Sectors_536871168_12-18-2012

    https://www.dropbox.com/s/l3rjzxvry31983t/Sectors_732558079_12-18-2012


    you wanted these right anything else?
Ask a new question

Read More

Hard Drives External Hard Drive Storage