- #Wd drive utilities attach a supported wd drive. install
- #Wd drive utilities attach a supported wd drive. drivers
- #Wd drive utilities attach a supported wd drive. pro
It sounds to me that you have a UEFI / GPT OS install, but are using legacy recovery media. It has the GPT partitioning scheme since it's 4TB.
#Wd drive utilities attach a supported wd drive. pro
The drive itself has been used on Win 7 pro 32-bit, Win 7 pro 64-bit, and Win 10 Home 64-bit. That's the only machine I've booted it on. But we could clarify with some screenshots or pictures based on how the rescue media is booting (blue graphical icons or a black menu with white text to select True Image, Universal REstore, etc.)ģ) I created the boot disk years ago on Win 7 Pro 32-bit. I think you solved the issue in your last post. Yes, I was suggesting some pics from your cell phone since it's not in Windows (unless you have a capture card that runs separately from the OS). Just to be certain though, when you boot the original OS, you can see all of the backup.tib files on the NTFS partition without issue?
#Wd drive utilities attach a supported wd drive. drivers
The rescue media in those is Linux as well, and drivers tend to fall out of date pretty fast which makes trouble shooting with that rescue media more difficult too. Unfortunately, the WD versions are vendor specific and support is provided by the OEM, but they seem to rarely upgrade.
#Wd drive utilities attach a supported wd drive. install
It sounds like you did based on the comment above, but I'm not certain.Īlso have you also booted the rescue media to match your OS install type? Legacy mode or UEFI mode? This typically doesn't matter when backing up, but makes a huge difference when recovering. Did I delete it? Is it necessary?Ĭould you take some cell pics and post for better reference?ĭid you pick the NTFS partition as the source already? If so, you can not pick the same destination as the source. My Easystore does not show something comparable. I installed WD Drive Utilities and found noĭoes anyone have an idea why this may be occurring? Are there any further troubleshooting steps that I might try? Do I need to create a new boot disk? On my Seagate USB drive I’ve noticed a small reserved partition at the beginning of the drive. On the Easystore with no indicated errors.
I’ve tried different USB ports without success. I’ve tried both of (yes I made two) the boot disks I made in the past. The problem only exists on the boot disk backup! I’ve run the Windows installed TI WD and everything still works. Had a problem seeing and selecting the NTFS partition! However, the choice of destination drive in the next step only recognizes the FAT32 partitionĪnd the NTFS partition is only listed as “Local Disk” with no content. TI WD lists possible source partition selections properly including a properĭisplay of the two Easystore partitions along with their correct disk and volume names. The Easystore has two partitions - a NTFS partition (for the backups) plusĪfter I start the boot disk and choose the proper bit size, the first option is to choose the source partition. Today, I was not able to start a backup by choosing one partition on the Easystore as a destination. I have used this boot disk to create numerous backups to my USB Easystore 4TB drive.
I installed Acronis TI WD edition years ago and created a boot (rescue) disk.