Cixert

@Andalu In NTFS one partition formated with cluster 4KiB I have tested up to 2.2 TiB with "H2testw" and the result is perfect. No problems, no data corruption, no BSOD. Afterwards I added 0.5 TiB with videos and tested Mediainfo, the information given by Mediainfo is correct. If your data is secure you should do a test with H2testw to clear up any doubts. Make sure in the Device Manager that the hard disk is working with the driver version 8.0.1.0. @Multibooter It's not unusual for you to be asked for .Net 4 and not for me. It's possible that I have some residual files from my previous installation of .NET Framework, I don't know. Other programs that require .NET 4 ask me to install it. I think the last version compatible with Windows XP is 813 for Hard Disk Manager, I haven't found an installer for Partition Manager (last 779). Only in WinPE version. @Dave-H Finally, I'm glad it works. Please keep us posted if you manage to get the eSATA adapter working as well. What physical sector size does your hard disk have? Model?

Yes, thank you very much. I have read about this patch for 3TB hard disks. https://msfn.org/board/topic/158361-2tib-external-usb-drive-and-winxp-of-course/ I understand that the partition style is MBR. So can I buy a WD "Easystore" hard disks up to 16TB and apply the patch on Windows XP? Is this hard disks readable by Windows Seven and 10 on the same computer?

This BSOD is described here, it seems that the 2 patches would have to be applied to improve the system http://hardwarefetish.com/524-paragon-gpt_loadersys-bsod-analysis-and-fix I am not very clear on how the patches are applied. It says that a bak file of gpt_loader.sys is created, but I don't know if the bak is the good one, the bad one, or if it needs to be renamed. It is necessary to apply the 2 patches and with each patch a bak file is created. http://hardwarefetish.com/777-paragon-gpt-loader-3

I read in some comments from the forum about an alternative partition system to GPT with the name EMBR that could work with inherited computers and hard disks + 2TB. I am not sure what it is and if there is an operational version. The info in this link says that it is not yet able to write in NTFS and other formats. I don't know if there is another version. https://www.fysnet.net/embr/index.php

Can you say that hard disks you have in MBR format and how have you managed to work in XP? Thanks @98SE Can you say what USB adapter did you connect the hard disk? I am having trouble finding a modern USB adapter that works with 5 TB

No paragon version has asked me .Net Framework 4.0 These require C++. MD5 checksums of Paragon Hard Disk Manager 15 build 779: gpt_loader.sys > MD5: B0AFB269EBA85F9EC264035640319138 gpt_loader.inf > MD5: B04C4E8E712B6CB283C4AB1C53F06226 gpt_loader.cat > MD5: 9FC7222187B2A809C21E543E928686BE The values are the same, can you also upload the MD5 value of... install_xp.reg > MD5: ED75D2BD6084EAD84A9ADABD4BD241DD install.reg > MD5: 22AA73696C1D1E4FFF650FC606A2192F install_xp.reg Make changes in the registry to avoid BSOD on Fat32 Boot, maybe some more change. This is a fork version, it was commented here. https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/22/#findComment-1263483 @Andalu I am reading other forum publications that report a 2TIB Limit for NTFS. I will verify that. What cluster size are you using to format, 4 KiB?

Once installed you can check the contents of the "gpt_loader" folder to see if it is different. I have downloaded the demo versions but these do not come with the driver.

@Andalu tell me what method you used to copy and verify files. I will try to replicate it to check what happens. That message appears when you install hardware that does not have a digital signature.You have to disable the option "do not install unsigned software drivers."My PC + Hardware + Driver Signature". You also have to include the Windows 2003 drivers in the sp3.cab file, I explain it here, now with the text crossed out... because the 2 TiB limitation https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/?do=findComment&comment=1249360

Oops, sorry. I don't know what could be wrong. My disk.sys version is different, it's 5.1.2600.5512. Although this seems unlikely to be the reason. I currently have a Toshiba HDWD260 "6Tb hard disk" with 6 exFAT partitions. The physical sector size is 512 bytes, most likely on that Seagate it is 4096 bytes. I initialized the drive quite a while ago, I think from Windows Seven and then defragmented the partitions. The first partition is 1.42 TiB and the rest are smaller. I also have the hard disk connected directly to the motherboard with IDE mode. In some kind of initial test I also had the BSOD occurred for gpt_lo~1.sys but then it has not happened again.

