G-Drive partition corrupted

G-Technology G-DRIVE
1

My external G-Drive USB 3.0 has become unreadable. When connected, Windows now prompts me to format the drive (which I haven’t done since that would wipe out all of my data).

The Disk Management system utility shows two partitions, one of them ___ and the other “RAW” (which is what used to be the NTFS partition containing all my data).

The WD Data LifeGuard Diagnostics tool (DLDIAG Windows) shows no errors for either the Quick Test or Extended Test.

The TestDisk utility shows a number of errors and says that the partition is not recoverable.

Example errors from TestDisk:

“Partition sector doesn’t have the endmark 0xAA55”

“check_part_i386 failed for partition type 0C”

“This partition ends after the disk limits. (start=8889149184, size=2861373044, end=11750522227, disk end=11720632320)”

I have data on that drive that isn’t currently backed up elsewhere, so I really really need this to be fixed.

I have had previous issues with this drive where it would disconnect after a while (see post).

Full TestDisk log (drive “P:” is the relevant one):

Fri Dec 7 19:32:20 2018
Command line: TestDisk

TestDisk 7.0, Data Recovery Utility, April 2015
OS: Windows 8 (9200)
Compiler: GCC 4.8, Cygwin 1007.34
Compilation date: 2015-04-18T13:01:55
ext2fs lib: 1.42.8, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: 20120504, curses lib: ncurses 5.9
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=960197124096
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdd)=5000981077504
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sde)=8001529315328
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdh)=6001175126016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive0)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive1)=960197124096
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive2)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive3)=5000981077504
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive4)=8001529315328
filewin32_getfilesize(\.\PhysicalDrive5) GetFileSize err Incorrect function.

filewin32_setfilepointer(\.\PhysicalDrive5) SetFilePointer err Incorrect function.

Warning: can’t get size for \.\PhysicalDrive5
filewin32_getfilesize(\.\PhysicalDrive6) GetFileSize err Incorrect function.

filewin32_setfilepointer(\.\PhysicalDrive6) SetFilePointer err Incorrect function.

Warning: can’t get size for \.\PhysicalDrive6
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive7)=6001175126016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\C:)=1999820029952
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\D:)=0
Warning: can’t get size for \.\D:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\E:)=0
Warning: can’t get size for \.\E:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\F:)=1000202241024
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\G:)=524288000
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\P:)=6000963747840
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\S:)=960194674688
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\T:)=8001527218176
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\U:)=5000845590528
Hard disk list
Disk /dev/sda - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512
Disk /dev/sdb - 960 GB / 894 GiB - CHS 116737 255 63, sector size=512
Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512
Disk /dev/sdd - 5000 GB / 4657 GiB - CHS 608001 255 63, sector size=512
Disk /dev/sde - 8001 GB / 7452 GiB - CHS 972797 255 63, sector size=512
Disk /dev/sdh - 6001 GB / 5589 GiB - CHS 729601 255 63, sector size=512
Drive C: - 1999 GB / 1862 GiB - CHS 243130 255 63, sector size=512
Drive F: - 1000 GB / 931 GiB - CHS 121600 255 63, sector size=512
Drive G: - 524 MB / 500 MiB - CHS 16000 2 32, sector size=512
Drive P: - 6000 GB / 5588 GiB - CHS 729575 255 63, sector size=512
Drive S: - 960 GB / 894 GiB - CHS 116737 255 63, sector size=512
Drive T: - 8001 GB / 7452 GiB - CHS 972796 255 63, sector size=512
Drive U: - 5000 GB / 4657 GiB - CHS 607984 255 63, sector size=512

Partition table type (auto): None
Drive P: - 6000 GB / 5588 GiB
Partition table type: Intel

Analyse Drive P: - 6000 GB / 5588 GiB - CHS 729575 255 63
Current partition structure:

Partition sector doesn’t have the endmark 0xAA55

search_part()
Drive P: - 6000 GB / 5588 GiB - CHS 729575 255 63
BAD_RS LBA=298927920 7071184
check_part_i386 failed for partition type 0C
FAT32 LBA 18607 102 40 282474 109 47 4239023804
BAD_RS LBA=494837054 5028020
check_part_i386 failed for partition type 0E
FAT16 LBA 298151 135 31 399066 75 48 1621195713
BAD_RS LBA=4217481962 12396754
check_part_i386 failed for partition type 0E
FAT16 LBA 529875 117 13 535280 180 20 86835302
BAD_RS LBA=299214592 6517089
check_part_i386 failed for partition type 0C
FAT32 LBA 553323 241 7 731436 45 53 2861373044
This partition ends after the disk limits. (start=8889149184, size=2861373044, end=11750522227, disk end=11720632320)
BAD_RS LBA=2926542007 6741544
check_part_i386 failed for partition type 0B
FAT32 716867 130 55 976877 219 36 4177066239
This partition ends after the disk limits. (start=11516476599, size=4177066239, end=15693542837, disk end=11720632320)
BAD_RS LBA=3611529357 13360268
check_FAT: can’t read FAT boot sector
check_part_i386 failed for partition type 01
FAT12 759506 0 60 884756 67 32 2012145444
This partition ends after the disk limits. (start=12201463949, size=2012145444, end=14213609392, disk end=11720632320)
BAD_RS LBA=1845239824 14208770
check_part_i386 failed for partition type 0E
FAT16 LBA 649559 144 10 773248 187 1 1987066486
This partition ends after the disk limits. (start=10435174416, size=1987066486, end=12422240901, disk end=11720632320)
BAD_RS LBA=3969295738 5485430
check_FAT: can’t read FAT boot sector
check_part_i386 failed for partition type 01
FAT12 781775 237 25 982425 145 14 3223436444
This partition ends after the disk limits. (start=12559230330, size=3223436444, end=15782666773, disk end=11720632320)
BAD_RS LBA=2497214740 2217883
check_FAT: can’t read FAT boot sector
check_part_i386 failed for partition type 01
FAT12 957492 121 26 1122012 192 51 2643018299
This partition ends after the disk limits. (start=15382116628, size=2643018299, end=18025134926, disk end=11720632320)
NTFS at 729575/157/54
filesystem size 11720632320
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 0 0 1 729575 157 54 11720632320
NTFS found using backup sector, blocksize=4096, 6000 GB / 5588 GiB
Partition not added.
Drive P: - 6000 GB / 5588 GiB - CHS 729575 255 63
Check the harddisk size: HD jumpers settings, BIOS detection…
The harddisk (6000 GB / 5588 GiB) seems too small! (< 9228 GB / 8595 GiB)
The following partitions can’t be recovered:
FAT32 LBA 553323 241 7 731436 45 53 2861373044
FAT16 LBA 649559 144 10 773248 187 1 1987066486
FAT32 716867 130 55 976877 219 36 4177066239
FAT12 759506 0 60 884756 67 32 2012145444
FAT12 781775 237 25 982425 145 14 3223436444
FAT12 957492 121 26 1122012 192 51 2643018299

