This is what my /var/log/syslog shows ( /dev/sdc is the drive): Aug 28 14:23:18 devgregw-Aspire-5742 kernel: sd 6:0:0:0: tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSEĪug 28 14:23:18 devgregw-Aspire-5742 kernel: sd 6:0:0:0: tag#0 Sense Key : Hardware Error Īug 28 14:23:18 devgregw-Aspire-5742 kernel: sd 6:0:0:0: tag#0 Add. Fails to write the partition table to the disk, regardless of partition and geometry configurations as described above ( Partition: Write error)Īlso, on Windows, attempts to write new MBR code would always succeed, but have no difference.Has differing default disk geometry settings (64 heads per cylinder and 32 sectors per track on Ubuntu versus 255 heads per cylinder and 63 sectors per track on Windows).As opposed to TestDisk on Windows, TestDisk on Ubuntu: I also tried recovery with TestDisk on Ubuntu 16.04 running off a USB. Whether or not I choose the default or the suggested configuration, most attempts to write the table to the disk succeed, but do not seem to make a difference: When I choose to analyze the disk, I initially get a Partition: Read error, but finds them anyway:Īs per a TestDisk Wiki article, I should configure the DellUtility partition as primary ( P), set its type to 0xDE, and the NTFS partition as primary and bootable ( *): TestDisk easily detects the drive as well: It also appears in Disk Management (unknown and unallocated), but when I choose to initialize with MBR, it fails with an I/O error: Seconds later, it appears in Task Manager, where I can watch its activity: On my Windows 10 PC, the drive appears in Device Manager: I'm connected to the drive via an IDE/SATA to USB adapter. I'm not an expert in this field, but I'll try to be thorough and provide as much information as possible. As a last resort, I thought I'd ask here before throwing in the towel. I've done plenty of research about this but I'm having a hard time. I'd ordinarily stop here and be happy with what I recovered, but I want to try to repair the drive enough to where it is at least accessible from File Explorer (if possible). Luckily, I was able to pull some data from it using TestDisk.
It died awhile back and I've been making attempts to recover photos and such off of it. 10 year-old Maxtor (acquired by Seagate) DiamondMax Plus 9 (the 160 GB model) that I'm trying to recover.
0 kommentar(er)