You can try this universal driver "VueScan 9.2.25 x86". This is the latest version compatible with Windows 2000.

A while ago I found this driver to work with exFAT partitions in Windows 2000 vanilla but it didn't work for me. https://web.archive.org/web/20130808055452/http://www.merawindows.com/Forums/tabid/324/forumid/15/postid/35485/scope/posts/Default.aspx I even tried using the Windows XP driver dlls but I still couldn't read exFAT partitions. Right now if I connect an external USB hard disk with an exFAT partition then Windows 2000 won't boot, nothing happens it just keeps trying to boot. If I connect the hard disk after Windows 2000 has booted then other partitions can be accessed. Do you know of any way to read exFAT partitions in Windows 2000 vanilla? Thanks

Working with the GPT driver 8.0.1.0 included in Paragon Partition Manager 15 from Windows XP, I have completely filled a 6 Tb hard disk and successfully verified that the data written to it is correct both from Windows XP and Windows Seven with the backup program "EaseUS Todo Backup 13.5". I think that the issue of working correctly with GPT disks in Windows XP can be considered "solved", without prejudice to fixing any problems that may arise regarding hardware compatibility and software tools. Apparently, the 2 TiB limit affects both MBR and GPT. The difference is that in Windows XP MBR partitions larger than 2 TiB are correctly read if we find the appropriate hardware, so right now the limitation is in the hardware. Meanwhile, the 2 TiB limitation remains built into Windows XP with GPT hard disks. This limitation prevents the hard disks from working properly unless is installed the GPT driver 8.0.1.0 contents at Paragon Partition Manager 15. At the moment it is not possible to properly install the driver without running the program installer. However, in the installer you can choose to install only the driver. I have not yet tested how Paragon Partition Manager works when editing GPT partitions. Chkdsk does not work until Windows XP is booted. Also most software tools for editing hard disk partitions do not work on Windows XP with GPT hard disks. See test tools edit partitions at: https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/3/#findComment-1249366

I have tested the drivers for Windows 2003. For some unknown reason, Windows 2003 drivers for GPT hard drives have a 2TiB size limit. Until we figure out why, please do not use these drivers. If you use a single partition on the hard drive it will appear to use all the available space, but if you have partitions that start above 2 TiB these will be marked as unformatted. If a partition starts before the 2 TiB limit it will be visible, but if it ends after the 2 TiB limit it will write with errors. I have also retested all my versions with Paragon GPT Loader. Below is a summary results. I have to point out that the newest version available for Windows XP contains the 8.0.1.0 driver with important fixes!!! The 10.5.0.95 driver by some mistake only works up to 2 TiB. This was offered before the latest Paragon Partition Manager 15 release, so Paragon Partition Manager 15 with 8.0.1.0 driver is the newest official version of Paragon GPT Loader, with important fixes in the Windows registry for FAT32 users. Blue screens for me occur on FAT32 boot drives in the versions indicated with these asterisks. *(1) Blue screen "gpt_loader.sys" on FAT32 boot drives if a GPT disk is connected, if no GPT disk is connected Windows XP boots normally. I think it worked in the past by modifying the registry as indicated below, but now I get a blue screen even after modifying the registry. *(2) Blue screen 0x7B on FAT32 boot drives if gptloader.sys registry key is not modified by gpt_lo~1.sys Install Paragon GPT loader, but before rebooting run regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gpt_loader change the value of the key ImagePath from system32\DRIVERS\gpt_loader.sys to system32\DRIVERS\GPT_LO~1.SYS and then reboot, problem solved. RELEASED VERSIONS Paragon GPT Loader 8.0.1.0 original --> Not tested Paragon GPT Loader 10.5.0.95 original --> Not tested FORK VERSIONS Paragon GPT Loader 8.0.1.2 fork --> Blue screen = gpt_loader.sys *(1) --> Works +2TiB = NO --> Driver version = 8.0.1.2 (gpt_loader.sys) --> Digital signature date 2010-12-13 Paragon GPT Loader 11.0.0.175 fork --> Blue screen = NO --> Works +2TiB = NO --> Driver version = 11.0.0.175 (gptmount.sys) --> Digital signature date 2016-09-23 HFS VERSIONS Paragon HFS for Win 10.5.0.95 (2015-06-22) --> Blue Screen = 0x7B *(2) --> Working +2TiB = NO --> Driver version = 10.5.0.95 (gpt_loader.sys) --> Digital signature date 2015-06-22 Paragon HFS for Win 11.0.0.175 --> Not Windows XP compatible Seagate Paragon HFS4WIN --> Not Windows XP compatible SUITE VERSIONS Paragon Hard Disk Manager 11 Suite "Paid" (2011-04-12) --> Blue Screen = 0x7B *(2) --> Working +2TiB = YES --> Driver version = 8.0.1.0 (gpt_loader.sys) --> Digital signature date 2011-02-16 Paragon Partition Manager 15 Professional x86 v10.1.25.779 (2015-09-18) --> Blue screen = NO* --> Works +2TiB = YES --> Driver version = 8.0.1.0 (gpt_loader.sys) --> Digital signature date 2011-02-16 *Contains "install_xp.reg" to fix blue screen on FAT32 boot drives. FIXED PATCHES Paragon GPT Loader 8.0.1.0 patch 1 (gptpatch1) Paragon GPT Loader 8.0.1.0 patch 2 (gptpatch2) -->These are fixes for the 8.0.1.0 driver Is it necessary to apply them on FAT32 or are for NTFS errors? It doesn't seem like it, considering that these patches were merged into the 8.0.1.2 fork and this one doesn't work for me. In any case, I don't understand the explanation given for applying the patches What is the gpt_loader.sys.bak file created, the good one or the old one? When applying the two patches, these two files have been created in \WINDOWS\system32\drivers gpt_loader.sys.bak gpt_loader.sys.bak2 Considering that my current version installed with Paragon Partition Manager 15 works without problems, I would prefer to revert the patch application. Read the instructions carefully and consider whether you need to apply patches. They can improve performance and fix a problem. http://hardwarefetish.com/777-paragon-gpt-loader-3 http://hardwarefetish.com/612-gpt_loader-sys-revisited-file-read-problem http://hardwarefetish.com/524-paragon-gpt_loadersys-bsod-analysis-and-fix

Personally I do not think that there is a limitation with the file system beyond the cluster size that I have mentioned above. But I encourage you to continue performing the tests, the more it is experienced better

Does anyone else work with MBR +2TB hard disks? A bit of literature: -USB to SATA bridge chips and >2Tb drives https://goughlui.com/2013/10/02/experiment-usb-to-sata-bridge-chips-and-2tb-drives/ -4ke (4k emulation) https://superuser.com/questions/1271871/4k-emulation-sata-usb-controllers -Convert unit 4096 to 512 https://www.hddoracle.com/viewtopic.php?f=117&t=1832 -LBA 32 vs LBA 48 vs Advanced Format (1) https://superuser.com/questions/852475/how-can-a-mbr-formatted-hard-drive-exceed-1-81-tib-capacity/866404 -LBA 32 vs LBA 48 vs Advanced Format (2) https://blog.fosketts.net/2010/10/05/hitachi-gst-advanced-format-hard-disk-drive/ -What's the point of hard drives reporting their physical sector size? https://superuser.com/questions/982680/whats-the-point-of-hard-drives-reporting-their-physical-sector-size -Non-AF large drives get no translation. https://www.hddoracle.com/viewtopic.php?f=117&t=1832

The content that big companies want you to see, because the rest is not available on any streaming platform. An ideologically driven society.

Here I published a test of partition programs working with GPT https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/3/#findComment-1249366

I put together the two screenshots previously published with DMDE, to be able to compare them more easily. AS INTERNAL HARD DISK AS USB HARD DISK The surprise comes now. I leave Windows XP with this Logilink USB adapter and start Windows Seven with the GPT hard disk The result is the same. This Logilink USB adapter that I am testing with GPT works well with MBR +6Tb in both Windows XP and Windows Seven and NT10 (always formatted by the same one, of course. If I format GPT with the same it also works). The surprise is that I have bought 2 new USB adapters that do not work as MBR or GPT +2Tb in Windows XP and in Windows Seven they have recognized this GPT hard disk perfectly. I have also tested these 2 new adapters with a 5Tb MBR hard disk which was working perfectly with the Logilink adapter on all the operating systems. The new adapters do not recognize their partitions properly on any system.

I'm surprised!!! Hard drives have not made any noise for many years. I only hear them on Western Digital.