Results
L FAT32 LBA 18607 102 40 282474 109 47 4239023804
L FAT16 LBA 298151 135 31 399066 75 48 1621195713
L FAT16 LBA 529875 117 13 535280 180 20 86835302
add_ext_part_i386: max
add_ext_part_i386: min

interface_write()
1 E extended LBA 18607 0 1 535280 254 63 8300367810
5 L FAT32 LBA 18607 102 40 282474 109 47 4239023804
6 L FAT16 LBA 298151 135 31 399066 75 48 1621195713
7 L FAT16 LBA 529875 117 13 535280 180 20 86835302
simulate write!

write_mbr_i386: starting…
Store new MBR code
write_all_log_i386: starting…
write_all_log_i386: CHS: 18607/0/1,lba=298921455
write_all_log_i386: CHS: 298151/134/1,lba=494836961
write_all_log_i386: CHS: 529875/116/1,lba=4217481887

TestDisk exited normally.

1 Like
2

The partition is corrupted and it needs to be formatted like it says. You can attempt to recover data from it using data recovery software.

3

So… this is just something that happens during normal operation of your drives, after less than a year?
Is there any reason to think that it isn’t just going to happen again?

4

partition corruption can occur on a fluke at random with any drive unfortunately. But it usually is due to a bad write, these are caused by possible power drops during a write process or index in the background. The biggest culprit is if the drive is unplugged without being ejected properly.

5

So this could be caused by the issue where it would randomly disconnect?

1 Like
6

Yes disconnecting is a big cause for corruption because it is similar to just unplugging it without ejecting it first. Disconnecting issues could be due to a few things:

  • lack of power
  • incorrect power adapter
  • bad USB cables
  • weak connection on computer end
  • hardware profile on the Mac side
  • settings on Mac energy saver to put hard drives to sleep
  • hardware issues on backplane of external drive(enclosure failure)
  • hardware issues with drive itself
7

YES! I just got a replacement 6TB drive and I still have the disconnect issue. I’m guessing that there is something inherent in the controller. Oddly, using the Windows 10 Backup on the drive encounters no problem. But using another application like GoodSync or Todo Home Backup always fails due to a disconnect of the drive from Windows. When I reconnect, I get the message that the drive has an error. I run CHKDSK and all is fine. This is a ROYAL PITA. :frowning:

8

I FINALLY found a solution that I didn’t find anywhere else and it WORKED. I no longer have disconnects on the G-Drive running write intensive applications. Everything is completing normally.

I found this article that talked about “Ghost Driver conflicts.” This occurs when we attach and remove devices from Windows. The definitions hang around. Here’s how to delete all those “ghost” devices and their associated drivers that fixed the issue for me. BTW, once I did this, the event on the G-Drive that stated the drive “could not be migrated” went away too. I think that was the crux of the problem.

https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/windows-10-usb-hard-drive-incorrectly-identified/3573eb53-e1d0-4e1f-9b7e-b6f3a290387b

In a nutshell…

Remove Ghost Devices

Note: Ghost devices are the previously installed devices which are not connected but the drivers for that device is still present in the computer and sometimes shows in the devices list.

To get rid of unwanted drivers, devices, or services, use the following steps:

1. Open the Start menu.
2. Type cmd in search box.

  • Select cmd from the displayed list, right click and *Open as administrator.
  • At the command prompt, type in set devmgr_show_nonpresent_devices=1 and press *Enter.

(Note that nothing seems to happen. This is expected. You are actually setting an environment variable which is going to help you to see hidden devices.)

1. On the next command prompt line, type devmgmt.msc and press Enter. This will launch the Windows Device Manager Console.
2. In the Device Manager Console, from the View menu, select Show Hidden Devices .

As you expand the different drivers and devices in the device manager, you will see not only the items that Windows currently detects as installed on your PC; but you will also see drivers, devices, and services which have been loaded in the past but were not uninstalled or are not currently started. You can find your offending device, right-click, and choose uninstall to remove it from the system completely.

Note that ghost devices, drivers, and services are “grayed” out, but that does not necessarily mean that you should delete all of them. Only remove items you know you do not need. Be careful that you do not change too many devices.

NOTE: I removed every single Ghost Device I found greyed out and rebooted my machine and checked again. All gone. Problem gone. Happy camper. I hope this helps anyone else with the issue. :slight_smile: