Jump to content

Chonan

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About Chonan

Profile Information

  • OS
    none specified

Chonan's Achievements

0

Reputation

  1. I read much on Spinrite 6.0. to recover data from bad sectors. Bought it and ran it just now. Very scary message! . Attached pic. Should I continue and let it attempt the recovery? Any other solutions or advice. I have to have this data.
  2. I went ahead and updated the firmware. It didn't help matters. I plugged it in with the boot drive and windows loaded very slowly. Again, it's still detected in bios, but not accessible in Windows still. I went ahead and ran Seatools again and copied the Results. Device 0 is Seagate Device st31000340as 9qj0j6bs On Generic PCI ATA Max Native Address 1953525167 Device is 48 Bit Addressed - Number of LBAs 1953525167 ( 1000.205 GB ) This Drive Supports Security Features SMART Is Supported And ENABLED SMART TRIPPED Warranty Validation Code : 6EDA06C SMART Has Been Tripped !!! DST Is Supported Logging Feature Set Is Supported POH 20184 Current Tmp 32 Hmmmmmmmm
  3. Gentleman, I have been reading for what feels like days here. I wasn't able to find anyone with my very specific issues. So, with that, I'll apologize if it's been covered already and I've missed it. I know having the same questions asked is annoying! I have the 1TB ST31000340AS with SD15. Made In Thailand. Like most people, it just stopped working. The one major difference is that mine CAN be detected by my bios. At times, when I boot into windows, it will even be seen in my device manager. However it gives it a generic name and times out if I click on it. I ran Seatools For DOS and the drive was detected, and it showed the correct file size as well. Running the "short" and "long test" revealed errors. The Seatools Test Code Number Is : 6ED3A06C - Google Reveals 0 results with this code. The one bright side I thought was that it prompted me to fix the bad sectors that it found in the long test. For now I opted to skip this repair and refer to you esteemed gentlemen. I also have the updated firmware here. But am too afraid to update it for now. My questions specifically are can I "repair" the bad sectors with seatools as it prompts me to. Or would that cause more problems? ie, cause me to lose my data. Transversely, should I just update the firmware myself? Will this cause me to lose my data? Thank you for your consideration and time reading this.
×
×
  • Create New...