I'm posting the screenshots with the DMDE program that @jaclaz mentioned for comparison because if it is formatted as an internal disk, the USB adapter does not recognize the partitions. The first thing that caught my attention as an internal disk is that the program says that only 1.4 TiB are available and that the data is at risk. This is similar to what HardDisk Sentinel indicated In the Disk Manager, it caught my attention that the partitions say 100% free space available. This is the capture of the sectors made by DMDE. This does not recognize partitions correctly, unlike other programs. In contrast to what Eassos Disk genius indicated, which says that everything is correct and that there are no errors. NOW I SHOW THE CAPTURE WITH DMDE CONNECTING THE HARD DRIVE BY USB, THE PARTITIONS ARE NO LONGER ACCESSIBLE BY WINDOWS XP BUT, UNLIKE PREVIOUSLY, NOW DMDE SEEMS TO SHOW THEM No partition is recognized by Disk Manager Disk Genius At first glance it seems that DMDE works the other way around, when other programs recognize the partitions this one does not recognize them and when others recognize them this one does see them. (as hidden partitions) see next post to compare both...

You say that Disk Manager recognized the hard drive connected directly to the SATA port. This is important. Do you think it is safe to try it with Paragon Partition Manager 15 Professional x86 v10.1.25.779 without losing data? I don't know exactly what a caddy is. Is it a box to connect the hard drive to the eSATA port? I'm looking at what model of eSATA adapter you bought, but sorry I don't see if you finally say... What model you have? you can't get a cable and power supply to connect the hard drive directly to the eSATA port? Most likely the problem could be the box.

In this post I intend for us all to make a list of devices that allow reading MBR +2Tb hard disks with Windows XP SP3. Also supporting GPT testing. It is known that working with MBR +2Tb hard disks is possible in almost all operating systems since Windows 2000 SP3: -Windows XP (only since SP2?) -Windows 2003 -Windows Seven (only since SP1) -Windows Eight -Windows 10 -GNU/Linux (only since the new 2008 kernel) -MAC??? (I have not tried it) Currently +2Tb hard disks usually have a physical sector of 4096 bytes, but firmware emit a 512 bytes emulation (512e) to the operating system. In XP these disks are seen as logical and physical sector 512, this way XP will not work as an MBR or GPT disk . In theory, some +2Tb drives work on XP as MBR or GPT because the adapter firmware or the driver hard disk translate the logical sectors to 4096 bytes instead of 512 bytes. It's not really a size question, it's a sectors question. MBR and GPT on XP can only access a limited number of sectors that represent LBA 32 bits (2^32). (4,294,967,296 sectors x 512 bytes = 2,147,483,648 KiB) If the sectors are 512 bytes the limit is 2TiB, if the sectors are 4096 bytes the limit is 16 TiB. Although there are still many questions to be answered. Can XP access a hard disk with 4096 bytes physical sectors? Supposedly the 512e emulation is established because systems prior to Windows Eight are not capable of working with 4096 bytes physical sectors. So why can XP access a disk with 4096 bytes logical sectors? There are also other limits, I have found that some USB adapters are limited to 4Tb in MBR and these same ones to 5Tb in GPT. ¡¡¡Caution: If we format a 512e hard disk +2TiB with an adapter that reports 4096 bytes logical sectors to the system, this will only be accessible from adapters that reports 4096 bytes.!!! ¡With -2TiB my adapters always identify the disk in XP as a physical and logical sector 512 bytes, although their physical sector is 4096 bytes. This does not represent a problem compatibility if the disk logical sector is 512e! ¡But it could happen that some adapters read all hard disks as a logical sector 4096 bytes! Typically, the adapter detects the hard disk physical sector, and if it occupies 4096 bytes, the adapter translates the logical sectors to 4096 bytes. If the hard disks physical sector measures 512 bytes, there is no logical sector translation. Perhaps the problem has been solved with internal GPT, but I still want to test it further. Also, GPT does not allow compatibility with Windows 2000. https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/23/#findComment-1276273 Please add the devices that you have tested and their limits. That way we will not have to buy blindly and then find out that this do not work. ¡¡¡If you also know the chip model it uses, it is important to mention it!!! Or mention the device Hardware ID listed in the device manager (USB Adapter is in USB Mass Storage Device). Attention: -Some devices with updated firmware lose the ability to translate logical sectors to 4096 bytes. -Some devices only translate AF disks (Advanced Format). DDO (software BIOS) -BOOTMAN3 DDO Inform @rloew https://msfn.org/board/topic/177171-what-a-single-8tb-mbr-hard-disk-drive-looks-like-in-windows-xp/page/2/#findComment-1146558 DOCKING STATIONS -Fantec MR-U3E (no tested) https://superuser.com/questions/719844/do-hard-disk-drives-turn-on-512e-512byte-emulation-of-4k-sectors-as-needed-dep -Sabrent DS-UBLK (no tested) --> Only translates AF disks EXTERNAL BOX I've tried some a while ago, I don't know any that work with MBR +2TB -StarTech.com 3.5-Inch eSATA USB Dual Removable SATA RAID External Hard Drive Enclosure (S352U2RER) --> No tested https://apple.stackexchange.com/questions/57249/how-to-fix-512-bytes-per-sector-to-4096-bytes-per-sector-for-an-advanced-fo -StarTech (no tested) Driver chip: ASM1051e https://goughlui.com/2013/10/02/experiment-usb-to-sata-bridge-chips-and-2tb-drives/#comment-17237 EXTERNAL HARD DISK -There are several available on eBay that claim to work with Windows XP. Do they really work? -Intenso 3TB USB 3.0 (no tested) -Driver Chipset: ASM 2115 (only translates to 4096 with controller Intenso) https://superuser.com/questions/1271871/4k-emulation-sata-usb-controllers -Iomega (no tested) https://superuser.com/questions/410606/logical-sector-size-changes-depending-on-whether-it-is-attached-via-usb-or-direc -Seagate FreeAgent GoFlex (no tested) -Seagate Backup Plus Desktop USB 3.0 3Tb (no tested) https://superuser.com/questions/848512/seagate-expansion-desktop-drive-only-working-with-own-sata-usb-adapter -Seagate Expansion Drive (3TB) (no tested) https://superuser.com/questions/848512/seagate-expansion-desktop-drive-only-working-with-own-sata-usb-adapter -Verbatim USB 3.0 SuperSpeed 3 TB (no tested) --> It splits the disk showing 2 hard drives (one virtual). -Western Digital Essential -Western Digital Easystore -Western Digital My Book (self-encrypts data by hardware) -Western Digital My Book Essential (self-encrypts data by hardware) -Western Digital My Passport --> MBR Limit: 16 TiB report sectors 4KiB with WD_Quick_Formatter_Win_1_2_0_10 (only for one partion NTFS) configuring the enclosure to report that the external mass storage device has a 4KB sector size rather than 512 bytes. Inform @Comos https://msfn.org/board/topic/158361-2tib-external-usb-drive-and-winxp-of-course/ https://web.archive.org/web/20111210043520/http://community.wdc.com/t5/My-Book-for-PC/Exceeding-2Tb-limit-questions/td-p/234694 Update 1: https://superuser.com/questions/463952/is-it-possible-to-set-the-logical-sector-size-of-a-usb-hard-disk-drive/1508559 Update 2: https://support-en.wd.com/app/answers/detailweb/a_id/16241 HARD DISKS FIRMWARE -Intel SSD DC S3510 (no tested) https://superuser.com/questions/719844/do-hard-disk-drives-turn-on-512e-512byte-emulation-of-4k-sectors-as-needed-dep MOTHERBOARDS -Asus M5A88-M (SB850) & J&W Minix 780G (SB700) in AHCI mode with this driver: ahcix86.sys V3.1.1540.25 works ahcix86.sys V3.1.1540.86 works ahcix86.sys V3.1.1540.127 (newer) does NOT work and cannot be even installed ahcix86.sys V3.2.1540.35 does NOT work ahcix86.sys V3.3.1540.29 does NOT work The hard disk may not be accessible from higher versions of Windows Inform @Snear https://msfn.org/board/topic/180915-i-can-use-a-5-tb-hdd-in-xp-how-is-that-possible/ SATA ADAPTERS* *Only GPT. Require Paragon GPT Loader 8.0.1.0 driver ¡¡¡CAUTION!!! Higher versions of the Paragon driver cause corruption exceeding the 2TB limit of data written to disk. PAE enabled causes corruption exceeding the 2TB limit of data written to disk. AHCI drivers cause corruption exceeding the 2TB limit of data written to disk (asahci32.sys which allows recognition of GPT partitions with disk.sys and partmgr.sys from Win2003 drivers). -ASMedia SATA cards with switch for mode change. The switch must be set to "no boot" mode or "IDE Boot" for allow recognition of GPT disks with the Paragon GPT Loader v8.0.1.0 driver in an XP system with others hard disks configured in AHCI mode. Or on systems whose BIOS/UEFI does not have IDE mode. Driver Chip --> ASM1061: correct recognition of GTP disks, safe disk removal feature working; Models without switch for mode change and AHCI drivers have data corruption exceeding the 2TB limit of data written to disk. Inform @Andalu https://msfn.org/board/topic/186645-devices-list-compatibles-mbr-hard-disk-2tb/#findComment-1277568 https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/28/#findComment-1277039 https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/29/#findComment-1277268 The board must have a switch to toggle between IDE boot, AHCI boot or No boot. 2 ports SATA: Possible models with the label SU-SA3002 4 ports SATA: Possible models with the label SU-SA3004.v2 and label SU-SA3004 -Mugast SA3004 SATA Expansion Card ---> Made by SSU (SU-SA3004 model) ---> Drivers: https://www.ssu-tech.com/JSZC/showdownload.php?id=4 -Ubit-SA3004 If the card has 4 SATA ports only two work. This is confirmed by the datasheet of the ASM1061: https://www.asmedia.com.tw/product/77BYq58SX3HyepH7/58dYQ8bxZ4UR9wG5 SOFTWARE (some hard drive manufacturers claim to provide software that enables MBR +2TB compatibility) -Asus Mobos with software Asus Disk Unlocker --> No tested, possibly GPT virtual drives) -Gigabite 3TB+ Unlock --> (virtual drives) is for XP or Seven? -Seagate Extended Capacity Manager --> MBR Limit = It split a +2TiB disk into 2 MBR disks --> I haven't tested it, some say it gives frequent blue screens I know of another manufacturer, but I can't remember the name now, I have it written down on another computer. USB ADAPTERS -Digitus SATA to USB 2.0 (no tested) https://forums.tomshardware.com/threads/having-issues-connecting-an-ex-laptop-hdd-to-my-computer-with-a-sata-adapter.3504275/ -Logilink AU0028 (without letter "A") --> Hardware Id.: USB\VID_152D&PID_0551\ --> Driver Chip: JMS551 --> MBR limit: No known. Work with 6 Tb --> GPT limit: No known. Work with 6 Tb. -Logilink AU0028A with old firmware v.915 --> Hardware Id.: USB\VID_ABCD&PID_6103\ --> Driver Chip: Innostor IS611 --> MBR Limit = 4 Tb --> GPT Limit = 5 Tb -Logilink AU0028A with updated firmware v.923 The update changes the logical and physical sector from 4096 to 512. It can be reverted in the file \Profile\IS611.ini changing the "4k_sector=" value from 0 to 1. But the limit on XP will still be MBR 4Tb & GPT 5Tb. With the update there is no known limit for GPT on NT6-10. With this update the hardware ID also changes. --> Hardware Id.: USB\VID_1F75&PID_0611\ --> Driver Chip: Innostor IS611 --> MBR Limit = 2 Tb --> GPT Limit = 2Tb on XP; Work with GPT 6 Tb on Windows NT6.x-10 but not on XP. -Oxford SATA to USB 2.0 (no tested) ---> https://goughlui.com/2013/10/02/experiment-usb-to-sata-bridge-chips-and-2tb-drives/#comment-1195. -Ugreen ---> (model pending testing) OTHER PARTITION SYSTEMS +2TiB COMPATIBLE -EMBR --> In development https://msfn.org/board/topic/186660-embr-partition-systemhttps://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/9/#findComment-1259400 LIST DOES NOT WORK ON XP WITH +2TiB HARD DISKS USB ADAPTERS: The following USB adapters have been found not to offer logical sector translation to 4096 bytes, and will therefore not work with +2Tb drives on Windows XP: -Driver chip JM20337: All models with driver chip JMicron JM20337 [Hi-Speed USB to SATA & PATA Combo Bridge] (USB 2.0). --> Hardware Id.: USB\VID_152D&PID_2338 --> Year: 2004 *There are reports that this model may cause data corruption with large files +20GiB. I am not sure if it is the chip or the adapter mentioned. https://bigacid.wordpress.com/2008/12/08/jm20337-read-data-corruption-solution/ The adapter reports on all Windows versions that all hard disks are 512 logical sector and 512 physical sector. It works as GPT +2TiB on Windows NT6-10 but not on XP. Some models are labeled like this: -Aukson -Coolmax -Iggual -NTY-M35HD -R-Driver III -Vcom -Driver chip JMS578: All models with driver chip JMicron JMS578 [SATA 6Gb/s]. --> Hardware Id.: USB\VID_152D&PID_0578\ --> Year: 2016 This model does not perform any translation of the hard disks logical sectors. Work with GPT 6 Tb on Windows NT6.x-10 but not on XP. Some models are labeled like this: -Undentified USB 3.1 / SATA Adapter with chip JMicron Tech SATA ADAPTERS For GPT... Models without switch for mode change and AHCI drivers have data corruption exceeding the 2TB limit of data written to disk. (asahci32.sys which allows recognition of GPT partitions with disk.sys and partmgr.sys from Win2003 drivers). Driver Chip --> ASM1064 and AHCI drivers have data corruption on disks +2TiB . Driver Chip --> ASM1166: no recognition of GPT disks.

crack, crack, crack, crack, crack, crack, crack... It's dead. This is the noise that started to sound on the Seagate hard drive model ST3000DM0001. Now if I connect the hard drive I hear some beeps, as if the hard drive had an internal speaker. It is true that some models can be turned back on, but this is not the case. Do you think I can update the firmware once it's dead? The disk is recognized by Windows, although it doesn't appear in disk manager. The problem occurred after trying a new USB adapter, but the crack came with the previous adapter. As for the virus, it's clear that it has nothing to do with it. But by slowing down the file explorer for so long, after deleting and copying folders, it caused the power to fail during this time. I haven't been able to find out what the virus was, I can only say that when I clicked on copying more than 20 files it took 15 minutes to react before I could click on paste. There was no problem if I clicked on copying less than 20 files. I gave up using Seagate hard drives years ago. I've never had a Maxtor hard drive fail me. I bought Seagate again because they bought Maxtor. I don't know what hard drive brand to buy, maybe Toshiba. I would never ever buy a Western Digital, all the ones I've tried have failed!!! I don't know how many hours of use it had, I was able to open Cristal Disk and see that there were no major errors, but I didn't find the number of hours tab at that time. I only saw that there were no major errors. I used this Seagate 3Tb frequently between 2014 and 2017 and kept it connected until 2019. But I always used it via USB 2.0 so its use should not have been strained. I find it hard to believe that if I had not made the security copy 2 days earlier he would have died. Since 2019 I have only used it once last June and now. Let us pray, as everyone knows, for his soul.

