Search the Community
Showing results for tags 'Hard Disk'.
I had discussed several problems with this 5 TiB Seagate hard drive in this post. https://msfn.org/board/topic/183934-seagate-external-hard-drive-is-xp-incompatible/ I have kept this 5 TB harddisk unused until now. I have proceeded to copy my 4 TB hard drive to this 5 TB hard drive by expanding the partitions. I have connected to the computer with the only Logilink USB adapter model that allows working with hard drives larger than 4 TiB. Oldest USB Logilink AU0028 (without letter "A") work with MBR hard drive with 5 TB, newer Logilink adapters are limited to 2 or 4 TB depending on the installed firmware. I HAVE SEVERAL PROBLEMS: 1-I have proceeded to create partitions with the Windows Disk Manager and it does not work correctly. It only allows me to create full disks with no partitions or partitions up to 63 MiB. When I move the box to expand size it gets stuck at 63 MiB. If I decrease the size it starts to show negative -100 MiB, -400 Mib, etc. 2-OK, I correctly partitioned the disk with MiniTool Partition Wizard 10.3 (higher versions don't work well with any disk). So I have 3 primary and 3 extended partitions. I proceed to copy the old disk partition by partition to the new disk with R-Drive Image. Partition 1 original 1.03 TiB on NTFS cluster 4 KiB I want to paste in new partition 1.32 TiB NTFS 8 KiB. This seems to work without problems. Partition 2 original 759 GiB on FAT32 cluster 8 KiB I want to paste in new partition 1.17 TiB on FAT32 cluster 16 KiB. The operation says to finish without problems, but when I go to My PC the file explorer says that instead of 1.17 TiB the partition measures 182 GiB. When entering the content the folders are visible but when trying to access the files these are faulty. When I go to Windows Disk Manager it says that the partition is correct and that it measures 1.17 TiB. When I examine the disk with any partitioning program it says everything is ok and the partition is 1.17 TiB, however My PC still says the partition is 182 GiB. what is the problem, why my computer doesn't show the partition correctly after copying with R-Drive Image? The old 4TB drive has the first partition in sector 63 and according to Minitools it is misaligned. I have aligned the new 5 TiB disk with MiniTool before starting the copy and it has put the first partition in sector 256. Is it correct for a partition to start at sector 256? I am checking the size of the clusters and I see that after proceeding with the copy the original cluster size has been respected, both in the NTFS partition and in the FAT32 partition. That is, R-Drive Image has not copied the partitions with the new assigned cluster size. I have tried to solve the problem with larger cluster sizes but when making the copy the original cluster size is assigned. 3-OK, I proceed to make more copies of FAT32 partitions with large sizes (600-800 GiB) without problems. The problem seems to be when I exceed 1 TiB in size in FAT32. How do I get My PC to correctly recognize the partition? Is it a size limit problem on 1TiB FAT32 or is the problem in the R-Drive Image software?
Long story short - I have a "1TB" (1000 Gbytes) Seagate Barracuda 7200.11 (ST31000340AS) that I can't access and I need help recovering darta. I have Googled this around and found the following posts that seem to be useful but link to content that is no longer available: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/ http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ http://www.msfn.org/board/topic/133387-debricking-the-seagate-drives/ I may try to imply the details if I have t but, if any of you can help, I would appreciate that very much. Details: Drive details: Seagate Barracuda 7200.11 1000 Gbytes S/N: 9QJOQKB3 ST31000340AS P/N: 9BX158-303 Firmware: SD15 Date Cide: 08456 WWN: 5000C5000CCFA291 Product of Thailand Label on the PCB says: 100468979 H 7840Y1DL Original symptom was that the OS (Windows 7) would start booting up from this drive but would stop some time later. Was never able to find which driver it was loading when it stopped, only the driver loaded before, and that is not relevant. I tried connecting the drive to my notebook using CablesToGo USB-to-SATA adapter but it refused to show up (other drives worked), yet it continued to partially boot the OS in its "home" computer. I was able to boot Linux based recovery tools from a DVD. It would see the hard drive and I was able to access and copy some files from it and copy them to other hard drives I have... but this would only work for a few minutes. Then all access to the drive would stop and I would have to turn the system off, then on and I would have another few minutes of access. Not sure if this was related to time, heat, accessed area of disc or anything else but it was so. I, unfortunately, had another accident and I had lost the copies I made too. For that reason I have replaced the motherboard (well, the entire computer really short of the case and drives). The new one could not see the drive at all (didn't try the Linux tools yet). I bought a used re-certified drive of same specs (another one of those, just different serial number and firmware) and swapped the electronics. Details on that one are (differences highlighted in red): Seagate Barracuda 7200.11 1000 Gbytes S/N: 9QJ2GZHP ST31000340AS P/N: 9BX158-303 Firmware: SD1A Date Cide: 0918-5 Site Code: KRATSG CSO: 0944-3 WWN: 5000C5000A120A81 Product of Thailand Label on the PCB says: 100468979 J C9112YFS That was no help, but behaviour was a bit different. With the "new" electronics the drive did emit different sounds and there was clunking too. But it did not report its presence to the motherboard - was not visible. It was visible via the CablesToGo USB-to-SATA adapter, but it reported a size of 0. I just swapped the electronics back - no change, of course. I judiciously ran CMOS/BIOS setup, SeaTools and other physical disk access software to see if it is at all visible. Neither BIOS nor SeaTools reported anything with either old or new electronics on it ever. I only saw it via the USB adapter, as noted above. Please help!