Jump to content

darien95

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About darien95

darien95's Achievements

0

Reputation

  1. I'm getting these errors when testing my still working ST3640323AS in TestDisk: The harddisk <640GB / 596 GiB> seems too small! <<220676 TB / 200704 TiB> Check the harddisk size: HD jumpers settings, BIOS detection... Warning: the current number of heads per cylinder is 229 but the correct value may be 128. You can use the Geometry menu to change this value. It's something to try if -some partitions are not found by testDisk -or the partition table can not be written because partitions overlaps What does this mean and is it related to this problem?
  2. The file in a smaller size for easier viewing in case anyone is bandwidth limited. http://www.dslreports.com/speak/slideshow/...mVzfnN0YXJ0PTYw My model is listed on that page. Does that mean my hard drive is going to be affected despite my different firmware and S/N? Barracuda 7200.11 ST3640323AS S/N: 5VK05SJF P/N: 9FZ134-568 Firmware: SD35 Data Code: 09077: August 22, 2008
  3. I have a 7200.11 that I purchased in October. I have had it running for many hours daily since mid October. It is still working but is it going to be affected by this problem? These are the details of my drive: Barracuda 7200.11 ST3640323AS S/N: 5VK05SJF P/N: 9FZ134-568 Firmware: SD35 Data Code: 09077: August 22, 2008 Purchased from Newegg in California
  4. I have a Seagate ST3640323AS which is still currently working. I noticed that no one else on the list had the 640GB model or had the 323 near the end. I purchased it from Newegg on 10/10/2008 and started using it about a week later. When I use testdisk, it says this under one of my partitions: "Incorrect number of heads/cylinder 255 <NTFS != 299 <HD> Incorrect number of sectors per track 63 <NTFS> != 12 <HD>" I'm not sure what this means or if it has anything to do with the problem being reported in this topic. Is there a way I could correct this error and is my hard drive still going to stop being detected?
×
×
  • Create New...