It's been a while, but I'm finally getting to it. @jaclaz Let's recall the problem... A GPT hard drive located as an internal SATA drive is formatted from Windows and then the partitions on this drive are not recognized correctly if it is connected with a USB adapter. The same thing happens in reverse. I have started the GPT Fdisk program, which seems to have several names (Gdisk) and I don't know how to continue to compare the GPT partition table. I type the letter "p" which according to the tutorial shows the partitions and then the program closes. https://www.rodsbooks.com/fixparts/ Just now I have encountered a similar problem with MBR. I have bought a new USB adapter and the partitions on the hard drive formatted with my previous USB adapter are not recognized in their correct size with the new USB adapter. EDIT: I start it manually from CMD and I see that I have to add a letter to the P command. I don't understand, this would not show the partitions. And it says MBR not GPT I'm putting the screenshots with DMDE and other programs below.

From the comment you wrote in this post https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/15/#findComment-1260709 I thought that the problem of the hard drive not appearing in the Disk Manager had been solved. (there are many posts you have made and it was not clear for me) I thought that the problem you had now was that the hard drive did not work well with +2TiB, which is what the driver contained in Paragon Partition Manager 15 Professional x86 v10.1.25.779 could solve. If the hard drive does not appear in the Disk Manager I think it is because the eSATA card or the USB adapter is not compatible with +2TiB hard drives in Windows XP at the firmware level. I have found that the Seagate 5 Tb external USB hard drive does not work with its case as GPT in Windows XP, not appearing in the disk manager, but removing the hard drive from the case and putting in a compatible GPT +5Tb USB adapter the hard drive does work. What USB adapter model do you have?